Payment tracking is the monitoring of a payment from submission through processing and completion. Useful tracking shows the latest confirmed event, timestamp, route reference and any action required. It should not imply final Recipient credit before that milestone is supported.
Tracking starts with confirmed events
| Data | Why it matters |
|---|---|
| Provider reference | Finds the payment in the sending system |
| UETR or network reference | Links events across supported institutions |
| Status timestamp | Shows when the latest event occurred |
| Intermediary event | Identifies where a payment paused |
| Fee or amount change | Explains a short credit |
| Required action | Shows missing data or review needs |
What is a UETR?
A Unique End-to-end Transaction Reference is used in Swift payment messages to preserve one payment reference through the chain. Swift explains that intermediary institutions should receive, copy and pass on the existing UETR rather than generate a new one.
What to do when a payment is late
- Check the latest timestamp against the route estimate and banking calendars.
- Confirm whether more information is required.
- Give the provider reference to the Recipient.
- Open an investigation with the sending provider when the estimate has passed.
- Record the result against the invoice.
A useful Quotable Payments timeline should separate confirmed provider or network events from estimated arrival times. When no new event exists, an unchanged estimate is not proof that the funds advanced.
