ai receipts
Search your own problem
Case study · From the Pluris libraryReceipt no. 9039
What sucked

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.

Financial ServicesFinance & AccountingUnder 4 weeks
What they built

QuantFi built a four-layer agentic month-end close system on Claude, a knowledge base layer encoding the company's chart of accounts, accounting policies, and prior-period logic; an integration layer connected to QuickBooks Online; an autonomous agent execution layer; and a human gate for controller review.

What changed
Variance commentary drafted in minutes, not hours.

The agent produces first-draft explanations for every line-item movement exceeding threshold, eliminating the most time-intensive manual step in a typical close.

Institutional memory compounds each cycle.

Each approved close decision is written back into the knowledge base, so the system's accuracy and autonomy increase over time rather than resetting to zero each month.

Close cycle time cut by 90%, from 10 days to 1 day

Speed of data gathering, human approval, and execution enabled faster decisions and faster close time.

Time to results
Under 4 weeks
Company size
1-50 people
Project cost
Under $25K
More fixes like this
Who did it
Kenny Jen
Co-Founder & Managing Partner, QuantFi

Vetted by Pluris.