There is a particular silence that every finance manager will recognise. A supplier is paid on the Monday. The bank confirms the payment has gone. Then nothing happens at all. By Thursday the supplier is asking where the money is, the bank is saying it left days ago, and both of those statements are entirely true at the same time.
Domestically, British businesses have been quietly spoiled out of tolerating this. Faster Payments moves money between UK accounts in seconds. CHAPS settles the same working day, which is why it carries the weight of property completions and corporate deals. A generation of finance staff has grown up expecting a payment to be a moment rather than a process. Send the same money to a manufacturer in Shenzhen or a contractor in Dubai, and that expectation quietly stops applying.
What faster payments taught British business, and where it stops
The reason a domestic transfer feels instant is that it travels a very short distance institutionally. Two UK banks, one shared real-time system, one set of rules. There is very little room in that arrangement for a payment to go missing, and almost no room for ambiguity about where it is.
A cross-border payment is a different kind of object. It does not travel from your bank to your supplier’s bank. It passes through one or more correspondent banks, institutions that hold accounts with one another and hand the payment along the chain until it reaches the beneficiary bank. Each of those banks is a separate organisation, in a separate jurisdiction, keeping its own records.
That structure is not a flaw in the system. It is the system. But it produces a consequence that catches finance teams out repeatedly: every bank in the chain can see only the leg it handled itself.
How long a SWIFT payment should actually take
Most payments sent over the SWIFT network reach the beneficiary within one to two working days. A meaningful share arrive the same day, and some arrive within minutes. A minority take three to five working days.
The spread is explained by a short list of ordinary causes. The payment may pass through more correspondent banks than usual. The sending or receiving country may be observing a weekend or a public holiday. The payment may need a currency conversion. It may have been submitted after the sending bank’s cut-off time, in which case the clock starts the following working day. A bank in the chain may be running additional checks on the payment details, which is routine and says nothing adverse about either party.
None of those explanations appear on the confirmation the sender was given, which is why a payment that is behaving perfectly normally can look identical to one that has gone wrong.
Why a payment can sit somewhere nobody is looking
When a supplier says the money has not arrived, the instinct is to ask the sending bank. The sending bank answers honestly that the payment was despatched, because it was. What it cannot tell you is what the correspondent in New York or Frankfurt did next, because it does not hold that record.
The supplier’s bank is equally honest in saying that nothing has been credited, because from its vantage point nothing has. The payment exists in the gap between those two accurate statements, and the person chasing it is the only party with an interest in seeing the whole route.
The reference that follows the money from end to end
There is one identifier that stays attached to a payment for its entire journey, and most people who send international payments have never had a reason to look at it.
It is the UETR, or Unique End-to-end Transaction Reference. SWIFT has required one on every customer credit transfer since 18 November 2018. It is 36 characters long, formatted like a UUID in five groups of eight, four, four, four and twelve characters, and it lives in field 121 of the MT103 message. In practice it appears on most bank payment confirmations and receipts. SWIFT itself compares the UETR to the tracking number a courier issues for a parcel: a single unalterable reference that lets any party in the chain locate the payment at any time. Intermediary banks are required to pass that same reference on rather than generate a new one, which is precisely why it works from end to end.
It is worth separating from the references that will not do this job. A bank’s own internal reference identifies the instruction inside that bank. An invoice number identifies the commercial agreement. Neither of those travels across the correspondent chain. The UETR does, and it is the same 36 characters at every bank that touches the payment.
How to track a SWIFT payment that has not arrived
The procedure differs depending on which end of the payment you are standing at, and this is the distinction most guidance skips entirely.
If you sent the payment, retrieve the MT103 confirmation from your online banking or from your relationship manager, and find the UETR in field 121. With that reference you can see what the banks handling the payment have reported about it. Independent services now do this without any banking login. The step-by-step procedure for both sides of a payment is set out in this guide on how to track a SWIFT payment, and uetr.ai itself is a free SWIFT payment tracker that takes the UETR, asks multiple international banks on the SWIFT network what they hold against that one reference, assembles the replies into a single timeline, and sets out the result in ordinary language. Checking costs nothing and requires no account.
If you are the party waiting to be paid, you will not have the MT103, because it belongs to the sender’s bank. Ask the sender for the UETR by name. It is a payment reference rather than a credential, so there is no reason to withhold it, and it is considerably more useful than the screenshot of a confirmation most senders offer instead.
What the four-letter codes mean
Tracking a payment tends to return an ISO 20022 status code rather than a sentence, and four of them account for most of what a finance team will see.
ACSP means accepted, settlement in process. The payment is moving and a bank in the chain currently holds it.
ACCC means the funds have been credited to the beneficiary account, at which point the question belongs with the supplier’s bank rather than yours.
PDNG means pending, which usually indicates that something is being checked or resolved.
RJCT means rejected, and the sender should be planning for a return rather than an arrival.
Those four outcomes call for four different conversations, which is the practical reason for looking them up rather than waiting.
What to ask the bank, and when
Tracking tells you where a payment is. It cannot move it. No tracking service can release, recall, cancel or accelerate a transfer, and any service that asks for online banking credentials in order to track one is asking for something no tracker requires.
When escalation is genuinely warranted, the request should be specific. Ask the sending bank to raise a SWIFT gpi trace, and quote the UETR when you do. Then ask which correspondent bank is currently holding the payment and what it is waiting for. Those two questions are markedly harder to answer with a general reassurance, because answering them requires somebody to look the payment up.
The small habit that saves the afternoon
The finance teams who handle this best have made one change, and it is not a system or a supplier. They capture the UETR at the moment the payment is made and record it against the invoice in the ledger, in the same way an earlier generation recorded a cheque number.
It costs seconds at the point of payment and it removes the twenty minutes of retrieval that otherwise happens later, usually while a supplier waits on the phone.
For London’s finance teams, the underlying point is a familiar one. Cross-border payments were never going to feel like Faster Payments, because they are not built like Faster Payments. What has changed is that the information exists now, attached to every payment, on the confirmation already sitting in the inbox. The difference between a lost afternoon and a two-minute answer is usually whether anybody thought to write it down.
Leave a Comment