Finance operations6 min read
Closing the books 3 days faster with AI agents
How the Close, Controls, Audit, and Planning Agents remove three business days from the month-end close: orchestration, reconciliations, evidence, controls, and a before-and-after close calendar.
Priya RamanHead of Finance Solutions
Updated
On this page
AI agents shorten the month-end close by taking over the coordination, reconciliation, and evidence-gathering work that consumes most of the calendar, while accountants keep the judgment and the sign-offs. In modeled design-partner deployments, Meridian's Close Agent, working with the Controls Agent, the Audit Agent, and the Planning Agent, shortens the close by 3 business days, typically from an 8-day close to a 5-day close.
Where the days go
The month-end close is the process of finalizing a period's accounting records so that financial statements can be produced. As of September 2026, most mid-size and enterprise closes take between 6 and 10 business days. Ask a controller where the time goes and the answer is rarely "accounting." It is waiting: waiting for a subsidiary to submit, waiting for a reconciliation owner to return from vacation, waiting for someone to find the support for a variance, waiting for approvals to move through email.
A close has four kinds of work:
- Orchestration: knowing what is due, from whom, in what order, and chasing it.
- Reconciliation: matching balances between the ledger and sub-ledgers, banks, and third parties, and explaining differences.
- Evidence: attaching support for balances, accruals, and adjustments so that reviewers and auditors can rely on them.
- Judgment: deciding accruals, estimates, and unusual items, and signing off.
Agents take most of the first three. Humans keep the fourth, and most of the sign-offs in the third.
What each agent does in the close
- The Close Agent orchestrates the close calendar. It knows every task, its owner, its dependencies, and its deadline; starts tasks whose inputs are ready; nudges owners; prepares reconciliations where the data is available; routes sign-offs; and reports status in real time.
- The Controls Agent tests transactions continuously during the month for duplicates, anomalies, and policy breaches, so exceptions are resolved before the close instead of during it. One design partner avoided about $283K per year in duplicate payments this way.
- The Audit Agent collects, labels, and packages evidence for balances and adjustments as they are booked, so the audit file is built during the close rather than reconstructed months later. Design partners model about 900 hours saved per year on evidence collection.
- The Planning Agent drafts variance commentary as actuals land, comparing to budget and prior period, so the management pack is ready when the ledger is.
The close calendar, before and after
The table below shows a representative calendar for a company with three legal entities, two ERPs, and a 12-person accounting team. "Day" counts business days after period end. The "before" column is the modeled baseline; the "after" column is the modeled outcome with agents in place.
| Task | Before (Day) | After (Day) | Who does it after |
|---|---|---|---|
| Sub-ledger cutoff confirmations (AP, AR, payroll, fixed assets) | 1 | 1 | Close Agent confirms cutoffs and flags late feeds |
| Bank reconciliations, 14 accounts | 2 to 3 | 1 | Close Agent prepares; staff accountant reviews exceptions |
| Intercompany matching and elimination | 3 to 4 | 2 | Close Agent matches; senior accountant resolves disputes |
| Accruals and prepaid amortization | 3 to 4 | 2 | Close Agent proposes from open POs and contracts; controller approves |
| Duplicate and anomaly review of period transactions | 4 to 5 | Continuous, cleared by Day 1 | Controls Agent flags; AP lead clears |
| Balance sheet reconciliations, 120 accounts | 4 to 6 | 2 to 3 | Close Agent prepares 90%; owners certify |
| Evidence attached to adjustments and estimates | 5 to 7 | As booked | Audit Agent packages; preparer confirms |
| Variance analysis and commentary | 6 to 7 | 3 to 4 | Planning Agent drafts; FP&A edits |
| Consolidation and management review | 7 to 8 | 4 to 5 | Controller and CFO |
| Sign-offs and close | 8 | 5 | Controller certifies; CFO approves |
Where the three days come from
Three business days come out of the calendar. They come from three places: reconciliations that are prepared the moment data lands instead of when a person gets to them, exceptions that are cleared during the month instead of in the close window, and status that is visible without a meeting.
Reconciliations in detail
A reconciliation is a comparison of two independent records of the same balance, with every difference explained and supported. The Close Agent prepares reconciliations by pulling both sides through Data Fabric, matching items by amount, date, and reference, and classifying unmatched items into known categories such as timing differences, bank fees, or unposted entries. What remains is a short list of true exceptions.
The human role changes but does not disappear. Instead of matching 400 items, the account owner reviews 12 exceptions, decides how to clear each, and certifies the reconciliation. Certification stays with the human because it is an attestation, and attestation is a matter of accountability, not computation.
Design partners report that after two closes, about 90% of balance sheet reconciliations arrive at the owner in a review-ready state, and the median time an owner spends per reconciliation falls from about 45 minutes to under 10.
Evidence and the audit file
Evidence is the documentation that supports a balance or an adjustment: invoices, contracts, calculations, approvals, and third-party confirmations. Traditionally evidence is gathered twice, once loosely during the close and again, properly, when the auditors ask. The Audit Agent gathers it once. As each adjustment is booked, the agent attaches the source documents, labels them to the audit firm's request-list conventions, and stores the package with the journal entry. When the auditor asks in March for support for an accrual booked in November, the package already exists.
Controls during the close
Controls are the checks that prevent or detect errors and fraud. Moving them earlier is the largest single source of calendar savings. The Controls Agent tests every transaction against duplicate patterns, vendor master changes, split invoices under approval thresholds, and unusual account combinations, continuously. By Day 1 of the close, the exception queue is short and the AP lead has cleared most of it.
The two controls that stay human
Two controls remain firmly human and are logged as approval-tier actions in Registry:
- Journal entries proposed by any agent require approval by a named preparer and reviewer before posting.
- Reconciliation certification is performed by the account owner, and the Close Agent cannot certify on anyone's behalf.
Implementation, close by close
- Close 1: run the Close Agent in shadow mode. It builds the calendar, tracks status, and prepares reconciliations, but staff continue their existing process. Compare its reconciliations to theirs.
- Close 2: switch bank and intercompany reconciliations to agent-prepared, owner-certified. Turn on the Controls Agent for the full month.
- Close 3: extend to balance sheet reconciliations and accruals. Turn on Audit Agent evidence packaging.
- Close 4: turn on Planning Agent commentary. Publish the new calendar with target Day 5.
Most design partners reach the 3-day reduction by the fourth close. Companies with a single ERP and fewer entities have reached it by the third.
What a faster close is worth
A 3-day shorter close is worth more than the overtime it removes. Management gets results three days earlier, which matters for a quarterly earnings cycle and for any decision that waits on actuals. The audit file is built continuously, which reduces year-end fees and staff disruption. And the accounting team's month has three more days that are not the close, which is the difference between retention and turnover for the people who know your ledger best.
Outcome figures in this article are modeled outcomes from design-partner deployments and are not guarantees of results.
Terms used in this guide
Frequently asked questions
Most mid-size and enterprise closes take 6 to 10 business days; a 5-day close is a common target and a 3-day close is considered leading practice for companies with simple entity structures. In modeled design-partner deployments, Meridian's Close Agent removes 3 business days, typically moving an 8-day close to 5 days by the fourth close after go-live.
On Meridian, agents propose journal entries; they do not post them. Every agent-proposed entry is an approval-tier action requiring a named preparer and reviewer before posting, and the proposal, its support, and the approvals are recorded in the audit trail. This preserves segregation of duties and keeps the control auditable.
The Close Agent pulls both sides of a reconciliation through Data Fabric, matches items by amount, date, and reference, classifies unmatched items into known categories such as timing differences, and presents the account owner with a short list of true exceptions. The owner clears the exceptions and certifies the reconciliation; certification is never delegated to the agent.
Auditors evaluate evidence on relevance, reliability, and provenance, not on who collected it. Evidence packaged by the Audit Agent carries source documents, timestamps, the query or system it came from, and the preparer's confirmation, which is more provenance than most manually assembled files. Involve your audit firm early so packages follow its request-list conventions.