Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
Most broken reconciliation processes are not obvious — they work well enough to prevent a crisis but not well enough to prevent the slow accumulation of errors, missed credits, and audit observations that compound over time.
The ten signs below are ranked from the most visible to the most subtle.
Sign 1: Month-End Close Takes More Than 5 Days
For a mid-size Indian company (₹50–200 crore turnover), the month-end close cycle — bank reconciliation, TDS matching, GSTR-2B vs purchase register, platform settlement verification — should complete in 3–5 working days. A close cycle consistently exceeding 7 days means the matching phase is manual, and the team is spending most of that time on data manipulation rather than exception resolution.
Sign 2: Frequent Audit Qualifications
If the statutory auditor raises reconciliation-related observations in two or more consecutive years, the reconciliation process is not improving. Common audit observations that signal a broken process: bank reconciliation statements not prepared for all accounts, TDS receivable not reconciled to Form 26AS, and accounts receivable with no counterparty confirmation above the materiality threshold.
Sign 3: Regular GST Notices
GSTR-2B mismatch notices are triggered automatically by GSTN when ITC claimed in GSTR-3B exceeds what appears in GSTR-2B. Receiving more than 2 such notices per financial year is a clear indicator that GSTR-2B vs purchase register reconciliation is not happening before GSTR-3B filing.
| Warning sign | Indicates | Root cause |
|---|---|---|
| Month-end close >7 days | Manual matching overloaded | Volume has outgrown spreadsheet tools |
| Audit observations on BRS | Bank reconciliation deferred | No daily or weekly matching discipline |
| GST mismatch notices | ITC claimed before GSTR-2B check | GSTR-2B reconciliation done after filing |
| TDS demand notices | Form 26AS credits not matched | TDS receivable ledger not maintained |
| Suspense balance above ₹1L | Deferred matching | Transactions parked rather than resolved |
Sign 4: TDS Demand Notices
A TDS demand notice from the income tax department typically arises from one of two failures: TDS deducted but not deposited on time (the deductor’s failure), or TDS deducted at the wrong rate or section code. For the deductee, the equivalent problem is TDS claimed in the ITR that does not appear in Form 26AS — because the deductor made an error that was never followed up.
If your organisation receives TDS demand notices, or discovers unclaimed TDS credits during statutory audit, the TDS receivable ledger is not being reconciled against Form 26AS systematically.
Sign 5: Finance Team Working Weekends
Weekend work during month-end close is the clearest signal that transaction volume has outgrown the reconciliation process. In a manual process, reconciliation time scales linearly with transaction volume. In an automated process, it does not — matching is handled by the tool, and the team reviews exceptions only.
Signs 6–10: Advanced Dysfunction Indicators
Sign 6: Suspense account balance above ₹1 lakh persisting beyond 10 days. Transactions parked in suspense should be resolved within 5 working days. A chronic large suspense balance indicates that matching is deferred, not completed.
Sign 7: Platform settlement variances carried forward month after month. MDR deduction variances, TCS mismatches, or refund reconciliation gaps that are “carried forward” accumulate into a reconciliation backlog that auditors find in year-end procedures.
Sign 8: ITC written off without investigating GSTR-2B timing. If your organisation routinely writes off small ITC amounts without checking whether the supplier filed late, you are losing legitimate credits. A systematic GSTR-2B matching process recovers these.
Sign 9: NACH or payroll disbursements not reconciled to individual accounts. A bulk NACH credit sitting in the bank account without disaggregation to individual loan or salary records is an unresolved reconciliation item — and a potential misstatement in the accounts receivable or liability schedule.
Sign 10: No documented escalation path for exceptions. If the finance team resolves exceptions informally — by Slack message or verbal agreement — without a written trail, the process is not auditable. A functioning reconciliation process has a documented escalation path for each exception type, with resolution SLAs and approver names.
What to Do When You Identify These Signs
Signs 1–5 (visible failures) require immediate process review. The practical starting point is mapping the current manual steps and identifying where time is actually spent — usually the matching phase, not the exception review.
Signs 6–10 (accumulated dysfunction) require a structured backlog elimination alongside a new matching process. Addressing the backlog without changing the process produces the same dysfunction within 3–6 months.
Reconciliation software India that automates the matching phase eliminates Signs 1, 5, 6, and 9 directly. Signs 2, 3, 4, 7, and 8 are prevented by systematic GSTR-2B, TDS, and platform settlement matching that runs before filing deadlines — not after.
Bank reconciliation software eliminates the specific signs related to deferred bank matching and suspense account accumulation.
The GST portal publishes the GSTR-2B reconciliation requirements and the timeline for responding to mismatch notices — useful when assessing whether Signs 3 and 7 require an immediate notice response.