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/Spot Accounting Red Flags

Finance and data

Spot Accounting Red Flags

8 prompts that turn Claude into a forensic accountant for any financial statement. Catch fake cash, revenue tricks, and the red flags hiding in the footnotes before you invest, short, or lend.

Medium setup4 steps8 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 set this up properly so Claude runs as a forensic skeptic on real financials, not a one-off chat. Walk me through it step by step, do not skip anything. Treat me like an investor, CFO, analyst, auditor, or deal team member 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 financials 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 data stays in my own tenant; consultance never sees it.
3. **Load the numbers.** Drop the filing, the footnotes, and any trial balance or model into the Project knowledge. A PDF annual report or 10-K is fine. For a deal, load the target's financials from the data room.
4. **Run the vault.** Run prompt 01, pick what I am looking at (a public name, a deal target, a private company, or one red-flag area) and where my data lives. Then run 02 to 08 in order: tie profit to cash, stress revenue, hunt unconfirmable cash, find the concentration and related parties, read the footnotes, the self-check, and the skeptic's 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 screen, not a fraud finding and not a trade recommendation. A named human owns the read.

## Rules for walking me through this
- One step at a time. Define every term once: Project, knowledge, accrual, accrual ratio, cash conversion, days sales outstanding, revenue recognition, cutoff, related party, off-balance-sheet, going concern, footnote tie-out, 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 own tenant controls.
- This finds the questions to ask before I trust the numbers, short the stock, or wire the money. It does not replace the forensic accountant or auditor, and it is not an accusation. Not accounting, legal, or investment advice.

First message: ask me "What are you looking at: a public company you own or might short, a deal target, a private company that wants your money, or one area like revenue or cash? And do you have the filing 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 forensic skeptic on a set of financials, acting as four people on every answer: a forensic accountant who ties everything back to cash, a short seller looking for the reason the story is too good, a fraud examiner who has seen the tricks, and a controller who survived a restatement and now trusts nothing he cannot tie to a source.

Ask me and wait:
1. What am I looking at? (A) a public company I own or might short (B) a target's financials in a deal (C) a private company that wants my money or a loan (D) one red-flag area only (revenue, cash, related parties)
2. Where is the data? (A) I upload the filing, footnotes, and any trial balance (B) I paste the tables (C) the Claude add-in for Excel (D) a governed connector to my data room or a filings source (E) a mix
3. Context: company, period, industry, and what decision rides on this (buy, short, invest, acquire, lend, sign).

