SWIFT gpi payment tracking: follow a cross-border transfer end to end

SWIFT gpi gives banks and corporate treasury teams a common way to track cross-border payments through the correspondent-banking chain. A unique end-to-end transaction reference can show where the payment is, whether it was credited, rejected or delayed, and which institutions handled it.

The UETR gives the cross-border payment a unique tracking reference

SWIFT gpi payments carry a Unique End-to-End Transaction Reference. Banks use that reference in the gpi tracker to follow the payment as it moves through the correspondent chain.

For a corporate finance team, the UETR is more useful than telling the bank only the amount and date. Store it with the supplier invoice and payment confirmation for material international transfers.

Tracking distinguishes credited, pending and rejected payments

SWIFT's gpi for Corporates materials describe status information such as delivery to the beneficiary bank, credit confirmation, pending status and rejection.

This helps finance answer a supplier saying "we have not received the money" without immediately sending a duplicate transfer. First identify where the original payment sits.

The tracker can improve visibility of intermediary routing and fees

Cross-border payments can move through several institutions. gpi data can provide greater transparency on routing and deductions along the chain.

Use that information when reviewing intermediary bank fees or recurring delays to one country. A payment route that is consistently slow can justify changing correspondent instructions or banking provider.

Large corporates can integrate tracking into ERP or treasury systems

SWIFT developed gpi for Corporates to allow multi-banked companies to initiate and track payments from treasury applications in a consistent format.

Integration reduces manual calls to banks, but the company needs clean UETR and payment-reference mapping so each status update reaches the right supplier or invoice.

Escalate payments that remain pending unusually long

A pending status can indicate compliance review, missing information or another operational issue. Contact the sending bank with the UETR and commercial evidence where the delay threatens the supplier relationship.

Do not route around a compliance hold by sending another payment through a different bank without understanding the reason for the first hold.

Use final credit confirmation to close the payment exception

When the payment reaches the beneficiary account, attach the final tracking status to the payment record where practical. That gives procurement and finance evidence that the supplier received funds.

Keep tracking separate from accounting settlement. The company bank can debit before the beneficiary is credited, so both states can matter for cash and supplier management.

Worked example: a UK company sends $750,000 to a supplier in Singapore and the supplier says the money is missing. The treasury team retrieves the UETR and sees the payment reached the beneficiary bank but is pending local compliance review. That information prevents an unnecessary duplicate transfer and gives the supplier a specific status to discuss with its bank.

Store payment tracking references in the ERP or treasury system rather than in personal email. When a supplier dispute arises months later, another employee should be able to retrieve the route, timestamps and final credit confirmation without asking the original payment creator to search old messages.

Use recurring gpi data to improve bank selection. If payments through one correspondent route consistently incur higher deductions or longer pending times, treasury can raise the issue with the bank and compare alternatives. Tracking becomes more valuable when it informs future routing, not only one-off investigations.

Set service-level triggers for investigation. A payment that normally reaches a supplier in two hours can be flagged after six hours, while another corridor may routinely take a full day. Data from past gpi payments can make exception thresholds more realistic than one global rule.

Share final UETR or tracking evidence with suppliers through a secure process when needed. This can reduce repeated "where is my payment?" emails and gives the beneficiary bank something precise to search. Avoid sending screenshots containing unrelated account information.

Link tracking to cut-off management. If a supplier must receive funds before shipment, treasury can use historic gpi data to estimate how early payment should be initiated for that corridor. Payment timing then reflects observed delivery rather than a generic "international transfers take a few days" assumption.

Where fees are visible, compare instructed amount with amount credited. Repeated intermediary deductions can cause suppliers to treat invoices as short-paid. That can justify changing charge instructions or payment route for future transfers.

Use gpi evidence when investigating fee disputes. If the supplier received less than expected, the tracking data can help identify where charges were applied. That allows the buyer and seller to decide whether the contract's OUR, SHA or other charge arrangement was followed in practice.