JapanDesk

Practical guides for selling to Japan — written by someone who does the paperwork.

Track partial delivery without calling the whole project complete

Keep each milestone's delivery, receipt, partial approval and missing inputs separate, then hand the right evidence to the next reviewer or billing contact.

Published November 2, 2026 · Updated November 2, 2026 · Checked against 2 primary sources · Drafted and checked by our engine

What happened

You deliver a research project to a Japanese client in stages. The first output is accepted, part of the next report has been approved, and the final report is still being prepared. An internal update asking whether the project is “complete” cannot represent those different facts with one yes-or-no answer.

Consider a fictional overseas research provider with a USD 3,000 project: research design due on 5 November 2026, an interim report on 19 November, and a final report on 3 December. The design has been accepted; the interim report’s fourth section needs supplementary client data. The project price and dates are invented for this example, not a market rate, standard timetable or basis for calculating an invoice.

Your useful output is an item-level milestone record. It shows what was delivered, which version the buyer received, what was accepted and who must act next. It does not turn the number of completed stages into a percentage payable or declare the entire engagement finished.

What’s going on on the Japanese side

Separate delivery, receipt and approval for each milestone

Give each milestone an output, scope and version. “Research 50% complete” describes an estimate of effort, not a named deliverable the reviewer can compare with an agreed requirement. If the agreement uses hours rather than outputs, retain that basis rather than converting it to milestones through this table.

The buyer may need references that connect project evidence with an order. Astellas, for example, asks suppliers to reference the purchase order and match the invoice to its relevant PO line items; it warns that mismatches may delay processing and approval. That is Astellas’s published process, not evidence that your buyer accepts partial delivery or that part of a project can be billed. Source

Keep operational labels separate from legal conclusions. The JFTC’s Freelance Act Q&A Q45 distinguishes receipt of information outputs from provision of services when explaining payment timing within that law, and points to exceptions. This guide does not determine whether that law covers your overseas transaction, classify this fictional research engagement or calculate a statutory payment deadline. Source

Show partial approval without closing the remaining work

The following is a fictional snapshot dated 22 November 2026. All messages and records shown are invented scenario inputs, not reports of actual customer activity. Read across each row; the accepted design does not change the status of either report.

Milestone and agreed due dateSubmitted versionReceipt evidenceReview result
M1: research design; 5 NovemberDesign v2, sent 5 NovemberReceipt reply on 5 NovemberDesign v2 accepted in reviewer reply on 6 November
M2: interim report; 19 NovemberInterim v1, sent 19 NovemberWhole file received, reply on 20 NovemberSections 1–3 accepted on 21 November; section 4 pending supplementary data
M3: final report; 3 DecemberIn preparation; not submittedNone: not submittedNot reviewed

The separate receipt and acceptance guide helps interpret a brief acknowledgment. Here, the additional task is coordinating several outputs and dependencies without losing their different states. A file manifest identifies the exact files; it does not replace this milestone decision record.

What to do next

Define each milestone by its output and agreed review condition

  1. Copy the baseline into your record. Use the agreed output ID, scope, version or specification, planned delivery date and review condition. Record the source document or message for each condition. If no review condition or authorized reviewer is identified, make that an unanswered question rather than filling it from habit.

For the fictional M2, the scope is interim report sections 1–4. The buyer’s decision covers sections 1–3 of v1 only. Do not rename that decision “M2 approved” or delete section 4 to make the milestone appear complete.

Keep production status separate from what the buyer confirmed

  1. Use separate fields rather than one completion label. Production may be not started, in progress or under revision. Submission is a dated event; receipt and review need their own evidence. “Unknown” is different from “not received,” and “review pending” is different from rejection.

Use these reusable columns in your existing spreadsheet or document. Keep long evidence references in linked private records rather than expanding a status email into the entire project archive.

Field groupWhat to record
Identity and scopeMilestone ID; exact output or sections; filename/version; agreed requirement reference
Plan and submissionAgreed delivery date; actual sent date/time/timezone; submission reference
ReceiptWhat was acknowledged; reply date; receipt evidence reference, or unconfirmed
ReviewReviewer; accepted IDs/sections and versions; pending or disputed items; dated decision reference
Dependency and actionRequired input; owner; proposed or confirmed input date; next action and person

Do not overwrite a sent v1 row when v2 is prepared. Preserve the v1 submission and the decision it received, then add the new version and its own receipt/review state. A later version number alone does not show that earlier acceptance still covers the revised content.

Split an interim report into accepted and unresolved sections

  1. Record a scoped decision. In the example, keep M2 sections 1–3 and M2 section 4 as subrows under the same milestone. The first subrow carries the 21 November decision; the second records the missing data and next owner. Preserve the original reply so a reader can check whether your summary matches it.