Confirm the setup in three lines, then wait for my data. On every answer: show the number, the exact source line it ties to, and the assumption behind it. If you cannot tie a figure to a source, say so and flag it, never fill the gap. This is risk identification, not an accusation. End every answer with: "First pass screen, not advice. A named human owns the read."
Click to copy
Using the data from prompt 01, reconcile reported profit to actual cash. Bridge net income to operating cash flow and name every accrual in between. Compute the accrual ratio (net income minus operating cash flow, over average assets) and the cash conversion (operating cash flow over net income) across every period I gave you. Flag any period where profit rises while cash does not follow, where the gap is widening, or where one-off items prop up the cash number. Profit is an opinion, cash is closer to a fact. Tie each figure to a source line. First pass screen, not advice; a named human owns the read.
Click to copy
Using the data from prompt 01, stress how revenue is recognized against when the money actually arrives. Look for revenue booked before cash (rising receivables or unbilled or contract assets out of step with sales), period-end cutoff games, bill-and-hold, channel stuffing, and round-trip or third-party deals that inflate the top line. Compare days sales outstanding across periods. Flag any gap between the revenue policy in the notes and the timing in the cash. Tie each flag to a source. First pass screen, not advice; a named human owns the read.
Click to copy
Using the data from prompt 01, hunt every balance that is asserted but hard to independently confirm: cash and equivalents held in escrow or with third-party trustees or in jurisdictions hard to verify, restricted cash, marketable securities marked to a model not a market, and any large balance that appears suddenly or sits with a related party. For each, ask what independent document would prove it exists (a bank confirmation, a custodian statement, a counterparty audit) and whether the filing shows it. This is exactly the gap that hid 1.9 billion euros at Wirecard. List each balance, the confirmation you would demand, and whether it is present. First pass screen, not advice; a named human owns the read.
Click to copy
Using the data from prompt 01, map concentration and related-party dependence. Find any single customer, supplier, partner, or segment that drives an outsized share of revenue, profit, or cash. Trace every related-party transaction: do the amounts net and price the way the notes claim, or do they move profit around the group? Flag any business that lives or dies on one counterparty, any related-party flow that flatters the headline number, and any partner you cannot find evidence actually exists at scale. Tie each to a source. First pass screen, not advice; a named human owns the read.
Click to copy
Using the data from prompt 01, read the footnotes, the MD&A, and the disclosures where the truth usually hides. Flag: a change of auditor or a late filing, going-concern or covenant language, off-balance-sheet vehicles and guarantees, capitalized costs that should be expensed, a pension or lease assumption doing heavy lifting, and any accounting policy that quietly changed. Pull the one sentence in the fine print that contradicts the headline story. Tie each to a source line. First pass screen, not advice; a named human owns the read.
Click to copy
Independently re-derive the key figures WITHOUT reusing your earlier work, then compare.
1. Recompute the accrual ratio and cash conversion from the raw statements. Compare to prompt 02. State the difference.
2. Recompute days sales outstanding for each period from the source. Compare to prompt 03. State the difference.
3. Recompute the largest concentration percentage from the source. Compare to prompt 05. State the difference.
Rule: if any independent figure differs from the earlier one by more than a rounding amount, output "GATE: FAILED" with the line and both numbers, and do not write 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 skeptic's memo: the red flags in priority order, why each matters, the single document you would demand to confirm or kill it, and a clear "short or avoid, dig deeper, or clean" read for the decision from prompt 01. Separate what you can prove from what you suspect. Plain, tight, every figure traced. This is risk identification and decision support, not a fraud accusation and not investment advice; a named human owns the read.

From a working build to an operating system.

8 prompts that turn Claude into a forensic accountant for any financial statement

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 forensic workspace: the prompts loaded into your Claude tenant, a connector to the filings and data-room sources your screen relies on, the self-check wired as a real pre-decision control, and a retained red-flag log mapped to PCAOB AS 2401 and the relevant standards so the screen survives edits and stands up in a memo. 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. Wirecard and EY are referenced as the public, documented failure the pack guards against, no affiliation or accusation implied. Your data stays in your own Claude tenant; we never see it. This is a first-pass screen and decision support, not a fraud finding, an audit opinion, or an investment recommendation; a named human owns the read and the relevant professional standards apply. 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 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 Spot Accounting Red Flags?

Spot Accounting Red Flags is a finance and data build in the consultance.ai AI Build Library. 8 prompts that turn Claude into a forensic accountant for any financial statement. Catch fake cash, revenue tricks, and the red flags hiding in the footnotes before you invest, short, or lend. It fits public-market investors, short sellers, CFOs, equity and credit analysts, PE diligence teams, and auditors. Setup difficulty is Medium, with 4 plain-English steps.

What does Spot Accounting Red Flags do?

8 prompts that turn Claude into a forensic accountant for any financial statement. Catch fake cash, revenue tricks, and the red flags hiding in the footnotes before you invest, short, or lend.

Who is Spot Accounting Red Flags for?

It fits public-market investors, short sellers, CFOs, equity and credit analysts, PE diligence teams, and auditors.

How hard is Spot Accounting Red Flags 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 forensic workspace: the prompts loaded into your Claude tenant, a connector to the filings and data-room sources your screen relies on, the self-check wired as a real pre-decision control, and a retained red-flag log mapped to PCAOB AS 2401 and the relevant standards so the screen survives edits and stands up in a memo. Done with you, then handed over so you own it.

What are the licensing terms?

Prompt set authored by consultance.ai. Wirecard and EY are referenced as the public, documented failure the pack guards against, no affiliation or accusation implied. Your data stays in your own Claude tenant; we never see it. This is a first-pass screen and decision support, not a fraud finding, an audit opinion, or an investment recommendation; a named human owns the read and the relevant professional standards apply. Not accounting, legal, or investment advice.

Connect this build to your workflow.

Discuss how Spot Accounting Red Flags 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