What Is a UETR Number? The Complete Guide to Tracking SWIFT Payments

Waiting for an international payment can feel uncomfortable. Your client says the money is sent, your bank sees nothing, and the funds seem stuck in banking limbo with no clear answers. This is exactly where the Unique End-to-end Transaction Reference (UETR) number steps in.

Think of the UETR as the FedEx tracking number for bank transfers. Introduced under the SWIFT GPI network, the UETR is a 36-character code that follows your payment across every bank it touches. With a UETR number, you no longer rely on guesswork or back-and-forth emails to locate funds.

Read on this guide to learn what a UETR number is, where to find it, and how to use it to track SWIFT payments in real time.

What Is a UETR Number?

A UETR number stands for Unique End-to-end Transaction Reference. It is a 36-character alphanumeric code automatically assigned to every SWIFT international payment at the time the transfer is initiated.

This reference acts as a single source of truth for the entire payment journey. No matter how many intermediary banks handle the transfer, the UETR stays the same. That consistency allows banks to identify, trace, and confirm the exact status of your payment without relying on vague timelines or manual follow-ups.

The Technical Structure of a UETR

Technically, a UETR follows the UUID Version 4 standard. Its structure looks like this:

xxxxxxxx-xxxx-4xxx-yxxx-xxxxxxxxxxxx

• 36 characters in total
• 32 hexadecimal characters (0–9, a–f)
• 4 hyphens for readability
• The “4” indicates the UUID version
• The “y” shows the variant and can be 8, 9, a, or b

This format ensures that every unique end-to-end transaction reference is globally unique and cannot clash with another payment.

Where Is the UETR Located in a SWIFT Message?

The UETR sits in a fixed, standardised location within a SWIFT FIN message, which ensures it remains consistent across banks.

• Block: Block 3 (User Header)
• Field tag: Field 121
• Mutability: Immutable and passed unchanged by all intermediary banks

Unlike internal bank reference numbers that may change at each stage, the UETR number remains constant, making it the most reliable identifier for tracking SWIFT payments end to end.

Explore Razorpay’s Global Payment Solutions

Why Is the UETR Number Critical for Global Business?

For years, international payments worked like a black box. Once money left the sender’s bank, you had little visibility until it arrived-or didn’t. The UETR number has changed this. It brings logistics-style transparency to banking, helping businesses track payments, forecast cash flows better, and avoid costly follow-ups with banks.

Real-Time End-to-End Tracking

• The UETR lets you see your payment’s status at every stage of the journey.
• You can identify exactly which intermediary bank is holding the funds.
• It also shows fees deducted and exchange rates applied along the way.

Faster Reconciliation and FIRC

For finance teams and exporters, this visibility makes a real difference. When the UETR appears in your bank statement, you can match it directly with outstanding invoices. This speeds up reconciliation and helps exporters close receivables faster. For inward remittances, the same reference supports quicker issuance of the Foreign Inward Remittance Certificate (FIRC), reducing follow-ups with your bank.

Reduced Fraud and Disputes

• Each UETR creates an immutable trail from sender to beneficiary.
• If funds stop unexpectedly, you can pinpoint the break and flag risks early.
• The clear audit trail also strengthens internal and regulatory compliance.

Before vs After UETR Tracking

UETR vs. Transaction Reference Number (TRN) vs. MT103

If you have ever followed up on an international payment, you have likely heard different banks quote different reference numbers. This is where confusion usually starts. While UETR, TRN, and MT103 all relate to the same transfer, they are not interchangeable. The most important point to remember is that only the UETR remains constant across the entire payment journey, regardless of how many banks are involved.

Comparison: UETR vs TRN vs MT103

What Is the Difference Between UETR and TRN?

A Transaction Reference Number is generated by the sending bank and stored in Field 20 of the SWIFT message. Banks use it mainly for their internal records and customer communication. As the payment moves through intermediary banks, this reference may change or may not be visible at all.

The UETR number, on the other hand, sits in Field 121 and never changes. It follows the payment from start to finish, which is why banks rely on it when they need to trace a transfer across borders.

How Does MT103 Relate to UETR?

Think of the MT103 as the shipping label on a parcel and the UETR as the barcode printed on it.

The MT103 is the standard SWIFT payment message-the envelope that carries all payment details. The UETR is one specific data point inside that envelope. So when a bank asks you for the “MT103,” they are effectively asking for the document that contains the UETR number used for tracking within SWIFT GPI, operated by SWIFT.

How to Find the UETR Number?

How you find the UETR number depends on whether you sent the payment or are waiting to receive it. The important thing to understand is that the UETR is always created at the source bank when the transfer is initiated. From there, it travels with the payment across every intermediary bank.

For Senders: Checking Payment Confirmations

• Log in to your bank’s online portal and open transaction history or payment details.
• Look for labels such as UETR, Unique Reference, or Payment ID.
• Download the official payment advice or debit confirmation PDF.
• The UETR usually appears in the detailed reference section of this document.

For Receivers: Requesting the MT103

As a receiver, you usually cannot see the UETR until the funds reach your bank. If the payment is delayed, ask the sender for the SWIFT MT103 confirmation. In that document, check Field 121, which contains the UETR number. Once you have it, your bank can trace the payment precisely across the SWIFT network.

