FinanceHQ at "MeshCo" · 4-person team · post-ERP rollout

Before ERP: 11 working days from month-end to MIS sign-off. Days 1-5 collecting data from 5 Tally companies + 14 Excel sheets. Days 6-8 reconciliations. Days 9-10 management adjustments. Day 11 print + sign + send.

After ERP (6 months post-go-live): 3 working days. Day 1: cut-off + accruals. Day 2: depreciation + close. Day 3: review + MIS delivery. Same team. Same accuracy. 73% less time. The CFO now spends the recovered week on FP&A and strategic finance.

This is the rhythm you're trying to build. Here's the 10-step monthly checklist that gets you there.

🪙 In 60 seconds
  • Two flavours of "close": soft close (mid-month or quick-cut, ~24 hours, used for monthly MIS) and hard close (quarter / year-end, full reconciliation + audit pack, ~3-5 days).
  • The 10 typical steps: (1) sales cut-off, (2) purchase cut-off, (3) inventory count / movement, (4) bank reconciliation, (5) accruals + prepayments, (6) depreciation + amortisation, (7) inter-company elimination (if multi-entity), (8) tax provisions (income tax + GST), (9) trial balance freeze, (10) MIS / management reports.
  • ERP doesn't eliminate the work; it eliminates the data-gathering and manual journal phases. The judgment work — accrual estimates, provision sizing, reclassification — stays human.
  • "₹100 mismatch" hunts are almost always: (a) timing differences (entry in one period, posting in another), (b) cut-off mistakes (March 31 invoice booked in April), (c) rounding in multi-currency / inter-branch transactions. Rarely fraud.
  • A 3-day close at scale requires: clean masters, disciplined day-to-day journal entries, integrated bank feeds, scheduled depreciation runs, and a finance team that knows the system. None of those are automatic.

The 10-step monthly close checklist

1
Sales cut-off

All invoices for the closing month must be raised + posted before close. Pending dispatches → invoice on cut-off date; partial deliveries → revenue recognition per Ind AS 115. In ERP: "post all unposted shipments" runs through Sales module. Should be ~30 mins.

2
Purchase cut-off

All GRN-received items must have a matching purchase invoice posted; GR/IR (Goods Received / Invoice Received) clearing account should be near-zero. Pending vendor invoices → accrual JV with "provision for purchases" account.

3
Inventory count / movement reconciliation

System stock vs physical stock. In ERP with WMS integration: daily auto-reconcile, monthly review of variances > threshold. In Tally + Excel: manual count, manual adjustment. This step alone often drives 4-6 days of the old workflow.

4
Bank reconciliation

Bank statement vs ledger. In modern ERP: bank feed auto-imports; only un-matched transactions surface for review. Should be 30 mins per account. Without auto-feed: 2-4 hours per account.

5
Accruals + prepayments

Salary accrual (last days of month, paid next month), audit fee accrual, electricity bill accrual, rent prepayment amortisation. Recurring accruals can be templated as "recurring journal" in ERP — run once a month.

6
Depreciation + amortisation

Run depreciation per block of assets (Income Tax block) + per WDV/SLM per asset (Companies Act). ERP modules automate via the fixed-asset register; one-click run. Without ERP: spreadsheet maintained by junior accountant, occasional errors.

7
Inter-company elimination

If you have multiple legal entities sharing transactions (e.g., parent-subsidiary). Eliminate inter-co sales / purchases / loans / receivables. ERP with consolidation: auto-eliminates. Without: manual schedule.

8
Tax provisions

GST: GSTR-1 + GSTR-3B reconciled with books, tax payable computed, ITC blocked-credit reversal applied. Income tax: quarterly advance tax provision, deferred tax adjustment. Without ERP: tedious Excel; with: built-in tax modules.

9
Trial balance freeze

TB balances reviewed. Suspense / clearing accounts → near-zero. Inter-co accounts reconciled. Once approved, lock the period in ERP so no further postings can occur. Tally lacks this: post-close adjustments leak in unnoticed.

