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/Second Opinion on Audited Financials

Big 4 advisory

Second Opinion on Audited Financials

A second review on financials someone already signed, in your own Claude. 8 prompts test every estimate and reserve, hunt fraud flags, and write a red-flag memo before you trust the numbers.

Medium setup4 steps8 prompts
Open the setup guide Discuss an implementation
Big 4 advisory

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 set this up properly so Claude runs a second read on real financials, not a one-off chat. Walk me through it step by step, do not skip anything. Treat me like a CFO, controller, audit committee member, or deal investor who has never built a Claude Project and does not write code. Define every term once.

This is NOT a Terminal or coding install. There is nothing to compile. It is a private Claude Project where the financial statements live so every prompt reads from one place.

## The setup — a private Claude Project
Walk me through ONE step at a time, waiting for me to confirm each:

1. **What I need.** A Claude account on a paid plan so I can pin the better model. Pin **Opus 5**. Nothing to install.
2. **Make the workspace.** In Claude, create a new **Project** named for the company and period. A Project is a private workspace with its own knowledge that other chats cannot see. My statements stay in my own tenant; consultance never sees them.
3. **Load the financials.** Drop the financial statements, the footnotes, and the trial balance into the Project knowledge. If I only have a PDF annual report, that is fine, upload it.
4. **Run the vault.** Run prompt 01, pick what I am reviewing (audited annuals, a deal target, a quarter, or one area) and where my data is. Then run 02 to 08 in order: tax provision, estimates and reserves, the fraud flags, related party and revenue, the footnote tie-out, the self-check, and the red-flag memo.
5. **Gate it.** Treat prompt 07 (the self-check) as a hard stop. A **GATE: FAILED** blocks the memo until the difference is resolved. This is a first-pass review, not an audit opinion. A licensed professional signs the opinion; a named human owns the decision.

## Rules for walking me through this
- One step at a time. Define every term once: Project, knowledge, provision, deferred tax, effective tax rate, estimate, reserve, related party, revenue recognition, footnote tie-out, foot, review gate.
- Do NOT tell me a step is "not possible." If I cannot find the Project button, it is in the left sidebar of claude.ai.
- Never paste data I am not allowed to share into a public chat. Use a Project with my tenant controls.
- This finds the questions to ask before I trust the numbers or close the deal. It does not replace the auditor. Not accounting, legal, or investment advice.

First message: ask me "What are you reviewing: audited annual financials, a target in a deal, a quarter, or one area like revenue or tax? And do you have the statements and footnotes ready to upload?" Then start step 1.
Step 2 · run it on your data

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

the vault

The 8 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 8 prompts, numbered, in order · nothing left out.
Click to copy
You are my second read on a set of financials, acting as four people on every answer: a forensic accountant, a PCAOB inspector, an audit committee chair, and a controller who survived a restatement and is paranoid.

Ask me and wait:
1. What am I reviewing? (A) audited annual financials (B) a target's financials in a deal (C) a quarter (D) one area (revenue, tax, reserves)
2. Where is the data? (A) I upload the statements, footnotes, and trial balance (B) I paste tables (C) the Claude add-in for Excel
3. Context: company, period, industry, and what decision rides on this (sign off, invest, acquire, lend)?

Confirm the setup in three lines, then wait for my files. On every answer: show the number, the source line it ties to, and the assumption. Flag anything you cannot tie, never assume it. End every answer with: "First pass review, not an audit opinion. A licensed professional signs."
Click to copy
Using the data from prompt 01, re read the income tax provision. Check the effective tax rate reconciliation, the deferred tax roll-forward, and any valuation allowance judgment. Flag any rate that does not reconcile, any deferred item without support, and any provision that looks built in a hurry. Tie each figure to a source line. First pass only; a licensed professional signs.
Click to copy
Find every management estimate and reserve in the statements (allowances, impairments, accruals, fair-value marks, contingencies). For each: what drives it, whether the disclosed assumptions are reasonable, and what would change it materially. Flag the estimates with the most room for management bias. First pass only; a named human owns the call.
Click to copy
Run the fraud consideration the standard requires and auditors most often miss. Look for revenue recognition stretch, period-end cutoff games, unusual journal entries, round-number adjustments, related-party flows, and incentives to hit a number. List each flag, why it matters, and the document you would pull to confirm. This is risk identification, not an accusation. First pass only; a named human owns the call.
Click to copy
Trace the related-party disclosures and the revenue recognition policy against the numbers. Do the related-party transactions net and price the way the notes claim? Does revenue timing match the policy and the cash? Flag any gap between the story in the footnotes and the figures in the statements. Tie each to a source. First pass only; a named human signs.
Click to copy
Tie every material footnote back to the face of the statements and recompute the key totals (revenue, EBITDA, debt, equity, cash). List anything that does not foot, does not cross-reference, or is disclosed in a note but missing from the statements. Produce a clean tie-out table. First pass only; a named human signs.
Click to copy
Independently re-derive the key figures WITHOUT reusing your earlier work, then compare.
1. Recompute the effective tax rate from the source data. Compare to prompt 02. State the difference.
2. Recompute revenue and EBITDA from the source. Compare to prompt 06. State the difference.
3. Re-add every column in the tie-out table.
Rule: if any independent figure differs by more than a rounding amount, output "GATE: FAILED" with the line and both numbers, and do not produce the memo. If all tie, output "GATE: PASSED" and the checked figures. Show the re-derivation, do not assert it.
Click to copy
Only if prompt 07 returned GATE: PASSED. Write the red-flag memo: the top flags in priority order, the question to get answered for each, the document to request, and a clear "proceed, dig deeper, or walk" read for the decision from prompt 01. Plain, tight, every figure traced. First pass review, not an audit opinion; a named human signs.

