Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
What Bank Reconciliation Is
Bank reconciliation is the process of comparing a company’s internal bank account ledger — as maintained in the ERP or cashbook — against the bank statement issued by the bank for the same period, and accounting for every difference between the two records. The process does not assume error; it assumes that legitimate timing differences exist and documents them.
The two records differ because the bank and the company book transactions on different dates. A cheque issued on 31 March appears in the company’s books immediately but may not clear the bank until 2 April. A bank charge levied on 28 March may not be in the company’s books until a finance team member reviews the statement. These are expected differences. The reconciliation statement explains each one.
In India, bank reconciliation covers NEFT, RTGS, IMPS, UPI, cheque, NACH batch credits, and payment gateway settlement credits — each with a different reference format, settlement cycle, and matching approach.
The Standard 4-Step Process
Step 1: Obtain the bank statement
Download the bank statement for the period via net banking or SFTP feed. Major Indian banks support MT940 or CSV formats for enterprise accounts. Note the distinction between transaction date and value date — for NEFT credits, the value date may be one day later than the transaction date, which creates a timing difference in date-based matching.
Step 2: Extract the cash or bank ledger from the ERP
Export the bank account ledger for the same period. Confirm that the export includes the narration or reference number field. If the ERP captures a vendor invoice number but the bank statement narration carries the UTR, matching will require a secondary lookup from the payment record to retrieve the UTR.
Step 3: Match entries using UTR and transaction reference
Match each bank statement entry to its corresponding ledger entry. The UTR is the primary match key for NEFT and RTGS. For NACH batch credits, match the net batch amount to the collection run total, then reconcile individual mandates separately. For UPI, the UPI reference number serves as the match key. Entries that match on reference and amount are marked reconciled. Remaining entries are classified as timing differences or exceptions.
Step 4: Classify and resolve exceptions
Classify each unmatched entry: outstanding payment (booked but not yet reflected in bank), deposit in transit (in bank but not yet booked), bank charge not recorded, or unexplained item. Resolve each category. Outstanding items older than defined aging thresholds should trigger an escalation.
Common Causes of Bank-vs-Ledger Mismatch
| Cause | Source | Typical Aging |
|---|---|---|
| Outstanding cheque | Issued, not yet presented to bank | 1–5 working days; investigate if >15 days |
| Deposit in transit | Cash/cheque deposited, not yet credited | 1–2 working days under CTS |
| Bank charges not booked | Account maintenance, NEFT/RTGS fees, SMS charges | Booked after monthly statement review |
| NACH batch return credit | Failed mandate debited back after initial credit | 3–5 working days after presentation date |
| Payment gateway settlement lag | Net credit for multiple orders, single bank entry | T+1 to T+3 depending on gateway contract |
India-Specific Considerations
The diversity of Indian payment instruments creates matching complexity that standard bank reconciliation templates do not address. RTGS transactions carry a 22-character UTR beginning with the bank IFSC code. NEFT UTRs follow a different format. IMPS uses a 12-digit reference. UPI uses a transaction ID from the NPCI switch. NACH batch credits appear as a single aggregate credit, with individual mandate-level data only in the NPCI-issued settlement file, not in the bank statement narration.
TDS deducted by customers appears as a net credit (invoice amount less TDS) rather than the full invoice amount. This requires the reconciliation to account for the TDS deduction before matching the bank credit to the invoice — a step that manual reconciliation frequently misses, creating an apparent shortfall that carries forward into the next period.
For finance teams managing more than 500 monthly bank transactions across multiple accounts, reconciliation software India purpose-built for multi-instrument matching — including UTR-based NEFT/RTGS matching and NACH batch grouping — reduces the time taken from 5–10 staff days to under 1 day per month. Where TDS entries are also part of the bank reconciliation workflow, TDS reconciliation software integrated with the bank reconciliation process eliminates the manual step of netting TDS before matching.