Three records answer three different questions
Ask for the record that supports the claim you need to prove.
Payment confirmation
Shows what the sender or bank submitted, accepted or released according to that document.
MT103 or message details
Shows structured customer credit transfer information used in a SWIFT payment flow.
Recipient statement
Shows the actual account credit, value date, currency and deductions visible to the beneficiary.
Trace result
Shows the latest status or bank response linked to the payment reference or UETR.
Read the useful fields without overclaiming
| Field or detail | What it can support | What it cannot prove alone |
|---|---|---|
| Ordering party | Who the message identifies as payer | That the payer was entitled to use the account |
| Beneficiary details | The destination named in the instruction | That the final account credit occurred |
| Amount and currency | What the instruction asked banks to process | The amount available after all deductions |
| Charge instruction | How fees were allocated in the message | A guaranteed final beneficiary amount |
| UETR or bank reference | A key for identifying and investigating the transaction | A status without a bank or tracker response |
Banks can present customer-facing confirmations differently. Ask the sending bank which document and reference its support team needs.
Build a proof pack for a delayed or disputed wire
Keep the instruction evidence and final-account evidence separate.
Save the original instruction
Keep the beneficiary details, amount, currency, requested date and payment purpose.
Save the bank confirmation
Record the release status, reference, charge option and any UETR shown.
Ask the recipient for account evidence
Use a statement entry or bank response that shows whether a credit, rejection or return occurred.
Request a trace
Give the sending bank the reference and ask for the current stage, last responding institution and next action.
Reconcile differences
Separate route fees, recipient fees, conversion and returned amounts instead of calling every gap a missing payment.
Example: sent is not the same as credited
A sender gives a supplier a bank confirmation marked sent. The supplier still cannot find the money. The document supports that the instruction left the sending side, but it does not resolve whether an intermediary paused it, the recipient bank rejected it or the supplier cannot allocate the reference.
The sender provides the UETR to the bank and requests a trace. The supplier checks its statement and incoming-payment queue. Together, those records locate the gap without creating a duplicate transfer.
Match each document to the claim it can support
A customer payment confirmation can show what the sender instructed and what the bank accepted or released. An MT103 or equivalent message detail can show structured information used in a customer credit transfer, including parties, amount, currency, references and charge information. The exact customer-facing format varies by institution.
Neither record alone proves that the beneficiary received final cleared funds. The payment may still be screened, repaired, rejected, returned or awaiting account allocation. A UETR or bank reference helps identify the transaction during a trace, while a recipient statement or bank response supports the final-credit claim. Keep instruction evidence and receipt evidence separate.
When a dispute arises, state the question before requesting documents. If the recipient needs proof that a payment was initiated, the confirmation may be enough. If the question is where the payment is, request a trace using the reference. If the question is whether an invoice was settled, compare the recipient's credited amount and reference with the commercial obligation.
Use the record in the payment route
Follow the reference through the international transfer tracking process.
If the route contains several banks, review how correspondent banking affects the payment.
MT103, UETR and payment-record sources
SWIFT references explain the MT103 and UETR, while payment guidance frames the customer record. Neither document alone proves that the beneficiary received final credit.
Questions about what payment records prove
Does an MT103 prove the recipient was paid?
It can document a customer payment message, but final receipt should be confirmed with transaction status and recipient-account evidence.
What is the UETR used for?
It is a unique end-to-end transaction reference that helps identify and track the payment across participating institutions.
Should I send another payment when the first is marked sent?
Not until the first payment is traced. A duplicate can create a second loss or a difficult refund process.
This page uses worked reasoning and authoritative references; it does not claim first-hand testing or personalized advice. See our editorial policy.
Place this step in the cross-border payment rails collection to follow routing, references, deductions and returns.