Login
Payment Problem — Proof, trace, and payment messages

A supplier is asking for MT103 proof of payment.

You are in the right place if a supplier is asking for MT103 proof of payment. A confirmation screen may calm your internal team, but the receiving side usually needs proof it can search, match, or investigate.

Proof is useful only if it gives the receiving side enough structured information to identify the transaction. A sent confirmation is not the same as evidence that the beneficiary bank has applied the funds. For this case, gather MT103 or PACS.008-style proof, UETR, amount, value date, and beneficiary fields. If the proof does not let the receiving bank locate the funds, the case has moved from proof-sharing into trace or investigation.

Canada-specific version

What the proof shows

Proof can show that the payment was instructed, debited, sent through a rail, or assigned a bank reference. It does not automatically prove the supplier has usable funds.

What the proof does not prove

A screenshot is rarely enough. Ask for MT103 or PACS.008-style proof, UETR, amount, value date, and beneficiary fields, then check whether the reference can be used by the receiving bank to search for the payment.

When proof becomes a trace

Move from proof to trace when the supplier bank still cannot locate the funds, the payment has passed the expected window, or the status stops changing. Move to investigation when a bank has to ask another bank in the chain what happened.

What to send next

Send Unicorn the proof, references, beneficiary details, and supplier correspondence. Treasury can help determine whether the next action is a bank trace, a receiving-side search, or a clearer proof pack for the supplier.