AI SOP Template: Financial Month-End Close

The month-end close still consumes 5 to 10 working days at most mid-market companies. Controllers chase reconciliations, accruals get reworked twice, and the variance commentary lands in the CFO's inbox three days after she needed it. None of that has to be true anymore.

Forty-four percent of finance teams now deploy agentic AI inside the close. The teams that have actually committed to it are cutting cycle time by 40 to 50 percent and dropping reconciliation error rates by up to 90 percent. The difference between the teams getting that result and the teams running pilots that go nowhere is one thing: a written SOP that names the role, the tool, the prompt, and the handoff for every step.

This article gives you that template. Copy it, adapt it to your ERP, and you can be running a measurably faster close inside one quarter.

The Five-Phase Close SOP

The template below assumes a standard accrual-basis close on a monthly cadence. Adjust the day numbering for your reporting calendar.

Phase 1: Pre-Close Prep (Day -3 to Day 0)

Owner: Senior Accountant. AI role: automated checklist runner and data quality scanner.

Three business days before close, an AI agent kicks off the close checklist. It pulls the prior-month close package, copies the task list, and sends each owner a Slack or Teams ping with their assigned items, deadlines, and any data gaps it has already detected (open POs, unposted invoices, unmatched receipts, unreviewed expense reports).

Sample agent prompt: "Review the open subledger items in NetSuite for the period ending [date]. List every item missing a category, missing approval, or older than 30 days. Output a Markdown table grouped by owner, with the count and dollar value per row. Flag any line item over $10,000 with a warning emoji."

The agent runs daily until close. By Day 0, the data is clean enough that the close can actually start on time.

Phase 2: Reconciliations (Day 1 to Day 2)

Owner: Staff Accountant supervised by Senior Accountant. AI role: reconciliation agent (Trullion, BlackLine Studio AI, ChatFin, or HighRadius).

The single biggest win in an AI close is here. A reconciliation agent ingests your bank statements, credit card feeds, and sub-ledger detail, then matches transactions against the GL automatically. Match rates in production routinely hit 92 to 98 percent on bank reconciliations and 85 to 92 percent on intercompany. The accountant reviews only the genuine exceptions.

The SOP step looks like this:

1. Upload or auto-pull bank statement, AR sub-ledger, AP sub-ledger, and intercompany detail.
2. Run the AI reconciliation pass. Review flagged exceptions in priority order (largest dollar first).
3. For each exception, accept the agent's proposed match, override with a manual match, or post a research item.
4. Sign off on the reconciliation in the platform; the agent locks the period.

The Senior Accountant reviews any exception over a materiality threshold (commonly 0.5 percent of revenue) before sign-off.

Phase 3: Accruals and Adjustments (Day 2 to Day 3)

Owner: Senior Accountant. AI role: journal entry drafter (Claude Sonnet 4.6 or GPT-5 inside an MCP workflow).

Routine accruals (utility estimates, payroll accrual, prepaid amortization, deferred revenue recognition) follow patterns. An LLM with access to the prior 12 periods of postings can draft them in seconds. The accountant reviews, adjusts, and posts.

Sample prompt for a Claude-based agent: "Using the journal history attached, draft the standard month-end accrual entries for [month/year]. For each, output: account number, debit/credit, amount, calculation logic, and the supporting source (which prior-month entry it pattern-matches). Flag any entry where the amount has moved more than 15 percent month over month and explain why."

The output goes into a queue. The Senior Accountant reviews each entry, either accepts it as drafted, edits the amount, or rejects with a reason. Accepted entries auto-post via the ERP API. Rejected entries with a reason train the next month's drafts.

Phase 4: Variance Analysis and Commentary (Day 3 to Day 4)

Owner: FP&A Lead. AI role: variance commenter and narrative drafter.

Once the trial balance is finalized, an AI agent runs the variance pass. It pulls actuals versus budget and actuals versus prior period, identifies any account with a variance over your defined threshold, and drafts a one-paragraph explanation per account.

The agent's draft commentary should never be the final commentary. It is a starting point that saves the FP&A analyst 60 to 90 minutes per close. The analyst edits, adds business context, and finalizes.

Sample prompt: "For each P&L line where actuals differ from budget by more than $25,000 or 10 percent (whichever is larger), write a two-sentence explanation. Reference the underlying transaction detail. If you can identify a likely driver from the GL detail (one-time vendor, headcount change, FX, timing), state it. If the variance is unexplained, flag it for analyst review."

Phase 5: Reporting Package and Sign-off (Day 4 to Day 5)

Owner: Controller. AI role: reporting package assembler.

The final phase is mostly assembly. An agent pulls the finalized financial statements, the variance commentary, the reconciliation sign-off summary, and the open exceptions list, then assembles the close package as a PDF for the CFO. The Controller reviews, signs off, and the package goes out.

If you use a board reporting tool like Cube or Vena, the agent can also push the results into the board deck and notify the executive assistant that the deck is ready for review.

The Tool Stack: What to Buy

You do not need a single megasuite to run this SOP. The pragmatic stack is three layers.

If your close runs on a small team and your ERP is NetSuite, QuickBooks Enterprise, or Sage Intacct, start with the three-layer pragmatic stack. The total monthly cost is usually under $3,000 and you can stand it up in 30 days. If you are at a larger company on Workday or SAP and you have audit committee scrutiny, the close management suite plus KPMG-style agent overlay is the safer path.

How to Roll This Out Without Breaking a Quarter

The number one mistake teams make is trying to automate the whole close in one cycle. Do not. Pick one phase per quarter.

Quarter 1: Implement Phase 2 (reconciliations). Every other phase stays manual. Measure cycle time and exception rate before and after.

Quarter 2: Add Phase 3 (accrual drafting) and Phase 4 (variance commentary). The reconciliation agent is now stable, your team trusts it, and you can layer.

Quarter 3: Add Phase 1 (pre-close prep) and Phase 5 (reporting assembly). At this point, you have an end-to-end agentic close.

Quarter 4: Tune. Look at where the agent still gets things wrong, retrain on the corrected examples, and tighten the materiality thresholds.

Roles and Responsibilities Matrix

Every step of the SOP needs an owner. Below is the default assignment for a 5-person finance team. Scale up the column count for larger teams.

Phase	Primary Owner	AI Reviewer	Final Sign-off
Pre-close prep	Senior Accountant	Agent flags gaps	Senior Accountant
Reconciliations	Staff Accountant	Reconciliation agent	Senior Accountant
Accruals and adjustments	Senior Accountant	LLM drafts	Controller
Variance and commentary	FP&A Lead	LLM drafts	Controller
Reporting package	Controller	Agent assembles	CFO

KPIs to Track from Day One

If you do not measure the close, you cannot prove the AI is working. Track at minimum:

• Total cycle days from period close to package delivery
• Manual journal entry count per close
• Exception count and dollar value per close
• Hours per accountant per close
• Audit adjustment count post-close
• Restatement rate (target: zero)

Publish these monthly to your CFO. The progression from baseline to month 6 is the proof your investment worked.

FAQs