UPI Payment Reconciliation in India: UTR Tracking & Settlement Matching

A customer says they paid through UPI. The payment screenshot looks successful, but the institute’s dashboard still shows the fee as pending. Later, the bank statement shows a credit, but the finance team cannot tell which invoice it belongs to. These are common payment-operations problems when transaction records, collection reports and bank statements are checked separately.

UPI payment reconciliation is the process of matching each payment recorded by your business with the transaction status reported by your payment provider and the money credited to the relevant bank account. A reliable process helps teams identify genuinely unpaid invoices, avoid asking customers to pay twice, track settlement delays and close the books with an audit trail.

This guide explains the identifiers used in UPI payments, the difference between a transaction reference and a settlement UTR, and a practical reconciliation workflow for schools, coaching institutes, NBFCs, credit societies and other Indian businesses.

What is UPI payment reconciliation?

Payment reconciliation is the process of confirming that the payments your business expected to receive match the payments that were actually processed and settled. For UPI, that means connecting the customer’s payment attempt to the transaction record from the bank, PSP or payment aggregator, and then to the relevant bank credit or settlement entry.

The process is not the same as simply checking whether a UPI app shows a green tick. That screen is one piece of evidence. The business should also check the transaction status available through its acquiring bank or payment provider, and separately verify the settlement record when funds are paid out in batches.

For a business collecting fees or instalments, reconciliation answers three questions: Was the customer payment successful? Which invoice, student, loan instalment or account should receive the credit? Has the corresponding amount reached the business’s bank account or settlement account?

UPI transaction reference vs RRN vs settlement UTR

A frequent source of confusion is that teams use the words transaction ID, UPI reference number, RRN and UTR as though they all mean the same thing. They do not always refer to the same identifier. The exact labels and formats can vary between banks, PSP apps, acquiring providers and payment gateways.

1. Merchant order ID or payment reference

This is the identifier generated by your own system when a fee, invoice or instalment becomes payable. It should connect the payment to the right customer, student, borrower, invoice or collection schedule. It is your internal reference, not a bank-generated UPI reference.

2. Gateway or provider transaction ID

A payment gateway, PSP or aggregator may create its own transaction identifier when it receives a payment request. This ID helps you find the payment in the provider’s dashboard, API response, webhook log or transaction report.

3. UPI transaction reference or RRN

UPI and bank records may contain a transaction reference, retrieval reference number (RRN) or customer reference number that helps the bank or acquiring provider trace an individual payment. NPCI’s UPI circular on bank statement narration identifies the transaction reference number as a 12-digit RRN. Customers may see this reference in their UPI app or bank statement. Preserve it exactly as supplied, including any leading zeroes.

NPCI’s UPI circular on transaction reference number and bank narration

4. Settlement ID and settlement UTR

When a provider settles a group of merchant transactions, the amount may be credited to the merchant’s bank account as one payout. The provider may assign an internal settlement ID to the batch, while the bank transfer has a separate Unique Transaction Reference (UTR). The settlement UTR helps the merchant trace the payout in the bank account. It is not necessarily the same as the reference for each customer’s individual UPI payment.

For example, 18 customers may pay separate fees during the day. The provider may report 18 payment transactions and later transfer one settlement amount to the institute. The finance team needs the individual transaction references to match the 18 invoices, and the settlement UTR to trace the bank credit for the batch.

A useful settlement report should identify each payout batch, list the transactions included, show gross collections and any documented deductions, and state the net payout with its settlement reference. These fields help the finance team compare the provider’s batch record with the matching bank credit.

Match the report’s net settlement amount with the bank credit, and use the settlement reference when tracing a missing or delayed payout.

The three records every business should reconcile

A practical UPI reconciliation process uses three records. The names of the files and columns may differ by provider, but the information should allow your team to connect each customer payment to the actual bank movement.

Record A: Your invoice or collection ledger

This is the source of what should have been paid. It may contain invoice ID, student or customer ID, instalment number, amount due, due date, payment link ID, mandate ID and current payment status.

Record B: Payment provider or bank transaction report

This is the source of what happened during the payment attempt. It may include provider transaction ID, merchant order ID, UPI reference or RRN, amount, transaction timestamp, status, response code, payment method, and refund or reversal status.

Record C: Bank statement or settlement report

This is the source of what reached the business’s account. Depending on the payment flow, it may contain individual UPI credits or a consolidated settlement entry, along with the bank reference or settlement UTR, credit date, amount and any deductions or adjustments.

A transaction should not be treated as fully reconciled just because two records appear to match. For an aggregated payout, the team should also ensure that the net settlement batch agrees with the bank credit after accounting for documented fees, taxes, refunds, reversals or adjustments.

How to reconcile UPI payments step by step

Step 1: Export the payment and collection records

Start with the list of invoices or instalments expected for the period. Download the transaction report from the acquiring bank, PSP or payment aggregator, and obtain the relevant bank statement or settlement report. Keep the original downloaded files unchanged for audit and investigation.

Step 2: Standardise the data fields

Different providers use different names for the same type of reference. Map the data into a consistent working format: merchant order ID, provider transaction ID, UPI reference or RRN, amount, transaction date and time, status, settlement batch ID, settlement UTR, bank credit date and net settlement amount.

