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.
What happened
Your client requested another deliverable after accepting the original scope
You are delivering a service from outside Japan. Your Japanese client accepted a quote, work started, and the project contact now asks for an additional language version, another deliverable or a different production approach. You can estimate the effort, but you do not yet know whether the request includes approval of the additional price and schedule.
Replacing the old quote with a higher total would hide what the parties previously agreed. Starting the extra work while approval is unclear would leave a different gap: the finished work might not match the record that purchasing expects.
This guide helps you prepare one change record that preserves the accepted scope and asks for an explicit decision on the addition. It is an editorial workflow, not a determination of contractual rights or Japanese law. If acceptance has not happened yet, use the guide to revising a quotation before acceptance instead.
What’s going on on the Japanese side
A project request and a purchasing update can require separate confirmation
Astellas provides a concrete company example. Its supplier instructions ask suppliers to obtain a valid purchase order before starting work or issuing an invoice, and to reference its PO number with matching invoice line items; mismatches can delay processing and approval. These are Astellas instructions, not evidence that every Japanese buyer uses the same process (source).
Your contact may be able to describe the desired result without being the person who approves the budget. Treat that as a question to resolve, not a cultural explanation for delay. Ask who can approve the amount and who maintains the purchasing record, then make the change summary usable by both people.
Separate additional scope from disputed corrections before discussing payment
The JFTC’s Q59 describes improper changes and rework, including situations where the supplier is not responsible and the ordering party does not bear costs or losses arising from changes, cancellation, or rework and additional work after receipt. That explanation concerns transactions covered by the relevant rule; it does not establish that the rule applies to an overseas supplier or this guide’s fictional project (source).
Our practical recommendation is to compare each request with the accepted specification before assigning a price. A new language page, a broken agreed feature and an unclear comment about quality need different questions. The categories below are working labels, not legal conclusions, and they do not establish that every additional request is chargeable.
What to do next
Preserve the accepted version and classify each requested difference
- Save the baseline. Record the quote ID, version, acceptance date and evidence reference beside the agreed deliverables, price and deadline. Keep the original file intact; if the accepted version is uncertain, ask the existing contact to identify it rather than reconstructing agreement from your preferred version.
- Separate the request from your interpretation. Copy a short description of what the client wants, then state the work you believe it entails. Label it an addition, a correction against an agreed requirement, or a question awaiting clarification; explain the comparison that supports the label.
- Record disagreements without deciding them unilaterally. If the client considers a Japanese page included in “website production” but your quote specifies English only, preserve both readings. Ask which specification or message supports the requested scope before treating the line as an approved paid addition.
Put the additional price and dated dependencies in one change record
The following record is entirely fictional. Its dates, amounts, identifiers and evidence labels illustrate a Singapore production studio’s project; they are not published rates, legal deadlines or an observed customer case. All dates below are in 2026.
| Field | Accepted baseline retained | Proposed change CR-01, awaiting approval |
|---|---|---|
| Reference | Q-104 v1; accepted 2 November; evidence: acceptance-email-02Nov | Request received 9 November; evidence: request-message-09Nov |
| Deliverable | One English landing page using supplied copy | Add one Japanese-language page using the same layout |
| Included work | English page build and agreed checks | Japanese copy placement and layout checks; no translation or new design |
| Client input | English materials already supplied in this fictional scenario | Final Japanese copy and written change approval by 12 November, 17:00 JST |
| Price | USD 1,800 | Additional USD 650; proposed combined total USD 2,450 |
| Delivery | English page: 20 November | Japanese page: proposed 25 November, subject to the dated inputs above |
| Purchasing | Original PO reference retained | Client to confirm amendment route and required approval evidence |
| Current status | Accepted work continues where independent | Proposed addition has not been approved or started |
| Decision record | Baseline acceptance reference retained | Decision: pending; approver: to confirm; decision timestamp: none; purchasing update: unconfirmed |
- Show the arithmetic and the boundary. USD 1,800 + USD 650 = USD 2,450. Keep the existing payment, currency and tax presentation visible, and identify any proposed change to those terms rather than letting a new total imply it.
- Check the dependency before offering the date. Here, the proposed Japanese-page date depends on final copy and approval arriving by 12 November. If either arrives later, discuss a replacement date; do not silently move the accepted English-page deadline or present 25 November as unconditional.
- Confirm the purchasing route. Ask whether your contact can approve CR-01 and whether purchasing needs a revised PO. Store the decision, approver, timestamp and purchasing reference together; a positive project chat does not establish that every required procurement step is complete.
Record approval, partial approval, rejection and pending status separately
- Update only the agreed change. If CR-01 is approved with its scope, price and conditions, record that decision and check the required purchasing step before scheduling the addition. Preserve Q-104 v1 as the baseline and link the approved change rather than overwriting the original file.
- Resolve partial approval before treating it as full approval. If the client accepts the additional page but not USD 650 or the proposed date, mark those fields unresolved. Offer a narrower deliverable or revised proposal for confirmation; do not convert enthusiasm for the output into acceptance of the whole package.
- Close a rejected proposal without deleting it. Mark CR-01 rejected and retain the reason if supplied. Confirm that the English-page plan remains the working baseline, unless a separate change has been agreed.
- Keep pending additions separate from continuing work. If no decision arrives by the requested response time, follow up and revisit the proposed date. Identify any original work that can continue and any specific dependency that needs discussion; this is not a recommendation to stop the whole project or a statement that you have a right to suspend performance.
Template
Ask for one decision on scope, price, timing and purchasing
Adapt this bilingual message to the fictional record above. Replace evidence labels with links available to the intended recipients, and use the actual authorized approval route.
Subject: CR-01 approval request — Japanese landing page addition
Q-104 v1, accepted 2 November, remains our baseline:
one English landing page, USD 1,800, delivery 20 November.
Your 9 November request adds a Japanese page using the same layout.
CR-01 proposes copy placement and layout checks, excluding translation
and new design: +USD 650; combined total USD 2,450.
Proposed Japanese-page delivery: 25 November, conditional on final
Japanese copy and written approval by 12 November, 17:00 JST.
The English-page deadline remains unchanged.
Could you confirm approval of this scope, amount and conditional date,
and whether a revised PO is required? Please identify the approver
and reply by 12 November, 17:00 JST. Pending approval, CR-01 remains
unstarted. Evidence: [accepted quote] [acceptance] [request] [CR-01].
件名:CR-01 承認のお願い — 日本語ランディングページの追加
11月2日合意のQ-104 v1(英語LP 1ページ、USD 1,800、
11月20日納品)は変更せず、元の合意として保持します。
11月9日のご依頼に対し、同じレイアウトの日本語ページを追加する
CR-01をご提案します。作業は原稿の配置・レイアウト確認で、
翻訳・新規デザインは含みません。追加USD 650、合計USD 2,450です。
日本語版の納品予定日は11月25日です。11月12日17時(日本時間)
までの確定原稿のご提供と書面承認を前提とします。
英語版の納品日は変更しません。
範囲・金額・上記条件付き日程の承認可否と、発注書の改訂要否を
ご確認いただけますか。承認者を明記のうえ、11月12日17時
(日本時間)までにご回答をお願いします。CR-01は承認待ち・未着手です。
参照:[合意済み見積書] [合意記録] [ご依頼] [CR-01]
When to bring in a professional
Get contract advice when the accepted obligation or suspension rights are disputed
Ask a lawyer familiar with the relevant cross-border contract when the parties disagree about what was accepted, whether a change is binding, or whether work can be paused. Bring the baseline, request, change record and correspondence, with a chronology of the disputed events. This guide does not decide applicable law, statutory coverage or entitlement to additional payment. A purchasing-record question can first go to the buyer’s procurement contact; a disputed contractual obligation needs a different kind of review.
Kit
No kit is needed for this workflow: use the record and bilingual message above. For an earlier negotiation stage, read revising a quotation before acceptance; for document references, use matching PO, quotation and invoice references. The selling to Japanese companies starting point connects the wider process.
This guide goes stale when
- JFTC changes its Q59 explanation of improper changes or rework.
- Astellas changes its published purchase-order or invoice-matching instructions.
- The linked JapanDesk quotation or purchase-order guides change their scope.
Sources
| Publisher | Document | Checked |
|---|---|---|
| other | JFTC Freelance Act Q&A — Q59 | October 27, 2026 |
| other | Astellas Suppliers — Purchase to Payment | October 27, 2026 |
Was this useful?
More on Selling B2B
-
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.
-
Define the billable unit before multiplying the price
Agree which source words, files and embedded text a translation quote covers, then give your Japanese buyer a count record and reproducible subtotal.
Get the next guide by email
Two emails a month: new guides, and what changed on the Japanese side. Unsubscribe in one click.