Finance operations still run on manual work: reconciliation, consolidation and reporting rebuilt by hand every period. The month-end close is where that work becomes visible, and where the days go. We know which of these operations respond to process and which are decided by the system underneath, and we share it here: the pains, the solutions, and where automation genuinely cuts the working time.
Controllers and accounting managers running the month-end close day to day, deciding whether the bottleneck is process or the system underneath it.
Where the close's days actually go, what an ERP's data model does and does not let you automate, what intercompany elimination requires structurally, and where an AI agent can safely touch the close and where it cannot.
Per APQC's General Accounting benchmarking, reported by CFO.com in 2018, the median close runs 6.4 calendar days, the top quartile closes in 4.8, and the bottom quartile takes ten or more. That range comes from 2,300 organisations with different structural floors, not a target to hit; the real question is which band your own system's data model allows.
The line runs along the ERP's data model, not the finance team's effort. Repetitive rule-based steps such as posting, coding, and period guards can run on nearly any platform. Reconciliation and elimination are different: whether they can run without a person depends on what the underlying system can structurally support.
Getting transactions in and explaining the result are effort problems: more people, better checklists and earlier cut-offs move them. Agreeing balances and the group-level consolidation join are not. They are decided by what the ERP's data model can express, and no amount of process discipline moves a ceiling the system itself sets.