From a working build to an operating system.

A second review on financials someone already signed, in your own Claude

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 would deliver a private review workspace: the prompts loaded into your Claude tenant, a connector to the documents your statements rely on, the self-check wired as a real pre-decision control, and a retained review log mapped to PCAOB AS 2401, AS 2501, and SOX 404 so the pass survives edits. Done with you, then handed over so you own it.

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. EY, KPMG, Deloitte, and PwC are referenced for public PCAOB inspection deficiency rates, no affiliation implied. Your financials stay in your own Claude tenant; we never see them. This is a first-pass review, not an audit opinion; a licensed professional signs the opinion and a named human owns the decision. Not accounting, legal, or investment advice.

Bring this workflow into your operation.

Book a build callBack to the library

Want this wired into your stack instead of running it yourself? That is our AI strategy consulting 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
Big 4 advisory
Big 4 advisory

Big 4 Consulting Prompts for Claude

Finance and ops teams run 12 Claude prompts for Big 4 consulting workflows like financial analysis and due diligence, shipping advisory work in minutes instead of weeks.

Setup guide
Big 4 advisory
Big 4 advisory

Free Big 4 Advisory Agent Kit

For PE deal teams and CFOs: three Claude agents that monitor tax and regulation exposure, read a data room like an FDD associate, and draft the IC memo. The diligence work KPMG advisors bill at $400 an hour, run in house.

Setup guide
Big 4 advisory
Big 4 advisory

The AI Output Verification Pack

For anyone who signs off on AI-assisted work: 13 Claude prompts that check every citation and quote, tie each figure to its source file or SEC filing, and block the send while a number is wrong.

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 Second Opinion on Audited Financials?

Second Opinion on Audited Financials is a big 4 advisory build in the consultance.ai AI Build Library. A second review on financials someone already signed, in your own Claude. 8 prompts test every estimate and reserve, hunt fraud flags, and write a red-flag memo before you trust the numbers. It fits CFOs, audit committee members, controllers, PE deal teams, and investors who rely on audited financials. Setup difficulty is Medium, with 4 plain-English steps.

What does Second Opinion on Audited Financials do?

A second review on financials someone already signed, in your own Claude. 8 prompts test every estimate and reserve, hunt fraud flags, and write a red-flag memo before you trust the numbers.

Who is Second Opinion on Audited Financials for?

It fits CFOs, audit committee members, controllers, PE deal teams, and investors who rely on audited financials.

How hard is Second Opinion on Audited Financials to set up?

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

How would consultance.ai build this out?

We would deliver a private review workspace: the prompts loaded into your Claude tenant, a connector to the documents your statements rely on, the self-check wired as a real pre-decision control, and a retained review log mapped to PCAOB AS 2401, AS 2501, and SOX 404 so the pass survives edits. Done with you, then handed over so you own it.

What are the licensing terms?

Prompt set authored by consultance.ai. EY, KPMG, Deloitte, and PwC are referenced for public PCAOB inspection deficiency rates, no affiliation implied. Your financials stay in your own Claude tenant; we never see them. This is a first-pass review, not an audit opinion; a licensed professional signs the opinion and a named human owns the decision. Not accounting, legal, or investment advice.

Connect this build to your workflow.

Discuss how Second Opinion on Audited Financials 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, serving businesses across the USA and Canada.

Book an audit