Bank Reconciliation for Indian Enterprises
Enterprise bank reconciliation is not BRS at scale — it is bank-specific format parsing, narration pattern matching, multi-bank consolidation, and audit-ready documentation. Guides covering HDFC, ICICI, SBI, MT940, and CARO 2020 audit workflows.
Basic bank reconciliation works when a business has one account and reads statements in a browser. It breaks the moment an enterprise has 15 current accounts across four banks, each with its own narration format, each integrated with a different ERP, and each subject to CARO 2020 audit scrutiny. At that scale, the reconciliation problem is not 'do the balances match' — it's 'can we classify every entry deterministically and show an auditor how we did it.'
India's bank-specific complexity is underrated. HDFC NetBanking, HDFC CMS, and HDFC MT940 are three different formats. ICICI CIB has its own narration grammar. SBI's YONO Business and CMP exports use different date and amount conventions. PSU banks ship dot-matrix-era statements in PDFs that need OCR before they can even be parsed. Co-operative banks often have no digital export at all.
This cluster covers the banks (HDFC, ICICI, SBI), the formats (MT940, CSV, PDF), the operational surfaces (narration patterns, opening balance, bank charges, payroll bank reconciliation), and the audit lens (CARO 2020). Articles are written for finance teams managing multi-bank consolidation — not for bookkeepers reconciling one account.
CARO 2020 and Bank Reconciliation: Audit Requirements for Indian Companies
Clause 3(ii)(b) of CARO 2020 requires auditors to report whether quarterly statements filed with banks agree with books of account for companies with working capital limits exceeding ₹5 crore. Finance teams that treat bank reconciliation as a month-end formality face audit qualifications, material weakness disclosures, and GST exposure from unreconciled bank credits.
Bank Charges Reconciliation in India: Service Fees, GST on Charges, and Auto-Debit Matching
Bank charges — service fees, NEFT and RTGS transaction charges, cheque book charges, annual maintenance fees, and GST on all of the above — are among the most consistently mismatched items in Indian bank reconciliation. They arrive as auto-debits without prior invoice, carry GST at 18%, and must be allocated to the right expense ledger. This guide covers how bank charge reconciliation works in India and why it generates disproportionate exceptions.
Bank Statement Narration Patterns in India: How Reconciliation Systems Parse Them
Narration-based matching is the core challenge in Indian bank reconciliation. NEFT, RTGS, IMPS, UPI, and NACH credits each arrive with different narration structures from different banks — and none follow a single national standard. This guide covers the narration patterns from major Indian banks, how reconciliation systems extract match keys, and where narration parsing fails.
HDFC Bank Reconciliation: Statement Formats, CMS API, and Narration Patterns
HDFC Bank is the most widely used bank for enterprise current accounts in India. Its NetBanking, CMS (Cash Management Services), and MT940 export have specific narration formats and field structures that affect how reconciliation systems parse and match transactions. This guide covers HDFC Bank statement types, narration structures, CMS integration, and configuration details for automated reconciliation.
ICICI Bank Reconciliation: CIB Statement Format and Enterprise Account Matching
ICICI Bank's Corporate Internet Banking (CIB) platform has specific statement export formats and narration structures that affect enterprise reconciliation. ICICI's MT940 implementation uses /TXT/ prefix in the :86: tag — different from HDFC's /INF/ — and its NEFT/RTGS narrations follow a format that requires specific parser configuration. This guide covers ICICI Bank statement types, narration patterns, and what enterprise finance teams should configure for automated reconciliation.
MT940 Bank Statement Format in India: How It Enables Automated Reconciliation
MT940 is the SWIFT message format used by India's leading banks for enterprise statement export. Unlike PDF or CSV downloads, MT940 delivers structured, parseable transaction data that reconciliation engines consume directly — no screen-scraping, no manual field extraction. This guide covers how MT940 works, which Indian banks support it, and what it changes for automated bank reconciliation at scale.
Opening Balance Reconciliation in India: Resolving Month-Start Discrepancies
Opening balance reconciliation is the first control check of every new accounting period — confirming that the opening balance in the books matches the prior period's closing balance. For Indian companies running monthly reconciliation across multiple bank accounts, GST ledgers, and TDS receivables, opening balance discrepancies are the first detection point for prior-period errors that were not resolved. This guide covers the common causes and resolution sequence.
Salary and Payroll Bank Reconciliation in India: Bulk Transfer Matching and TDS Alignment
Salary disbursements generate some of the largest single-day bank debits for Indian companies — and some of the most persistent reconciliation exceptions. A bulk salary NEFT to 400 employees appears as a single bank debit but must align with an itemised payroll register that includes TDS deductions (Section 192), PF contributions, ESI deductions, and professional tax. This guide covers how salary payroll bank reconciliation works and where it breaks.
SBI Bank Reconciliation: Government Account Formats, YONO Business, and Statement Parsing
State Bank of India (SBI) is the primary bank for PSUs, government-linked companies, and many large Indian enterprises. Its YONO Business platform, CMP (Cash Management Product) service, and statement formats differ from private banks — particularly for government credits: PFMS disbursements, GST refunds, subsidy receipts, and TDS challan payments. This guide covers SBI bank reconciliation for enterprise finance teams.
See how TransactIG handles reconciliation for your industry
TransactIG is configurable for your ERP, your bank feeds, and your compliance requirements. Most implementations complete in 2–4 weeks without code development.