Your bank just asked for audited financial statements before it renews your line of credit, and the engagement letter from the CPA firm reads like a foreign language: management assertions, walkthroughs, tests of controls, substantive procedures, sampling. You signed it anyway, and now a cheerful senior associate has emailed you a "PBC list" — Provided By Client — with 60 line items and a polite request for "read-only access to everything." What happens next is not a bookkeeping tidy-up contest. The auditors are running a structured interrogation of five specific claims you made the moment you handed them your financial statements, and understanding those claims is the difference between a smooth fieldwork week and a month of follow-up requests that reads like an exam you did not study for.
This guide explains what auditors actually test: the five management assertions behind every number on your statements, the procedures they run against each one, why they test samples instead of everything, and how to prepare your books so fieldwork ends on schedule.
The Five Claims Hiding Inside Your Financial Statements
When management presents financial statements, auditing standards treat that presentation as a bundle of implicit claims called management assertions. Under AICPA standards (AU-C 500 and related sections), every reported balance rests on them. The auditor's entire job is gathering enough evidence to say these claims hold, at least for anything big enough to matter — the concept of materiality, covered below.
The classic five, for account balances at period end, are:
- Existence. The assets, liabilities, and equity interests reported actually exist at the balance-sheet date. Your reported equipment is really in the warehouse; the liabilities are real obligations.
- Completeness. Nothing that should be recorded has been left out. All of the period's liabilities, including bills received after year-end for December work, made it into the books.
- Valuation and allocation. Amounts are measured correctly and assigned to the right accounts and periods. Receivables reflect what you will actually collect, inventory is stated at the lower of cost or market, and December revenue is not hiding January shipments.
- Rights and obligations. The company actually owns the assets and actually owes the liabilities. Leased equipment is not presented as owned, and a loan your sister company owes is not sitting on your balance sheet.
- Presentation and disclosure. Items are classified correctly and the footnotes say what they must. A loan due in full next March is current, not long-term, and the related-party lease is disclosed rather than buried.
For transactions during the period, the same ideas wear slightly different names — occurrence, completeness, accuracy, cutoff, and classification — but the logic is identical: did it happen, did all of it get recorded, at the right amount, in the right period, in the right account.
Notice the pairing that drives most audit work: existence guards against overstatement (things recorded that should not be), while completeness guards against understatement (things missing that should be there). Auditors test the two in opposite directions. To test existence, they start from your books and trace outward to reality — pick recorded receivables and confirm them with customers. To test completeness, they start from reality and trace back into your books — pick shipping documents or vendor invoices and check each one was recorded. Remember that directional logic and half the auditor's requests suddenly make sense.
Substantive Procedures: How Each Assertion Gets Tested
Substantive procedures are the tests that speak directly to whether the numbers are right, as opposed to tests of controls, which check whether your processes would catch errors. Auditors mix two kinds: tests of details and substantive analytical procedures.
Confirmations: existence and rights, straight from third parties
A confirmation asks an outside party to verify a balance directly with the auditor — not through you. The classic case is accounts receivable: the auditor selects customer accounts and mails or electronically sends confirmation requests asking the customer to agree or disagree with the amount owed. Bank confirmations verify cash balances, loans, and borrowing terms; legal confirmations ask your attorney about pending litigation and unasserted claims.
Confirmations are prized because the evidence comes from outside your company, which makes it harder to fake. Your job is to make them painless: keep customer contact details current, respond fast when the auditor asks you to nudge a non-responding customer, and understand that a confirmation reply the customer sends to you instead of the auditor is worthless — the chain of custody is the point.
Observation: existence and condition, with their own eyes
For inventory, AU-C 501 effectively requires the auditor to attend your physical count when inventory is material, unless doing so is genuinely impractical. They watch your team's count procedures, do their own test counts of selected items, and note the condition of what they see — dusty, obsolete, or damaged goods raise valuation questions on the spot.
If you count only at year-end with a skeleton crew and no written instructions, expect this to be the most stressful day of fieldwork. Cycle-count programs with documented procedures, pre-numbered count tags, and a clean cutoff make observation boring, which is exactly what you want.
Cutoff testing: the right period, not just the right amount
Cutoff is where small businesses most often stumble. The auditor pulls the last few shipping documents and receiving reports before year-end and the first few after it, then checks each landed in the correct period's sales, purchases, inventory, and payables. A December 31 shipment recorded as January revenue understates this year and overstates next year; a January vendor bill for December services that never gets accrued understates liabilities.
Clean cutoff starts with clean books: record shipments and receipts by their actual dates, accrue known year-end bills, and keep bills of lading and receiving logs where you can find them in February.
Inspection, recalculation, and reperformance: trust, then verify
Auditors inspect documents and assets (invoices, contracts, loan agreements, board minutes), recalculate your math (depreciation schedules, loan amortization, the allowance for doubtful accounts), and occasionally reperform your procedures. The allowance is a favorite target: they will age your receivables, compare your historical write-off rates to the reserve, and ask pointed questions about any large past-due balance you reserved at zero.
Estimates get special scrutiny because they are where honest judgment and wishful thinking look identical on paper. Document your assumptions — why this bad-debt percentage, why that warranty rate — before the auditor asks.
Analytical procedures: does the story hang together
These compare recorded amounts to expectations: current year versus prior year, gross margin versus industry norms, payroll expense versus headcount, interest expense versus average debt. A stable business whose revenue jumped 40 percent while cost of goods barely moved has some explaining to do. Analytics rarely prove a balance on their own, but they decide where the detailed testing goes. If your margins swung wildly and you cannot articulate why, expect that account to get the full sample treatment.
Walkthroughs and Tests of Controls: Testing the Machine, Not Just the Output
Before or alongside substantive testing, auditors map how transactions flow through your business. A walkthrough follows one transaction of each major type from initiation to the financial statements — a sale from quote to cash collection, a purchase from requisition to payment — with the auditor asking questions and watching controls operate at each step. The three-way match of purchase order, receiving report, and vendor invoice before payment is the textbook example.
If your controls look well-designed, the auditor may test them across a sample of transactions and then do less substantive work — good controls earn you a lighter detail-testing load. If the walkthrough reveals that the same person orders, receives, and pays for inventory with no review, the auditor skips control reliance entirely and expands substantive testing instead. That expansion costs you twice: more of your staff's time pulling documents, and often a higher fee, since substantive work is labor-intensive.
Small businesses usually fail the segregation-of-duties ideal, and auditors know it. Compensating controls — an owner who reviews the bank reconciliation, approves every disbursement over a threshold, and signs off on payroll changes — can partially fill the gap. The key word is documented: a review nobody can evidence might as well not have happened.
Sampling: Why They Check 25 Invoices Instead of 25,000
Nobody re-performs your whole year. Auditors set materiality — the largest misstatement that would not change a reader's decision, often derived as a percentage of revenue, assets, or pre-tax income — and then design samples that give reasonable assurance nothing above that threshold slipped through. A typical detail sample might be 25 to 60 items per account, selected to cover large or unusual items individually plus a random or systematic pull of the rest.
Two practical consequences follow. First, the odd items get picked: round-dollar journal entries posted late at night, entries to rarely used accounts, anything just under an approval threshold. Post clean, well-described journal entries with supporting attachments and you remove most of the temptation. Second, every error found in a sample gets projected across the population. One pricing error in 30 sampled invoices becomes an estimated misstatement for all invoices — so a single sloppy process, not a single sloppy entry, is what fails.
The Mistakes That Extend Fieldwork
Across small-business audits, the same findings recur:
- Unreconciled balance-sheet accounts. Bank accounts, credit cards, loans, and intercompany balances that nobody reconciled monthly become multi-day archaeology projects in fieldwork.
- Stale receivables and missing reserves. A two-year-old invoice carried at full value with no allowance invites the auditor to question every estimate you made.
- Cutoff errors. Late postings around year-end, unrecorded liabilities, and revenue recognized on shipment terms you cannot document.
- Undocumented related-party transactions. Loans to owners, leases with family entities, and personal expenses through the business need agreements, market-rate support, and disclosure — discovered mid-audit, they look like concealment even when they were laziness.
- Commingled personal and business activity. Every personal transaction in the business accounts is a completeness and classification problem the auditor must untangle by hand.
Each finding costs more than the adjusting entry: it erodes the auditor's assessment of your control environment, which expands testing everywhere else.
Getting Your Books Audit-Ready
Start before year-end, not when the PBC list arrives. Reconcile every balance-sheet account monthly so December's reconciliation is routine. Accrue what you owe: year-end payroll earned but unpaid, unbilled vendor work, warranty obligations. Age your receivables and support your allowance with history, not hope. File contracts, loan agreements, leases, and board minutes where someone other than you can find them. And freeze the period — late entries after you hand over the trial balance force the auditor to re-verify everything downstream.
Plain-text accounting users can encode this discipline directly in the ledger. A year-end wage accrual with its January reversal is explicit rather than implied:
2025-12-31 * "Accrue Dec 28-31 wages, paid Jan 08" ^payroll-accrual
Expenses:Payroll:Wages 18,400.00 USD
Liabilities:Accrued-Payroll -18,400.00 USD
2026-01-08 * "Pay Dec 28-31 wages, reversing accrual" ^payroll-accrual
Liabilities:Accrued-Payroll 18,400.00 USD
Assets:Checking -18,400.00 USDThe linked tag lets anyone — auditor included — trace the accrual to its reversal in seconds, which is precisely the completeness-to-existence round trip described above. Clean sub-accounts for accruals, prepaids, and reserves, plus dated memos on every estimate, turn the PBC list from a scavenger hunt into a file export. If you keep your books this way, the Beancount documentation covers accrual patterns and report queries in more depth, and Fava gives the auditor-friendly balance sheet and income statement views straight from the same file.
When fieldwork starts, designate one person with authority to answer questions and pull records, respond to sample requests within a day, and never hand over a schedule you have not tied to the trial balance yourself. Auditors are professionally skeptical of numbers their client has not reconciled — be the client whose numbers always tie, and the assertions test themselves.
