How a Finance Team Cut Month-End Close 10 Days to 1

Month-end close at most finance functions is a manual, people-intensive process with no memory, no self-correction, and no leverage. Each close starts from scratch: pulling the same reports, chasing the same reconciliations, answering the same variance questions. The controller carries the entire process in their head, which makes every close dependent on one person's bandwidth and creates no institutional learning. QuantFi ran this problem on itself before building for clients.

QuantFi built a four-layer agentic close system using Claude as the orchestration model. The architecture consists of: (1) a knowledge base layer that encodes the company's chart of accounts, entity structure, accounting policies, and prior-period close logic; (2) an integration layer connected to QuickBooks Online and relevant source systems; (3) an agent execution layer that runs the close workflow autonomously, pulling trial balance data, identifying variances against prior periods, drafting explanations, and flagging anomalies that require human review; and (4) a human gate layer where the controller or CFO reviews, approves, or overrides agent outputs before anything is finalized. The system improves each cycle: approved explanations and decisions are written back into the knowledge base, so the next close starts with more institutional memory than the last. The result is a close process that runs faster, documents its own work, and gets more accurate over time. QuantFi built a four-layer agentic system on top of its existing QuickBooks Online stack: a knowledge base encoding the chart of accounts, prior-period logic, and company accounting policies; an integration layer pulling live transaction data; an agent execution layer running the close workflow autonomously (journal entry drafting, variance detection, flux commentary); and a human gate layer where the controller reviews and approves before anything is finalized. What specifically changed: the close no longer depends on a single person remembering why last month's accruals were structured a certain way. Every approved decision writes back to the knowledge base, so the system compounds across cycles. The result is that QuantFi compresses a multi-day, controller-dependent close into a same-day agent-driven process, with the human reviewing outputs rather than producing them from scratch.

QuantFi treated its own month-end close as the first engagement, on the principle that you cannot automate judgment you have not first codified. Phase one built the knowledge base before any agent logic — the company's chart of accounts, entity structure, accounting policies, and prior-period close decisions were encoded into a structured, queryable layer. With that foundation in place, the team wired up an integration layer to QuickBooks Online and mapped the trial balance to the entity structure with logic for detecting period-over-period variances at the line-item level. The agent execution layer was built on Claude as the orchestration model: it pulls the trial balance, identifies variances against prior periods, drafts journal entries and variance explanations, and flags anomalies that require human review. A human gate layer is deliberately retained — for auditability and SOX-adjacent control, the agent never finalises anything without controller or CFO approval. Each approved decision is written back into the knowledge base, so accuracy and autonomy compound across cycles rather than resetting every month. The full build ran in under four weeks, and the month-end close dropped from ten days to one.

PE-backed portcos and middle-market CFOs who run a monthly close with a lean team and want to eliminate the manual, repetitive steps without replacing their controller. Specifically relevant for companies that have adopted cloud accounting software (QBO, Sage Intacct) but have not rebuilt any of the workflows on top of it.