Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
A mid-market retailer with 500 UPI transactions per day accumulates 15,000 bank credits per month — each a separate line in the bank statement with its own UPI Reference ID. Manual matching using VLOOKUP fails above roughly 200 transactions per day. Above that volume, the only viable approach is automated reconciliation using the UPI Reference ID as the primary match key. This article is for finance and operations teams at merchants receiving UPI payments directly or via payment aggregators at scale.
What UPI Settlement Is
UPI (Unified Payments Interface) is India’s real-time payment network managed by NPCI. For merchants, UPI settlement refers to the process by which customer payments made via UPI apps — PhonePe, Google Pay, Paytm, BHIM — are cleared and credited to the merchant’s bank account or payment aggregator’s nodal account.
The defining characteristic of UPI settlement is T+0 real-time credit at the NPCI level. This means the merchant’s account (or the aggregator’s nodal account) receives the credit on the same day the transaction is authorised. This is structurally different from card settlements, which batch overnight and settle T+1, or from NEFT, which settles in half-hourly batches.
UPI P2M (Person to Merchant) transactions below ₹2,000 carry 0% MDR, per RBI circular. This means no fee deduction for the majority of small-ticket UPI transactions. For transactions above ₹2,000 and in certain merchant categories, MDR may apply based on the aggregator agreement. The MDR structure determines the reconciliation formula: zero-MDR transactions reconcile at gross = net, while MDR-bearing transactions require fee deduction to reconcile.
How UPI Settlement Reconciliation India Works
Direct UPI Settlement: One Credit Per Transaction
For merchants with direct bank UPI merchant IDs, each UPI transaction produces an individual credit in the bank statement. The bank narration format is: UPI/P2M/[12-digit UPI Ref ID]/[VPA or merchant name]. The UPI Reference ID in this narration is the primary match key.
Reconciliation involves extracting the UPI Reference ID from each bank credit narration and matching it to the corresponding order ID in the point-of-sale system, e-commerce platform, or ERP. The match is deterministic: one UPI Ref ID maps to one transaction, and one transaction maps to one bank credit. The challenge at scale is parsing thousands of narration strings per month to extract the reference ID, and then joining that extracted key against the order database. At 500 transactions per day, this is a 15,000-row matching task per month — manageable with automation, not with manual review.
Aggregator-Routed UPI: Batch Settlement Matching
Most mid-market and enterprise merchants process UPI through payment aggregators — Razorpay, PayU, BillDesk, Cashfree. In this configuration, UPI transactions do not credit the merchant’s bank directly. Instead, they settle to the aggregator’s nodal bank account in real time (T+0), and the aggregator then batches all settled transactions and issues a consolidated credit to the merchant — typically T+1 or daily.
This creates a two-layer reconciliation requirement. At the outer layer, the batch bank credit from the aggregator must be matched to the aggregator’s settlement report. At the inner layer, each UPI transaction within the aggregator report must be matched to the corresponding order in the merchant’s system using the UPI Reference ID. The outer match is straightforward — one batch credit per settlement file. The inner match is the volume problem: each aggregator settlement report can contain hundreds to thousands of individual UPI transaction lines.
Handling Failed and Refunded UPI Transactions
UPI transactions that fail after initiation but before settlement can create reconciling items if the order system records the payment attempt but the bank never receives a credit. Failed UPI transactions carry a transaction ID in the UPI app but no bank credit, so they appear in the order system as pending and do not appear in the bank statement at all.
Refunded UPI transactions settle in reverse — the merchant’s bank is debited and the customer’s account is credited. In the bank statement, UPI refunds appear as debit entries with UPI Reference IDs. These must be matched to the corresponding original transaction and the refund event in the order system. In aggregator-routed flows, refunds are typically netted against the settlement — a deduction from the batch credit rather than a separate debit.
UPI Reconciliation: Transaction Type Reference
| Transaction Type | Settlement Timing | MDR | Match Key | Reconciliation Method |
|---|---|---|---|---|
| P2M below ₹2,000 (direct) | T+0 to merchant bank | 0% | UPI Reference ID (12-digit) | One credit per transaction in bank statement |
| P2M above ₹2,000 (direct) | T+0 to merchant bank | Per aggregator agreement | UPI Reference ID (12-digit) | One credit per transaction, net of MDR if applicable |
| P2M via aggregator (any amount) | T+0 to nodal; T+1 to merchant | Per aggregator agreement | UPI Ref ID within settlement report | Two-layer: batch credit + transaction-level match |
| UPI refund (direct) | T+0 debit to merchant | N/A | UPI Ref ID of original transaction | Debit match to original credit and refund event in order system |
| Failed UPI transaction | No settlement | N/A | UPI transaction ID (no bank credit) | Open item in order system; cleared once failure confirmed |
India-Specific Compliance Angle
UPI infrastructure is managed by NPCI. Settlement occurs through nodal bank accounts — designated accounts maintained by payment aggregators under RBI’s Payment Aggregator guidelines, which require aggregators to maintain merchant funds in escrow-like nodal accounts separate from their own funds.
For GST-registered merchants, MDR on UPI transactions carries 18% GST where MDR applies. For transactions below ₹2,000 where MDR is 0%, there is no MDR and therefore no GST on MDR. For transactions above the threshold in MDR-applicable categories, the 18% GST on MDR is generally eligible as ITC for registered businesses — but only if the aggregator provides a valid tax invoice. GST reconciliation on UPI MDR follows the same GSTR-2B matching process applicable to other payment processing fees.
For enterprises handling high-volume UPI flows alongside card and net banking, structured payment gateway reconciliation frameworks that handle multiple concurrent data sources reduce the manual effort required. Reconciliation software India finance teams deploy for UPI-heavy transaction profiles can parse bank narrations to extract UPI Reference IDs, match them to order records at volume, and flag failed or unmatched transactions. The NPCI UPI product overview defines the UPI Reference ID standards and transaction flows that underpin this matching logic.
Merchants that have moved from manual VLOOKUP-based UPI matching to automated reconciliation report improving match rates from 51% to 88%, with deployment completed in 2–4 weeks through configuration only — no code development required. Full audit trail functionality — with every match, exception, and manual override time-stamped — provides the transaction-level documentation required for GST assessments and payment aggregator dispute resolution. ISO 27001:2022 certified infrastructure ensures that high-volume transaction data is handled within a controlled security environment.
The following questions address the reconciliation mechanics and compliance requirements most frequently raised by finance teams managing UPI settlement at scale.