Guide · Reconciliation
UPI reconciliation: matching switch, network and core every day.
UPI volumes make month-end reconciliation impossible. A break that is not found today becomes a customer complaint, a dispute or a GL difference next week.
UPI reconciliation confirms that every UPI transaction is recorded consistently across the systems it passes through: your switch, the network’s settlement data and your core banking or ledger, and that the money settled matches.
The sources being matched
| Source | What it shows |
|---|---|
| Switch logs | Every transaction your switch processed and its status |
| Network settlement data | What the network says was settled, and net positions |
| Core banking or ledger | What was posted to customer and settlement accounts |
| GL and settlement account statements | Money that actually moved |
Common break types
- Successful at the switch but not posted in core, or posted twice.
- Debited from the customer but failed at the network: a reversal is due.
- Pending or timed-out transactions whose final status arrives later.
- Amount or reference mismatches between files.
- Disputes and chargebacks that change an earlier settled position.
- Settlement totals that do not agree with the sum of transactions.
A daily UPI recon process
- Load each source as it lands, mapped to one schema.
- Match on transaction reference first, then on amount, date and account with tolerances.
- Classify each break by type and give it an owner.
- Age breaks and escalate before they become customer complaints.
- Post corrections through your normal maker-checker process.
- Close the day and carry open breaks forward with their age.
Turnaround and reversal requirements are set by the network and regulators; confirm them with your operations and compliance teams.
How AutoRecon does it
AutoRecon is built for finance, operations and treasury teams at banks, NBFCs and payment companies. Switch, network, core, GL, bank and MT950 statements and ERP files are loaded as they land and mapped to one schema, with bad rows rejected and the reason given. UPI and IMPS, cards, NEFT/RTGS, nostro and vendor recons are matched daily on rules you write: exact, tolerance and fuzzy narration matching. Each break is classified, aged and given an owner; recurring breaks become a suggested rule, which takes effect only after maker-checker. The daily close is approved by maker and checker, and MIS, board packs and regulatory returns are drafted with every number traced to the query that produced it. It is read-only by default and writes nothing to your core unless you open the path.
Questions
What is UPI reconciliation?
Confirming that every UPI transaction is recorded consistently across the switch, the network’s settlement data and the core or ledger, and that settled money matches.
What are common UPI reconciliation breaks?
Transactions successful at the switch but not posted in core, debits without a successful transaction, pending or timed-out transactions, reference or amount mismatches, and disputes changing a settled position.
How often should UPI be reconciled?
Daily at least, because of volumes and because unreconciled debits quickly become customer complaints.
See it on your own data. AutoRecon — Close the day before it starts. Book a 30-minute working session with an engineer.