JapanDesk

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

Submit an invoice once and keep proof of receipt from your Japanese customer

Confirm the invoice submission route, keep a receipt record, and resolve missing acknowledgments without creating a duplicate invoice.

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

What happened

You finish a consulting assignment for a Japanese company and email the invoice PDF to your project contact. Your sent folder shows the message, but you cannot tell whether accounts payable (AP) has it. A portal link appears in an older email. Uploading there feels like a sensible backup, yet it could create a second submission for the same work.

This is a fictional situation, not a report of customer demand or a measured outcome. The task here starts with an invoice ready for submission. Supplier registration, tax treatment and correcting invoice fields are separate work. Your outcome is one record connecting the invoice to its authorized destination, receipt evidence and next person responsible.

What’s going on on the Japanese side

Identify the buying entity’s route rather than a national rule

A published company process illustrates why destination matters. Astellas says its use of Ariba depends on country or location. Where its suppliers do not use Ariba, PDF invoices go to the local email address specified on the purchase order. These are Astellas instructions, not a submission rule for Japanese companies generally. Confirm your buyer’s process instead of treating this example as its policy. Astellas: Purchase to Payment.

A project contact and an invoice-processing contact may handle different parts of your transaction. Ask your contact who owns intake for the purchasing entity. Receipt by a person, entry into an AP queue, approval of the charge and release of payment are different questions. The distinction below is an editorial tracking method, not a claim that every buyer exposes these exact statuses.

Distinguish generated, finalized, sent, received, approved and paid invoices

  • Generated: the document or invoice record exists in your system.
  • Finalized: your invoicing system has completed its finalization step.
  • Sent: you have evidence of transmission to a specified destination.
  • Received: the designated intake channel or AP has acknowledged this invoice.
  • Approved: the buyer has confirmed the relevant approval, with its scope recorded.
  • Paid: payment is evidenced; reconcile the amount against your payment records.

Stripe provides a concrete product example: finalization moves an invoice from draft to open, while sending is a separate operation. Its email behavior depends on configuration; disabling “Email finalized invoices to customers” means finalization does not send the invoice. A PDF or finalized status therefore cannot establish buyer receipt. These are Stripe behaviors, not evidence about your customer’s AP queue. Stripe: Status transitions and finalization.

What to do next

Confirm one official destination before submitting

Check the purchasing entity named on the current transaction, the current PO instructions and the buyer’s authenticated portal guidance. Do not reuse another affiliate’s address because the brand is the same. Ask whether email or portal is authoritative, whether copying the project contact is requested, and which file formats and attachments are accepted.

If the buyer mentions a cutoff, request its date, time and timezone. Record Japan Standard Time (JST, UTC+09

) separately from your local time. A cutoff for intake is not a promised approval date. Ask who can confirm receipt and when you should follow up if the normal acknowledgment is absent; do not invent an industry-wide response deadline.

Send the requested package, without extra sensitive material

Attach the completed invoice and only the delivery, acceptance or other supporting records this buyer requests. Keep a copy of the exact submitted version. Review the filename as well as the contents so an obsolete draft is not uploaded under a current invoice number.

Bank verification and identity documents do not belong in a routine submission merely as a precaution. If an unfamiliar address requests them, verify the request through a known buyer contact before sending. For mismatched references, use PO, quote and invoice references before submission rather than improvising a correction inside an email.

Capture a receipt and assign the next check

For a fictional worked example, assume you submit INV-204 for USD 2,400 on 5 November 2026 at 10

JST through the buyer’s designated portal and obtain receipt R-580. Save the confirmation showing the invoice reference and submission time, not only a screenshot of the upload screen. The result is “received; approval unconfirmed.” It does not establish a payment date.

Use the record below as a working structure. Bracketed fields need your transaction facts. If you have only an outgoing email, replace the receipt ID with “none” and the status with “sent; receipt unconfirmed.” Preserve the sent message, recipient address and attachment alongside the record. Store supporting evidence in an access-controlled location, with enough context for another person to find it.

