Month-end close: why it takes so long and how to fix it
Waiting three weeks for numbers you can't act on is common, while the accounting benchmark says eight days. Why both are true, and how to get the close to the 15th.
January's numbers on February 23 are accurate and almost worthless. By then you are three weeks into a month you cannot change, looking at a period you can no longer influence.
A slow close usually gets treated as an accounting inconvenience. It is a decision-making constraint. Every day the close takes is a day you are running the business on memory.
What "close time" means
Before any benchmark is useful, be clear about what is being timed, because two common definitions differ by weeks.
The accounting definition runs from the start of close procedures to the end of the adjustments and reconciliations. APQC's open-standards measure for the monthly financial close (measure 104615) puts the median at 8 days across 3,389 organizations. APQC's public listing does not state whether those are calendar or business days, so check before you compare yourself to it.
The owner's definition runs from month-end to the numbers arriving in front of the person who makes decisions with them. That span includes everything the accounting definition excludes: waiting on receipts, waiting on a statement, waiting on someone to explain a payment, and then waiting for the reporting to be assembled.
This is why an owner can be told the close takes a week and still not see numbers until the 23rd. Both statements can be true. The figure that matters to you is the second one, because it determines whether you can still act.
What causes the delay
It is rarely the bookkeeping itself. In a slow close, the accounting work is usually a small fraction of the elapsed time. The rest is waiting.
Waiting for information
Receipts that haven't been submitted. A credit card statement that arrives on the 12th. Someone on vacation who is the only person who knows what a vendor payment was for. Each of these is a small delay; together they set the floor.
Uncategorized transactions
If the month ends with 200 transactions nobody can code, the close cannot start. This compounds: the longer since the transaction, the harder it is to remember what it was.
Reconciliations left to the end
Bank, credit card, payroll clearing, merchant deposits. Done monthly in one block, they're a bottleneck. Done weekly, they're routine.
No definition of "done"
Plenty of closes stay open because nobody agreed what closed means. Without a checklist, the close ends when someone decides it feels finished.
Getting to the 15th
The 15th is roughly ten business days after month-end, depending on where the weekends fall. For most companies without unusual complexity, that target is reachable without hiring anyone. It requires moving work out of the close rather than doing the close faster.
- Reconcile weekly. The single highest-leverage change. Four small reconciliations beat one large one, and errors surface while they're still cheap to fix.
- Set a hard cut-off for expense submissions. Employee receipts in by the 3rd. Anything later lands next month. This feels harsh once and then stops being an issue.
- Automate the feeds. Bank, cards and payroll flowing in directly removes both delay and transcription error.
- Write the checklist. Every task, an owner, a due day. Unglamorous and effective: it converts the close from judgment into process.
- Accrue known costs rather than wait for the paperwork. If a vendor invoice reliably arrives on the 18th, book a reasonable estimate and true it up next month. Precision that costs a week isn't worth having.
- Separate the close from the analysis. Close the books, then explain them. Bundling the two means neither gets finished.
The cut-off and the accrual are not the same rule
Those two items look contradictory. They cover different costs.
The cut-off is for small, unpredictable, employee-submitted costs. A $90 receipt that arrives on the 9th is not worth reopening a closed period for. Push it to the following month, apply the same rule every month, and the distortion stays small and consistent.
The accrual is for costs you already know you incurred and can estimate: the contractor who bills in arrears, the utility, the software renewal. You don't need the invoice to know the expense belongs to the month. Book the estimate, reverse it when the real number lands.
The test is materiality, not timing: would the missing item change a decision, a margin you report, or a covenant calculation? If yes, accrue it, whatever the cut-off says. If no, let the cut-off handle it. Anything large and known does not get deferred to make a date: that is not a fast close, it is a wrong one.
What changes when it's fast
The obvious benefit is timeliness. The bigger one is that a fast close changes what the numbers are for.
On the 23rd, your financials are a record. By the 15th, they're an input.
When January's numbers land by February 15, you can still act on them in February. A margin slip gets caught in the quarter it happened, not the quarter after. A customer whose payments have slowed gets a call while the balance is small.
A fast close also tends to signal an accounting system that's under control. Businesses that close by the 15th rarely have surprises hiding in their balance sheet, because there's nowhere for them to hide.
Where to start
Time your last three closes on the owner's definition: elapsed days from month-end to the numbers landing in front of you, not the days your accountant spent working. If they land after the 15th, the fix is almost certainly weekly reconciliation and an expense cut-off, and you can implement both this month without spending anything.
If you'd rather have the process built for you, a Close Process Build sets up the checklist, cut-offs and reconciliation rhythm once, so the 15th holds every month after.
