Closing the month took 11 working days at a 200-person food producer with three production sites. The plant controller described it as “two weeks of hunting.” The interesting part is not that they got it to 3 days. It is where the 11 days were actually going.
Where the 11 days went
We logged every task for one close. Day one through three were waiting for data, not working on it. Confirmed production quantities came from paper batch sheets that a supervisor collected on Fridays. Warehouse movements were reconciled separately and did not match production.
Days four through seven were reconciling inventory. Perishable goods made this worse, because waste and rework had to be estimated from memory when the paperwork was thin. Days eight through nine were margin review. Days ten and eleven were rework caused by everything upstream.
So roughly 6 of the 11 days were spent fixing or waiting, not analyzing anything. The close was slow because the data arrived late and wrong, not because the accounting team was slow.
The three blockers nobody put on the project plan
The first blocker was batch sheets. Production recorded quantities on paper and entered them into a system days later, so inventory and output told different stories. Moving recording to a station terminal at the end of each shift fixed this in about five weeks.
The second was waste. Nobody wanted to record it, because recording waste looks like a personal failure. We made it a field with a reason code, reviewed it weekly by shift instead of by person, and the resistence disappeared once it stopped feeling like blame.
The third was cut-off discipline. A shipment loaded at 6 p.m. on the last day of the month might be recorded on the 1st. Setting a hard daily cut-off at 4 p.m. for stock movements, with late items going to the next day, removed a fight that had lasted years.
What the close looks like now
The sequence changed more than the speed. Here is the pattern that worked:
- Production and waste recorded per shift, every day, at the station terminal.
- A five-minute daily check by the plant controller: any negative stock, any variance over 3%, any missing reason code.
- Inventory accuracy verified weekly by counting 30 high-value items, so month end holds no surprises.
- Month-end tasks started on day one because the data was already there, not gathered.
Day three now produces a reviewed margin report by product line. The controller’s team spends its time asking why cheese yields dropped 2% in week three, instead of chasing batch sheets from week one.
ERPNext Consulting worked with the operations and finance leads on those three blockers, and the honest finding was that only about 20% of the effort was configuration. The rest was agreeing that waste gets recorded even when it looks bad, and that a 4 p.m. cut-off applies to everyone, including the sales director.
If your close runs past 7 days, do not start with the accounting process. Time your data. Ask when the production number is first written down, and where it travels before it becomes a journal entry. The close ends when the data arrives, and that date is set on the shop floor.