Store identifiers as text, not numbers. This helps preserve leading zeroes and long reference values. Standardise timestamps and time zones before comparing records, and do not round amounts during matching.

Step 3: Match exact transaction references first

The strongest match is normally a unique reference shared between your system and the provider’s transaction record. Match on merchant order ID or provider transaction ID where available, then use the UPI reference or RRN to investigate payments that need bank-level tracing.

Amount and timestamp can help locate a record, but they should not be treated as a unique identifier on their own. Two students can pay the same instalment amount within a few seconds of each other.

Step 4: Verify the transaction status

Separate successful, failed, pending, reversed and refunded transactions. Do not mark a pending transaction as successful simply because the customer has shared a screenshot. Equally, do not ask a customer to pay again until the first attempt has been checked with the acquiring provider or bank.

If the provider’s status and the customer’s UPI app disagree, capture the reference number, amount, date and time, then raise a status check with the acquiring bank or payment provider. Keep the case open until the outcome is clear.

Step 5: Match the settlement to the bank credit

If payments are settled individually, compare the transaction reference and amount with the corresponding bank statement entries. If the provider settles in batches, match the settlement ID and settlement UTR to the bank credit, then confirm that the total of the included transactions explains the batch amount.

A settlement amount may differ from the gross amount collected if the provider applies fees, taxes, refunds or other documented adjustments. Compare like with like: gross transaction value against gross transaction records, and net settlement value against the actual bank credit.

Step 6: Create an exception queue

Anything that cannot be matched should move to an exception queue with an owner and next action. Useful categories include pending status, missing reference, amount mismatch, duplicate payment, failed transaction awaiting reversal, refund pending, missing settlement, and bank credit not identified.

Step 7: Close the case with an audit trail

Record the action taken, supporting reference, provider response, person who resolved it and date of closure. If a payment is allocated to a different invoice or corrected manually, preserve the reason and approval instead of silently changing the original entry.

What to do when a UPI payment is successful but not visible in your records

First, check the payment status in the acquiring provider’s dashboard or API record. Search using the merchant order ID, provider transaction ID or UPI reference supplied by the customer. Confirm the amount, timestamp and payee details before changing the invoice status.

If the provider confirms a successful transaction, update the customer’s payment record and investigate why the status did not reach your collection system. The issue may be a delayed webhook, a failed callback, an incorrectly mapped order ID or an integration that did not process the final status.

Do not ask the customer to pay again just because your internal dashboard has not refreshed. Record the case, verify it with the provider and communicate the status clearly. If the provider cannot confirm success, keep the transaction in an exception state until the bank or acquirer provides a final outcome.

Common UPI reconciliation exceptions and how to handle them

Customer account debited, merchant status pending

Capture the UPI reference or RRN, amount, timestamp and merchant order ID. Check the acquiring provider’s status and follow its process for pending or timed-out transactions. Avoid creating a second payment request while the first attempt is unresolved.

Payment failed but the customer says the amount was debited

A failed payment and a completed refund are different events. Track the original transaction and the reversal or refund separately. Ask the customer to check the bank statement, and raise a trace or dispute with the relevant bank or acquiring provider when the expected reversal is not visible.

Provider shows success but the settlement credit is missing

Look for the settlement record rather than only the individual UPI transaction. Check the payout status, settlement date, settlement UTR and destination bank account details. If the provider shows that the batch was paid, use the settlement UTR to trace the credit with the bank.

Bank credit exists but no invoice matches it

Search the bank reference, amount, date and any remitter information in the provider’s report. Check for a payment made against an older invoice, a different customer reference or a payment link created outside the usual workflow. Keep unidentified credits in a suspense or unapplied-payment queue until verified.

Duplicate payments

Compare the two provider transaction IDs and UPI references. Confirm whether both transactions succeeded before arranging a refund or applying the extra amount to another invoice. Keep the original payment and refund records linked so that the account history remains clear.

Partial payment or amount mismatch

Check whether the customer used an approved partial-payment option, paid multiple invoices together, or entered a different amount. Allocate the payment according to your business rules and retain the outstanding balance. Do not automatically mark the full invoice as paid when only part of the amount has been received.

RBI timelines for failed UPI transactions

The Reserve Bank of India’s 20 September 2019 circular sets an outer limit for reversal of specified failed transactions. It distinguishes a UPI funds transfer from a merchant payment where the customer’s account is debited but the merchant does not receive transaction confirmation.

For a UPI funds transfer where the payer is debited but the beneficiary account is not credited, the framework provides for auto-reversal by T+1 day. For a UPI merchant payment where the payer is debited but confirmation is not received at the merchant location, the framework provides for auto-reversal within T+5 days. The circular specifies compensation of ₹100 per day for delay beyond the applicable timeline.

These are customer-side failed-transaction reversal timelines. They are not a promise that a merchant’s normal payment-gateway settlement will arrive in one or five days. Merchant settlement timing is a separate process governed by the provider’s settlement arrangement, bank working days and applicable terms.

