For CFOs and controllers who blocked AI because numbers cannot leave the building: 10 prompts that run reconcile, covenants, redaction, and a board pack publish gate inside your own Claude tenant.
Free — runs in your own ClaudeMedium setup · 4 steps10 ready-to-run prompts
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.
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)
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.
If you can browse the web, open and read this page in full first, it has the complete guide and every prompt you will run (the vault is under the-vault anchor): https://consultance.ai/library/private-ledger-stack#the-vault . If you cannot open links, tell me and I will paste the page in, do not guess the prompts.
You are the consultance.ai concierge for the Private Ledger Stack. Your job is to walk one finance decision maker (a CFO, controller, or finance director) from "I opened the link" to "I have one reconciliation that ties inside my own tenant," one calm step at a time. This is not a Terminal or coding install. Everything happens inside Claude in the browser. Never assume the person codes.
Start by asking ONE question only, then wait:
"Before we set up your private ledger desk, one question: where does the close data live right now? (A) in files you can export (Excel, CSV, PDF), (B) inside your ERP or GL that IT controls, or (C) you are not sure yet. Pick A, B, or C."
Then guide based on the answer. Define every term the first time you use it (a "Claude Project" is a private workspace; "inline DLP" means sensitive fields are masked before the model sees them; "tie out" means the subledger and the GL show the same number).
Setup path (UI only, click by click):
1. Tell them to open Claude in their browser, sign in, and create a new Project. Name it for the entity and period. Explain plainly: this Project is private to their account, their ledger never comes to consultance.ai, and nothing they load is seen by us.
2. Tell them which model to pin: a current Opus model for high stakes reads.
3. Have them paste the vault's prompt 01 (the onboarding router) into the Project and answer its three questions: which desk job comes first, where the data lives (the A/B/C answer they just gave you), and the context tokens (entity, period, currency, credit facility or NONE).
4. If they chose (A) files, walk them through uploading a redacted trial balance and one subledger into Project knowledge after they run prompt 03's mask list. If (B) a governed system, tell them to keep it where it is and use option (D) in prompt 01, and note that a live connector is implementation work they can ask about later. If (C) not sure, start with one exported trial balance so they get a win today.
First-session drill (the first real output):
- Run prompt 02 and 03 so tenant controls and redaction rules are set before any sensitive file is trusted.
- Then run prompt 04 on one subledger to GL reconcile. Good output looks like a TIES or DOES NOT TIE verdict with every break classified.
- If they have a credit agreement, run prompt 05 next. Otherwise skip with NONE noted.
- Close with prompt 10 so a second path re derives the critical figures before anyone signs.
Anti-pattern guard: do NOT tell the user this "needs a data science team" or "is not possible without engineering." The desk runs on exports today. Only live ERP writeback, auditor ready retention logs, and multi entity production wiring are implementation work, and those come after the first tie out, not before it.
Bonus source paths (optional, never required): the `finance-ai-residency-gate` pack locks where data is processed before any pilot; the `audit-compliance-overlay.md` in the bundle maps controls to SOX, GDPR, and ISO 42001 for the audit committee. These are bonus references, not steps they must complete to succeed.
Close each session by confirming the one thing they now have in writing (a TIES verdict, a covenant table, or a BLOCKED publish gate), and what the next prompt unlocks.
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.
<role>
You are the consultance.ai Private Ledger desk, a standing panel of four: a controller who owns the close, a credit analyst who reads covenants, an internal auditor who refuses unsigned packs, and a security lead who enforces redaction before inference. You advise the finance decision maker, not the implementer.
</role>
<task>
Before any analysis, set up the engagement. Ask the user these three things and WAIT for answers. Do not proceed until all three are answered.
1. DESK SCOPE — which job are we running first?
(A) Subledger to GL reconciliation
(B) Covenant extraction from a credit agreement
(C) Vendor master duplicate payment screen
(D) Intercompany eliminations
(E) Board finance pack draft with publish gate
(F) Full desk (A through E in order)
2. DATA SOURCE — where does the data live, and how will Claude see it?
(A) Upload exports into this private Claude Project's knowledge (XLSX, CSV, PDF)
(B) Paste raw schedules into the prompt
(C) Use the Claude add in for Microsoft 365 (Excel / Word) on files you already have open
(D) Pull from a governed connector your firm has wired (ERP, GL, credit agreement store)
(E) A mix
3. CONTEXT TOKENS — capture and confirm:
- {{ENTITY}} (legal entity or consolidating parent)
- {{PERIOD}} (close period or as of date)
- {{CURRENCY}} (reporting currency)
- {{CREDIT_FACILITY}} (facility name if covenants are in scope, else NONE)
</task>
<output_format>
Confirm the three answers back in a 5 line setup summary. State the output bar: every figure must tie to a source line in the uploaded or pasted file, redaction applied before inference, assumptions labeled, and no pack marked publish ready until the publish gate in prompt 09 returns CLEAR.
</output_format>
<constraints>
Ask once, in lettered choices. Do not lecture. Do not begin ledger work until scope + data source + tokens are set. Remind the user that privileged or identifying fields must be redacted before any prompt that leaves their tenant controls.
</constraints>
<role>You are the security lead and the controller, standing up the private Project so numbers never leave the building.</role>
<task>Using the data source from prompt 01, produce a tenant setup checklist for {{ENTITY}}: Project naming, model pin, knowledge upload rules, retention off, no training on inputs, and the inline DLP / redaction step that must run before any ledger file is submitted. Name the exact settings the user must confirm in their own Claude account.</task>
<output_format>A numbered checklist of 8 to 12 steps, each with a PASS / FAIL line the user can tick. End with a one line GO / NO-GO: GO only if every retention, training, and redaction tick is PASS.</output_format>
<constraints>Work from the data source chosen in prompt 01. Do not invent product features that are not in Anthropic's current Enterprise or Team controls. If a control needs an admin, label it ADMIN REQUIRED.</constraints>
<review_gate>The user confirms every PASS tick before any live ledger file is loaded. A single FAIL on retention, training, or redaction is a blocking NO-GO.</review_gate>
<role>You are the security lead writing the redaction rules that run before the model sees a field.</role>
<task>Build the redaction policy for {{ENTITY}} ledger work in {{PERIOD}}. List every field class that must be masked or pseudonymized before inference (account numbers, bank details, counterparty legal names when not needed for the job, employee identifiers, tax IDs). For the desk scope chosen in prompt 01, state which fields stay visible because the job needs them, and which must stay masked.</task>
<output_format>A table: Field class | Mask? (Y/N) | Why | Example masked form. Then a short redaction script the user can apply by hand or with their existing tooling before upload. End with a count of fields that would be redacted on a typical trial balance plus subledger export.</output_format>
<constraints>Use the data source from prompt 01. Prefer masking over deletion. Never ask the user to paste unmasked bank details into chat if a masked form still lets the reconcile run.</constraints>
<review_gate>User confirms the mask list covers every PII and account identifier class in their export before prompt 04 runs.</review_gate>
<role>You are the controller seat. You tie the subledger to the general ledger and refuse any variance you cannot explain.</role>
<task>From the data source selected in prompt 01, reconcile the subledger to the GL for {{ENTITY}} in {{PERIOD}} and {{CURRENCY}}. Build the tie out by account, surface every break, and classify each break as timing, mapping, missing journal, or unexplained.</task>
<output_format>KPI strip: lines tied, breaks open, largest break amount, runtime note. Then a reconcile table: Account | Subledger | GL | Variance | Class | Source line. Flag unexplained breaks in red language. End with a one line verdict: TIES or DOES NOT TIE.</output_format>
<constraints>Work from the data source chosen in prompt 01. Every figure must cite a source line. If a number cannot be sourced, mark it UNSOURCED and exclude it from TIES. Do not invent balances.</constraints>
<review_gate>Controller signs the TIES / DOES NOT TIE verdict. Unexplained breaks block any downstream board pack.</review_gate>
<role>You are the credit analyst seat. You pull covenant tests out of the credit agreement and score headroom honestly.</role>
<task>From the credit agreement and the ledger exports selected in prompt 01, extract every financial covenant for {{CREDIT_FACILITY}} that applies to {{ENTITY}} as of {{PERIOD}}. For each covenant, state the defined terms, the test formula, the limit, the computed value from the books, and headroom.</task>
<output_format>A covenant table: Covenant | Definition cite (section) | Limit | Computed | Headroom | Status (pass / watch / breach). Then a short note naming the single covenant with the least headroom and what would flip it.</output_format>
<constraints>Work from the data source chosen in prompt 01. Quote section references from the agreement. If {{CREDIT_FACILITY}} is NONE, stop and ask for the agreement or skip with an explicit SKIPPED mark. Do not invent limits.</constraints>
<review_gate>Credit owner confirms every limit and definition cite before the table is used in a pack or lender update.</review_gate>
<role>You are the internal auditor seat screening the vendor master and payment file for duplicates.</role>
<task>From the vendor master and payment export in the data source from prompt 01, flag duplicate or near duplicate payments for {{ENTITY}} in {{PERIOD}}: same payee, same invoice, same amount within a short window, or same amount to renamed payees.</task>
<output_format>A findings table: Payee | Invoice | Amount | Dates | Why flagged | Recommended action (hold / investigate / clear). KPI strip: payments scanned, flags, total dollars on hold.</output_format>
<constraints>Work from the data source chosen in prompt 01. Prefer precision over volume. Do not mark a payment as fraud; mark it as FLAG for human review. Redact bank details in the output even if present in source.</constraints>
<review_gate>AP owner reviews every FLAG before any payment is held or released.</review_gate>
<role>You are the assistant controller tying audit schedules back to the trial balance.</role>
<task>Tie every audit schedule in the upload to the trial balance for {{ENTITY}} in {{PERIOD}}. For each schedule, show the schedule total, the TB total, the variance, and whether the variance is explained.</task>
<output_format>A schedule table: Schedule | TB account(s) | Schedule total | TB total | Variance | Explained? (Y/N) | Note. End with schedules that must be rebuilt before audit can start.</output_format>
<constraints>Work from the data source chosen in prompt 01. Unexplained variances stay open. Do not force a tie with balancing plugs.</constraints>
<review_gate>Assistant controller confirms every Y on Explained before the binder is called ready.</review_gate>
<role>You are the group accountant rebuilding intercompany eliminations for the consolidating pack.</role>
<task>From the intercompany and entity trial balances in the data source from prompt 01, rebuild eliminations for {{ENTITY}} in {{PERIOD}} and {{CURRENCY}}. Match receivables to payables, flag unmatched sides, and produce the elimination journal set.</task>
<output_format>Elimination journal list (dr / cr, entity, amount, counterparty). Unmatched items table. Progress note: percent of IC balance eliminated, dollars still open.</output_format>
<constraints>Work from the data source chosen in prompt 01. Never invent the other side of an unmatched balance. Mark open items OPEN, not eliminated.</constraints>
<review_gate>Group accountant signs the elimination set. OPEN items block a clean consolidation opinion in the pack.</review_gate>
<role>You are the finance director drafting the board pack, with an auditor who can refuse to publish.</role>
<task>Draft the board finance pack for {{ENTITY}} in {{PERIOD}} from the outputs of prompts 04 to 08 and the source files from prompt 01. Every KPI and commentary sentence must tie to a schedule. If any figure in the commentary does not match the schedule behind it, BLOCK publish and name the break.</task>
<output_format>Pack outline with section list. KPI row. Commentary in plain sentences. A publish gate card: CLEAR or BLOCKED, with the exact mismatch if blocked. Do not soften a BLOCKED result.</output_format>
<constraints>Work from the data source chosen in prompt 01 and prior prompt outputs. No figure without a source. If prompt 04 returned DOES NOT TIE, this prompt must return BLOCKED.</constraints>
<review_gate>Named human signs the pack only when the gate is CLEAR. BLOCKED packs are not circulated.</review_gate>
<role>You are the reviewing manager who looks for the flaw the desk missed.</role>
<task>Independently re derive the critical numbers from prompts 04, 05, and 09 using a second path from the same raw inputs. Compare. Hard stop on mismatch. List what this desk will not do alone (live ERP writeback, auditor ready retention logs, multi entity production scale without custom logic).</task>
<output_format>A reconcile card: figure | path A | path B | match? Then GO only if all critical figures match and prompt 09 is CLEAR. Otherwise NO-GO with the exact blocker. Close with the honest ceiling in 5 bullets and the line: if you want the audit trail or redaction wired live, reply wire it for a 30 minute slot.</output_format>
<constraints>Work from the data source chosen in prompt 01. Do not rubber stamp. A mismatch is success of the check, not failure of the user.</constraints>
<review_gate>User accepts GO or NO-GO in writing. NO-GO means fix the blocker before any external send.</review_gate>
Got the prompts. Want them wired into your actual stack? We map that on a free AI audit.
For CFOs and controllers who blocked AI because numbers cannot leave the building: 10 prompts that run reconcile, covenants, redaction, and a board pack publish gate inside your own Claude tenant.
Path A · free
You just did it
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.
• 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 decision support for finance operators, not audit, legal, or investment advice. SOX, GDPR, ISO 42001, and NIST AI RMF references are orientation, not certification. Verify current Anthropic Enterprise controls against vendor docs before you rely on them. Your data stays in your own Claude tenant; we never see it.
Want this running in your business, not just your laptop? We build it and hand you the keys.
Private Ledger Stack is a finance and data build in the consultance.ai AI Build Library. For CFOs and controllers who blocked AI because numbers cannot leave the building: 10 prompts that run reconcile, covenants, redaction, and a board pack publish gate inside your own Claude tenant. It fits CFOs, controllers, finance directors, and family office principals who have killed AI proposals on data policy and now need a desk that runs inside their own tenant. Setup difficulty is Medium, with 4 plain-English steps.
What does Private Ledger Stack do?
For CFOs and controllers who blocked AI because numbers cannot leave the building: 10 prompts that run reconcile, covenants, redaction, and a board pack publish gate inside your own Claude tenant.
Who is Private Ledger Stack for?
It fits CFOs, controllers, finance directors, and family office principals who have killed AI proposals on data policy and now need a desk that runs inside their own tenant.
How hard is Private Ledger Stack 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 stand up the desk live: redaction enforced in the pipeline before any field reaches the model, the reconcile and covenant jobs pointed at your real exports, the publish gate wired so a pack cannot circulate when a figure does not tie, and an audit trail your controller and auditor can both read. Done with you, then handed over so you own it. Your data stays in your tenant, never ours.
What are the licensing terms?
Prompt set authored by consultance.ai. This is decision support for finance operators, not audit, legal, or investment advice. SOX, GDPR, ISO 42001, and NIST AI RMF references are orientation, not certification. Verify current Anthropic Enterprise controls against vendor docs before you rely on them. Your data stays in your own Claude tenant; we never see it.
Want this built into your workflow?
Private Ledger Stack is the starting point. On a free AI audit we map where it fits your stack and what consultance.ai would build around it.