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.
What happened
Your project contact says to begin by email. Purchasing says to wait for a PO, and the supplier-registration contact says bank verification is pending. You can see three messages, but not whether the instructions concern the same work, whether one supersedes another, or who will reconcile them.
The fictional case in this guide concerns a website-copy engagement, quote Q-28 Rev2. The project contact proposes starting on 9 November 2026; purchasing and onboarding have not confirmed readiness. These are teaching facts, not evidence that Japanese companies share a particular approval structure.
Your next output is a conflict-and-role map and a request for one buyer-coordinated answer. It is not a list of people to chase or a conclusion about who can legally bind the buyer. Once the conflict is resolved, use a separate readiness record to track any remaining start conditions and dates.
What’s going on on the Japanese side
Write down the conflicting instructions exactly
Keep each instruction’s sender, role as described to you, timestamp, route, quote version and work scope. Preserve the original text separately from your interpretation. If the scope is unclear, mark that as a question rather than rewriting the message to make it fit.
| Fictional message | Stated role and date | Scope question | Unresolved conflict |
|---|---|---|---|
| “Please begin the copy work on 9 November.” | Project contact, 4 November 2026 | Does this cover all of Q-28 Rev2 or preliminary preparation only? | Conflicts with purchasing’s instruction if both cover production |
| “Please wait until the PO has been issued.” | Purchasing contact, 5 November 2026 | Which work must wait, and which order is being prepared? | Buyer needs to reconcile this with the start request |
| “Bank verification is still pending.” | Onboarding contact, 5 November 2026 | Does verification block PO issuance, work, payment setup, or only registration completion? | A dependency is unknown; the message alone does not establish a sequence |
A pending registration check and a request to start might be compatible if they concern different activities. They might also be incompatible under this buyer’s process. The buyer needs to identify the applicable scope; the supplier should not select the most convenient interpretation.
Astellas describes Global Business Services as supporting purchase-to-pay transactions, including orders, invoices, payments and supplier-master administration. This supports the limited observation that a buyer can allocate these functions to a dedicated organization. It does not establish the structure of your buyer or any person’s contractual authority. (Source)
Separate approval roles from communication roles
A project contact may relay decisions without making all of them. Conversely, one person may hold several functions. Map the decision to be confirmed, who supplies the evidence and who communicates the combined answer; do not assume a job title proves legal authority.
Use the following as questions to adapt. Remove roles the buyer says are unnecessary for this engagement. Do not require a formal organization chart or collect personal contact details unrelated to resolving the issue.
| Function to clarify | Decision or evidence sought | Question for the existing contact |
|---|---|---|
| Project scope | What work the start request covers | Who confirms scope and any preparation-only boundary? |
| Purchasing | Order status and applicable start procedure | Who reconciles the wait instruction with the project request? |
| Supplier registration | Check status and what it blocks | Who can state the dependency without circulating sensitive documents? |
| IT access | Whether access is required and ready | Is this needed now, later, or not at all? |
| Invoice intake | Future submission route | Is this relevant to starting work, or a separate later step? |
| Coordinated response | One consolidated process answer | Who will collect these answers and communicate the result? |
What to do next
Ask the project contact to identify the accountable owner
-
Use the established contact first. Ask who will coordinate the buyer’s response for Q-28 Rev2. “Accountable owner” here means the buyer-confirmed person responsible for collecting and reporting the answers, not a finding that this person can sign a contract or waive requirements.
-
Request introductions where needed. If the project contact cannot answer a purchasing question, ask them to introduce the appropriate person or obtain the answer internally. Do not infer email addresses, message people found through unrelated searches, or send a blanket reminder to everyone copied on old correspondence.
If the buyer names several decision owners, that can still work: ask who will return the consolidated response and which owner confirms each point. If nobody takes that coordinating role, keep it unassigned and request escalation through your existing relationship. Do not appoint a buyer employee yourself.
Build the dependency order from buyer answers
-
Ask what must precede what. Does bank verification have to finish before a PO can be issued, or can those tasks proceed in parallel? Does a PO need to exist before production, and does that restriction include any requested preliminary work? Ask which steps are unrelated to starting this engagement.
-
Record the answer and its evidence. The table below shows possible branches, not a standard buyer workflow. A dependency is confirmed only when you have a relevant buyer answer; a blank answer stays unknown.
| Buyer-confirmed answer | Record to make | Next action |
|---|---|---|
| Verification blocks PO; PO is required before production | Link both dependency statements to Q-28 Rev2 and named owners | Ask for completion evidence and a coordinated start update |
| Verification and PO proceed in parallel | Separate owners and completion evidence for each | Ask which condition governs production; do not infer permission from parallel processing |
| No PO used for this engagement | Applicable alternative instruction and its scope | Request the buyer’s written route and confirmation; do not invent a PO number |
| Preliminary work is distinguished from production | Exact permitted activity, limits and unresolved terms | Confirm whether you agree to that scope; obtain advice if obligations are disputed |
| Answers conflict or remain vague | Preserve both messages and the unanswered question | Ask the coordinator to reconcile them; leave readiness unresolved |
If bank verification is pending, the coordination note usually needs only its status, the verified responsible team and the approved route. Keep bank details, identity documents and access credentials out of the shared conflict table. Use the buyer’s established secure submission procedure for any required evidence rather than forwarding it to a broad email group.
Send one decision request with the unresolved conflict
- Name the incompatible actions. Explain that starting production and waiting for the order cannot both be followed for the same activity at the same time. Ask which instruction applies, what earlier message it replaces and what remains pending. Include the proposed start date so the buyer sees the consequence of an unresolved answer.
Use a response request only when it reflects a real scheduling dependency. For example, if you need to allocate a production slot, give the actual decision date, time and timezone and ask whether a response is feasible. Do not manufacture a deadline or imply silence will authorize work.
- Keep the request narrow. Send the note below through the existing contact or the coordinator they have identified. Include only information those recipients need for this engagement. The note requests alignment; it does not decide the dispute or accept a new scope on your behalf.
Replace conflicting notes with a traceable agreed instruction
- Add the consolidated answer without deleting history. Store the prior instructions and link the new response to them. Identify the quote version, activities covered, each decision owner, remaining conditions and the date of the response. Ask explicitly whether the new answer supersedes the earlier start or wait instruction and within what scope.
| Record field | What to retain |
|---|---|
| Original instruction | Exact text, sender, date, route and document reference |
| Role / decision owner | Buyer-confirmed function and the particular decision it covers |
| Scope / dependency | Work affected, preceding condition or confirmed parallel task |
| Coordinating owner | Person identified by the buyer to return the consolidated answer |
| Consolidated response | Dated message, scope, handling of prior instructions and remaining unknowns |
| Next check | Outstanding evidence, owner and agreed follow-up |
If the answer only says “all approved,” ask what that includes and how it resolves the conflicting messages. If it resolves order issuance but leaves access or inputs missing, transfer those remaining facts to the start-conditions table. Internal process alignment is not a legal opinion on contract formation or authority.
Template
Replace the fictional identifiers and describe only the actual messages. Avoid including verification documents or bank details. Both language versions ask for the same coordinated response.
Subject: Coordinated start instruction — Q-28 Rev2
Could you help align the project, procurement and onboarding
instructions and identify who will confirm the start conditions
for this engagement?
The project message proposes starting copy work on 9 November 2026.
Purchasing says to wait for the PO; onboarding reports bank verification
pending. Please confirm the scope of each instruction and whether
verification blocks the order or can proceed in parallel.
Who will provide one coordinated answer for Q-28 Rev2, identifying
the applicable start instruction, the treatment of earlier messages,
and any remaining conditions and owners?
The proposed start remains to be confirmed. Please let us know when
the coordinated answer can be provided.
件名:着手指示の整理のお願い — Q-28 Rev2
案件担当・購買・登録担当のご案内を整理し、本件の着手条件を
どなたが確認してくださるか、お知らせいただけますでしょうか。
案件担当のご連絡では2026年11月9日の原稿制作開始が提案されています。
購買からはPO発行待ち、登録担当からは銀行確認待ちとのご案内です。
各指示の対象範囲と、銀行確認が発注の前提条件なのか、
並行して進められるのかをご確認ください。
Q-28 Rev2について、適用される着手指示、以前のご連絡の扱い、
残る条件と担当者をまとめて回答いただける方をご案内ください。
開始案は未確認のため、回答予定時期もお知らせいただけますと幸いです。
When to bring in a professional
Use the buyer’s coordinator for process questions and evidence gathering. Consult a qualified legal adviser if people dispute authority, whether an instruction binds a party, whether work must begin or may be paused, or how conflicting communications affect contractual terms.
Preserve the original messages, accepted documents and the new consolidated response for that review. A missing PO does not establish that no legal obligation exists, and an internal approval does not settle every contractual question. Do not use this role map as a legal-authority certificate.
Kit
No kit, software purchase or registration is needed: copy the tables into your existing project record. Use PO reference matching once the correct order is identified, and the scope-change record if instructions change accepted work. See selling to Japanese companies for the broader workflow.
This guide goes stale when
- Astellas changes the functions described for its Purchase to Pay support organization.
- Your buyer changes its coordinating contact, approval roles or supplier-registration process.
- New instructions change the agreed work scope or dependencies.
Sources
| Publisher | Document | Checked |
|---|---|---|
| other | Purchase to Payment | 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.
-
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.