Month-End Is Broken. Here's Why Your Close Keeps Taking 10+ Days.
Month-End Is Broken. Here's Why Your Close Keeps Taking 10+ Days.
Labels: Finance Operations
Every finance professional knows the feeling. The last day of the month arrives, and instead of wrapping up, the real work begins. The next two weeks — sometimes three — are consumed by chasing figures, resolving discrepancies, rebuilding reports from scratch, and somehow producing a management reporting pack that management needed "last Tuesday."
The uncomfortable truth is that a 10-to-15-day close is not normal. It is a symptom. And the most expensive thing finance teams do is accept it as inevitable.
Over a career spanning more than 20 years across NFP, NDIS, aged care and SME organisations, I've walked into a lot of month-end closes. Some were running beautifully — day four, everything locked, management reporting pack ready for review. Others were still unravelling on day twelve with reconciliations outstanding and journals flying around in email chains. The difference was rarely the quality of the people. It was almost always the design of the process.
Here's what actually causes a slow close — and how to start diagnosing where your breakdown is.
|
8–12 days
Typical month-end close time for organisations without a structured close process — often longer in multi-entity environments.
|
3–5 days
What a well-designed close process can consistently achieve — same data, same complexity, fundamentally different process design.
|
The Myth: It's a People Problem
When a month-end close runs long, the instinct is to look at capacity — not enough staff, too much volume, people are slow. Sometimes that's a factor. But in most organisations I've observed, the constraint isn't the number of people available. It's the structure they're working within.
Finance teams often inherit close processes that were designed by someone who no longer works there, built around a system that's since been replaced, or simply accumulated over time without anyone ever stepping back to ask whether the sequence made sense. The result is a process that works — technically — but burns far more time than it should, creates bottlenecks at predictable points each month, and leaves the team exhausted before the reporting cycle has even started.
Hiring more people to do a broken process faster is not a solution. It's an escalation of the problem.
The Five Real Causes
1. Upstream data arrives late
The most consistent cause of a slow close is that the finance team is waiting on information controlled by someone else. Payroll figures that aren't confirmed until day five. Purchase orders from operations that land on day seven. Revenue data from a business system that requires a manual extract — run by someone who is usually busy. When the close process is built on the assumption that data will be available on day one, and it consistently isn't, every subsequent step is pushed back by the same lag.
The fix requires going upstream — not downstream. It means agreeing cut-off deadlines with operational teams, building those deadlines into their workflows (not just finance's), and making the consequence of late data visible to whoever owns it. This is a conversation finance often avoids because it feels like confrontation. But soft agreements that aren't enforced are not agreements.
2. Reconciliations happen at month-end instead of throughout
A reconciliation that takes three hours at month-end can often be reduced to thirty minutes if done continuously — because the volume of discrepancies is smaller and the trail is fresher. Organisations that treat reconciliation as a month-end task concentrate all the exception-handling work into the same two-week window where everything else is already under pressure.
Moving even a subset of reconciliations to a weekly or rolling cadence — bank recs, high-volume accounts, intercompany — changes the shape of month-end dramatically. The principle is the same one that makes progressive filing easier than EOFY scrambling: smaller, consistent effort beats a single large effort under time pressure every time.
3. Journal entries have no clear ownership or deadline
In most organisations, journal entry preparation is distributed. Accruals sit with one team member, prepayments with another, depreciation runs from a system, payroll allocation gets done by someone who's also responsible for three other close tasks. When there's no sequenced journal entry schedule — with individual ownership and a completion deadline — the close waits on whoever is slowest that month.
A journal entry schedule isn't complicated to build. It's a list: entry type, preparer, reviewer, due date within the close cycle. That structure alone removes significant ambiguity and makes it obvious, early in the close, whether the process is on track or slipping.
4. The management reporting pack design causes rework
The close isn't finished when the numbers lock. It's finished when the pack is out. Finance teams that produce the same format they've always used — regardless of what management actually needs — end up revising it two or three times post-distribution. If the management reporting pack design is inefficient, the close is inefficient.
A well-designed pack template — one agreed with the people who receive it — pays back at every subsequent close. The best packs tell a clear story with minimal formatting effort because the structure does the work, not the presenter.
5. Approval bottlenecks aren't managed
In organisations with appropriate authorisation frameworks, journals and reports need sign-off before the close is complete. If the approval pathway isn't structured — if it relies on whoever happens to be available checking their inbox at the right time — it becomes a single point of failure. A CFO who is in meetings for three days during close week, or a Finance Manager who's travelling, can hold up the entire close simply because no one built a backup into the process.
Approval workflows need to be explicit: who approves what, in what sequence, with what turnaround expectation, and who is the delegate when the primary approver is unavailable. This is administrative detail that close processes consistently overlook.
The Hidden Cost of Getting This Wrong
A slow close isn't just a finance team problem. It's an organisation problem with a price tag. When the management reporting pack arrives on day twelve instead of day five, management has been making decisions for a week without an accurate financial picture. In a cash-constrained NFP or NDIS organisation, that lag has real consequences — capital decisions made on gut feel, cost overruns undetected for an extra fortnight, budget conversations anchored to stale data.
There's also a people cost. Finance teams that operate in a state of monthly crisis tend to have high turnover. The analytical work that creates genuine value — variance investigation, scenario modelling, business partnering — doesn't get done because the team is too busy closing the books. A well-run close is a prerequisite for a finance function that does the job it's supposed to do.
A Diagnostic: Five Questions Worth Asking This Month
🔍 Close Process Self-Audit
- When does data actually arrive? Map every upstream data source and the realistic day it lands. If it's consistently day four or five, your close cannot start before then — regardless of what the schedule says.
- Which reconciliations are done at month-end that could be done weekly? Bank recs and high-volume transactional accounts are the usual candidates. Moving even two or three to a weekly cadence changes the month-end load.
- Is there a written journal entry schedule with named owners and deadlines? If it lives in someone's head, it's not a process — it's a dependency on one person.
- How many times does the management reporting pack get revised before it's finalised? More than once is a signal that either the format or the narrative process needs redesigning.
- What stopped the close last month? Be specific. Not "it was busy" — what specifically was outstanding on day seven that wasn't on day three? That's where the bottleneck lives.
The answers to those five questions will tell you more about where your close is losing time than any benchmarking report. Most close breakdowns are visible when you look at them clearly — they're just not looked at clearly very often because the team is too busy closing the books to stop and examine the process.
Is Your Close Cycle Running Longer Than It Should?
PFL works with finance leaders to map, diagnose and redesign month-end close processes — cutting cycle times and freeing up team capacity for analysis work. If your close is consistently running past day seven, it's worth a conversation.
Talk to PFL →
Comments
Post a Comment