Close Lag Continues: The Real Reason Your Finance Teams Are Still Slow to Close, and a Fix That Works
It's a few days after the month-end and the numbers still aren't final. Someone's still chasing a reconciliation that should have closed weeks ago. Reports go out, but finance is quietly still adjusting prior-period entries to make this month's numbers make sense.
Sound familiar?
While not-for-profit and education organisations sit in different sectors, ask either how month-end is going and you'll hear the same two answers: not enough resources, and a finance function that never quite catches up.
There's some truth to that. We've seen finance teams work hard, maintaining budgets, running reports within their ERP, and chasing invoices, often all at once. But the reality is the real cause of month-end delay is different: no planned structure, and no clear ownership for each task.
Together, that's what delays month-end, and what carries the delay into the next one.
This is close lag. Most finance teams are living with it long before anyone gives it a name.
In our experience working closely with NFP and education finance teams, we believe that 95% of month-end close tasks are repetitive. The gap shows up when there's no documentation, and the same manual process gets repeated on systems that were never built to carry it.
Most finance teams are missing that operational structure entirely. So what should they actually be measuring instead?
What are finance teams actually measuring when it comes to month-end close?
That's a question most finance teams haven't unpacked.
Imagine a clearly defined metric that shows exactly how many days your month-end close takes. Now imagine the metric that matters most sitting right next to it: what's actually causing those extra days?
That question gets neglected because most finance teams haven't defined what "close" actually means for them. The last date on the calendar might be the date they claim to close. The real date can bleed well into the following weeks of the new month, simply because no one has codified what the measure is, let alone tracked it.
Without that tracking in place, three things happen:
The close flows into the new month
No documentation exists, so people move into panic mode
Close lag becomes the problem finance is solving, instead of the growth and strategy work they should be doing
Fixing that starts with a single step: defining the number itself.
Where should finance teams start?
Define close lag.
Say it out loud. Describe exactly what it means inside your organisation.
It's the last transaction you record that relates to the month you're closing, one that doesn't spill into the new month. So ask: what date did that transaction happen?
For example: if you're closing November and the last transaction you record for that period is dated 12 December, and you lock the accounts on 12 December, then 12 December is your close date.
That's the lag.
Once you have the definition, the next step is turning it into a number you can track.
How can you calculate your close lag, step-by-step?
After speaking with our team of experts, we've found a set of simple but effective questions that can prepare you to measure your close lag, and find real ways to reduce your month-end process.
1. What is your average close date?
The first step is to take a close look at your finance system over the past six months.
Record the date you closed month-end for each of those months. This makes it easy to track your average close date, and whether that date is consistent month to month.
From this, ask the obvious question: what is your average close date? This is your starting point.
If you find your average close takes 15 days, the natural next step is to look at your transactions. When were they recorded, and which types arrived later than expected?
You might find, for example, that the last transactions recorded each month are revenue recognition entries or overhead allocations. That tells you exactly where the delay is coming from.
2. Is your close dragging because of the wrong systems?
Knowing which transactions run late points to a second question: why do they run late in the first place?
Often it comes down to a system that isn't built to capture information quickly, or structured to support a continuous close. The result is manual intervention, usually in Excel or other side systems. That manual work is what holds the close open, and drags the end-of-month process out to more and more days.
Once a team identifies which tasks are running late, the real question becomes: can any of this be done earlier, during the previous month, instead of after it ends? If those tasks are already done by the time the month closes, the close happens sooner.
3. Are you sure your close date is honest?
Even with a system fix underway, one trap remains: measuring the wrong thing entirely.
A close date can look good on paper and still be wrong. The trap is measuring the day the report was published, or the day the board pack went out, rather than the day the last transaction was actually posted. A team can hit their reporting deadline every month and still be quietly adjusting the prior period weeks later.
So check your own number against the definition from earlier. Not when the numbers were sent. When the ledger for that period actually stopped moving.
Do this monthly, not once. A close lag measured once is a snapshot. Measured every month, it becomes a trend, and trends are what tell you whether you're actually improving or just getting used to the delay.
Once you know your own number, the next question is what it should be compared against.
What does a genuinely good close look like for complex organisations?
A good close isn't hard to define. If your organisation struggles to describe what one looks like, that's a sign your finance function needs a closer look.
A genuinely good close starts with the right data entering the finance system at a granular level, from the very beginning.
Take schools as an example.
Finance teams capture each revenue transaction with enough detail to know who the customer is, which student it belongs to, what the transaction relates to, which campus it applies to, and which revenue stream it should be recognised against.
Once that data is captured at that level, the reporting workflow is already set up. The system generates the reports you need without anyone having to step outside it, or fall back on Excel.
But the close process doesn't end there.
What's a realistic range for getting to a good close?
Most organisations come to us with month-end dragging past 10 days, often well beyond it. From there, the goal isn't a single fix. It's a steady reduction, month over month, until close lag stops being something the team has to think about at all.
Most finance teams accept stress and pressure at month-end as simply part of the job, something they've lived with for their entire career. But it doesn't have to be that way, and that acceptance is the first thing to challenge.
Once you accept that, the next step is straightforward: move from a reactive, stressful close to a proactive, continuous one.
Realistically, if your month-end doesn't bleed into the new month, and can be finalised within the same month it belongs to, you're on the road to eliminating end-of-month close altogether.
Each funding stream that needs separate tracking gets its own place in the ledger. Whether that is a school building fund, scholarship fund, specific capital grant, or tied donation, with the structure reflecting the conditions and reporting requirements attached to it. Because education finance is so often analysed by campus, faculty, or program, this is also where the dimensional structure is set: so a report by campus or program is a view that already exists, not one rebuilt each time it is requested.
Is a slow month-end an effort problem or a design problem?
It's both, and the two aren't equal in weight.
The system has to be designed first. No amount of effort fixes a process that was never built to close quickly. But design alone isn't enough either. The finance team needs to be comfortable with the new design, trained on it, and given time to build the habit of using it well.
Good systems only work when the team adopts the habits that go with them. That's why it's both: design creates the possibility, and discipline makes it happen.
Where does your close lag actually stand?
You've seen how close lag is measured, what a realistic range looks like, and why closing it is a design problem before it's an effort problem. The next step is finding out where your own organisation sits.
Take our Close Lag Self-Assessment. In a few minutes, you'll see how your close compares to other NFP and education finance teams, and where the design gaps are most likely sitting in your process.