Audit Assertions Explained With Practical Examples
By SimplyCPA · 11 October 2026
On this page (7)
- Meaning: Assertions are the claims management implicitly makes in the financial statements — that a balance exists, is complete, is correctly valued and so on.
- Transactions: Occurrence, completeness, accuracy, cutoff, classification and presentation.
- Balances: Existence, rights and obligations, completeness, accuracy valuation and allocation, classification and presentation.
- Direction of testing: Vouch from the records to source documents for existence and occurrence (overstatement); trace from source documents to the records for completeness (understatement).
- Why it matters: Auditors assess risk and design procedures at the assertion level, so most AUD questions are really asking "which assertion?"
Why assertions exist
When management presents a $2 million inventory figure, it is implicitly claiming that the inventory exists, that the company owns it, that nothing is missing, and that it's valued correctly. Each of those claims is an assertion. The auditor identifies risks of material misstatement at the assertion level and designs procedures that respond to each one.
Assertions about transactions and events
- Occurrence — recorded transactions actually happened and relate to the entity.
- Completeness — every transaction that should have been recorded was recorded.
- Accuracy — amounts and data were recorded correctly.
- Cutoff — transactions were recorded in the correct period.
- Classification — transactions were recorded in the proper accounts.
- Presentation — transactions are appropriately aggregated, described and disclosed.
Assertions about account balances
- Existence — assets, liabilities and equity actually exist.
- Rights and obligations — the entity holds or controls the rights to the assets, and liabilities are its obligations.
- Completeness — all balances that should have been recorded were recorded.
- Accuracy, valuation and allocation — balances are included at appropriate amounts and any adjustments are properly recorded.
- Classification and presentation — as above, for balances.
Matching procedures to assertions
| Procedure | Main assertion tested |
|---|---|
| Observing the physical inventory count | Existence (and completeness, if test counts are traced to the records) |
| Confirming receivables with customers | Existence |
| Searching for unrecorded liabilities (reviewing payments after year-end) | Completeness |
| Examining title deeds or loan agreements | Rights and obligations |
| Reviewing the ageing of receivables and the allowance | Valuation |
| Examining shipping documents a few days either side of year-end | Cutoff |
| Reading disclosures against the framework's checklist | Presentation |
Direction matters: Starting from the ledger and going back to invoices (vouching) can only prove that what's recorded is real — it tests existence or occurrence. Starting from shipping documents and following them into the ledger (tracing) proves nothing was left out — it tests completeness.
Practical examples by audit area
| Area | Key risk | Assertion | Practical procedure |
|---|---|---|---|
| Revenue | Sales recorded before goods ship to hit a target | Cutoff, occurrence | Match the last and first shipments around year-end to invoices and the ledger |
| Receivables | Old balances that won't be collected | Valuation | Review the ageing; test cash received after year-end; challenge the allowance |
| Inventory | Goods held on consignment counted as owned | Rights and obligations | Review consignment agreements; confirm goods held by third parties |
| Inventory | Obsolete stock carried at cost | Valuation | Compare cost with recent selling prices; review slow-moving reports |
| Payables | Invoices left unrecorded to boost profit | Completeness | Examine payments and invoices received after year-end; obtain supplier statements |
| Cash | Overstated balances | Existence | Confirm balances with banks; review bank reconciliations |
| Debt | A loan presented as noncurrent despite a covenant breach | Classification, presentation | Read loan agreements; test covenant calculations; review waivers |
| Related parties | Undisclosed transactions | Presentation (completeness of disclosure) | Review minutes, inquiries and large or unusual transactions |
Assets vs liabilities
Management is usually more tempted to overstate assets and understate liabilities. So the auditor focuses on existence for assets and completeness for liabilities — a pattern that answers a lot of exam questions on its own.
See our notes on evidence types and procedures and responding to assessed risks.