Advertisement /206696744/dsx/crmroute_top_over_banner · 970×90
CRM Route
Advertisement /206696744/dsx/crmroute_top_below_banner · 728×90

Shortening the Month-End Close Without Cutting Corners

A ten-day close is rarely caused by hard accounting. It's caused by waiting — for a bank feed, a stock count, an approval nobody chased.

Shortening the Month-End Close Without Cutting Corners

Ask a finance team why the close takes nine days and the answer is usually a list of things they are waiting for. Very little of the elapsed time is spent on judgement; most of it is queueing. That makes the close a scheduling problem more than an accounting one, which is good news, because scheduling problems are tractable.

Map the dependencies before optimising

Write out every task, its owner, its inputs, and how long it actually takes. The critical path is almost always shorter than the close, and the gap is queueing time. Attack the gap first — it is free — before trying to make anyone work faster.

Move work before the period end

A surprising amount of the close does not depend on the last day of the month.

• Reconcile bank, control and clearing accounts weekly, not at close.

• Review and clear the suspense account continuously — it is where unexplained items go to be forgotten.

• Chase supplier invoices and timesheets during the month.

• Prepare recurring journals, prepayment and depreciation schedules in advance.

• Agree intercompany balances mid-month, when both sides have time to argue.

Advertisement /206696744/dsx/crmroute_scroll_in_articles · 300×250

Intercompany disputes take days because both parties are busy. Raise them on the fifteenth and they take an hour.

Use materiality deliberately

Set a threshold below which an unreconciled difference is written off rather than investigated, document it, and apply it consistently. Chasing an immaterial variance for two days is not diligence, it is a cost. Reserve the investigation capacity for differences that could matter and for anything that recurs — a small difference appearing every month is a process defect regardless of its size.

Close in a fixed order, with a hard cutoff

Publish a calendar with sub-ledger cutoffs and stick to them. A late invoice accrues into the current period and posts in the next; it does not reopen a closed sub-ledger. One exception per quarter is manageable, and one exception per month means there is no cutoff.

Report the flux with the numbers

The review step is faster when the variance analysis arrives with the trial balance rather than being requested afterwards. Automated comparison against prior month, prior year and budget, with a threshold for what needs a written explanation, turns the reviewer's job from finding the movements into judging the ones that were found.

Retrospective every month

Thirty minutes after each close, with the whole team, on one question: what did we wait for? Note it, assign it, and check it next month. Two or three cycles of this reliably takes days off a close, because the same three bottlenecks come up every time and nobody had previously been made responsible for removing them.

Discussion (3)

You
JW
Janet W. Aug 20, 2026

Raising intercompany on the fifteenth is the single best idea here. Both sides have time to actually look, and the dispute takes an hour instead of consuming days three and four of the close.

OM
Oscar M. Aug 23, 2026

We went from eleven days to six almost entirely on the 'what did we wait for' retrospective. Same three bottlenecks came up for two months until someone owned them.

DR
Deepa R. Aug 29, 2026

Careful with the materiality write-off threshold though. Ours was set once and never revisited, and as the company grew it quietly became large enough to hide a real problem for two quarters.

Ready for more?

Subscribe