Month-End Close with MCP: A Step-by-Step Playbook

Month-end close is the job of making one month's books complete and correct, then freezing them. In a small business it usually falls to the owner, a bookkeeper or an outside accountant. MCP (Model Context Protocol, the open standard that lets AI apps use outside tools) lets an assistant such as Claude pull the data, find the gaps and draft the reports, while a person still signs off.

This playbook covers three ledgers with documented MCP servers: LedgerMCP (built by eSEOspace), QuickBooks Online and Xero. Because we built LedgerMCP, its details here come only from its own public docs. Tool names below are copied from each vendor's documentation as of October 2026.

What you need

A client. Any MCP client that accepts remote servers works. Claude's connector setup is covered in our guides to connecting Claude to QuickBooks, Xero and LedgerMCP.

One ledger server:

Sources: LedgerMCP's tool reference, Claude's QuickBooks listing, Intuit's QuickBooks MCP repository, Claude's Xero listing and Xero's MCP repository.

Your statements. Bank and card statement ending balances are the proof of a close. Have them ready as PDFs or numbers.

The workflow

1. Load the book's rules. In LedgerMCP, start with list_conventions and list_questions. These hold how past sessions agreed to book things and what is still waiting on the owner. QuickBooks and Xero have no equivalent tool, so paste your close checklist into the chat.
2. Bring in every transaction. LedgerMCP uses sync_connections for bank feeds and import_transactions for CSV statements. QuickBooks's hosted connector has quickbooks-transaction-import, which Intuit says "Categorizes and imports transactions into your General Ledger," plus quickbooks-import-status. With Xero, the read-only connector can list bank transactions with get_bank_account_transactions, but imports happen in Xero itself.
3. Categorize what's left. LedgerMCP's bulk_categorize handles up to 200 rows per call, and many write tools accept dry_run to preview the journal lines first. In Xero's local server, update-bank-transaction changes a bank transaction. Keep a person on anything unusual.
4. Match transfers and bills. LedgerMCP's find_matches suggests invoice, bill, duplicate or transfer counterparts, and confirm_transfer books a pair as one transfer. In QuickBooks, review open receivables with qbo_accounting_get_ar_aging_summary; in Xero, use get_aged_receivables and get_aged_payables.
5. Check integrity. LedgerMCP's verify_books re-derives the ledger's invariants. Its docs call it "NECESSARY, NOT SUFFICIENT," because only a statement tie-out proves a period. In QuickBooks or Xero, pull the trial balance (get_trial_balance locally, list-trial-balance in Xero's local server).
6. Reconcile last. LedgerMCP's reconcile_account ties an account to a statement ending balance. A difference of zero means reconciled; a nonzero difference "returns a ranked suspects object." The docs say to "RECONCILE LAST, after the history is in." Neither Intuit's nor Xero's MCP pages list a reconciliation tool, so do that step in the app.
7. Draft the reports. Run profit and loss and the balance sheet for the month: run_pnl and run_balance_sheet in LedgerMCP, profit-loss-quickbooks-account and qbo_accounting_get_balance_sheet in QuickBooks, get_profit_and_loss and get_financial_position in Xero. LedgerMCP's export_report makes a CSV or an expiring link for your CPA.
8. Owner locks the period. LedgerMCP's set_lock_date closes a period so nothing dated on or before it can post. The docs call this "THE OWNER'S DECISION, NOT YOURS." Have the AI ask, not act.

Example prompts

• "List this book's conventions and open questions, then tell me what must be answered before we close September." (LedgerMCP: list_conventions, list_questions)
• "Preview categorizations for every uncategorized September transaction with dry_run. Don't post anything yet." (LedgerMCP: bulk_categorize with dry_run)
• "Reconcile the operating checking account to the September 30 statement ending balance of [amount], and show me the suspects if it doesn't tie." (LedgerMCP: reconcile_account)
• "Show the September profit and loss and the balance sheet as of September 30, and list aged receivables over 60 days." (QuickBooks: profit-loss-quickbooks-account, qbo_accounting_get_balance_sheet, qbo_accounting_get_ar_aging_summary)
• "Compare September profit and loss with August, and show the cash position at month end." (Xero: get_profit_and_loss, get_cash_position)

Guardrails

• Start read-only. LedgerMCP's read-only keys "can run every list and report but never write." Xero's hosted connector is read-only by design. Intuit's local server can switch off writes with QUICKBOOKS_DISABLE_WRITE, QUICKBOOKS_DISABLE_UPDATE and QUICKBOOKS_DISABLE_DELETE.
• Preview before posting. Use dry_run where the server supports it, and ask for a summary before any bulk change.
• Know what's permanent. LedgerMCP says "Postings are immutable: corrections are reversals, never edits." Intuit says invoices Claude creates appear in QuickBooks immediately, and deleting invoices or estimates needs your confirmation.
• Keep humans on judgment calls. Accruals, owner draws, loan splits and anything tax-related need a person. LedgerMCP's ask_user parks such questions in the ledger instead of guessing.
• Leave the lock alone. The AI should never move or clear a lock date to get a post through.
• Watch for injected instructions. Bank memos and vendor names are outside text. Read our prompt injection guide and the MCP security center.

What to measure

Track these each month, and compare them with your own baseline from before the change:

• Calendar days from month end to a locked period.
• Number of transactions still uncategorized when the close starts.
• Accounts that tie to the statement on the first reconciliation attempt, and the size of any difference.
• Open questions parked for the owner, and how long they stay open.
• Reversals posted after the close, which signal entries that were wrong.
• Accountant review notes or adjustments per month.

Don't count "hours saved" unless you time the close before and after.

Next step

Compare ledgers in Best MCP Accounting and Bookkeeping Tools, see how we built an MCP-native ledger in our LedgerMCP spotlight, and browse more workflows in the MCP playbooks hub.

Frequently asked questions