Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
A retail chain with 12 stores processes ₹90 lakh in UPI payments and ₹30 lakh in card (POS) payments per month. Monthly bank reconciliation takes 4 days — because the bank statement shows 60 bulk credits (5 UPI settlements × 12 stores) that must be disaggregated into 8,000+ individual transactions.
This is a data volume problem and a format mismatch problem. Both are solvable — but not with a spreadsheet.
UPI Settlement Structure
UPI payments in India do not settle individually to the merchant’s bank account. They aggregate into daily or periodic batch settlements, depending on the payment aggregator.
UPI Settlement Flow
- Customer initiates UPI payment — UTR generated, funds transfer confirmed
- Aggregator collects payments across the day
- Aggregator sends bulk settlement to merchant’s nodal/settlement account
- Merchant bank receives a single credit — the sum of all UPI payments for the period, net of refunds and chargebacks
- Aggregator provides settlement report — line-by-line breakdown of individual transactions
The reconciliation task: match each line in the aggregator’s settlement report to a transaction in the order management system, then match the settlement total to the bank credit.
Settlement Timing Differences
| Payment method | Settlement to bank | Bank statement visibility |
|---|---|---|
| UPI (standard) | T+1 business day | T+1 by end of day |
| UPI (instant settlement — premium) | Same day | Same day |
| Credit card (standard) | T+2 to T+3 | T+2 or T+3 |
| Debit card RuPay | T+1 | T+1 |
| POS terminal (most banks) | T+1 | T+1 |
| BNPL / EMI at POS | T+7 to T+15 | Varies by issuer |
These timing differences create legitimate outstanding items in bank reconciliation — credits in the order management system for which no bank credit has arrived yet.
POS Terminal Reconciliation
POS terminal reconciliation has two components: MDR reconciliation and transaction-level matching.
MDR Deduction Handling
For credit card POS transactions, the acquirer deducts MDR before crediting the merchant. A POS terminal processing ₹50,000 in credit card transactions at 2% MDR credits ₹49,000 to the merchant’s account, not ₹50,000. The reconciliation must:
- Post the gross transaction amount to revenue (₹50,000)
- Post the MDR to a fee expense account (₹1,000)
- Match the net bank credit of ₹49,000 against the gross receipt net of MDR
POS terminals often aggregate multiple days’ transactions in a single settlement. A Monday morning credit of ₹1,23,456 may represent Saturday and Sunday transactions combined — a timing difference that the reconciliation must carry correctly.
POS Settlement File Parsing
Most acquiring banks provide a daily settlement file in CSV or flat-file format containing:
- Terminal ID and merchant ID
- Transaction date and time
- Card type and last 4 digits
- Gross transaction amount
- MDR percentage and amount
- Net settlement amount
- Batch reference number
The reconciliation system maps this file against the POS transactions recorded in the billing or ERP system using the transaction date and gross amount as the primary matching key.
Daily vs Month-End Reconciliation for UPI and POS
Monthly reconciliation of UPI and POS is practically difficult for high-volume merchants: 30 days of settlements must be disaggregated simultaneously, with chargebacks and refunds from earlier in the month affecting later settlements.
Daily reconciliation is more efficient: each day’s settlement is matched within 24–48 hours, while transaction data is fresh and customer disputes can be identified quickly. The end-of-month bank reconciliation then matches only the settlement totals — because the individual transactions have already been verified.
The daily-first approach requires:
- Automated download of the aggregator’s daily settlement report
- Automated matching against the order management system
- Exception flagging for unmatched items (typically 1–3% of transactions)
- Human review of exceptions before the settlement is posted
Handling Chargebacks in UPI and POS Reconciliation
Chargebacks — disputed transactions where the customer has successfully reversed the payment — appear as deductions in subsequent settlement reports. A chargeback processed in month 2 reduces a settlement in month 2 for a transaction that was originally processed in month 1.
The reconciliation must:
- Identify the chargeback in the settlement report
- Match it to the original transaction in month 1
- Reverse the revenue entry for the original transaction
- Record the chargeback as a deduction from settlement
Untracked chargebacks overstate revenue and cash. Companies with high chargeback rates (above 0.5% of GMV) may have significant revenue overstatement if chargebacks are not systematically tracked.
Bank reconciliation software that parses aggregator settlement files — Razorpay, PayU, Cashfree, and bank POS settlement CSVs — and disaggregates bulk credits into transaction-level matches eliminates the primary manual effort in UPI and POS reconciliation.
Reconciliation software India that handles both the aggregator-level reconciliation (settlement file vs order system) and the bank-level reconciliation (bank statement vs settlement total) in a connected workflow produces a complete cash-to-bank trail without intermediate spreadsheet steps.
The Reserve Bank of India publishes guidelines on UPI settlement timelines, merchant discount rates for card payments, and settlement obligations for payment aggregators — the regulatory framework that governs what finance teams should expect in their settlement files.