Explore the build library
consultance.ai
Deal Copilot
Build libraryControlsAboutCase studiesBlogBook an audit
consultance.ai

Systems

WorkflowsDeal CopilotPrivate knowledgeFinance automationBuild library

Company

About usCase studiesBlogContact

Start a conversation

Free AI auditfounder@consultance.ai

Teams

Investment bankingCFOs & financePrivate equityPrivate creditReal estateProperty managementProfessional servicesOther industriesAll industries

Legal

Privacy policyTerms of service

Our approach

Audit the workflow.Build in your environment.Hand over a system you own.
Build something useful © 2026 consultance.ai
Build library/Month-End Close Automation Pack

Finance and data

Month-End Close Automation Pack

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.

Medium setup4 steps10 prompts
Open the setup guide Discuss an implementation
Finance and data

Start with the guided setup

Follow the setup below in your own workspace. For a demonstration of the prompt-copying process, open the optional walkthrough.

Watch the setup walkthrough
Step 1 · setup
Three minutes, four steps, nothing to install by hand

Claude sets it up for you. You just paste.

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.

  1. Tell Claude how to talk to you

    One tap. It changes how much Claude explains, and how slowly it goes. You can change it any time.

  2. Copy your setup instruction

    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.

  3. Open Claude in a new tab

    Free account, no card, 30 seconds. This tab stays open so you can come back.

    Open claude.ai
  4. Paste, send, and answer one question

    Claude reads this page, asks one question about your work, then guides you step by step until your first output is right. If anything looks wrong, tell Claude what you see, and it fixes it with you.

▸Prefer the full prompt instead of the link? (optional)
Click to copy
I am comfortable copy-pasting and following instructions, but I am not a developer.
There is nothing to install for this one and no commands to type: it all happens inside Claude. If any instruction below implies a Terminal, translate it into the equivalent click path for me instead.
- Plain English. Define jargon the first time it appears.
- One step at a time, then wait for me to confirm before the next one.
- Tell me what success looks like at each step, and diagnose any error before moving on.

Follow the instructions below with those rules applied.

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 5. 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.
Step 2 · run it on your data

Step 1 set it up. These 10 prompts do the work.

the vault

The 10 prompts

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.

One .md file · all 10 prompts, numbered, in order · nothing left out.
Click to copy
<role>
You are a controller's close team in one: a staff accountant who reconciles, a senior who reviews, a consolidations lead, and a controller who signs. You replace the mechanical grind, not the controller's judgment.
</role>

<task>
Before any work, set up the close. Ask me to confirm each block, present lettered options, and WAIT.

1. CLOSE SCOPE — what are we closing?
   (A) Single entity month-end
   (B) Multi-entity consolidation
   (C) Quarter-end with board package
   (D) A specific area (revenue, AP/AR, payroll, intercompany)

2. WHERE DO THE BOOKS LIVE? This decides how every later prompt runs.
   (A) Upload exports into this Claude Project (trial balance, sub-ledgers, bank statements, prior-period close)
   (B) Paste figures or a TB excerpt
   (C) Pull from your ERP/GL via the relevant connector (NetSuite, QuickBooks, Odoo, your warehouse)
   (D) A mix

3. CONTEXT — entity/entities {{ENTITY}}, period {{PERIOD}}, GAAP framework {{GAAP}}, materiality threshold {{MATERIALITY}}.

4. OUTPUT BAR — confirm: every adjustment ties to a source, nothing is invented, variances above {{MATERIALITY}} are explained, and a named controller signs before the board package ships.
</task>

<output_format>Confirm the four answers in one block, then: "Close desk live. Load the trial balance the way you chose, then run prompt 02." Do not work yet.</output_format>

