Why Your Month-End Close Still Takes 10 Days (And What Actually Fixes It)
A day-by-day breakdown of a 10-day close at a ₹500Cr company. Where the time goes — and the structural fix.
At a ₹500Cr company, month-end close runs 10 days. Not because the team is slow — because the work it does in those 10 days is mostly chasing, not analysis.
Where the time actually goes
Days 1–2: Cash app pile-up. Payments that landed in the last week of the previous month sit unmatched. The AR team works backward from the bank statement, matching receipts to invoices. Anything ambiguous — wrong customer ID, partial pay, TDS deduction — gets a sticky note for tomorrow.
Days 3–4: TDS reconciliation. Customers deducted TDS when they paid. The team has to reconcile what was deducted with what appears in Form 26AS. Mismatches are common — wrong section, wrong rate, wrong PAN. Each one needs follow-up.
Days 5–6: Scheme deductions. FMCG distributors and channel partners net off scheme claims, trade discounts, and quality adjustments. The team has to validate each one against approved scheme records. Unapproved deductions need owner assignment.
Days 7–8: Suspense account triage. The amount sitting in suspense has been growing every month. Some of it is unmatched cash. Some of it is cleared deductions waiting for journal entry. Some of it is genuine reconciliation gaps from prior months that no one has time to investigate.
Day 9: Reconciliation review. Senior finance reviews the working files. Catches mistakes. Sends them back. Junior team re-runs.
Day 10: Board pack assembly. Numbers get pulled into slides. Caveats get drafted. Questions get pre-empted.
The structural fix
No amount of "working faster" closes the gap, because the work is inherently sequential — and most of it is reactive: chase the deduction, wait for the customer, then post the journal.
The fix is structural: do the execution work continuously, not at month-end. Match cash daily. Reconcile TDS section-by-section as it occurs. Surface scheme mismatches the day they hit. Resolve the suspense account every Friday, not every quarter.
Done that way, month-end becomes a verification event, not an execution one. The numbers are already right. The close is a sign-off, not a sprint.
This post is a brief — the full version (1,000–1,200 words, with India TDS specifics and worked examples) will be published shortly.