Confirm delivery receipt and acceptance as two different steps
Record what arrived, who will review it and what remains unresolved without treating a received message as acceptance or a payment-date decision.
What happened
You send a delivery link to a Japanese client and receive a short reply: “Received.” You still do not know whether the files opened, whether the agreed review is complete, or who can answer about the remaining items. Sending the same link again will not resolve all three questions.
In this fictional example, an overseas designer submits ten website images, version 3, through an approved shared location on 12 November 2026 at 15:00 JST. The contact replies “Received,” and the project record gives 16 November as the agreed review date. The reviewer has not been identified; none of these fictional dates represents a standard review period.
Keep delivery evidence and review results in separate fields. The immediate outcome is a specific question for the right contact, not a declaration that the work has been accepted or that payment is now due. This record helps you gather facts without deciding the legal effect of a message.
What’s going on on the Japanese side
Identify the exact deliverable and the agreed review process
Start with the agreed specification and the version actually submitted. Separate technical access, comparison against the specification, and completion of any buyer paperwork. A person who acknowledges an email may not be the person assigned to review the images.
The JFTC’s Freelance Act Q&A Q35 lists delivery or service dates separately from an inspection-completion date when inspection is performed. Q45 explains receipt-based payment timing within that statute’s scope and expressly points to exceptions for information outputs and services. These are reasons to preserve separate facts, not grounds for deciding that the statute applies to your overseas transaction or calculating your due date here. Source
Do not assume an unfinished internal review extends a statutory deadline. Equally, this guide does not establish that an email timestamp is the legally relevant receipt date for your transaction. If timing is disputed, preserve the records for an adviser who can assess the parties, work, applicable law and exceptions.
For the fictional submission, create this starting record. The ten filenames and versions can be kept in a separate delivery manifest, rather than compressed into a vague folder label.
| Field | Fictional starting entry | Missing confirmation |
|---|---|---|
| Deliverable | Website images 01–10, each v3 | Confirm this is the set being discussed |
| Specification | Agreed image specification; retain its actual reference | Reviewer to identify any specific difference |
| Submission | 12 November 2026, 15:00 JST, approved shared location | Whether all ten files are accessible |
| Receipt evidence | Contact’s “Received” reply; preserve actual reply time separately | Whether the reply acknowledges the message or the files |
| Review | Agreed review date: 16 November 2026 | Reviewer and expected response time/timezone |
| Result | Unconfirmed | Full, partial or outstanding review, with item references |
What to do next
Preserve evidence of delivery without exposing client files
-
Save the submission record. Keep the timestamp, intended recipient, approved channel, file list and reply together in the project record. Record the actual time and timezone from each message; do not substitute your send time for the buyer’s receipt time. Retain the specification version used for the delivery.
-
Check technical failures first. Ask whether the recipient can access the approved location and open the named files. An expired link, missing permission or damaged file requires a technical next action, not an acceptance debate. Record any check actually performed, who performed it and which version was tested; leave untested items marked untested.
Use the established secure channel to repair access or resubmit. Keep the earlier attempt and the new submission as separate events, and ask the contact to confirm the affected files. Do not distribute passwords, private links or confidential images to a wider group in a status email.
Ask whether received means accessible or accepted
- Split the question. Ask whether all ten images can be opened, then whether the agreed review is complete. If the contact only confirms access, request the reviewer’s name or verified response route and the expected review answer. Do not treat technical success as specification approval.
| Answer received | Record now | Next action |
|---|---|---|
| Email received; files not checked | Message acknowledged; access and review unknown | Ask about the exact file set and access |
| Link fails or a file will not open | Technical issue for named items | Repair through the approved route; retain resubmission history |
| Files open; review pending | Access confirmed; acceptance unconfirmed | Ask reviewer, criteria and response date |
| Some items accepted | Item-level decision only | List accepted IDs/versions and unresolved IDs separately |
| Review complete for the named set | Save exact decision and scope | Reconcile against agreed criteria; keep billing questions separate |
A statement about one image does not close the whole set. If only part of a delivery is under review, identify the included and excluded IDs and use the existing agreement to determine how that partial result is handled. Do not expand the buyer’s words beyond the items they identify.
Turn a rejection into a list of specific differences
- Request a reproducible issue list. Convert “not what we expected” into a file ID, version, agreed requirement, observed difference and proposed recheck. Preserve the original comment alongside your structured summary. Ask the reviewer to correct the summary if it misstates the issue.
| Issue field | What to record |
|---|---|
| Item | Exact ID, filename and version |
| Agreed requirement | Specification section or approved reference |
| Reported difference | Buyer’s description; separate your observation |
| Classification to resolve | Specification correction, new request or disputed requirement |
| Proposed next step | Correction or clarification, owner and recheck method |
| Outcome | Dated response and the version it covers |
A reported defect and a new preference can require different discussions. Do not silently accept unlimited revisions or label a disputed request as out of scope without evidence. Use the additional-work record to separate the original requirement from a proposed change, including unresolved price or schedule effects.
Follow up on the agreed review date without inventing acceptance
- Follow the actual agreement. At the agreed review point, ask for the result or a revised response plan. If no review date exists, request one instead of imposing an automatic approval deadline. A requested response date is not a buyer commitment until confirmed.
Record no response, partial review and complete review distinctly. If the answer is late, retain the agreed date, actual reply date and unresolved items. Silence alone does not supply an acceptance rule through this checklist; the meaning of existing terms is a separate question.
Keep invoice preparation and payment timing in their own records. Confirm the applicable billing conditions and buyer process, while obtaining advice where legal timing is uncertain. The invoice receipt guide concerns whether an invoice entered the buyer’s process; it does not prove acceptance of these images.
Send a concise acceptance question and retain the answer
- Close the record with a scoped answer. Use deliverable ID, version, receipt date and evidence, reviewer, review condition, planned date, result and unresolved item as your reusable columns. Attach or reference the current manifest through the approved route. Preserve earlier states when adding the answer.
Share only the facts needed by the billing contact: relevant item references, confirmed review outcome and unresolved conditions. Keep private creative files and unrelated discussion out of that handoff. Your next action can be as small as separating “receipt confirmed” from “review unconfirmed” before sending the question below.
Template
Replace these fictional details and remove questions already answered. Both versions ask about access and review separately; neither states that receipt means acceptance.
Subject: Delivery receipt and review — images 01–10, v3
Thank you for your receipt reply concerning the ten v3 images
submitted on 12 November 2026 at 15:00 JST.
Could you confirm whether all ten files are accessible and can be opened?
Could you also confirm whether the agreed review is complete,
or identify any items still under review and the expected response date?
Our record lists 16 November 2026 as the agreed review date.
Please identify the reviewer and, for any differences, the file ID,
version and relevant agreed requirement.
件名:納品物の受領と確認状況 — 画像01〜10、v3
2026年11月12日15:00(日本時間)に提出したv3の画像10点について、
受領のご返信をありがとうございます。
10点すべてにアクセスでき、ファイルを開けるかご確認いただけますか。
また、合意した確認が完了しているか、確認中の項目と回答予定日を
お知らせいただけますでしょうか。
当方の記録では、合意した確認予定日は2026年11月16日です。
確認担当者と、相違がある場合はファイルID、版、該当する合意仕様を
お知らせください。
When to bring in a professional
Use the project contact for access and reviewer questions. Obtain legal advice when the parties dispute completion, acceptance, rejection, suspension, billing entitlement or payment timing. An internal status table does not resolve those questions.
Provide the agreement, specification versions, delivery attempts, receipt messages, item-level decisions and relevant party details. The JFTC material describes a particular legal framework; this guide does not determine coverage, exceptions or a deadline for an overseas provider.
Kit
The tables and message are free to reuse in your existing document or spreadsheet. No kit, new account or registration is required. Keep them alongside the selling-to-Japanese-companies workflow and the delivery manifest, updating evidence rather than replacing the original records.
This guide goes stale when
- The JFTC changes its explanations of delivery, inspection or payment timing in Q35 or Q45.
- Your agreed deliverables, review criteria or confirmation route change.
- The delivery channel or access arrangements change.
Sources
| Publisher | Document | Checked |
|---|---|---|
| other | Freelance Act Q&A — Q35 and Q45 | October 27, 2026 |
Was this useful?
More on Selling B2B
-
Japanese Client Requests Extra Work After Accepting Your Quote: Agree on the Change
Preserve accepted scope, price a requested addition, and ask your Japanese client to approve the work, delivery conditions and purchasing record.
-
Give a budget estimate without presenting it as a final quote
Build a defensible budget range from named uncertainties, show assumptions and exclusions, and identify what is needed for a final proposal.
-
Three buyer contacts give different instructions: map who owns each approval
Record conflicting project, procurement and onboarding instructions, ask the buyer to name a coordinating owner, and preserve one traceable answer.
Get the next guide by email
Two emails a month: new guides, and what changed on the Japanese side. Unsubscribe in one click.