Invoice number: INV-204
Amount and currency: USD 2,400
Purchasing legal entity: [exact name on current PO/contract]
Authorized route: [portal name and verified URL]
Route confirmed by: [buyer instruction/contact and date]
Submitted at: 2026-11-05 10:00 JST (UTC+09:00)
Submitted version: INV-204-v1.pdf
Other attachments: [requested files, or none]
Receipt ID: R-580
Evidence location: [saved confirmation and submitted files]
Current status: Received; approval and payment unconfirmed
Missing documents: None reported; completeness not confirmed
Next owner: [named supplier-side person]
Buyer contact: [verified AP contact]
Next check: [agreed date, time and timezone; pending confirmation]
Approval evidence: None
Payment evidence: None
History: [dated updates; preserve earlier entries]

Check missing receipts, drafts, errors and duplicates before resubmitting

No receipt: Search your sent mail, bounce notices and portal history using the invoice number. Ask AP to locate the original using its amount, timestamp and destination. Do not attach another payable copy by default. If AP requests one, identify it as a copy of the existing invoice and follow its submission instructions.

Draft only: A saved upload may still require a submit action. Verify that the portal shows a draft and no completed submission before completing that action. Retain the resulting receipt. Your own invoicing software’s draft status and the buyer portal’s draft status are separate records; inspect the system where submission was supposed to occur.

Error or timeout: Save the error and time, then check submission history before retrying. A timeout leaves receipt uncertain. If the system confirms failure with no submission record, follow its retry instructions using the existing invoice. If the evidence conflicts, ask AP or portal support to resolve it first.

Receipt exists, review pending: Keep the receipt and ask whether a specific document is missing or an internal owner needs to act. Do not submit again to accelerate review. If the document itself is returned, use the returned-invoice guide and preserve the correction history.

Duplicate already submitted: Give AP both receipt IDs, the routes and timestamps, and identify the shared invoice number and amount. Ask which submission should remain active and how to close the duplicate. Do not create a fresh invoice number to make the records look distinct or cancel a record without checking the buyer’s instructions. Record its decision and confirmation.

Template

Ask AP to confirm receipt, not promise payment

Use this message after checking your evidence. Replace the bracketed route and recipient details. The Japanese version requests the same action; choose the language your contact uses rather than sending both without a reason. This is a draft for your use, not a message sent on your behalf.

Subject: Receipt confirmation — INV-204 / R-580

Dear [AP contact],

Could you confirm receipt of invoice INV-204 for USD 2,400,
submitted on 5 November 2026 at 10:00 JST through [portal],
reference R-580?

I am checking receipt, not submitting a second invoice.
Please let me know if any document is missing and when I should
check again if receipt cannot yet be confirmed.

Thank you,
[Name / supplier name]

件名:請求書 INV-204 の受付確認(受付番号 R-580)

[ご担当者名] 様

2026年11月5日10時(日本時間)に[ポータル名]から提出した
請求書 INV-204(2,400米ドル、受付番号 R-580)について、
受領状況をご確認いただけますでしょうか。

本メールは受付状況の確認であり、請求書の重複提出ではありません。
不足書類がございましたらお知らせください。
現時点で受領確認が難しい場合は、次回の確認時期もお知らせください。

[氏名/事業者名]

If you only know the project contact, ask for the official AP route first: “Who can confirm receipt for [purchasing entity], and does my earlier email count as formal submission?” If there is no receipt ID, state that explicitly instead of copying R-580 from this example.

When to bring in a professional

Escalate the unresolved issue to the right owner

Use AP or portal support for intake uncertainty. Give them the record and evidence rather than a new invoice. If unanswered, return to the agreed escalation contact and update your next check; an unanswered message does not close the issue.

Bring tax-field corrections to an appropriately qualified tax professional, and contractual disputes or collection options to a qualified legal adviser. If the confirmed payment due date has passed, move to payment-delay handling with the receipt history attached. Receipt confirmation alone does not settle tax validity, contractual acceptance or whether payment is overdue.

Kit

No kit is needed. Use the submission record above. Related reading: returned invoices, PO, quote and invoice references, and selling to Japanese companies.

This guide goes stale when

  • Astellas changes its country-specific Ariba or PDF invoice submission instructions.
  • Stripe changes invoice finalization, sending behavior, or status transitions.
  • Your purchasing entity changes its submission route, receipt evidence, or escalation contact.

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 October 27, 2026
stripe Status transitions and finalization October 27, 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 Invoicing & tax paperwork

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