Agentic Books Close: Write the Close SOP and Tie-Out Standard Before the Agent Runs Your Clients' Month-End
Agentic Books Close, announced by Intuit on October 27, 2026, will run month-end steps from a firm's uploaded standard operating procedures and log what it does. Before it touches a client file, the firm needs a written close SOP and a tie-out standard that says what each step must prove, who reviews it, and who closes the period.
Why this matters now
On 2026-10-27 Intuit used its Intuit Connect event to announce Agentic Books Close, an add-on to Intuit Accountant Suite. The release describes it as a capability that "runs more of the monthly close process automatically, following a firm's own standard operating procedures and tracking actions in an audit log, while accountants supervise, review, approve, and manage exceptions." It is listed as coming soon. The same release put Firm Playbooks and portfolio intelligence into beta, so the firm-level workflow layer is arriving in pieces over the next few months.
Intuit chief executive Sasan Goodarzi gave Accounting Today, on 2026-10-27, the clearest description of the mechanics so far. Firms "will be able to upload their existing standard operating procedures to create an agentic workflow," then "customize their workflow tasks each step of the way." Once deployed, the agent "will do the work at the accountant's direction, showing progress and flagging what needs their attention," continuing "all the way to reviewing and preparing to send the financial summary to the client," and "when the agent completes all the tasks, the books will be closed." CPA Practice Advisor's report the same day adds that the audit log tracks all actions and that accountants keep supervisory oversight over completed work, approvals, and exceptions.
The agent is built on a close workflow that already exists. Intuit's ProAdvisor walkthrough of the Books Close beta, updated 2026-10-19, shows a firm-level checklist with pre-close tasks that carry over month to month, bank and credit card accounts pulled in for reconciliation, a transaction review that flags uncategorized items, missing payees, and amounts above a customizable threshold that defaults to $2,500, a year-to-date profit and loss and balance sheet review, and a final task that sends financials to the client. Intuit's accountant pricing page says Agentic Books Close will be $0 per client per month during beta and a paid add-on after it.
What none of that coverage answers is the firm's question. The moment a firm uploads an SOP, that document stops being guidance for staff and becomes an instruction set executed across every client it is assigned to. Most firms don't have one written down at the level an agent needs; the close lives in a senior bookkeeper's head and a half-maintained checklist. The rest of this article is the SOP content and tie-out standard to write before the beta invitation arrives, and the review that makes the saved hours real.
What the SOP must say for each close step
An SOP an agent can follow needs four things per step that a human-facing checklist usually leaves implicit: the source data the step reads, the deterministic tie-out the step must produce, the rule that turns a difference into an exception, and the named reviewer who clears it. "Reconcile the bank" is a task name. "Reconcile each bank and card account to the statement closing balance, list every reconciling item with its date, and flag any item older than 30 days or any unexplained difference above $25" is an instruction.
Write the SOP at the level of the business event, not the screen. A client's October close is the same set of accounting assertions whether a person or an agent performs it: cash exists and is complete, payables and receivables agree to their subledgers, prepaid and accrued balances roll forward, and the profit and loss for the month explains itself against the prior month and the budget. The table below is a starting standard for a bookkeeping client on QuickBooks Online. Thresholds are examples; set them per client and record who approved them.
| Close step | Source data | Tie-out the agent must produce | Exception rule (example) | Reviewer check |
|---|---|---|---|---|
| Pre-close | Bank feeds, payroll journals, open client requests | Feeds current through month end; payroll journals posted for every pay date; request list empty or aged | Any feed gap, missing pay date, or request open more than 10 days | Confirm the period is complete before any balance is tested |
| Bank and card reconciliation | Statement closing balance, ledger balance, uncleared items | Statement balance less outstanding checks plus deposits in transit equals ledger balance, to the cent | Unexplained difference above $25, or any uncleared item older than 30 days | Inspect the aged items, not the zero difference |
| Transaction review | All posted transactions for the month | Count of uncategorized, no-payee, over-threshold, and possible duplicate items, each with an identifier | Any uncategorized item; any item above $2,500 without an attachment | Sample routine items too, not only flagged ones |
| Subledger tie-outs | AR aging, AP aging, undeposited funds detail, ledger control accounts | Aging totals equal ledger AR and AP; undeposited funds cleared within 5 days | Any difference; any undeposited item older than 5 days | Trace each difference to a specific document |
| Period-end schedules | Prepaid, accrual, fixed asset, and loan schedules; lender statements | Opening plus additions less amortization or payments equals closing; loan balance equals lender statement | Any schedule that does not roll; loan difference above $10 | Re-perform one schedule each month |
| Financial review | Month and prior-month profit and loss, budget, balance sheet | Variance by account versus prior month and budget, with an explanation attached to each flagged line | Movement above 20% and above $1,000 without an explanation | Read the explanations as a client would |
| Send financials | Final report package, version, approver | Package version recorded with the approver's name and date | Any package released without a named approver | Only the named approver releases |
Two of these rows deserve a sentence each. Subledger tie-outs are where agent-run closes will earn or lose trust, because a bank reconciliation can be perfect while accounts payable is wrong. And the send-financials row is the one step the SOP should never delegate: the agent can prepare the package, but a named person releases it. If the firm has already written a responsibility agreement for Intuit's transaction-posting service, the Books Upkeep responsibility matrix is the right template to extend; the agent-run close adds rows, it doesn't replace the agreement.
For firms with multi-entity clients, add a row for intercompany balances: due-to and due-from accounts must agree across entities before either entity's close is marked complete, and the group mapping must be stable. The shared chart of accounts mapping guide covers why a close that is correct at the entity level can still produce an inconsistent group report.
One client's October close, run against the standard
Larkspur Landscaping is a bookkeeping client of a twelve-person firm, on QuickBooks Online with one operating account, one credit card, payroll through a third-party provider, and an annual insurance policy. The numbers below are illustrative. The method is what carries to every other client.
Bank reconciliation ties, and the aged item is the finding
The October 31 statement closing balance is $84,312.50. Outstanding checks total $4,100.00 across three checks, and one deposit of $900.00 is in transit. Statement balance less outstanding checks plus the deposit in transit is $81,112.50, which equals the ledger balance. The tie-out passes. The exception rule still fires, because one of the three outstanding checks is dated August 19 and is 73 days old. The agent's log should show both facts: a zero difference and an aged item routed to the reviewer. A reviewer who sees only the zero would miss a stale check that may need to be voided and the payable reinstated.
Accounts payable does not tie, and the log has to show the fix
The AP aging report totals $38,680.00. The ledger accounts payable balance is $37,480.00. The difference is $1,200.00. The agent flags it under the subledger rule and the reviewer traces it to a journal entry dated October 14 that debited accounts payable $1,200.00 and credited repairs expense $1,200.00 for a returned mower part. Because the entry carries no vendor name, it reduced the ledger control account without touching any vendor's open bills, so the aging still shows the full invoice as unpaid.
The correction is to reverse the journal entry and record a vendor credit of $1,200.00 against the vendor, then apply it to the open bill. Accounts payable and repairs expense end at the same balances as before, so there is no profit and loss effect. What changes is that the subledger and the control account agree, the vendor's remittance will show the credit, and the next bill run will not pay a liability the client no longer owes. The audit log needs three entries here: the detection, the reviewer's conclusion, and the correcting documents with their identifiers. A log that records only "AP tie-out resolved" is not evidence.
Prepaid insurance rolls, and the entry is pre-approved by the SOP
Larkspur paid $12,000.00 on August 1 for a policy running August 1 through July 31. The SOP's schedule amortizes $1,000.00 per month. Opening prepaid at October 1 is $10,000.00, October amortization is $1,000.00, and closing prepaid is $9,000.00. The agent posts the entry, debit insurance expense and credit prepaid insurance, because the SOP authorizes that specific recurring entry from an approved schedule. The log records the schedule it used and the manager who approved the schedule on September 5. An entry the SOP does not pre-authorize, such as a new accrual, stops at the reviewer instead.
The financial review flags fuel, and the explanation is the deliverable
October revenue is $142,600.00 against $151,900.00 in September, down 6.1%, which is below the 20% rule and consistent with the season. Fuel expense is $6,420.00 against $4,980.00, up 28.9% and up $1,440.00, so it clears both halves of the rule. The reviewer attaches the explanation: a second crew started October 6 and fuel prices rose during the month. That one sentence is what the client's financial summary needs, and it is the part of the close no SOP can write in advance.
What the first close cost
Before the pilot, Larkspur's close took a staff accountant 6.5 hours and a manager 1.5 hours, for 8 hours. In the first agent-run close, staff time fell to 2 hours, manager review rose to 2.5 hours because every exception was examined and the AP finding took 40 minutes, and coordination added 0.5 hours, for 5 hours. Three hours were saved and the review got deeper. That is a capacity gain, not cash, until the firm redeploys the hours or avoids a hire, and the second close should be measured again with the same boundaries.
Accounting controls for an agent-run close
Source data: the bank and card statements, the ledger detail for the period, the AR and AP aging reports as of month end, the prepaid, accrual, fixed asset, and loan schedules with their approval dates, the payroll provider's journal summaries, the client's open request list, and the SOP version the agent executed. Keep the entity, period, and accounting basis visible on every extract. Record the SOP version with the close, because a close run on last month's SOP is a different procedure from one run on this month's.
Calculation: every tie-out in the standard is a deterministic equation the agent should reproduce and the reviewer can re-perform: statement balance less outstanding checks plus deposits in transit equals ledger cash; aging total equals control account; opening schedule balance plus additions less amortization equals closing. Preserve debit and credit polarity in the comparisons. Cash and prepaid assets carry debit balances; accounts payable carries a credit balance. A report that shows all of them as positive numbers needs a declared sign convention before any difference is computed, or a correction can look like it halves a gap when it doubles it. Keep flows and balances separate: the prepaid closing balance is a point-in-time number, the $1,000.00 amortization is October's flow, and the bank reconciliation tests a balance at a date, not activity over the month.
Review: a reviewer who did not configure the SOP re-performs at least one tie-out per close from source documents, reads every exception the agent raised and a sample of items it did not raise, confirms that each correction in the audit log points to a document identifier rather than a description, and checks that the financial-review explanations would make sense to the client. The reviewer also confirms that nothing in the close was marked complete by the agent that the SOP reserved for a person. The audit-ready close controls guide covers how to keep that evidence retrievable months later without adding hours to each close.
Decision: the engagement manager owns the SOP content and its thresholds, approves recurring entries the agent may post, and decides when a client moves from supervised pilot to routine. The named approver, usually the engagement partner or the client's finance lead, releases the financial package. The firm's quality lead owns the decision to extend the agent to more clients, based on measured exception rates and review findings rather than saved hours alone. Write each of those decisions down with a date, because the first question an auditor or a departing staff member's replacement will ask is who decided the agent could post that entry.
Limits and common mistakes
Agentic Books Close is coming soon and being piloted with select firms, by Intuit's own description. Feature detail, thresholds, and pricing after the beta may change, and nothing above describes product behavior beyond what Intuit has published. Treat the standard here as the firm's own procedure, which it should have whether or not it adopts the add-on.
The most common mistake will be uploading the checklist the firm already has. A checklist names tasks; an SOP for an agent names evidence and thresholds. A second mistake is reading a clean exception list as a clean close. The Larkspur bank reconciliation produced a zero difference and still contained a finding; a close that raises no exceptions for three months in a row deserves a re-performed tie-out, not a celebration.
A third mistake is letting the agent's audit log substitute for the firm's own evidence. The log shows what the agent did. It doesn't show whether the SOP was right, whether the reviewer looked, or who released the package. Keep the firm's review record alongside the log, and make sure both can be exported, because an engagement file that lives only inside a vendor's workflow is harder to defend in a dispute or a peer review.
Finally, don't count saved hours as revenue. A three-hour saving per client per month is real capacity, and it becomes advisory revenue only when the firm sells and delivers advisory work in that time. Measure the hours, then decide separately what to do with them.
Frequently Asked Questions
What is Agentic Books Close?
Agentic Books Close is an add-on to Intuit Accountant Suite that Intuit announced on October 27, 2026. According to Intuit, it runs more of the monthly close process automatically by following a firm's own uploaded standard operating procedures, tracks its actions in an audit log, and leaves accountants to supervise, review, approve, and manage exceptions. Intuit lists it as coming soon.
What should a close SOP contain before a firm uploads it?
For each close step, the SOP should name the source data the step reads, the deterministic tie-out it must produce, the threshold that turns a difference into an exception, and the reviewer who clears it. It should also state which recurring entries the agent may post from approved schedules and which steps, such as releasing the financial package, are reserved for a named person.
Can a clean bank reconciliation prove the close is right?
No. A bank reconciliation with a zero difference can still contain stale outstanding items, and it says nothing about whether accounts payable or accounts receivable agree to their aging reports. Subledger tie-outs and schedule roll-forwards are separate tests and should be separate steps in the SOP.
Who should release the client's financial package in an agent-run close?
A named approver, usually the engagement partner or the client's finance lead, should release the package. The agent can prepare and stage it, but the release decision and its date should be recorded by a person, separately from the agent's audit log.
How should a firm measure whether the agent saved time?
Measure the whole close, including staff preparation, reviewer time, exception handling, and client coordination, using the same boundaries before and after the pilot. Treat the difference as capacity rather than cash until the firm redeploys the hours, avoids a hire, or delivers additional billable work in that time.
A firm that runs an agent-driven close for dozens of clients still has to prove each month's numbers to the client, and that proof lives in the ledger, not the task list. FinBoard reads each client's QuickBooks Online ledger into one reporting view, so a reviewer can trace a flagged variance or a subledger difference from the financial package back to the transactions behind it, across every entity in the client group. See how FinBoard gives the close review a ledger-level audit trail.