<review_gate>Stop. Wait for my answers before proceeding.</review_gate>
Click to copy
<role>You are a Big 4 audit senior reconciling the balance sheet account by account.</role>
<task>For {{PERIOD}}, reconcile each balance sheet account to its supporting detail: cash to bank, AR to aging, AP to aging, prepaids, accruals, fixed assets to the register. Flag every unreconciled difference.</task>
<output_format>Reconciliation status per account: balance | support | difference | status (tied/open). Then an open-items list ranked by size.</output_format>
<constraints>Use the data source from prompt 01. Every balance ties to support. Differences above {{MATERIALITY}} are flagged, never plugged.</constraints>
<review_gate>Senior clears open items before prompt 03.</review_gate>
Click to copy
<role>You are a senior accountant enforcing cutoff and completeness.</role>
<task>For {{PERIOD}}, identify required accruals and prepaids, test revenue and expense cutoff against supporting documents, and flag anything recorded in the wrong period.</task>
<output_format>Accrual schedule (each sourced), cutoff exceptions, and proposed adjusting entries for controller approval.</output_format>
<constraints>Use the data source from prompt 01. Propose entries; never post without controller sign-off. Cite the support for each accrual.</constraints>
<review_gate>Controller approves entries before they post.</review_gate>
Click to copy
<role>You are a consolidations lead eliminating intercompany and rolling up the group.</role>
<task>For {{ENTITY}}, reconcile intercompany balances, identify eliminations, apply any currency translation, and roll the entities into a consolidated trial balance.</task>
<output_format>Intercompany reconciliation, elimination entries, translation summary, and the consolidated TB with the bridge from standalone to consolidated.</output_format>
<constraints>Use the data source from prompt 01. Every elimination ties to both sides. Flag intercompany that does not net to zero.</constraints>
<review_gate>Controller confirms eliminations before consolidation is final.</review_gate>
Click to copy
<role>You are a controller writing the variance commentary the board will question.</role>
<task>Compare {{PERIOD}} to prior period and to budget. For every variance above {{MATERIALITY}}, write the explanation tied to the underlying GL activity, not a guess.</task>
<output_format>Flux table: account | current | prior | budget | variance | explanation (with GL reference). Material variances first.</output_format>
<constraints>Use the data source from prompt 01. Every explanation cites the driving GL line. No hand-waving on a material variance.</constraints>
<review_gate>Controller owns the commentary before it reaches the board.</review_gate>
Click to copy
<role>You are a revenue accountant confirming ASC 606 / IFRS 15 treatment.</role>
<task>For {{PERIOD}}, test that revenue is recognized correctly: performance obligations, timing, deferrals, and any contract requiring judgment. Flag aggressive or premature recognition.</task>
<output_format>Revenue test by stream: recognized | basis | standard reference | flag. Then a list of contracts needing judgment.</output_format>
<constraints>Use the data source from prompt 01. Cite the standard for every treatment. Flag, never normalize aggressive recognition.</constraints>
<review_gate>Controller reviews flagged contracts before close.</review_gate>
Click to copy
<role>You are a VP Finance assembling the package the board reads.</role>
<task>From the reconciled, consolidated books, build the close package: P&L, balance sheet, cash flow, the flux commentary, and the one-page CFO summary.</task>
<output_format>Close package: three statements, flux commentary, one-page summary. Every figure ties to the TB.</output_format>
<constraints>Use the data source from prompt 01. No figure that does not tie to the consolidated TB. Label any estimate.</constraints>
<review_gate>NAMED controller signs the package before it reaches the board.</review_gate>
Click to copy
<role>You are running the close PMO so nothing is missed.</role>
<task>Build the close checklist: every task, owner, dependency, and status, with the critical path that determines the close date.</task>
<output_format>Checklist: task | owner | dependency | status. Plus the critical path and the current projected close day.</output_format>
<constraints>Use the data source from prompt 01. Flag any task blocking the critical path. No task closes without its review gate met.</constraints>
<review_gate>Controller confirms the checklist is complete before sign-off.</review_gate>
Click to copy
<role>You are the desk's check: every number in the package must trace to a source.</role>
<task>Scan the close package. For every figure, confirm it ties to the trial balance, a reconciliation, or an approved entry. List anything that does not tie. A single untied number blocks the package.</task>
<output_format>Pass/fail per figure, then a BLOCK list of untied numbers. GO only if the BLOCK list is empty.</output_format>
<constraints>Use the data source from prompt 01. No figure passes on trust. Untied = blocked.</constraints>
<review_gate>This auditor informs the controller; the controller still signs.</review_gate>
Click to copy
<role>You are the controller giving final close approval.</role>
<task>Confirm every account is reconciled, every material variance is explained, every required entry is posted and approved, and the source-tie auditor returned GO. Produce the sign-off memo.</task>
<output_format>Sign-off memo: scope, open items resolved, exceptions noted, and the explicit statement of what is being signed.</output_format>
<constraints>Use the data source from prompt 01. Do not sign with open material items. This gate is the human's, not the model's.</constraints>
<review_gate>The named controller signs. The model prepares the memo; the human signs it.</review_gate>

10 to 12 days of quarter-end all-nighters, every period, forever.

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.

Path A · free

Run the build independently

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
Path B · done with you

Connect it to your operation

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
data safety

Before you use live numbers

  • • Run last quarter's numbers first. Live data is not a test bed.
  • • Nothing here uploads to us. It runs in your own Claude account, on your own machine.
  • • A named human reviews and signs every output before it reaches a board, lender, or client.
  • • Mask account numbers and names to the minimum the task needs.
the fine print

Straight answers on ownership

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.

Read this far? You're done burning 10 to 12 days on the close. Let us build the desk — source-tied, with a controller signing before the board.

Book a build callBack to the library

Want this wired into your stack instead of running it yourself? That is our AI deal desk and finance automation service.

Newsletter

New builds, as they ship

One short note when a new build ships: what it does, who it is for, and how to run it in your own Claude.

Free. One email a week at most. Unsubscribe in one click.

More like this

Related builds

All builds
Finance and data
Finance and data

Month End Close AI Agent Team

For controllers and CFOs: a 12 agent month end close team in your own Claude that preps reconciliations, accruals, entries and flux notes as a structured review. You approve every ledger post.

Setup guide
Finance and data
Finance and data

Ramp Claude Connector Setup Guide

For controllers and finance ops teams on Ramp: Claude setup steps plus 12 read only prompts for spend baseline, close readiness, accruals and flux. Replaces the manual Ramp export to Excel.

Setup guide
Finance and data
Finance and data

Claude and NetSuite Setup Guide

For controllers, CFOs and FP&A leads on NetSuite: the setup steps for Oracle's Claude connector plus 12 read only prompts for close, receivables, payables and cash.

Setup guide
Get the free kitBook a call

Share with your workflow owner.

Bring the relevant team into the conversation with the build and setup guide.

Forward by email
in one line

What is Month-End Close Automation Pack?

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.

What does Month-End Close Automation Pack do?

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.

Who is Month-End Close Automation Pack for?

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.

How hard is Month-End Close Automation Pack to set up?

Medium to set up — one guided setup instruction covering 4 plain-English steps, plus 10 ready-to-run prompts on the resource page.

How would consultance.ai build this out?

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.

What are the licensing terms?

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.

Connect this build to your workflow.

Discuss how Month-End Close Automation Pack fits your systems, controls, and team. We define the integration, review process, and deployment requirements with you.

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.

Book an audit