10
MIS / management reports

P&L by branch / product / customer, balance sheet, cash flow summary, key ratios. ERP: dashboard refreshes auto. Without: Excel pivot tables, often outdated by the time CFO sees them.

Soft close vs hard close

Soft close

Monthly, fast

Most adjustments. Best-estimate accruals. Bank reconciled, inventory variances logged but not necessarily resolved. Aim: 2-4 days from month-end. MIS-grade. Inputs to next month's planning.

Hard close

Quarterly + yearly

All reconciliations resolved to zero. Statutory audit pack ready. Tax provisions finalised. Inter-co eliminations exhaustive. Aim: 5-8 days for quarter-end; 10-15 for year-end. Audit-grade.

Most teams should target soft-close at the 2-3 day mark, hard-close at 5-7 days. Anything longer suggests structural problems — not just process problems.

What an ERP changes structurally

The ₹100 mismatch hunt

The most demoralising part of the old workflow: trial balance is off by exactly ₹100 (or some round-ish amount). The team spends 4 hours hunting. It's almost always one of three things:

  1. Cut-off timing: an invoice for March 31 booked in April. Reverse + repost in the right period.
  2. Rounding: GST / tax / multi-currency rounding causing 1-2 paise per transaction, accumulated.
  3. Suspense account leak: a JV booked to suspense and never cleared.

In ERP-led close, ₹100 mismatches usually surface within the period (auto-reconcile catches them), not at month-end. The hunt time drops from 4 hours to 20 minutes.

💡 The discipline that makes the 3-day close work

Daily journal posting (not monthly batch), daily bank reconciliation, daily inventory movement entry, daily GR/IR clearing, daily customer / vendor sub-ledger review. Most month-end pain is accumulated daily-discipline debt. ERP doesn't fix the discipline; it just makes the discipline visible. A team that doesn't post entries daily will still have an 11-day close even after the ERP rollout.

The funny historical wrinkle

Indian finance teams accept long close cycles as normal because the comparable global benchmarks are usually US-listed companies with mature SAP S/4HANA + Hyperion / Tagetik consolidation tooling. The middle-market truth: a 3-5 day soft close is achievable in mid-market Indian businesses on D365 BC / SAP B1 if the discipline is built in. Most companies hover at 7-12 days because nobody insists on faster — until a private equity investor or banking auditor does.

Quick answers

Not overkill if you have an actively managed business. The recovered 8 days = FP&A capacity = better decisions. SMEs that don't aim for fast close usually find they don't actually use the MIS until it's stale.

Common reaction. Reality: total posting work doesn't change — it's spread differently. Daily = 30 mins/day = 10 hrs/month. Batched = 10 hrs cramming into month-end. The latter is what causes the 11-day close.

No. Soft close has tolerated unreconciled items. Quarterly hard close is required for board reporting; annual hard close mandatory for statutory audit. Skipping these accumulates problems.

For micro businesses, yes. For mid-market with multiple plants / branches / project costing — no. The institutional knowledge of why an account behaves the way it does lives with insiders. Outsource accounts-payable transaction processing, not the close itself.

Soft close 3-5 days, hard close 6-8 days quarter, 10-14 days year-end. If you're well past these, look at the 10-step checklist for which step is the bottleneck.

For the ERP decision itself
When to outgrow Tally — the D365 / BC jump

When you might want help

Two situations: (1) Finance team currently at 8-15 day close, wants to shorten — process diagnostic + 90-day re-engineering. (2) Post-ERP-rollout team struggling to operationalise — embedded support to build the close rhythm.

Close cycle stuck?

Process diagnostic, re-engineering, 90-day support to get to 3-5 day close. Fixed scope.

Was this guide helpful?

👍 Yes👎 Could be better

"MeshCo" finance team is a composite illustration. Your close cycle depends on team capacity, transaction volume, and ERP maturity.