The month-end close is not a law of nature. It's a batching artifact: the shape finance work takes when reconciliation, matching, and eliminations are expensive human tasks that have to be saved up and done in one push. For most multi-entity companies that push consumes the first week of every month, and everything the business learns from its numbers arrives that much later.
Agentic accounting removes the reason the batch exists.
Work the moment it appears
Agents don't save work up. A payment lands and is matched against its bill within minutes. A receipt is missing and the chase starts the same day in Slack, not three weeks later from a spreadsheet of exceptions. An intercompany transaction posts and its elimination is drafted immediately. Reconciliations run continuously against live bank feeds instead of once, heroically, at month end.
Each task is small. That's the point. The close was only ever a mountain because thirty days of small tasks were left to accumulate.
What's left of "the close"
Not nothing: review remains. Judgment calls, estimates, accruals that need a human decision: those still happen on a cadence. But they happen against books that are already current, so the close stops being reconstruction and becomes confirmation. Teams running this model, like Oper Credits, watched a half-week consolidation grind become something that posts as transactions happen.
Why this needs one ledger
The continuous close has an architectural precondition: the agent has to see the whole transaction. If AP lives in one tool, expenses in another, and the ledger in a third, no agent can match, chase, and post across the gaps, and the batching returns at every system boundary. This is why the continuous close is a property of agentic accounting platforms rather than a feature that can be added to a Frankenstack.
The close was a workaround. Agents make it unnecessary, and give finance back its first week.
See how Consolidation posts continuously across entities in Light.