Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
A CFO who reviews reconciliation only when a demand notice arrives is reviewing outcomes. A CFO who tracks reconciliation patterns reviews leading indicators — the metrics that predict demand notices 3–6 months before they arrive.
The difference is not access to information. It is knowing which patterns to track.
The Five CFO-Level Reconciliation Patterns
Pattern 1: Match Rate Trend
Match rate is the percentage of transactions that reconcile automatically without manual intervention. The trend matters more than the point-in-time value.
| Match rate trend | What it signals | CFO action |
|---|---|---|
| Stable above 85% | Process is functioning | Monitor quarterly |
| Stable 70–85% | Process has systematic gaps | Review exception classification |
| Declining from above 85% | New root cause emerging | Investigate immediately |
| Below 70% and stable | Process is fundamentally broken | Rebuild matching rules |
| Below 70% and declining | Multiple root causes accumulating | Escalate to restructure |
A match rate that drops 5–10 percentage points over two months typically indicates a data source change (a supplier changed their GSTIN, a bank changed their statement format) or a volume surge that has exceeded the current process capacity.
Pattern 2: Exception Aging Distribution
At any point in time, the exception queue should be dominated by recent exceptions — items less than 7 days old that are within the normal resolution SLA. When the aging distribution shifts toward older exceptions, the reconciliation function is producing exceptions faster than it is resolving them.
The warning threshold: if more than 20% of open exceptions are older than 30 days, the backlog is growing and will accelerate toward regulatory deadlines.
Pattern 3: Reconciliation Debt Velocity
Reconciliation debt — the cumulative unresolved amount — should be tracked in rupee value, not just item count. A team resolving 40 items per month but adding 60 per month is accumulating debt at 20 items per month. If the average value per item is ₹50,000, that is ₹10 lakh per month in accumulating risk.
The formula: Debt velocity = (New exceptions per month × Average value) − (Resolved exceptions per month × Average value). A positive velocity means debt is growing. A velocity above ₹5 lakh per month warrants CFO attention.
Pattern 4: Reconciliation Type Breakdown
Different reconciliation types have different risk profiles and different regulatory deadlines. CFOs should track exception rates separately for:
- Bank reconciliation: Lower risk individually; high volume means aggregate risk accumulates quickly
- TDS reconciliation: Correction returns have quarterly deadlines; Section 245 set-off requires clean Form 26AS
- GSTR-2B reconciliation: ITC claim deadline is September return of the following year; excess claims carry 18% interest
- Platform settlement reconciliation: MDR and TCS mismatches are cash items, not regulatory items — but they compound daily if uncaught
Pattern 5: High-Value Exception Concentration
A reconciliation queue with 200 exceptions worth ₹5 crore in aggregate may have 180 items worth ₹10,000 each and 20 items worth ₹2.5 lakh each. The 20 high-value items represent 90% of the financial risk.
CFOs should receive weekly visibility on exceptions above ₹1 lakh and immediate notification on exceptions above ₹10 lakh. These are not back-office items — they are CFO-level decisions about how to resolve.
Industry-Specific Patterns
Reconciliation risk concentration varies by industry:
IT services and professional services: TDS Section 194J is the dominant exception source — clients deducting 10% TDS on professional services, with net-of-TDS receipts creating amount mismatches at scale.
E-commerce and marketplace: Platform settlement disaggregation is the primary challenge — single bulk credits representing hundreds of orders, each with different MDR rates and TCS deductions.
Manufacturing: GSTR-2B mismatch driven by supplier filing delays is the primary pattern — late-filing suppliers create recurring monthly mismatches that accumulate toward the September ITC deadline.
NBFCs and lending: NACH bounce reconciliation is the primary real-time exception type — bounced mandates must update the LMS same-day for retry logic.
Building a Pattern Dashboard
A CFO reconciliation dashboard requires five views:
- Match rate by type — bank, TDS, GST, platform — with trend arrows for current vs prior month
- Exception aging heatmap — 0–7, 8–30, 31–90, 90+ days buckets, in both item count and rupee value
- High-value exception list — all open exceptions above ₹1 lakh with responsible owner and age
- Debt velocity — month-over-month change in total unresolved value
- Close cycle time — days from period end to reconciliation completion, with target
This dashboard should be auto-generated from the reconciliation system — not assembled manually each month. Manual assembly of a reconciliation dashboard takes 1–2 days and is itself a reconciliation activity that adds to the close time.
Reconciliation software India that generates these five views automatically — as outputs of the matching engine, not as manual reports — gives CFOs real-time reconciliation pattern visibility without additional reporting overhead.
TDS reconciliation software that tracks Form 26AS match rates by deductor over time surfaces the specific deductors generating the most persistent TDS exceptions — the 80/20 of TDS reconciliation effort.
The Institute of Chartered Accountants of India publishes guidance on internal control frameworks for CFOs — reconciliation pattern monitoring is a core component of the internal control environment over financial reporting.