Key Highlights
- A UTR number is the 12-digit Unique Transaction Reference your bank assigns to every NEFT, IMPS, and UPI credit; it is the single identifier that links a bank deposit to a specific Tally receipt
- Every UPI and bank transfer carries exactly one UTR, and the same UTR appears in the payer's app, your bank statement, and the payment confirmation, which makes it the reliable key for matching a payment to an invoice
- When a distributor collects on a UPI link with 0% MDR on UPI collections, no transaction cap, no monthly fee, the UTR rides along with the credit so the receipt can post against the right bill-by-bill reference automatically
In This Article
- What a UTR number is, in plain terms
- Where to find the UTR in a UPI app and a bank statement
- How UTR differs from order ID, RRN, and cheque number
- How a UTR matches back to a Tally receipt and closes a bill
- Why manual screenshot matching breaks at scale
- Frequently Asked Questions
What a UTR Number Is
A UTR number is the Unique Transaction Reference that your bank stamps on every electronic payment that lands in or leaves an account. UTR stands for Unique Transaction Reference, and it is exactly that: one transaction, one reference, no duplicates. When a retailer pays you ₹47,800 over UPI, IMPS, or NEFT, the banking network generates a UTR for that single credit, and that string is the closest thing to a fingerprint a payment has.
For an Indian distributor, the UTR number is the most useful field on the whole transaction. The amount can repeat (three retailers might each pay ₹12,000 on the same day), the date repeats, and the payer name is often a personal account that looks nothing like the shop's billing name. The UTR does not repeat. That is why it is the field you reach for when a payment lands and you need to know which bill it settles.
A typical UTR is a 12-character alphanumeric string for IMPS and UPI, and a 16- or 22-character reference for NEFT and RTGS depending on the bank. The format varies slightly by rail and by bank, but the rule holds: one credit, one UTR, and it appears identically on both sides of the transaction.
Where to Find the UTR Number
The same UTR shows up in several places, which is exactly what makes it trustworthy for matching. A retailer can read it off their phone, and you can read the same value off your bank statement. Here is where each side finds it.
| Channel | What to open | What the UTR is labelled |
|---|---|---|
| Google Pay | Tap the transaction, scroll to details | "UPI transaction ID" / "UTR" |
| PhonePe | Transaction history, then transaction details | "UTR" or "Transaction ID" |
| Paytm | Passbook, open the payment | "UPI Ref No." / "UTR" |
| Bank statement (net banking / passbook) | Narration column of the credit row | "UTR" / "Ref No." inside the narration |
| NEFT / IMPS receipt | Bank's transfer confirmation SMS or PDF | "UTR Number" |
On the payer's side, almost every UPI app exposes the UTR under the transaction's detail view, usually labelled "UPI transaction ID," "UTR," or "UPI Ref No." It is the long number a retailer can copy and paste into a WhatsApp message when they want to prove a payment went through.
On your side, the UTR sits inside the narration of the credit line on your bank statement. If a retailer pays ₹47,800 and tells you the UTR, you search that string in your statement and the exact credit surfaces. No guessing by amount, no scrolling through twenty similar deposits. The UTR a retailer sends and the UTR in your statement are the same value, which is the whole reason it works as a matching key.
UTR Versus Order ID, RRN, and Cheque Number
Payments carry several identifiers, and distributors often confuse them. They are not interchangeable. Matching on the wrong one is how a receipt ends up against the wrong bill.
| Identifier | Who issues it | What it identifies | Reliable for bank matching |
|---|---|---|---|
| UTR number | Your bank / NPCI rail | The actual bank credit or debit | Yes, this is the key |
| RRN (Retrieval Reference Number) | UPI / card network | The switch-level transaction; often equals the UTR on UPI | Mostly, on UPI it usually matches |
| Order ID | Payment gateway or app | The merchant order, not the bank leg | No, never hits your statement |
| Cheque number | The payer's chequebook | A paper instrument, not an electronic credit | Only for cheque clearing |
The UTR is the only one of these that you can find on your bank statement and that the payer can also see. An order ID lives inside a payment gateway and never appears in your passbook, so it cannot close a bank credit. On UPI, the RRN and the UTR are frequently the same string, which is why UPI matching is clean. A cheque number belongs to a different world entirely, the paper-clearing world that the UTR was built to replace.
For reconciliation, treat the UTR number as the spine and everything else as context. If the amount, date, and payer name all line up but you cannot find a matching UTR in your statement, the payment has not actually credited yet, and posting a receipt against it is premature.
How a UTR Matches Back to a Tally Receipt
Here is the moment that matters for a distributor. A bank credit lands. You have a UTR. You have an open invoice in Tally. The job is to connect the three so the bill is marked paid and the party ledger is correct.
The manual version goes like this. The retailer sends a screenshot: "Bhai, ₹47,800 bhej diya, UTR 4291XXXX2210." You open your bank statement, search that UTR, confirm the ₹47,800 credit is real. Then you open Tally, find the party, see they have three open invoices (₹18,000, ₹47,800, and ₹29,200), and create a receipt entry against the ₹47,800 bill using bill-by-bill allocation. The UTR goes into the narration so anyone auditing later can trace the receipt back to the exact bank credit. That is a clean reconciliation, and the UTR is the thread that held it together.
The catch is that this is four lookups and a typed entry for a single payment, and a distributor collecting from 30 to 300 parties is doing it dozens of times a day. The UTR is also where it most often goes wrong: a digit gets mistyped, the wrong open bill gets picked because two are close in value, or the receipt never gets posted at all because the accountant was busy at 9 PM.
When the collection happens on a payment link instead of a raw bank transfer, the link already knows which invoice it was raised against. The credit arrives with its UTR, and the receipt can post against the correct bill-by-bill reference without a human re-typing the UTR. That is the principle behind auto-reconciliation back into Tally: the payment carries enough context, anchored on the UTR, to find its own home. Distributors who run this on mobile describe it as Tally payment reconciliation on mobile finishing before they get home, instead of a 9 PM data-entry session.
A payment link tied to the Tally invoice closes the loop, because the link carries the invoice reference from the start. The UTR confirms the money is real; the link confirms which bill it belongs to. Together they let a receipt post itself.
Why Manual UTR Matching Breaks at Scale
A UTR is perfect for matching one payment. The trouble is volume and the gap between when money lands and when someone has time to reconcile it.
Consider a Dibrugarh wholesaler whose retailers pay across UPI, IMPS, and the occasional NEFT. On a busy day, 40 credits land. Each one has a UTR sitting in the bank narration, and each one needs to find its open bill in Tally. By evening, the statement has 40 rows and the accountant is matching them against memory and a pile of WhatsApp screenshots. Two of the ₹12,000 payments came from personal accounts with no shop name, so the only way to tell them apart is the UTR each retailer sent. Miss one, and a real payment shows as outstanding while the retailer insists "paisa toh bhej diya tha."
The 0% MDR angle matters here in a practical way. When collection moves to a UPI payment link with 0% MDR on UPI collections, no transaction cap, no monthly fee, the distributor has no reason to push retailers toward off-app bank transfers to dodge a fee. Every collection flows through the link, every credit carries its UTR with the invoice context attached, and the statement stops being a wall of anonymous deposits. Takkada is the only Tally-native distributor collection app in India with genuine 0% MDR on UPI, which means the cheapest collection path is also the one that reconciles itself.
The UTR is not going away as the matching key. What changes is whether a human has to read it off a screenshot and re-type it, or whether the payment arrives already knowing which Tally bill it closes.
Frequently Asked Questions
Q: What is a UTR number?
A: A UTR number is the Unique Transaction Reference your bank assigns to every electronic credit or debit, including UPI, IMPS, NEFT, and RTGS. It is a 12- to 22-character alphanumeric string, unique to that single transaction, and it appears identically in the payer's app and in your bank statement. That uniqueness is why it is the reliable key for matching a payment back to a specific invoice or Tally receipt.
Q: Where do I find the UTR number for a UPI payment?
A: Open the transaction in the UPI app, scroll to the transaction details, and look for "UTR," "UPI transaction ID," or "UPI Ref No." In Google Pay and PhonePe it is in the transaction detail view; in Paytm it is in the passbook entry. On your side, the same UTR sits inside the narration of the credit row on your bank statement.
Q: Is the UTR the same as the UPI transaction ID?
A: On UPI they are effectively the same value. Apps often label the UTR as "UPI transaction ID" or "UPI Ref No.," and the retrieval reference number (RRN) on a UPI payment usually equals the UTR. For matching against your bank statement, treat the UTR as the canonical reference, because that is the string the bank stores in the credit narration.
Q: How do I match a UTR to a Tally receipt?
A: Search the UTR in your bank statement to confirm the credit is real and note the amount, then open the party in Tally, find the open invoice that matches, and post a receipt against it using bill-by-bill allocation with the UTR written into the narration. When the payment came in on a payment link tied to the invoice, the receipt can post against the correct bill automatically instead of being typed by hand.
Q: Can I reconcile a UTR without opening Tally on my laptop?
A: Yes. A mobile layer that syncs with Tally can show the bank credit, surface its UTR, and post the receipt against the right open bill from your phone, so the reconciliation finishes the moment the money lands rather than at a 9 PM laptop session.
Q: What happens if the UTR number doesn't match anything in my statement?
A: If a retailer sends a UTR but you cannot find it in your statement, the payment has either not credited yet or the UTR was mistyped. Do not post a receipt until the matching credit actually appears, because posting against a phantom UTR leaves your party ledger overstated and the real payment, when it lands, gets double-counted.
Takkada is the Tally-native, 0% MDR option that lets distributors collect on UPI links, match each UTR to the right bill, and auto-reconcile receipts back into Tally without the 9 PM data entry. Book a free demo.