Cards and UPI

UPI transaction ID, UTR and RRN: which number is which

UPI transaction ID vs UTR vs RRN explained: what each number is, which one to quote to a merchant or bank, and which to store in your records.

Editorial illustration for UPI transaction ID, UTR and RRN: which number is which

A UPI payment can carry several numbers, and the confusion is that apps use different labels for them. In short: the UPI transaction ID is usually generated by the app, while the UTR and the RRN are reference numbers that the banking side uses. When you contact a bank or merchant, quote the reference number your app shows as UTR, RRN or UPI reference, together with the date, amount and payee.

What does each number mean?

NumberWhat it generally isWhere you see it
UPI transaction IDAn identifier created by the app or service provider for that paymentPayment detail screen of your app
UTRUnique Transaction Reference, a reference for the fund movement used by the banking networkPayment detail screen, SMS or statement
RRNRetrieval Reference Number, a reference used by banks and card or UPI networks to trace a transactionPayment detail, and sometimes inside the statement narration
Order or merchant referenceA number from the shop's own systemThe shop's invoice or app

Labels differ between apps and banks, and in many apps the number shown as UPI reference is the same number as the RRN. Check one payment in your own app to see which labels it uses.

Which number should you quote?

  • To your bank: the reference number that appears in your statement narration if there is one, the date, the amount and the payee handle.
  • To a merchant: the number in your app's payment detail screen, plus the amount and the time. Merchants can often search on their side by that reference.
  • To the app's support: the transaction ID and reference exactly as the app shows them, with a screenshot.
  • For a dispute: all of the above in one message, because each party searches in a different system.

Which one should you store in your records?

Store the number that also appears in the bank statement, because that is the one that lets you match a row later. If the narration contains a long number, that is usually the one. Keep the app's own transaction ID in a notes column as backup. In a sheet, call the columns Statement reference and App ID. Paste, do not retype; one wrong digit makes the number useless.

A worked example of matching

Say your app shows a payment of ₹760 to a pharmacy on the 9th with a 12-digit reference. Your statement shows a UPI row of ₹760 on the 9th with narration containing a number. You search the statement for the first digits of the reference you have. If the digits match, you have the same payment and can store that reference against the row. If they do not, match by date, amount and payee instead, and note that the reference did not appear.

Can you keep the proof with the entry?

For anything you might need to prove later, such as a deposit or a large purchase, save a screenshot of the success screen. SpendixAI keeps receipts with their transactions, so a screenshot attached to the right row stays with it. Make a habit of doing this for payments above whatever amount matters to you.

A short routine

  1. Note which labels your app and bank use.
  2. Add a Statement reference column to your sheet.
  3. For large payments, save the screenshot on the day.
  4. When a payment goes wrong, send the reference, date, amount and payee in one message.
SPENDIXAI JOURNAL

Useful ideas start with a clearer picture of your own spending.

Explore your reports