Payment Trace

A payment trace is a request to establish where a transfer currently is and what has happened to it. It follows the payment from the sending bank through any intermediary banks to the beneficiary bank, using identifying data such as the payment message, the reference number, the value date, the amount and the beneficiary details. A trace answers the question of whether the funds were credited, are being held or have been rejected or returned.

Traces are most often requested for international wires, where a payment may pass through several institutions in different time zones, but domestic systems also provide trace references. A trace is usually the first step before a fuller payment investigation.

• The payment message: for SWIFT transfers, a copy of the MT103 or ISO 20022 pacs.008, which shows the sender's reference, the banks involved and the instructions given.
• The UETR: the Unique End-to-End Transaction Reference, a 36-character identifier that stays with a SWIFT payment from start to finish.
• Value date and amount, including the currency.
• Beneficiary details, such as name, account number or IBAN, and the beneficiary bank's BIC.
• Intermediary information, showing which correspondent banks were used.

Traditionally, a trace was a chain of inquiries. The sender's bank asked the first intermediary whether it had received and forwarded the payment; that bank then asked the next, and so on. Each step could take a day or more, and an unresponsive bank could stall the process. This is the procedure described in older guidance on the SWIFT wire trace.

The introduction of SWIFT gpi changed this substantially. Each gpi payment carries a UETR, and every participating bank reports status updates, such as received, forwarded, credited or rejected, to a central tracker, together with fees deducted and the exchange rate applied. A bank, and often the customer through online banking, can see the payment's journey in close to real time. Guidance on tracing your own SWIFT wire explains how customers can use these references.

Domestic systems

Domestic rails have their own identifiers. In the US, each Fedwire transfer carries an Input Message Accountability Data (IMAD) reference and an Output Message Accountability Data (OMAD) reference, which banks use to confirm that a transfer was sent and received, while ACH entries carry a 15-digit trace number. In Europe, SEPA credit transfers carry end-to-end and transaction identifiers.

A trace commonly reveals one of a few outcomes: the payment was credited and the beneficiary has not checked or recognized it; it is held at an intermediary for compliance review; it was rejected because of incorrect details and is on its way back as a returned payment; or it was credited for less than expected because of fees under the OUR, SHA and BEN charge codes. If the trace shows that a payment was sent in error or to a fraudster, the sender may follow it with a payment recall.

A trace is a status inquiry: it locates the money. An investigation goes further, asking banks to explain, correct or reverse something, such as refunding a deducted fee, amending a beneficiary name or returning funds. In practice, the terms are often used loosely, and many banks offer a single trace and investigation service for which they may charge a fee. Supplying the UETR or a copy of the payment message at the outset usually shortens the process considerably.