The Close Cycle Has a Map. Nobody's Drawn It
Manufacturers can usually tell you, to the day, how long month-end close takes.Almost none can tell you, to the step, where it actually gets stuck and that gapis why the same close problems survive every new tool a finance team buys.
Ask a controller how long close takes and the answer arrives instantly, to the day. Ask where it gets stuck and the answer gets vague fast “spreadsheets,” someone says, or “the plants are slow.” Nobody has actually walked the calendar step by step. That's not a knowledge gap. It's the reason close stays slow even after a company buys new software.
Where Manufacturing Closes Break
Five patterns explain most of it, and they tend to show up in the same order every time:
- Consolidation by spreadsheet. Multi-entity eliminations combining several legal entities' books
into one group result rebuilt by hand, every month, by whoever remembers how it worked last
time.
- Two sets of books, one deadline. Many Indian manufacturers with global parents or investors
report under both Ind AS India's local accounting standard) and US GAAP (the standard most US
linked parents and lenders require). Running both in parallel doubles the adjustment work instead of
sharing one base.
- The slowest plant sets the pace. Inventory and cost-of-goods-sold COGS reconciliation waits on
plant-level data that isn't late by policy just late by habit.
Provisions nobody owns. Accrual logic living in a spreadsheet built by someone who left the
company two closes ago.
- Mismatches that surface too late. Accounts payable and receivable sub-ledger gaps discovered
during close, because nothing checks them before it