THE IDEA TO TAKE WITH YOU

Trace the specific payment through the institution that initiated it. Collect the correct rail reference and confirmed status before treating a screenshot, a sender debit, or a missing receipt as the full answer.

To trace an international bank transfer, first establish that it was actually submitted, identify the payment rail, and obtain the sending institution’s transaction reference. Then ask the responsible provider to investigate that specific payment.

“The money has not arrived” can mean several different things: the payer scheduled it but has not sent it, the transfer is processing, the recipient cannot match it, or the funds are being returned. Each situation needs different evidence.

This guide provides a practical investigation workflow. It does not offer a public tracking service or promise that every transfer can be located instantly.

Confirm the payment, not just the intention

Ask the payer whether the payment is scheduled, awaiting approval, submitted, or debited. A payment entered into a company’s approval queue has not necessarily reached a bank. A screenshot of saved beneficiary details is not a transfer confirmation.

Request the bank- or provider-issued record showing the amount, currency, submission date, beneficiary, status, and transaction reference. Check that the destination matches the current instructions you supplied.

If the payer cannot establish submission, the next step is inside its own payment process. A recipient-side trace cannot locate a transaction that was never sent.

Identify the rail before asking for a reference

USD can move through different systems. EUR can arrive through a supported SEPA flow or another route. “Bank transfer” and “international payment” are not precise enough to identify the investigation tools.

Payment routeEvidence to requestWho usually starts the investigation
Applicable Swift transferUETR and bank-issued payment confirmationSending bank or provider
U.S. ACHACH trace information supplied by the bankOriginating institution or provider
FedwireBank confirmation and IMAD/OMAD information where relevantSending bank
Other local railProvider reference and rail-specific confirmationSending institution or provider

The Federal Reserve’s Fedwire information explains that successfully processed messages contain IMAD and OMAD identifiers. Ask the bank for the relevant evidence; do not expect every payment app to expose those identifiers directly.

Understand what a UETR does

A Unique End-to-end Transaction Reference identifies an applicable payment across the Swift chain. Swift’s UETR guide describes a 36-character reference used for tracking and related payment information.

The UETR is not your account number, invoice reference, or a password. Having it does not automatically give you access to the banks’ tracking systems. Your bank or provider should explain what tracking information it can supply.

Use its official channels. Avoid uploading full payment confirmations to an unfamiliar website merely because it promises to “track any wire.” Financial documents can contain names, addresses, account identifiers, and commercially sensitive information.

Build a small evidence pack

Collect the invoice or payment purpose, the receiving instructions actually shared, the sending confirmation, and any statement entry visible at the destination. Add the amount, original currency, expected destination currency, date, timezone, and sender and recipient names.

Keep the sender’s reference separate from the invoice number. If the transfer involves a conversion or an intermediary provider, include those transaction references too. A single invoice can be associated with several related records.

Send only the documents requested through the verified support channel. Redact unrelated statement entries when permitted, while preserving the information needed to locate the payment. Never send passwords, one-time authentication codes, or wallet recovery phrases.

Compare expectations with the applicable window

Check when the institution accepted the payment, not only when the payer filled in the form. Then look at the stated route window, cutoff, business-day calendar, and any review notice.

A payment sent after a banking cutoff can enter the next processing cycle. A compliance request may mean the ordinary estimate no longer describes the present situation. Conversely, “pending” without an explanation is worth clarifying once the provider’s own window has passed.

See international transfer times and delays for the difference between bank processing, review, and recipient availability.

Ask a question that identifies the missing stage

Instead of asking only “Where is my money?”, ask what stage is confirmed, what institution or process owns the next step, and whether any action is required from you or the payer.

Here is an adaptable message. Replace the brackets with information from your records; do not guess missing values.

Subject: Investigation request for transfer [reference]

The sender confirms that [amount and currency] was submitted on [date and timezone] to the receiving instructions attached. The expected processing window has passed and I cannot identify a corresponding available credit.

Please confirm the latest verified stage, whether the receiving institution has acknowledged the payment, and whether further information is needed. The sending confirmation and relevant invoice reference are attached.

Please provide the investigation reference and the next update date.

Distinguish a trace from a recall

A trace investigates a payment. A recall or return request asks for a different action concerning funds already sent. Asking the bank to investigate does not necessarily ask it to cancel, and requesting cancellation does not guarantee funds can be recovered.

State your objective clearly. If the recipient details are wrong or fraud is suspected, contact the sending institution promptly and explain that a potential recovery action is needed. Do not wait for the normal arrival estimate simply to expire.

The feasibility, deadlines, charges, and recipient consent requirements depend on the rail and circumstances. Your provider must assess the actual transaction.

Do not resend while the original remains unresolved

A second transfer may arrive alongside the first. That can turn a delay into an overpayment, a refund dispute, or a more complicated reconciliation problem.

If a commercial deadline makes an alternative payment necessary, agree in writing how the original will be tracked and how any duplicate receipt will be handled. Confirm with the provider whether cancellation or return has actually completed rather than assuming a request achieved it.

Keep both payment references linked to the same invoice. Mark the unresolved item as such until reliable evidence establishes its outcome.

Check whether the payment arrived under a different label

A bank statement may display a processor, marketplace, or institution name rather than the client’s trading name. The amount may also reflect a documented fee or conversion. Search using the actual expected amount, currency, date range, and reference.

This is a matching exercise, not permission to assume that any similar deposit belongs to the invoice. Reconcile the evidence before closing the case. If a provider uses a required reference to allocate incoming funds, a missing reference may require manual assistance.

Our guide to payment references explains why preserving the original reference matters.

Treat a return as its own journey

“Returned” does not always mean the sender can already spend the funds. The provider may have initiated a return that still needs to move through the relevant institutions and be credited back.

Ask for the reason, return amount and currency, return reference, and expected credit window. Compare the returned amount with the original debit and any documented charges or conversions.

If corrected instructions are needed, verify them independently before resending. Do not edit only the field that appears suspicious while leaving the underlying route mismatch unresolved.

Keep an investigation timeline

Record when the transaction was submitted, when the expected window ended, when a case was opened, what evidence was supplied, and when the next update is due. Keep subsequent replies in the same case where possible.

If progress stalls, use the provider’s escalation or complaints process. Applicable rights and external complaint routes differ by jurisdiction, institution, and customer type; do not assume another country’s process covers your transaction.

After resolution, save the final outcome with the cross-border payment records. That history helps identify whether future problems share the same avoidable cause.

Frequently asked questions

Is a payment receipt proof the recipient received the money?

It proves what the issuing institution says it proves. Some receipts confirm submission; others confirm a later stage. Check the wording and corroborate the recipient’s available credit.

Can the recipient start the trace?

The recipient can ask its provider to check incoming records. A formal investigation through the sending route often requires the payer’s institution. The two sides may need to cooperate using the same reference.

Does every transfer have a UETR?

No. It is relevant to applicable Swift payment messages. Other rails use their own identifiers. Ask for the reference appropriate to the actual route.

Can support reverse a payment immediately?

Not universally. Recovery depends on the rail, stage, destination, and circumstances. Contact the responsible institution promptly, but do not treat an investigation or recall request as a guaranteed refund.

Explore the linked sources, practical tools and related guides for more on this topic.

Explore more payment guides ↗