Read RBI’s circular on the time limit for reversing failed payments.

Direct UPI collections vs payment gateway settlements

The reconciliation method depends on how the business accepts UPI. In a direct UPI collection flow, the bank or acquiring provider may provide transaction-level credits and references. In a payment gateway or aggregator flow, the provider may first record individual customer payments and later transfer a combined net settlement.

The second model requires two separate matches: each customer transaction to the relevant invoice, and the settlement batch to the bank statement. A single bank UTR for the payout does not replace the individual references needed to identify which customers paid.

For recurring collections, include the mandate or schedule reference as well as the individual debit transaction reference. A mandate authorisation confirms permission for future debits; it does not itself prove that a particular instalment was successfully collected.

eNACH vs UPI AutoPay for Indian businesses and UPI AutoPay for businesses

How often should businesses reconcile UPI payments?

For high-volume collections, reconcile transactions and settlements daily. A daily process helps the team identify missing records while the payment details are easy to retrieve and before month-end closing turns a small mismatch into a large investigation.

A simple operating cadence can include an intraday check for pending or failed payments, a daily match between provider transactions and invoices, a daily or provider-cycle match of settlements to bank credits, and a monthly review of unresolved exceptions.

Smaller teams may start with a daily spreadsheet and a clear owner for unmatched entries. As volumes grow, automate exact-reference matching, status updates and exception alerts so that finance staff spend time on the exceptions rather than copying and comparing every row.

What should payment reconciliation software include?

A useful reconciliation workflow should make it easy to search transactions by customer, invoice, payment link, mandate, provider reference or UTR. It should show the current status, transaction history and settlement information in one place.

Look for provider and bank report imports, API or webhook updates, duplicate detection, configurable match rules, partial-payment handling, refund and reversal tracking, settlement batch matching, role-based approvals, exception ownership and downloadable audit reports.

The system should preserve the raw provider reference and original transaction record. If a team member changes an allocation or resolves an exception manually, the change should be logged with a reason and timestamp.

A practical daily reconciliation checklist

1. Download or sync the collection ledger, provider transaction report and relevant bank or settlement report.

2. Check that the date range, bank account, currency and payment provider are correct.

3. Match records using unique order IDs and provider transaction IDs before using amount and time as secondary clues.

4. Verify the final status of pending, failed and timed-out transactions.

5. Match each settlement batch and UTR with the corresponding bank credit.

6. Explain differences using documented fees, taxes, refunds, reversals or adjustments.

7. Assign unmatched records to an exception owner and track them until closure.

8. Keep source files, status responses, approvals and manual adjustments for audit.

How SlashCollect supports collection visibility

SlashCollect helps businesses manage scheduled collections, payment reminders, transaction tracking and reconciliation in one workflow. For institutions collecting fees or instalments, the goal is to connect what was due, what customers paid and what the business can verify in its collection records.

A clear payment status and reference trail also makes customer support easier. Instead of asking a parent or borrower to repeat the same information to different teams, an operations team can use the transaction reference to investigate the payment and route unresolved cases to the relevant provider or bank.

SlashCollect’s payment collection software guide

Frequently asked questions

What is a UTR number in UPI payments?

UTR stands for Unique Transaction Reference. The reference shown for an individual UPI payment may be labelled as a UPI reference, RRN or customer reference number by the bank or PSP. A merchant settlement may have a separate UTR for the payout credited to the business bank account. Use the exact reference supplied for the transaction or settlement you are tracing.

Is the UPI transaction reference the same as the settlement UTR?

Not necessarily. An individual customer payment has its own transaction identifiers, while a payment provider may create a separate settlement reference for a batch transfer to the merchant. A business may need both to reconcile customer invoices and bank credits.

How do I check whether a UPI payment reached my business account?

Check the transaction status in your acquiring bank or payment provider’s dashboard, then check the relevant bank statement or settlement report. For a batch payout, compare the settlement UTR in the provider report with the bank credit reference.

What should I do if a customer says they paid but my dashboard shows pending?

Search using the merchant order ID and the UPI reference or RRN supplied by the customer. Verify the status with the acquiring provider or bank, and do not request a second payment until the original attempt has a clear final status.

Can UPI reconciliation be automated?

Yes. Businesses can automate data imports, exact-reference matching, duplicate detection, status updates and exception alerts. Cases involving unclear bank status, missing credits or manual allocation still need review by an authorised team member.

Should a mandate be marked as paid after it is approved?

No. A mandate represents authorisation for future debits. Each scheduled debit is a separate payment attempt and should be reconciled using its own transaction status and reference.

Conclusion

UPI reconciliation is more than matching amounts in a spreadsheet. It connects the customer invoice, the individual payment transaction and the settlement or bank credit. Understanding which reference belongs to each stage helps teams investigate pending payments, avoid duplicate collection attempts and close their records accurately.

Start with consistent transaction identifiers, daily matching and a clear exception queue. As payment volumes grow, automate the routine matches but retain human review, source records and an audit trail for every unresolved or manually adjusted payment.

The NPCI circular explains the UPI reference field, while the RBI circular covers failed-transaction reversals. Neither replaces the provider’s merchant-settlement report.