Month-End Close Shouldn't Take Two Weeks. Here's Why It Does.

The dirty inventory of a slow close: waiting on AP to confirm outstanding bills, chasing intercompany eliminations across entities, reconciling the billing system to the GL, posting accruals for things the system didn’t capture automatically, and investigating the three items that don’t tie and never obviously explain themselves. Every one of those steps exists because the system didn’t enforce something it should have at transaction time.

The average month-end close in mid-market companies takes six to ten business days.¹ In practice, this means that companies are regularly making decisions in the first week of the month without accurate prior-month financials. It means the board doesn’t see results until the second or third week. It means the finance team spends the first half of every month in close mode, unable to give full attention to anything else.

Most CFOs accept this as a given. It doesn’t have to be.

The anatomy of a slow close

The steps that extend the close aren’t random. They fall into recognizable patterns that trace back to specific architectural decisions about how the systems are built.

Intercompany reconciliation takes time because the entities maintain separate books that need to be reconciled against each other before eliminations can be posted. If the books aren’t separate — if intercompany transactions are tagged rather than independently maintained — this step doesn’t exist.

Subledger-to-GL reconciliation takes time because the AR subledger and the AP subledger need to agree with the corresponding GL accounts before the books can be closed. If the subledgers are views of the GL rather than independent sources, this step doesn’t exist either.

Billing system reconciliation takes time because the invoices generated in the billing system need to match the revenue and AR entries in the GL. If the billing system posts directly to the GL rather than syncing to it, this step becomes a completeness check rather than a reconciliation exercise.

Accruals take time because the system doesn’t capture them automatically. An expense incurred in month X that won’t be invoiced until month Y requires a manual accrual in month X and a reversal in month Y. The volume of manual accruals is a measure of how many things the system doesn’t handle natively.

The ten-business-day target

Industry benchmarks suggest that a well-run close for a mid-market company should take four to six business days for companies with relatively simple structures, and up to eight for those with meaningful complexity — multiple entities, international operations, complex revenue recognition.² Two weeks, in most cases, is not a complexity problem. It’s a process and architecture problem.

Companies that achieve fast closes typically share a few characteristics: their systems are more tightly integrated (or genuinely unified), their transaction coding discipline is high enough that few items require reclassification at close, their accrual process is systematic rather than ad hoc, and their intercompany transactions are managed in a way that makes elimination straightforward.

The connection to system design

The close duration is a lagging indicator of system quality. A well-designed system that enforces business rules at transaction time — requiring proper account coding, requiring segment attribution, capturing accruals as they accrue rather than as they’re invoiced, maintaining intercompany balance natively — produces a close where most of the validation has already happened and the close process is confirmation, not investigation.

A poorly designed system, or a well-designed system that’s been poorly configured, produces a close where the cleanup work is concentrated at month-end because the ongoing process didn’t capture what it needed to. The close is long not because closing is hard but because the month itself left too many open questions.

The real cost

Finance teams normalize their close duration over time, and the cost of a slow close becomes invisible. The visibility it creates: for a ten-person finance team running a ten-business-day close, roughly 50% of the team’s capacity is consumed by close-related activities for half of every month. That’s 25% of the team’s annual capacity going to a process that a better-architected system could reduce by half or more. The opportunity cost — the analysis, forecasting, and business partnering that doesn’t happen because the close is consuming the bandwidth — is real and significant.

Sources