ScopeEvidence in the fictional recordOpen itemNext owner/action
M2 sections 1–3, v1Reviewer’s 21 November acceptance replyNo issue recorded for those sectionsProvider retains decision with v1
M2 section 4, v1Same reply requests the supplementary datasetDataset not yet suppliedClient data contact to confirm the proposed 23 November handoff
M3 final reportOriginal schedule lists 3 DecemberDepends on updated section 4 and its reviewProvider to reassess feasibility after input and review dates are confirmed

If the comment changes the requested research rather than supplies an already-agreed input, use an additional-work record. If it concerns revisions within the agreed work, use the revision-versus-new-request guide. Do not resolve a disputed classification by choosing a convenient status label.

Name the missing input and reconfirm any affected delivery date

  1. Make the dependency actionable. Specify which dataset, version or permission is missing and who is being asked to supply it. In this example, 23 November is a proposed handoff date, not a confirmed promise. Ask the client to confirm the date and the reviewer for the updated section.

If the input arrives in usable form and the remaining work fits the agreed schedule, record that assessment. If it arrives incomplete, ask for the missing fields rather than changing the receipt date to hide the gap. If the date or review period makes 3 December infeasible, explain the affected output and seek a revised plan; the table does not grant a unilateral extension.

A pause or delay can also affect contractual or statutory obligations. Preserve the original dates, proposed replacement dates and actual replies separately. Do not treat a schedule discussion as permission to move a payment deadline.

Hand milestone evidence to billing without inventing a charge

  1. Check the actual billing arrangement separately. Identify the agreement’s billing trigger, relevant PO line if any, evidence required and submission route. Ask the billing contact to resolve missing references. A receiver’s acknowledgment is not proof that an invoice entered the accounts-payable process.

The fictional USD 3,000 is a project total only. Three milestones do not imply three equal invoices, and approval of three report sections does not establish a three-quarter charge. Once the billing basis is established, use the milestone invoice reconciliation to distinguish new charges from earlier invoices; this record does not calculate entitlement.

Send the unresolved question, not a blanket completion request

  1. Close with one scoped next step. Confirm the meaning of the recorded partial decision and ask for the missing input owner/date. If M1 acceptance is already explicit, keep it as evidence rather than repeatedly asking the buyer to approve it. Replace the fictional references below with your actual records and use an approved private channel for supporting files.

Template

This single bilingual message preserves the accepted scope and asks about the remaining input. It does not ask the buyer to close the project or approve payment.

Subject: M2 partial review record and section 4 input

Thank you for your 21 November reply on interim report v1.
We recorded acceptance of sections 1–3 only.
Section 4 remains pending the supplementary dataset.
Please let us know if this does not reflect your decision.

Could your data contact confirm whether the dataset can be supplied
on 23 November 2026, and who will review the updated section 4?
That handoff date is currently a proposal in our record.
We will check the effect on the agreed 3 December final-report date
and discuss any necessary schedule change with you.
The final report has not been submitted; this does not close the project.

件名:M2の一部確認結果と第4章の追加データについて

中間レポートv1への11月21日のご返信をありがとうございます。
第1〜3章のみ承認済みとして記録しています。
第4章は追加データ待ちです。
ご判断と異なる点があればお知らせください。

データ担当の方に、2026年11月23日に追加データをご提供いただけるか、
また更新後の第4章をどなたが確認されるか、ご確認いただけますか。
当方の記録では、このデータ受渡日は現在提案中です。
合意した最終レポートの12月3日納品への影響を確認し、
日程変更が必要な場合はご相談します。
最終レポートは未提出であり、今回の記録で案件全体を完了とはしていません。

When to bring in a professional

Use project contacts to resolve file identity, missing inputs and reviewer assignments. Seek legal advice if the parties disagree about partial performance, acceptance, suspension, liability or the timing or entitlement to payment. Do not wait for every milestone to close before seeking advice about an already-disputed obligation.

Provide the agreement, party details, scope versions, dated submissions and replies, proposed schedule changes and billing records. This operational record does not establish applicable law, overseas coverage, statutory receipt dates or accounting treatment.

Kit

Reuse the tables and bilingual message in your existing project record without registration or purchase. Start by splitting one partially approved milestone into accepted and unresolved scopes, retaining the evidence for each. The selling-to-Japanese-companies workflow links this delivery record with the surrounding quote, order and billing steps.

This guide goes stale when

  • Astellas changes its published PO-line matching instructions.
  • The JFTC changes its explanation of receipt and service timing in Q45.
  • Your agreed milestones, review criteria, delivery dependencies or billing conditions change.

When one of these happens, the guide goes back into the queue for a re-check against the sources below.

Sources

Publisher Document Checked
other Purchase to Payment November 2, 2026
other Freelance Act Q&A — Q45 November 2, 2026

This guide summarizes publicly available information from the sources listed above. It is not tax, legal, or immigration advice. A tax accountant (税理士, zeirishi) or a lawyer licensed in Japan can tell you how it applies to your case.

Was this useful?

More on Selling B2B

Get the next guide by email

Two emails a month: new guides, and what changed on the Japanese side. Unsubscribe in one click.

On this page