How to Track a Payment Using the UETR Number?

Using Your Bank’s GPI Tracker

Most modern corporate and business banking portals now offer a built-in “Track Payment” feature linked to SWIFT gpi. If your bank participates in the GPI network, this tool gives you direct visibility into the movement of your international transfer.

You enter the UETR number, and the system pulls live data directly from the SWIFT network. You can usually see clear statuses such as processing, credited, or rejected, along with timestamps. Because this information comes straight from SWIFT, banks treat it as the most accurate source when resolving delays or disputes.

Using Public SWIFT Tracking Tools

If your bank does not offer GPI tracking, you may come across third-party tools. Most of these platforms work by aggregating available SWIFT status data or by simulating a SWIFT GPI lookup using the UETR number.

How to Generate a UETR Number?

If you are looking up how to generate a UETR number, it helps to first understand how the system works in practice. In most cases, you are not expected to generate anything yourself. For the majority of users, the uetr number is created automatically when an international payment is initiated. Manual involvement only comes into play in more advanced or high-volume payment setups.

Automatic Generation by Banks

For nearly all individuals, freelancers, and businesses, the UETR number is generated by the sending bank itself. Global transaction data indicates that over 99% of UETRs are created this way.

When you click Send on a SWIFT transfer, the bank’s system automatically calls a UUID generator and assigns a unique end-to-end transaction reference to that payment. You are not required to create, request, or input anything manually. The UETR simply appears in the payment details or the MT103 once the transfer is processed.

Generation in ERP Systems (SAP/Oracle)

Large organisations often handle cross-border payments in bulk using FileAct or ISO 20022 payment files. In such setups, enterprise systems like SAP S/4HANA or Oracle Financials can generate the UETR even before the payment file is sent to the bank.

This approach gives finance teams early visibility. They receive the tracking reference upfront instead of waiting for the bank’s acknowledgement, which helps with reconciliation and faster follow-ups for payments moving through SWIFT GPI.

Can You Generate Your Own UETR?

From a technical standpoint, yes. Developers can generate a valid UETR using UUID version 4 library.

However, this only works if your bank’s payment interface allows you to pass a custom UETR. Many banks overwrite customer-provided values. If that happens, the self-generated UETR loses all tracking value and should not be relied upon.

Common UETR Issues and Troubleshooting

Even with end-to-end visibility, UETR tracking may not always return a clear result. Most issues relate to timing delays, data mismatches, or limitations within legacy banking systems. The table below summarises the most common scenarios and the correct action to take in each case.

UETR Troubleshooting Guide

Simplify Global Payments with Razorpay MoneySaver Export Account

Tracking an international payment is useful, but it does not solve the root problem if collections remain slow, expensive, or difficult to reconcile. To reduce follow-ups, avoid hidden forex costs, and keep export payments predictable from day one, many Indian businesses choose the Razorpay MoneySaver Export Account as their international collection setup. With this you can:

• Receive overseas payments via local bank transfers from major markets like US, UK and EU without opening a foreign bank account.
• Use a dedicated virtual account in your business name for cleaner identification and reconciliation.
• Collect funds with transparent pricing and zero forex markup on incoming payments.
• Get quicker settlements and bank-issued FIRC support to stay compliant with export regulations.

Conclusion

The UETR number sits quietly behind the scenes, but it has become the backbone of transparency in modern cross-border payments. While the name sounds technical, its purpose is very practical: it helps you locate money that would otherwise feel lost between banks. By giving every transfer a single, permanent identity, the UETR removes guesswork and speeds up resolution. For businesses and freelancers alike, the habit is simple-always ask the sender for the UETR as soon as a payment is initiated. As global banking moves steadily towards faster and near real-time settlements, this level of traceability is no longer optional; it is quickly becoming the standard.

FAQs

Q1. What is the difference between UETR and TRN?

The UETR is a globally unique code that stays the same from the moment a payment is sent until it is credited. A TRN, by contrast, is created by an individual bank for internal use and may change or drop off as the payment moves through intermediary banks.

Q2. Is the UETR number mandatory for all SWIFT payments?

Yes. Under SWIFT GPI standards, a UETR is mandatory to enable end-to-end visibility and transparency for cross-border payments handled on the SWIFT network.

Q3. Can I track a SWIFT payment without a UETR number?

You can try, but it is slow and unreliable. Without a UETR number, banks usually have to rely on manual references such as the TRN or raise a formal tracer request through the SWIFT. 

Q4. Where can I find the UETR number on a bank advice?

Technically, the UETR appears in Field 121 of the SWIFT MT103. On a bank advice or receipt, it is often shown as “End-to-End Reference,” “Unique Reference,” or as a 36-character alphanumeric code.

Q5. How do I generate a UETR number for a payment?

In most cases, you don’t need to. The bank’s system generates the UETR automatically when you initiate a transfer. Only large corporates or developers using ERP systems like SAP or Oracle may generate a valid UETR themselves using a UUID version 4 library.

Q6. Why does my UETR search show ‘Payment Not Found’?

This usually means the payment is very recent and has not yet propagated through the SWIFT network, or there is a small typing error in the code. Waiting for an hour or two and rechecking the exact 36-character UETR often resolves the issue.