Your Japanese client says they paid: trace the transfer before sending a reminder
Separate payment advice, execution, tracking and bank credit, then assemble a safe trace packet for the same invoice and transfer.
What happened
Your Japanese client’s accounts-payable contact says the invoice has been paid, but your account shows no matching credit. Before repeating a payment reminder, establish what “paid” describes and whether both sides are discussing the same transfer. A scheduled payment, bank instruction and credited balance are different pieces of evidence.
In a fictional case, INV-047 is for USD 2,400. The buyer says it sent the money on 6 November 2026; on 10 November, you still cannot match a credit. Those dates describe the example only: they do not establish a normal international transfer duration or prove a delay for any particular bank route.
Your next step is a trace packet: a small record linking the invoice, executed payment and bank inquiry. Start by obtaining one missing reference rather than requesting another payment. Keep the status unresolved until reliable evidence supports a more specific conclusion.
What’s going on on the Japanese side
Confirm what paid means in the client’s message
Separate the contact’s reply date from the payment instruction date, execution date and any bank status timestamp. Ask whether the reply refers to an approved payment run, an instruction submitted to the bank, or bank-confirmed execution. Preserve the original wording while adding the clarified meaning.
| Evidence | What to establish from it | What not to infer from it alone |
|---|---|---|
| Payment schedule or approval | Intended invoice, amount and planned date | Transfer executed |
| Remittance advice | Buyer-reported allocation and payment details | Money credited to your account |
| Bank-issued confirmation | Exact transaction reference, execution details and stated status | Final receipt if the document only confirms an instruction |
| Tracking result | Reported stage, scope and update time | A current account balance or a result outside that tracker’s coverage |
| Receiving-bank credit record | Matching amount, currency, reference and credit entry | That an unexplained short amount settles the whole invoice |
Swift describes a UETR, or Unique End-to-end Transaction Reference, as a reference carried in payment instructions over its network to identify and track a payment. This is a transaction reference, distinct from a bank’s SWIFT/BIC identifier. It is relevant to a Swift route, not a requirement to impose on every payment service. Source
NatWest’s tracker is a useful bank-specific example: it describes processing, completion, rejection and unavailable tracking, but warns that results are not real-time and may be delayed. It excludes routes outside its Swift tracking coverage, including SEPA and Faster Payments. Do not generalize its screen, coverage or timing to your banks. Source
What to do next
Match the payment to the correct invoice and beneficiary
- Reconcile the identifiers. Compare invoice number, amount, currency, paying entity, beneficiary name and limited account identifiers. If the buyer combines invoices, request the allocation so INV-047 can be linked to its share of that payment. Do not assume the transfer total should equal a single invoice in a grouped payment.
Use an established secure channel for full details required by the bank. An ordinary status email can refer to the verified beneficiary name and account ending rather than repeating the full account number. Do not send unrelated statements or customer transactions as evidence.
If the conversation introduces changed bank details, verify the request separately with a known contact using an established channel. Do not use newly supplied contact details as the sole verification route. Keep that verification separate from the investigation of the transfer already sent.
Ask for a bank reference that identifies this transfer
- Choose the reference for the actual route. For a Swift payment, ask the buyer for the bank-issued confirmation and the UETR if available. For another service, ask for that provider’s transaction reference and support route. A missing UETR does not prove failure when the payment did not use Swift.
Ask the buyer to confirm the amount and currency instructed, the execution date, sending bank or provider and current stated status. Read what the confirmation actually says; a document labeled payment confirmation may still need clarification about processing versus execution. Do not invent a reference or substitute the bank’s BIC for the transaction identifier.
Treat reference numbers and confirmations as private transaction information. Use your bank’s verified support channel or a tracker explicitly confirmed by the bank for that route. Do not enter them into an unverified third-party tracking site, even if it appears in a search result.
Give each bank the same trace packet
- Maintain one consistent record. Use the fields below in your existing document or spreadsheet, with source references and timestamps. Add updates rather than overwriting earlier answers. Share only the subset each authorized recipient needs.
| Trace field | Entry or unresolved question |
|---|---|
| Invoice / allocation | INV-047; USD 2,400 in this fictional example; identify any combined payment |
| Buyer report | Exact message, reply date/time/timezone and meaning of “paid” |
| Execution | Bank-confirmed date and status, or explicitly unconfirmed |
| Amount / currency | Instructed amount and currency; record any conversion separately |
| Parties / route | Paying entity, sending bank/provider, receiving bank and verified beneficiary reference |
| Transaction reference | UETR for applicable Swift transfer, or provider reference |
| Current status | Exact bank/provider wording, source and update time |
| Inquiry | Bank case reference, requester, missing information and next action |
| Next response | Named owner or verified team, agreed update date/time/timezone |
| Resolution | Credit entry or other confirmed outcome, with evidence and open issues |
- Follow each bank’s inquiry procedure. Ask your receiving bank whether it can identify the incoming payment and what it needs to investigate. If the sending bank must initiate a trace, ask the buyer to contact it with the same packet. Confirm who may request information; access to an inquiry is determined by the institution, not by possession of a reference alone.
Do not guess an intermediary’s contact or circulate the packet to several unverified addresses. Keep separate inquiry references for each bank while linking them to the same transaction. If one answer differs from another, ask the responsible bank to reconcile the statuses and their timestamps.
Separate in progress from rejected and unable to track
- Use the reported state to choose a question. The table gives editorial next steps, not a promise that every bank uses these labels. Ask the bank what its particular result means before taking action.
| Reported situation | Next question | Keep unresolved |
|---|---|---|
| Planned or approved, execution unconfirmed | When was it executed, and what evidence identifies it? | Whether a transfer was sent |
| Processing or awaiting information | What information is needed, who should provide it and when will status be updated? | Cause and arrival date unless confirmed |
| Rejected or returned | What is the reason, and has the return reached the sender? | Refund completion and any replacement-payment plan |
| Unable to track or no result | Is this route supported, is the reference correct, and can the bank investigate directly? | Whether the payment succeeded or failed |
| Reported complete, credit not matched | Which beneficiary credit and timestamp does the result refer to? | Reconciliation with the receiving account |
Do not ask the buyer to resend while the original transfer’s outcome remains uncertain. If rejection or return is confirmed, coordinate any correction or replacement with the buyer and bank after establishing the original payment’s status. This prevents an unclear tracking display from becoming a duplicate-payment instruction.
Close the trace with a supported outcome
- Record the next owner before ending the conversation. In the fictional INV-047 case, suppose a bank inquiry establishes that additional information is required. Record the actual request, the responsible party and an agreed recheck on 11 November 2026, with a time and timezone to be confirmed. That is a follow-up plan, not a promised credit date or an inferred reason for the hold.
When a credit appears, match its reference, amount and currency to the trace. If it is short, continue with the invoice, remittance and bank-credit reconciliation guide; do not label the difference a fee without evidence. If currencies differ, obtain the conversion record rather than subtracting unlike amounts.
A confirmed return can close an investigation with a returned outcome, but it does not mark the invoice paid. Keep that distinction in the payment record. If the buyer instead reports an invoice-processing issue, use the invoice receipt guide rather than continuing to trace a transfer that was not executed.
Template
This is one reusable trace request with recipient-specific wording. Send only the relevant block through the established channel; replace fictional details and omit information already confirmed.
To the buyer's AP contact — INV-047, USD 2,400:
Could you share the bank-issued payment confirmation, execution date
and transfer reference for INV-047? If this was sent through Swift,
please include the UETR if available.
Please confirm the instructed amount/currency and the current bank status.
We have not yet matched the credit; this is a trace request, not a request
to send a second payment.
To the receiving bank, with the relevant trace packet:
Can you check whether this incoming payment has reached your bank,
and tell me what information is needed to investigate?
Please provide the inquiry reference and the next update arrangement.
買い手の支払担当者宛て — INV-047、2,400米ドル:
銀行発行の送金確認書、実行日、取引参照番号を共有いただけますか。
Swift経由の場合は、入手可能であればUETRもお知らせください。
送金指示額・通貨と銀行の現在の処理状況もご確認ください。
現時点で入金との照合ができていないための照会であり、
再送金をお願いするものではありません。
受取銀行宛て(必要な照会情報を添えて):
この送金が貴行に到着しているか、調査に必要な情報は何かを
ご確認いただけますでしょうか。
照会番号と次回の状況確認方法もお知らせください。
When to bring in a professional
Start with the banks or payment provider for execution and tracing evidence. Escalate suspected account-detail fraud through their verified security process. Seek legal advice if the payment obligation or dispute cannot be resolved from the transaction records; a tracking status alone does not determine those rights.
An accountant can help reconcile grouped credits, conversions or adjustments using the supporting records. This guide does not diagnose a compliance hold, a tax deduction or a bank’s reason for rejecting a payment.
Kit
No kit, new account or registration is needed for the trace record. Use the existing bank relationships and verified channels. The selling-to-Japanese-companies workflow provides context, but the immediate action is to obtain the missing execution detail or transaction reference for this payment.
This guide goes stale when
- Swift changes its explanation of UETRs and payment tracking.
- NatWest changes the tracker limitations or status descriptions cited here.
- Your banks or payment provider change their investigation process or required references.
Sources
| Publisher | Document | Checked |
|---|---|---|
| other | What is a Unique End-to-end Transaction Reference (UETR)? | October 27, 2026 |
| other | International payment tracker | October 27, 2026 |
Was this useful?
More on Invoicing & tax paperwork
-
Make a bilingual invoice without creating two different bills
Keep one invoice identity across English and Japanese, reconcile dates and amounts, and tell the buyer how the translated document relates to the original.
-
Allocate one combined payment across several invoices without guessing
Keep a bank credit separate from proposed invoice allocations, request a remittance breakdown and preserve unexplained balances without double-counting.
-
Put the correct buyer and supplier names on the invoice
Map the contracting buyer, brand, department, supplier identity and trading name before finalizing an invoice for a Japanese client.
Get the next guide by email
Two emails a month: new guides, and what changed on the Japanese side. Unsubscribe in one click.