Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
At 50 NACH mandates per day, a monthly reconciliation process is adequate — 1,500 transactions per month is manageable in a spreadsheet. At 5,000 NACH mandates per day, monthly reconciliation means discovering a systematic matching error 30 days after it began — by which time 1,50,000 transactions have been processed against the same incorrect logic.
The decision between daily and monthly reconciliation is not a preference — it is a function of transaction volume, settlement timing, and regulatory requirement.
Benefits and Costs of Daily Reconciliation
The Case for Daily
Daily reconciliation catches errors within 24 hours of occurrence — before they compound. For specific transaction types, this matters operationally:
- NACH bounces: An NBFC must update its LMS (Loan Management System) with bounce status the same day to trigger the correct retry logic and DPD counter. A 30-day delay in bounce processing distorts the delinquency portfolio.
- Payment aggregator settlements: RBI requires payment aggregators to settle funds to merchants within T+1 or T+2 depending on transaction type. Daily reconciliation confirms settlement is on schedule.
- E-commerce revenue: Daily matching of order revenue to gateway settlements prevents revenue leakage from refund processing errors or MDR miscalculation.
The Cost of Daily
Daily reconciliation is more expensive — primarily in technology and process overhead:
| Cost component | Monthly | Daily |
|---|---|---|
| Data ingestion | Manual file download, once/month | Automated API or SFTP, daily |
| Matching engine compute | One batch/month | Daily batch (365 runs/year) |
| Exception reviewer time | 2–3 days focused effort | 30–60 min daily review |
| Tooling requirement | Spreadsheet viable at low volume | Requires purpose-built engine |
The technology cost of daily reconciliation is fixed (software subscription), while the cost of monthly reconciliation is variable (staff time grows with transaction volume). At scale, daily reconciliation is consistently cheaper.
When Monthly Is Sufficient
Monthly reconciliation remains viable when all of the following are true:
- Monthly transactions below 800 across all types
- No NACH, EMI, or mandate-based collections
- No marketplace or platform settlement activity
- TDS deductors fewer than 15
- GST turnover below ₹3 crore
Below these thresholds, the error rate from monthly matching is low enough that the staff cost of daily matching exceeds the cost of occasional exceptions.
Industry-Specific Frequency Recommendations
| Industry | Bank | TDS | GST (GSTR-2B) | Platform settlements | NACH |
|---|---|---|---|---|---|
| NBFC | Daily | Weekly | Monthly | N/A | Daily |
| E-commerce | Daily | Monthly | Monthly | Daily | N/A |
| Healthcare | Weekly | Monthly | Monthly | Weekly (TPA) | Weekly (NACH EMI) |
| IT Services | Monthly | Monthly | Monthly | N/A | N/A |
| Real estate | Weekly | Monthly | Monthly | N/A | N/A |
| Payment aggregator | Daily | Daily | Monthly | Daily | Daily |
Hybrid Approach: High-Value Daily, Low-Value Monthly
The practical middle ground for mid-size companies: apply daily matching to bank and platform settlements (where errors compound fastest), weekly matching to TDS receivable (Form 26AS updates with a 3–7 day lag anyway), and monthly matching to GSTR-2B (only available on the 14th).
This hybrid approach captures 80% of the error-detection benefit of daily reconciliation at 40% of the operational overhead.
Moving from Monthly to Daily Incrementally
The transition works best in three phases:
Phase 1 (Weeks 1–2): Automate bank statement ingestion via API or SFTP. Run daily bank vs cash book matching automatically — this is the quickest win and requires no process change beyond the tool configuration.
Phase 2 (Weeks 3–4): Add platform settlement matching. Configure gateway settlement file ingestion and match daily to order data. Exception queue feeds the finance team each morning.
Phase 3 (Month 2): Add exception SLAs — each exception type has a named resolver and a resolution deadline. The daily reconciliation becomes self-managing.
Bank reconciliation software with API-based bank statement ingestion makes Phase 1 achievable in under a week for most Indian banking relationships (HDFC, ICICI, Kotak, SBI all support MT940 or bank API formats).
Reconciliation software India that handles bank, platform settlements, and TDS in a single engine enables the full hybrid approach without managing three separate tools.
The Reserve Bank of India publishes settlement frequency requirements for payment aggregators and NBFCs — the regulatory floor that determines whether daily reconciliation is operationally required for specific entity types.