Why Close Week Is Spent Chasing Evidence
Every month the same team chases the same unreconciled balances, rebuilds accrual spreadsheets and rewrites variance explanations, and the close calendar leaves little time for actual analysis.
AI helps the month-end close by preparing work a controller can check quickly: drafting recurring accruals from contracts, receipts and prior bookings, matching bank and subledger balances to the ledger, writing first-pass flux commentary and tracking the close checklist, with every draft linked to its source records. To avoid control gaps, the AI gets read-only access, its drafts pass the same preparer and reviewer sign-offs, and a person posts every journal entry.
Trigger: The accounting period ends and the close calendar opens its first task. Owner: Financial Controller. Primary output: Reconciliation workpapers with matched items and open differences. Consequential actions require approval.
Assess your workflowEvery month the same team chases the same unreconciled balances, rebuilds accrual spreadsheets and rewrites variance explanations, and the close calendar leaves little time for actual analysis.
VDF AI agents read ledger, bank and subledger data through read-only queries, prepare reconciliation workpapers, propose accruals with their supporting documents and draft commentary that controllers edit and approve.
Tracks every close task against its owner and due day, and reports which tasks are blocked and what is blocking them.
Compares ledger balances with bank statements and subledgers, matches items inside the tolerances finance has set and lists the remainder with likely causes.
Finds goods received but not yet invoiced and recurring costs with no booked charge, then proposes accrual entries with the evidence attached.
Drafts explanations for movements above the materiality threshold and names the transactions driving each one.
Assembles reconciliations, approvals and supporting documents into a binder indexed by account for reviewers and auditors.
Each month-end close source has a defined purpose, freshness expectation, quality gate, and sensitivity boundary.
Purpose: Provide the balances and transactions every reconciliation and variance draft starts from.
Freshness: Refreshed after each posting run during close week.
Quality: Account mappings, entity codes and period flags must agree between ledger and subledgers.
Sensitivity: Restrict payroll and executive compensation accounts to named reviewers.
Purpose: Supply the evidence behind matched items and proposed accruals.
Freshness: Loaded daily during the close and once more at cut-off.
Quality: Every document carries a reference that links it to the ledger line it supports.
Sensitivity: Mask bank account numbers in drafts that circulate beyond treasury.
Purpose: Tell agents which differences to clear, which to escalate and which accounts need commentary.
Freshness: Reviewed every quarter and whenever the auditor revises materiality.
Quality: Each threshold has an owner, an effective date and an approval record.
Sensitivity: Keep policy edits under change control in the finance system of record.
Review results after every close in the pilot and quarterly afterwards, and recheck tolerances when the chart of accounts changes.
AI in the month-end close is a preparer, not an approver. It drafts the recurring accruals, ties bank and subledger balances to the ledger, explains movements above materiality and keeps the checklist current, and it attaches the evidence to each draft. The controller’s team reviews, edits and posts. Done that way, the close keeps every control it had and gains earlier, better-documented first drafts.
It pays off when the close repeats the same mechanics every month: a stable chart of accounts, reconciliations with named owners and data that can be queried without manual exports. It helps less during a restructuring, an ERP migration or a period dominated by one-off judgements.
The scope is the period-end financial reporting process that auditors already test. The SEC’s 2007 interpretive guidance on internal control describes that process as including the entry of transaction totals into the general ledger, journal entry processing, recurring and non-recurring adjustments, and preparation of the statements and disclosures. Agents can prepare parts of each step. None of them changes who is accountable.
Most ERPs already automate the deterministic part of the close: auto-reconciliation rules, recurring journal templates, allocation runs. AI earns its place where those rules stop, because the work involves reading documents or writing explanations.
| Close work | Rules-based automation is enough | AI adds value |
|---|---|---|
| Bank matching | Exact amount and reference matches | Partial payments, batched deposits, free-text remittance |
| Recurring accruals | Fixed monthly amounts on a template | Amounts that depend on contracts, usage or late invoices |
| Flux analysis | Flagging movements above a threshold | Drafting why the account moved, citing the transactions |
| Close checklist | Due dates and owners | Summarising blockers from comments, emails and open items |
| Journal entry prep | Standard allocations | Assembling support and a description for non-standard entries |
If a task can be written as a fixed rule, keep it as a rule. Use AI for the residue that currently lands on a staff accountant’s desk.
| Task | What the AI drafts | Evidence attached | Who signs |
|---|---|---|---|
| Recurring accruals | Amount, method and reversal date | Contract, prior bookings, post-cut-off invoices | Preparer, then journal approver |
| Goods received, not invoiced | Accrual per open receipt | Purchase order and goods receipt | Preparer |
| Bank and cash reconciliations | Matched items and open differences | Bank statement lines, ledger detail | Reconciliation reviewer |
| Subledger and intercompany tie-outs | Differences by entity and counterparty | Subledger and counterparty balances | Account owner |
| Prepaid and deferral roll-forwards | Updated schedule and amortisation | Invoices and contract terms | Preparer |
| Flux and variance commentary | Explanation per account above materiality | Transactions driving the movement | FP&A or account owner |
| Close checklist | Status, blockers and late items | Task log and comments | Close manager |
Start with three or four rows from this table, on one entity, where a reviewer can check the output in minutes. Leave impairments, legal provisions, tax positions and revenue judgements with people.
The figures below are illustrative. Suppose the accrual schedule for October lists three recurring lines.
Each proposal arrives with its method, sources and a confidence note. The preparer edits the utilities line for the new site, accepts the other two and books them through the ERP’s journal approval. The edits and the approval become part of the evidence.
These steps line up with the control components in the COSO internal control framework: the control activities stay, and the information and monitoring around them get better records.
| Document | What it covers | Kept where |
|---|---|---|
| Intended use | Tasks in scope, entities, and what the tool may not do | Close policy or control narrative |
| Data sources | Systems, extraction time and completeness check | With each period’s workpapers |
| Rules | Tolerances, materiality, accrual methods, approver, effective date | Close policy, under change control |
| Configuration | Model and instruction version, change log, who approved changes | IT or finance systems change record |
| Period evidence | Draft, sources, human edits, reviewer sign-off, timestamps | Reconciliation or close tool |
| Exceptions | Items the AI could not match or explain, and their resolution | Reconciliation workpaper |
| Validation | Parallel-run results and periodic sample re-tests | Internal control testing file |
Auditors tend to ask the same two questions about any system-generated workpaper: how do you know the data it used was complete, and how do you know a person reviewed the result. The first four rows answer the first question; the last three answer the second.
| Day | AI prepares | People decide |
|---|---|---|
| Day -2 | Cut-off reminders, open purchase orders and receipts, last month’s reversals | Close manager confirms the calendar |
| Day 1 | Bank and cash matches, recurring accrual drafts | Preparers review accruals and book them |
| Day 2 | Receipts-not-invoiced accruals, subledger and intercompany tie-outs | Account owners clear differences outside tolerance |
| Day 3 | Flux commentary drafts, prepaid roll-forwards | Reviewers sign off reconciliations |
| Day 4 | Evidence binder by account, list of open items | Controller reviews top-side adjustments |
| Day 5 | Management pack commentary draft | Controller signs off the period |
An agent can take on much of a staff accountant’s preparation: pulling reports, matching, rolling forward schedules, drafting accruals and chasing checklist owners. It cannot hold responsibility. It does not post entries, approve its own drafts, decide whether an estimate is reasonable or sign anything. The practical model is one accountant supervising the agent’s drafts across more accounts, not an agent replacing the accountant.
| Close task | Agent prepares | Person decides |
|---|---|---|
| Bank reconciliation | Matched items and open differences | Clearing of differences outside tolerance |
| Accruals | Draft entries with receipts and contracts | Booking, amount and reversal date |
| Variance analysis | Draft commentary with named drivers | Final wording sent to management |
| Sign-off | Evidence binder by account | Period sign-off |
Map each agent step to an existing control in your COSO-based internal control framework instead of inventing new ones. The control owner stays the same; what changes is the evidence they review.
VDF AI Agents run on-premises, in a private cloud or air-gapped, so ledger data stays inside your environment. Agents query databases through the read-only SQL tool, which cannot write and logs every query, and they parse workbooks and exports with the XLSX and CSV tools.
Draft entries and reconciliations can pause for a named reviewer through the human approval request tool, and the audit trail query tool answers what an agent did and when. Role-based access control decides who can change thresholds and instructions and who can only review drafts.
For the close as a whole, the AI financial reporting agent covers period-end reporting, and the AI accounting agent handles transaction coding and balance explanations.
See the finance use cases for adjacent work, including financial reporting, AP invoice matching and payment reconciliation for banks.
Control: Only differences inside approved tolerances clear automatically; everything else goes to a named preparer.
Accountable owner: Financial Controller
Control: Re-run the invoice match at cut-off and show the preparer every document behind the proposal.
Accountable owner: Accounts payable lead
Control: Commentary must name the transactions behind each figure, and the account owner edits before release.
Accountable owner: FP&A manager
Pilot on one legal entity and its bank and accrual reconciliations for two closes, running alongside the existing process before anyone relies on the drafts.
Assign these prebuilt tools to the bounded agents in AI Month-End Close Automation, or browse all VDF AI tools.
These sources inform the governance and evaluation approach for AI Month-End Close Automation. They do not certify a specific deployment.
Written by VDF AI Editorial Team. Last reviewed 30 October 2026.
Answers for Financial Controller evaluating this workflow's data, controls, measures, and operating boundaries.
Talk to an expertGive it the accrual schedule, the contracts behind each line, last month's bookings and the invoices received after cut-off. For every recurring accrual it proposes an amount, shows the method used (contract rate, run rate or receipts not yet invoiced), attaches the documents and flags lines where the pattern broke, such as a price change or an invoice that already arrived. A preparer accepts or edits each draft and books it through the normal journal approval.
Attach the AI to controls you already run instead of inventing new ones. Give it read-only access, let it clear differences only inside tolerances the controller approved, route every draft through the same preparer and reviewer sign-offs, and run it in parallel for two closes. Measure reviewer edits as well as preparer hours: if reviewers rewrite most drafts, narrow the scope before going live.
Document the intended use and the tasks the tool may not perform, the data sources and how their completeness is checked, the approved tolerances and accrual methods, the model and instruction version in use, and the change log for both. For each period, keep the draft, the source records, every human edit, the reviewer's sign-off with a timestamp and the exceptions the tool could not resolve.
Several products are marketed that way, and agents can do much of a staff accountant's preparation: pulling balances, matching transactions, drafting accruals, rolling forward schedules and chasing checklist items. What they should not do is post entries, approve their own work or make estimates that need judgement. Treat the agent as a preparer whose every output a named accountant reviews.
No, and it should not try. AI can prepare most of the mechanical work: matching, roll-forwards, accrual candidates, first-draft commentary and the checklist. Posting journal entries, judging estimates and signing off the period stay with accountable people, because those decisions carry personal responsibility under internal control over financial reporting.
Start building it free in the cloud, or describe your AI Month-End Close Automation workflow and we will help map the appropriate governed agent network for your environment.