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.
Payment Problem — Proof, trace, and payment messages
Your supplier is asking for an MT103.
You are in the right place if your supplier is asking for an MT103. 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 payment message copy, UETR, sender reference, beneficiary details, and charges field. 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 versionWhat the proof does not prove
A screenshot is rarely enough. Ask for payment message copy, UETR, sender reference, beneficiary details, and charges field, 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.
Your supplier is asking for an MT103 means the receiving side needs bank-usable evidence, not just a screenshot. Check whether the proof includes traceable identifiers such as UETR, bank reference, amount, value date, sender, beneficiary, and routing details before deciding whether to share proof, request a trace, or open an investigation.