Study smarter with Fiveable
Get study guides, practice questions, and cheatsheets for all your subjects. Join 500,000+ students with a 96% pass rate.
Audit assertions are the foundation of every audit engagement—they're the specific claims management makes about the financial statements that auditors must verify. When you're tested on auditing, you're not just being asked to list assertions; you're being evaluated on your ability to match assertions to audit procedures, identify which assertions carry the highest risk for specific accounts, and explain why certain tests address certain assertions. Understanding the logic behind each assertion transforms rote memorization into practical audit thinking.
These assertions fall into distinct categories based on what is being tested: account balances at period-end, transaction classes during the period, and presentation in the statements themselves. Don't just memorize the nine assertions—know which category each belongs to, what audit evidence addresses it, and how misstatements related to that assertion would distort the financial statements. This conceptual framework is what separates strong exam performance from weak recall.
These assertions address the fundamental question: Did this actually happen, and does it actually exist? They protect against overstatement by ensuring reported items are real and transactions genuinely occurred.
Compare: Existence vs. Occurrence—both confirm something is "real," but existence applies to account balances (does this asset exist now?) while occurrence applies to transactions (did this sale happen?). FRQs often test whether you can match the right assertion to the right account type.
These assertions ensure nothing is missing and everything is recorded in the right period. They protect against understatement—the opposite risk direction from existence and occurrence.
Compare: Completeness vs. Cut-off—completeness asks "is it recorded?" while cut-off asks "is it recorded in the right period?" Both can cause understatement in one period and overstatement in another. When analyzing revenue manipulation, consider both assertions together.
These assertions address whether recorded amounts are correct—not just whether items exist, but whether they're stated at appropriate values using proper calculations.
Compare: Accuracy vs. Valuation—accuracy is about computational correctness (did you multiply correctly?), while valuation is about measurement appropriateness (did you use the right method and assumptions?). An inventory balance can be accurately calculated but improperly valued if obsolete items aren't written down.
These assertions confirm the entity's legal relationship to reported items and whether those items are properly categorized in the financial statements.
Compare: Rights and Obligations vs. Classification—rights addresses legal ownership (do we own it?), while classification addresses proper categorization (where does it belong in the statements?). An entity might have clear rights to an asset but misclassify it between current and non-current categories.
This assertion ensures the financial statements communicate information clearly and completely to users, meeting all applicable reporting requirements.
Compare: Classification vs. Presentation and Disclosure—classification is about putting items in the right accounts, while presentation and disclosure is about how those accounts appear in the final statements and whether accompanying disclosures are adequate. Both affect financial statement usability.
| Concept | Best Examples |
|---|---|
| Overstatement Risk | Existence, Occurrence, Valuation |
| Understatement Risk | Completeness, Cut-off |
| Balance Sheet Assertions | Existence, Rights and Obligations, Valuation, Completeness |
| Transaction Assertions | Occurrence, Completeness, Accuracy, Cut-off, Classification |
| Presentation Assertions | Presentation and Disclosure, Classification, Accuracy |
| Judgment-Heavy Testing | Valuation, Presentation and Disclosure |
| Document-Based Testing | Rights and Obligations, Occurrence, Cut-off |
Which two assertions both protect against overstatement but apply to different elements of financial statements (balances vs. transactions)?
If an auditor traces shipping documents to recorded sales entries, which assertion is primarily being tested—and why does the direction of testing matter?
Compare and contrast accuracy and valuation: How could an inventory balance satisfy the accuracy assertion but fail the valuation assertion?
An FRQ describes a company that recorded a sale on December 28 for goods shipped January 3. Which assertion is violated, and what audit procedure would detect this?
For accounts payable, why is completeness typically a higher-risk assertion than existence, and what does this imply about the direction of audit testing?