Introducing Continuous Close: The End of Month-End

For as long as accounting software has existed, closing the books has worked the same way. You spend the month collecting transactions. Then, when the month ends, you run a sequence of batch processes -- amortization, allocation, accruals, reconciliation, flux analysis -- one step at a time, in order, until the books are closed. This is called a periodic close, and it has been the standard for 50 years.

It is also, increasingly, the biggest bottleneck in modern finance.

What is continuous close?

Continuous close is an accounting operating model where the general ledger is kept accurate, complete, and reviewable at all times -- not just at month-end. Instead of batching work into a stressful close window, accounting activities happen continuously:

• Transactions are recorded as they occur
• Accounting rules and controls are enforced at entry
• Reconciliations and validations run in real time
• Issues surface immediately

There is still review, judgment, and oversight -- just without waiting for month-end.

Why periodic close made sense -- and why it no longer does

The periodic close was not a bad idea. It was a rational response to the limitations of early computing. Running batch processes was expensive and slow, so you batched everything together and ran it once a month. The system was designed around what the technology could support.

That technology is not a constraint anymore.

But the accounting systems most finance teams rely on today -- NetSuite, Sage, Workday -- were built when it was. Their core architecture is sequential: transactions are stored, and processing happens in scheduled batches. That fundamental design has not changed in 15 or 20 years, even as everything around it has.

The result is a persistent data lag that touches every part of the finance function. Leaders make decisions on numbers that are 30 days old. Finance teams spend the best weeks of every month just trying to close, rather than doing the work that requires their actual judgment.

What continuous close looks like in practice

The clearest way to see the difference is to follow a single transaction through both systems.

In a periodic close system, a bill comes in and syncs to the ERP. It sits there. At month-end, the batch runs: amortization first, then allocation, then accruals, then reconciliation, then flux. Each step processes everything that accumulated during the month, in sequence. Until that batch runs, none of the downstream calculations exist.

In a continuous close system, the same bill arrives and every downstream calculation runs immediately. Amortization is posted. Allocation is applied. The reconciliation updates. Flux reflects the new transaction. By the time the next bill arrives, the previous one is already fully closed.

Multiply that across every transaction in a month and the difference is not incremental. The work of closing is distributed across every day of the month instead of compressed into the final days. Month-end becomes a confirmation, not a crisis.

The impact goes beyond a faster close

A faster close is the obvious benefit. It is not the most interesting one.

When transactions are processed in real time, finance teams can answer questions the same day they are asked instead of after the next close cycle. Anomalies get caught when they are small, before they have compounded. The books reflect what is actually happening in the business right now, not what happened 30 days ago.

Periodic close was the best accounting could do with the technology available at the time. Continuous close is what accounting looks like when the infrastructure finally catches up.

Next week we'll get into what the old architecture is actually costing you -- and why the pain shows up in places most finance teams aren't looking.