consultance.ai
Finance and data

Finance Reporting Pack — Claude vs the BI stack

AI now builds financial reporting that rivals JPMorgan analysts, packaged as 12 prompts your finance team runs on its own data. Board P&L packs, 3-statement models, variance commentary, KPI scorecards, cash forecasts, and consolidations, for the price of a Claude seat instead of Power BI plus Tableau plus a BI hire. Plus a live Reporting Stack Spend Calculator.

🔥 optional · live interactive tool

Open the Reporting Stack Spend Calculator

Browser-based. No signup. Drop in your numbers and see the trade in real time. Opens in a new tab so the prompts stay where you left them.

Power BI, plus Tableau, plus a BI hire — every month, forever.

Finance teams pay for Power BI and Tableau seats plus a dedicated BI hire to produce board packs and 3-statement models. This pack does it as 12 prompts your team runs on its own data, for the price of a Claude seat.

Source repo
https://github.com/anthropics/claude-cookbook

The code is public and free. The setup prompt below installs and wires it for you.

Step 1

Paste this setup prompt — Claude installs it for you

Easy mode · paste this into Claude

Claude installs it for you, step by step.

Never used Claude before? It is free to start. Open it in a new tab, copy the prompt, paste it in. It asks one question, then walks you through everything.

  1. Step 1
    Open claude.ai ↗

    Sign up free. No card. Takes 30 seconds.

  2. Step 2

    One click. Lands on your clipboard.

  3. Step 3
    Paste + send

    Claude asks what you need + guides you the rest of the way.

Open claude.ai ↗
Tune the prompt for your level (optional)
Preview the prompt (you do not need to read it)
I want to start building my financial reporting with the Finance Reporting Pack on my own numbers. Walk me through it.

This is NOT a Terminal or coding install. There is no `git clone`, no `npm install`, no command line. It is all inside the Claude app (claude.ai in a browser, the Claude desktop app, or the Claude add-in inside Excel). Treat me like a finance director or CFO who has never touched code.

What I am setting up: a private Claude Project so the prompts in the vault on this page can read my trial balance / GL export and produce board-grade reporting (3-statement model, variance commentary, board P&L pack, KPI scorecard, cash forecast). Nothing installs on my machine. Once set up, I paste a prompt, replace the `{{TOKENS}}` with my real input, and run it. A finance owner reviews before any report goes to the board.

Walk me through this one step at a time. Wait for me to confirm each step before moving on:

1. Open a browser and go to `claude.ai`, or open the Claude desktop app. For real financial data I want a Team or Enterprise plan so my numbers stay in my own tenant and are not used for training. Tell me how to confirm that setting. If I prefer to work in Excel, tell me how to enable the Claude add-in from the Excel ribbon instead.

2. In the left sidebar, click "Projects", then "Create Project". Name it "Finance Reporting" or the entity name.

3. In Project Knowledge, add the data the prompts will work from (the source I pick in prompt 01): my trial balance, GL export, or prior board packs as CSV or PDF. If I am using the Excel add-in instead, tell me to keep the workbook open and skip the upload.

4. In the Project's Custom Instructions box, paste this: "You are a finance reporting team supervised by a finance owner. Every figure must tie to a source document or my input. Never invent a number. Flag every report for human review before it is issued."

5. Open a new chat inside the Project. Copy prompt 01 (the reporting router) from the vault on this page. Paste it. Answer its questions (entity + basis, which report first, where my data lives, context). This configures every later prompt.

6. Run prompt 02 (3-statement model) or 05 (board P&L pack) and rebuild ONE report I already trust, so I can reconcile the output line-for-line against the version I know is right. Replace each `{{TOKEN}}` with my real input.

7. Read the output. Confirm it followed the `<output_format>`, tied every figure to a source, did not invent anything, and flagged everything per the `<review_gate>`.

8. Before any pack goes to the board, run bonus prompt B4 (source-tie auditor). A single untied figure blocks the pack.

Rules for walking me through this:

- One step at a time. Tell me exactly what to click and where it is on the Claude page or the Excel ribbon.
- Define jargon once: Project, Project Knowledge, Custom Instructions, add-in, ribbon, `<review_gate>`, `{{TOKEN}}`.
- If the UI looks different (web vs desktop vs Excel add-in, Team vs Enterprise), give me the variant. Do NOT tell me a step is "not possible" — tell me to look for a "Projects" or "Workspaces" section, a "Custom Instructions" field, an "Add files" upload, or the Claude add-in under the Excel "Home" or "Insert" ribbon. If none exist, fall back to pasting the trial balance straight into a chat.
- Never tell me to install anything via Terminal. The whole bundle runs from a browser tab, the desktop app, or Excel.
- Anti-pattern call-outs: if I say "my IT blocked claude.ai", tell me about the Team/Enterprise plan with SSO or the desktop app. If I say "I do not have a paid plan", tell me the free plan tests the first prompt but real financial work needs the firm tenant. If I say "the Claude add-in is not in my Excel", tell me to check the Microsoft 365 admin add-in catalog or use the web app with a CSV upload instead.

First message: ask me only "Are you working in claude.ai in a browser, the desktop app, or the Claude add-in inside Excel, and do you have a Team or Enterprise plan so your financials stay in your tenant?" Then start with step 1.

When prompts 01 and 02 (or 05) run cleanly and reconcile to a report I trust, switch into "DM mode" and ask me which report eats the most of my team's month so I can help wire that one live.
Step 2

Step 1 installed it. Now run these 12 prompts on your own data.

the vault

The 12 prompts

Tap a prompt to jump to it. Hit copy. Replace the tokens. Paste into Claude Opus 4.7.

where it breaks

Before you connect live data

  • • Run dummy data first. Real client data is not a test bed.
  • • API keys never go in a public repo. Use env vars and a secrets manager.
  • • Add logging, access control, monitoring, and a rollback path before launch.
  • • Read the license. Forking a repo without checking is how lawsuits start.
license note

Credit the original author

Outputs are a first pass; a qualified finance owner reviews and signs off before any report is issued. Keep financial data in your own Claude tenant. This is not accounting or audit advice.

the newsletter

AI news worth opening.

The AI tools, launches, and shifts that actually matter, in plain English. New library drops the moment they land.

100% freeNo paywall, everUnsubscribe anytime

Read this far? You want the reporting stack without Power BI plus Tableau plus a hire. Let us wire it — with a parity check before you cancel a thing.