Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
A finance team at a mid-size NBFC was confident their reconciliation process was performing well — until a competitor’s CFO mentioned that their team closes bank reconciliation by day 2 of the following month, while the NBFC’s team was routinely closing by day 12.
The 10-day difference was not a staffing issue. It was a process architecture difference. The competitor had configured automated bank statement ingestion; the NBFC team was still downloading PDFs manually.
Performance benchmarks exist in reconciliation — and the gap between current performance and benchmark is measurable.
Match Rate Benchmarks
Match rate is the percentage of transactions that reconcile automatically without human intervention. Higher is better, but the variance across reconciliation types reflects the inherent complexity of each type.
| Reconciliation type | Manual (spreadsheet) | Automated (best practice) | Industry stretch target |
|---|---|---|---|
| Bank vs cash book | 70–80% | 90–96% | 97%+ |
| TDS receivable vs Form 26AS | 55–70% | 80–90% | 92%+ |
| GSTR-2B vs purchase register | 60–75% | 80–88% | 90%+ |
| Platform settlement vs revenue | 50–65% | 85–92% | 95%+ |
| NACH batch vs mandate register | 45–60% | 82–90% | 93%+ |
The gap between manual and automated match rates (roughly 15–25 percentage points) represents the exceptions that automated rules can resolve without human review — but that manual matching routes to the exception queue instead.
Close Cycle Benchmarks
“Days to close” measures how many business days after the period end the reconciliation is completed and signed off.
| Company size | Manual close (days) | Automated close (days) | Benchmark target |
|---|---|---|---|
| Below ₹10 crore turnover | 5–8 | 2–3 | 3 days |
| ₹10–100 crore turnover | 8–12 | 3–5 | 5 days |
| ₹100–500 crore turnover | 10–15 | 3–5 | 5 days |
| Above ₹500 crore turnover | 12–20 | 4–7 | 7 days |
Companies that close reconciliation after day 10 typically find that month-end management reporting is delayed — because the reconciliation is on the critical path to producing accurate P&L and balance sheet numbers.
Exception Volume and Resolution Benchmarks
Exception Rate
Exception rate is the percentage of transactions that require human review. The benchmark targets:
- Bank reconciliation: Below 5% exception rate (95%+ auto-match)
- TDS reconciliation: Below 15% exception rate
- GSTR-2B reconciliation: Below 20% exception rate (supplier filing delays are inherent)
- Platform settlement: Below 10% exception rate
An exception rate above these thresholds indicates systematic matching problems — wrong rates in the matching engine, missing counterparty configurations, or data source format issues.
Exception Resolution Rate
The percentage of exceptions resolved within SLA. The benchmark: 90% of exceptions resolved within their target SLA. An exception resolution rate below 80% indicates insufficient staffing or insufficient tooling for the exception review workflow.
Exception Aging
The percentage of open exceptions older than 30 days should be below 10%. Above 20% indicates a growing backlog — the reconciliation function is generating exceptions faster than it is resolving them.
Staff Productivity Benchmarks
| Metric | Manual process | Automated process |
|---|---|---|
| Invoices matched per analyst per day | 200–300 | N/A (engine matches) |
| Exceptions reviewed per analyst per day | 30–50 | 80–100 (classified) |
| Staff days per month for bank recon (5 accounts) | 8–12 | 1–2 |
| Staff days for GSTR-2B (500 invoices/month) | 4–6 | 0.5–1 |
| Staff days for TDS recon (30 deductors) | 3–4 | 0.5–1 |
The automation productivity improvement is most significant in the matching phase. The exception review phase shows a smaller improvement — a human reviewing 100 classified exceptions per day vs 50 unclassified exceptions per day sees a 2x productivity gain, not 10x. This is by design: exception review is where human judgment adds the most value.
Benchmarking Against Industry Peers
Reconciliation performance varies by industry — not because the underlying process is different, but because transaction mix and data quality differ:
- IT services: High TDS complexity (Section 194J at scale); bank and TDS match rates are the primary benchmarks
- Manufacturing: High GSTR-2B complexity (500+ purchase invoices per month); GST match rate is the primary benchmark
- E-commerce/marketplace: High platform settlement complexity; MDR and TCS match rates drive performance
- NBFC/lending: NACH batch reconciliation complexity; mandate-level match rates and LMS update latency are the primary benchmarks
The comparison that matters is: how does current performance compare to the benchmark for the same industry and transaction volume — not against a company with a different business model.
Reconciliation software India that logs match rates, exception volumes, resolution times, and close cycle duration automatically — producing benchmark comparison reports without manual calculation — gives CFOs the data to manage reconciliation as a measured function rather than an intuitive one.
TDS reconciliation software with deductor-level match rate tracking shows which of the 30–50 active TDS deductors are driving the exceptions that bring the overall TDS match rate below benchmark.
The Institute of Chartered Accountants of India publishes guidance on finance function performance benchmarks — including standards for close cycle times and reconciliation control expectations for Indian companies.