What a first audit actually asks for
Founders prepare for an audit as if it checks whether the numbers are right. It checks whether you can prove they are. That is a different, and larger, ask.
Most founders walk into a first audit expecting a grade on their numbers: right or wrong. An audit asks a harder question. Not "is this number correct," but "show me how you know." The shift from assertion to evidence is what catches first-timers, and it is the whole game.
The short version
- An audit tests whether you can prove your numbers, not only whether they are right.
- It probes three things: the evidence behind each number, your documented judgment, and cutoff and controls.
- Fieldwork is a small slice of the timeline. Preparation is the long pole, and it starts earlier than most expect.
- "We have the number" is not "we can support it." The gap between them is the work.
What you think it asks, and what it asks
You think the question is whether the numbers are right. The question is whether you can support them. An auditor does not take a figure on trust. They select samples and test them against evidence, and a number you are confident in but cannot evidence is, in their eyes, unsupported.
This is why founders who "know their numbers cold" can still have a rough first audit. Knowing the number is not the deliverable. Being able to hand over the contract, the bank statement, and the schedule that ties it to the ledger is the deliverable.
An audit is not a test of whether your numbers are right. It is a test of whether you can prove they are.
What you have
"$2.4M in revenue this year, and we know it is right."
What the audit needs
- Signed contracts for the sampled deals
- A revenue recognition memo behind the policy
- Revenue by customer that ties to the ledger
- Cutoff testing around period end
Knowing the number is not the deliverable. Being able to evidence it, the way an outsider can follow without your narration, is. Illustrative.
The three things it actually probes
Underneath a long request list, an audit is really examining three things.
- Evidence behind the number. Contracts, bank statements, and schedules that reconcile to the ledger. Everything material needs support an outsider can follow without your narration.
- Documented judgment. Your positions on revenue recognition, capitalization, and stock compensation, written down. Not just the entry, but the memo explaining why. An undocumented judgment is a question waiting to be asked.
- Cutoff, timing, and controls. Did revenue and expenses land in the right period, and who is able to change the books. A first audit also forms a view on whether your process can be relied on at all.
Why it starts earlier and takes longer than you think
Fieldwork is the visible part, and the short part. The real work is the months before it: assembling support, writing the memos, reconciling every material account. Companies that begin near fieldwork scramble through it. Companies that begin months ahead treat fieldwork as a formality.
Fieldwork, review, and the opinion are a narrow slice of the calendar. Preparation is the long pole. The companies that struggle are the ones that begin near fieldwork instead of months ahead. Illustrative.
None of this means the accounting has to be flawless on day one. It means the support has to exist, the judgments have to be written down, and the timeline has to respect how long that takes. The first audit is a documentation exercise as much as an accounting one, and the founders who treat it that way are the ones who pass it without drama.
Facing your first audit?
A working session shows you what the auditor will test, how far off your support is, and the order to close the gap, before fieldwork. A sample of the work, not a sales call.
Request a consultation →