Twelve-day closes are usually not a staffing problem. A $45 million manufacturer I worked with had five people in finance, and three of them lost the first weekend of every month to the close. When we asked what would happen if the close took four days, the controller laughed. Then she started listing reasons it couldn’t.
We wrote the reasons on a whiteboard. There were seven. Six of them were self-inflicted.
The four things eating the calendar
We tracked where the hours actually went during one full close, and the picture was lopsided.
- Waiting on inventory. The warehouse counted every month-end and delivered numbers on day three, so finance sat on its hands for 60 hours.
- Freight invoices arriving after cutoff. About 300 invoices a month landed with dates from the previous period, and each one meant a manual adjustment.
- Nine spreadsheets reconciled by hand. Each took two to three hours, and at least one had a broken formula nobody had noticed.
- Approvals sitting in inboxes. Expense and journal approvals averaged 2.4 days to come back.
Only one item on that list was a real constraint — the physical count. The other three were habits.
Start with the last three days, not the first
Most teams try to speed up the beginning of the close. That’s the wrong end. The last three days are where the rework lives, and rework is where the time goes.
- Move the physical count off month-end. Count the highest-value items weekly all month so the month-end figure is a confirmation, not a discovery.
- Set a hard cutoff for freight and receiving documents at 5 pm on the last business day. Anything later goes to the next period and gets disclosed, not adjusted.
- Replace one spreadsheet at a time. Pick the worst one, rebuild it inside the system, and run both for one close before you retire the old file.
- Give approvers a fixed 15-minute window every morning. Everything above $5,000 clears in one sitting.
This is the kind of work where ERP Consulting pays for itself in weeks rather than years, because someone has to sit with the controller and argue about the cutoff rule until it sticks.
What the team got back
By the fourth close they were done in four and a half days. By the sixth, four. Nobody was hired, and nobody worked a weekend.
The bigger win wasn’t the calendar. It was that the numbers arrived while they still mattered. Sales could see month-to-date margin on day five instead of day thirteen, and the owner stopped making pricing decisions on nine-day-old data.
One useful ERP Consulting rule of thumb: never automate something you haven’t simplified first. Every hour spent deleting a step is worth three hours of configuration.
If your close runs past eight days, do this before you change anything else. For one month, have everyone log what they were waiting on, in 30-minute blocks. The answer is almost always waiting, not working — and waiting is fixable.