Prompts for controllers and CFOs to run the month-end financial close in Claude: reconcile accounts, post accruals, write flux commentary, and ship the board close package in days, not 10 to 12.
Never used Claude? It is free and takes 30 seconds to open. Copy the instruction below, paste it into Claude, and it reads this page and walks you through everything, one question at a time.
A short instruction plus a link to this page lands on your clipboard. First copy asks for your email once. That unlocks every button across the whole library.
Free account, no card, 30 seconds. This tab stays open so you can come back.
Open claude.ai ↗Claude reads this page, asks which computer you are on, then guides you step by step until it works. If anything errors, tell Claude what you see, and it fixes it with you.
I want to run my month-end close in Claude on my own books. Walk me through it.
This is NOT a Terminal or coding install. The prompts run inside the Claude app. Treat me like a controller or finance lead who has never coded. Nothing installs on my machine.
What I am setting up: a private Claude Project that holds my trial balance and sub-ledgers, so the vault on this page can reconcile every account, run the consolidation, write the flux commentary, and build the board close package. A named controller signs the close.
Walk me through ONE step at a time. Wait for me to confirm each.
1. Open `claude.ai`, sign in, pin Opus 4.8. For real financial data use Team or Enterprise so the books stay in my tenant and out of training.
2. Left sidebar → "Projects" → "Create Project". Name it for the period (for example "Q3 Close").
3. Export from my accounting system and upload into Project Knowledge: the trial balance, the sub-ledger detail (AR aging, AP aging, fixed asset register), bank statements, and the prior-period close for comparison. This is data source (A) in prompt 01. NetSuite, QuickBooks, Odoo, and Xero all export these as CSV or Excel.
4. Optional, pull from the ERP directly. If my system has a connector, use it (option C). Otherwise the upload in step 3 is all I need; no integration required for a monthly cadence.
5. Set Custom Instructions: "You are a controller's close team supervised by a named controller. Every adjustment ties to a source. Never plug a difference or invent a number. Variances above materiality are explained against the GL. A named controller signs before the board package ships."
6. Run prompt 01 (the router): pick close scope and where the books live, set the materiality threshold. Then run 02 to 10: reconcile, accruals/cutoff, consolidation, flux, revenue check, board package, checklist, source-tie audit, controller sign-off.
7. Confirm the output bar: every account ties to support, material variances explained, prompt 09 blocks any untied number, and prompt 10 is the controller's signature, not the model's.
## Rules for walking me through this
- One step at a time. Tell me exactly what to export and where to upload.
- Define jargon once: Project, Project Knowledge, Custom Instructions, trial balance, sub-ledger, accrual, cutoff, flux, materiality, `<review_gate>`, `{{TOKEN}}`.
- Never tell me to use a Terminal. The vault runs from a browser; I export from my accounting system the normal way.
- Anti-pattern call-outs: if the trial balance is huge, upload it plus the open-item sub-ledgers first and add detail as prompts need it; if my firm blocks claude.ai, use Claude Enterprise with SSO; do NOT tell me a step is "not possible", give me the upload-in-pieces fallback. Never tell me to post an entry without my approval.
- A named controller signs the close. Claude reconciles, consolidates, and ties sources; the controller signs.
First message: ask me "What scope, single entity or a multi-entity consolidation, and how will you get the trial balance in, upload an export or pull from your ERP? And what is your materiality threshold?" Then start step 1.
When prompts 01 to 04 run on a real period (reconcile, accruals, consolidation), switch into "close mode" and help me build my standard close checklist so every period runs the same way.Grab the whole pack as one file, or tap any prompt below to copy it on its own. Placeholders that look like {{THIS}} get swapped for your own numbers — and if you ran Step 1, Claude fills them in for you.
The close eats 10 to 12 days and a close-automation seat every period. This runs it inside Claude on your own trial balance and sub-ledgers — reconciliation, consolidation, accruals, flux against the GL, revenue check, and the board package — every figure tied to a source, with a named controller signing before anything reaches the board.
The setup rail and every prompt above are free and stay free. The cost is your time, and the risk of wiring it wrong on live data.
Back to the prompts ↑We deliver a private close desk: the 10 prompts loaded into your Claude tenant, your chart of accounts and close checklist built in, the ERP export or connector wired, your materiality and GAAP framework set, and a source-tie gate so no untied figure reaches the board — then handed over so you own it. You cut the close from days to days without a number going unchecked.
Book a build call →Prompt set authored by consultance.ai. This is not accounting or audit advice; a named controller signs every close, and external audit is unaffected. Your financial data stays in your own Claude tenant; we never see it. Close-automation incumbents are referenced as the workflow being replaced, no affiliation implied.
Want this wired into your stack instead of running it yourself? That is our AI deal desk and finance automation service.
The AI tools, launches, and shifts that actually matter, in plain English. New library drops the moment they land.
More like this
For founders, CFOs, and deal teams: 9 Claude prompts that rebuild the cap table from the signed documents instead of the spreadsheet, run the waterfall clause by clause against the actual LPA or charter, and recompute fee and carry independently, so a stale sheet gets caught before a round closes on it.
For CFOs and finance leaders: the map of seven finance desks, deal, diligence, close, tax, underwriting, family office, and market, each one a free prompt vault that runs inside your own Claude, plus the order to install them in so a team actually adopts them.
For CFOs and controllers: 11 Claude prompts that run the month end close reconciliation itself, match bank and subledgers both directions, catch the account that will not foot, and draft the flux memo, so a 6 day close lands in 2.
The person drowning in this every week is the one who'll actually want it.
Month-End Close Automation Pack is a finance and data build in the consultance.ai AI Build Library. Prompts for controllers and CFOs to run the month-end financial close in Claude: reconcile accounts, post accruals, write flux commentary, and ship the board close package in days, not 10 to 12. It fits Controllers, CFOs, VP Finance, and founders whose team burns 10 to 12 days every period on the close and wants Big 4 rigor without the manual grind or a five-figure close-automation seat. Setup difficulty is Medium, with 4 plain-English steps.
Prompts for controllers and CFOs to run the month-end financial close in Claude: reconcile accounts, post accruals, write flux commentary, and ship the board close package in days, not 10 to 12.
It fits Controllers, CFOs, VP Finance, and founders whose team burns 10 to 12 days every period on the close and wants Big 4 rigor without the manual grind or a five-figure close-automation seat.
Medium to set up — one guided setup instruction covering 4 plain-English steps, plus 10 ready-to-run prompts on the resource page.
We would deliver a private close desk: the 10 prompts loaded into your Claude tenant, your chart of accounts and close checklist built in, the ERP export or connector wired, your materiality and GAAP framework set, and a source-tie gate so no untied figure reaches the board. Done with you, then handed over so you own it.
Prompt set authored by consultance.ai. This is not accounting or audit advice; a named controller signs every close, and external audit is unaffected. Your financial data stays in your own Claude tenant; we never see it. Close-automation incumbents are referenced as the workflow being replaced, no affiliation implied.
Month-End Close Automation Pack is the starting point. On a free AI audit we map where it fits your stack and what consultance.ai would build around it.
This build comes from our AI consulting and AI implementation practice — see the full AI in finance guide and how we work with CFO teams.