Audit Assertions Explained: Examples and Audit Procedures
Audit assertions are the claims management makes, explicitly or implicitly, when it prepares financial statements. The main ones are existence, occurrence, completeness, accuracy, cutoff, valuation and allocation, rights and obligations, and classification, presentation, and disclosure. Auditors test the relevant assertions to find possible misstatements and decide what evidence they need.
For CPA AUD candidates and accounting students, the easiest way to learn them is to ask three questions every time: What could be wrong? Which assertion is affected? What evidence would address that risk?
This guide covers eight study concepts, practical audit procedures, and common exam mistakes. The eight concepts line up closely with the AICPA framework used for audits of nonissuers, which are mostly private companies, with classification and presentation combined into one row. The PCAOB groups the same ideas into five categories for audits of issuers, which are mostly public companies. We compare both below.
Written by Professor Mansour Farhat, DBA, CPA, CIA. Last updated October 30, 2026. Checked against PCAOB AS 1105 and AICPA AU-C section 315.
What Are Audit Assertions?
Management, not the auditor, is responsible for preparing the financial statements. So every number management reports carries built-in claims about the transactions, balances, and disclosures behind it. These claims are called management assertions or financial statement assertions.
For example, a reported inventory balance conveys that the inventory exists, that the company holds the relevant rights, and that the amount is appropriate under the applicable accounting requirements. Each claim can be misstated for a different reason and may require different evidence.
The auditor focuses on the relevant assertions, meaning the ones where a material misstatement could reasonably occur, and tests them by obtaining sufficient appropriate audit evidence. ‘Sufficient’ refers to how much evidence you have, and ‘appropriate’ refers to its quality, meaning its relevance and reliability. A material misstatement is an error or omission that could reasonably be expected to influence the decisions of people who rely on the financial statements.
Assertions themselves do not provide assurance. An audit provides reasonable assurance, which is a high but not absolute level of assurance, about whether the financial statements are free from material misstatement. It does not guarantee that every error or fraud will be found.
Video: How Management Assertions Guide an Audit
Watch Professor Farhat explain explicit and implicit management assertions and how they guide audit objectives, procedures, and evidence collection. This excerpt covers the opening 4 minutes and 39 seconds of his audit assertions lesson.
What else the full 28-minute lesson covers:
- 9:51: Transaction assertions (occurrence, completeness, accuracy, cutoff, classification, and presentation)
- 18:00: Account balance assertions (existence, completeness, valuation, and rights and obligations)
- 24:36: How the AICPA and PCAOB assertion frameworks compare
- 26:30: Example: testing the existence assertion with confirmations
Watch the full audit assertions lesson on the Farhat Lectures YouTube channel. Continue with the table below to connect each study concept with a possible misstatement and an example audit procedure.
What Are the Main Audit Assertions? Examples and Procedures
The table combines classification, presentation, and disclosure into one study concept. Its procedures are illustrations rather than complete audit programs. The auditor selects procedures based on the circumstances, assessed risks, and reliability of the available evidence.
| Study concept | Meaning | Possible misstatement | Example audit procedure |
|---|---|---|---|
| 1. Existence | Recorded balances represent items that exist at the reporting date. | The inventory listing includes nonexistent goods. | Select items from the listing and physically inspect them during inventory count attendance. |
| 2. Occurrence | Recorded transactions happened and relate to the entity. | A sale was recorded for an order that was never fulfilled. | Vouch the recorded sale to the customer order, shipping evidence, and relevant contract terms. |
| 3. Completeness | All items that should be recorded or disclosed are included. | A supplier obligation existing at year-end is omitted. | Examine subsequent payments and supporting invoices for unrecorded year-end liabilities. |
| 4. Accuracy | Transaction amounts and other data are recorded appropriately. | An invoice uses an incorrect quantity or price. | Recalculate the invoice and compare its inputs with supporting records. |
| 5. Cutoff | Transactions are recorded in the appropriate accounting period. | January revenue is recorded in December. | Inspect transactions around year-end and compare recognition dates with contractual terms and shipping evidence. |
| 6. Valuation and allocation | Reported amounts include appropriate measurements, estimates, and allocations. | The allowance for credit losses is understated. | Evaluate the allowance methodology, assumptions, underlying data, and relevant collection evidence. |
| 7. Rights and obligations | The entity holds or controls the rights to its reported assets, and the reported liabilities are its obligations. | Goods held for another owner are included in inventory. | Inspect purchase and consignment agreements to determine the company’s rights. |
| 8. Classification, presentation, and disclosure | Items are assigned to appropriate accounts, presented clearly, and adequately disclosed. | Debt is misclassified or a required restriction disclosure is omitted. | Inspect agreements and compare the classification and notes with applicable reporting requirements. |
Measurement reminder: Valuation does not require every asset to be measured at fair value. The appropriate basis depends on the accounting requirements for the item. Allocation may involve depreciation or amortization; assigning an item to the proper account is a classification issue.
How the AICPA Groups Audit Assertions (AU-C 315)
For audits of nonissuers, such as private companies, the AICPA’s auditing standards apply. AU-C section 315, as updated by Statement on Auditing Standards (SAS) No. 145, splits the assertions into two groups. SAS No. 145 is effective for audits of financial statements for periods ending on or after December 15, 2023.
| Group | Assertions |
|---|---|
| Classes of transactions and events, and related disclosures (for the period) | Occurrence, completeness, accuracy, cutoff, classification, presentation |
| Account balances, and related disclosures (at period end) | Existence, rights and obligations, completeness, accuracy, valuation, and allocation (one combined assertion), classification, presentation |
Notice the pattern. Occurrence and cutoff apply only to transactions. Existence and rights and obligations apply only to balances. Completeness, classification, and presentation show up in both groups. Disclosures are no longer a separate third group; they are built into each assertion.
Older textbooks may show 13 assertions in three groups: transactions, account balances, and presentation and disclosure. That list came from the AICPA standard before SAS No. 145. The ideas carry over, but the current AICPA wording is the two-group list above.
Exam tip: The AUD section tests AICPA standards for nonissuers and PCAOB standards for issuers. Check which type of entity the question describes before you pick a framework.
How the PCAOB Groups Audit Assertions
PCAOB AS 1105, Audit Evidence, identifies five broad categories:
- Existence or occurrence: whether balances exist and recorded transactions happened.
- Completeness: whether required transactions and accounts are included.
- Valuation or allocation: whether financial statement components are reported at appropriate amounts.
- Rights and obligations: whether assets represent the entity’s rights and liabilities represent its obligations.
- Presentation and disclosure: whether items are appropriately classified, described, and disclosed.
AS 1105 also permits alternative assertion groupings when they adequately address potential misstatements and the related risks. Therefore, the number of labels is less important than understanding the underlying audit objective. Use the framework specified in an exam question. See PCAOB AS 1105, paragraphs .11–.12, for the authoritative categories.
What Is the Difference Between Existence and Completeness? (Vouching vs. Tracing)
Existence asks whether a recorded item is real. Completeness asks whether something that should be recorded is missing. That is why the starting point of your test, and the direction you move in, matter so much. In auditing, the ‘population’ is simply the full set of items you select your sample from.
Vouching: accounting records to supporting evidence
To test whether recorded sales occurred, the auditor selects sales entries and examines relevant supporting evidence. For inventory existence, the auditor selects items from the inventory listing and locates the goods. These procedures help address potential overstatement.
Tracing: source evidence to accounting records
To test whether shipments were recorded, the auditor selects shipping documents from an appropriate source population and follows them into the sales records. For inventory completeness, the auditor selects goods on the warehouse floor and checks their inclusion in the listing. These procedures help identify potential omissions.
Study tip: Identify the starting point before naming the assertion. A procedure may provide evidence about more than one assertion, and its purpose depends on how it is designed.
Which Audit Procedures Test Which Assertions?
Here is a quick map of common procedures and the assertions they mainly support. Real audit programs combine several procedures, so treat this as a starting point.
| Procedure | Assertions it mainly supports |
|---|---|
| Confirming accounts receivable with customers | Primarily existence. Evidence about rights depends on the information requested and the circumstances; additional procedures may be needed to identify assigned or pledged receivables. |
| Observing the physical inventory count | Existence (records to floor) and completeness (floor to records) |
| Searching for unrecorded liabilities using payments made after year-end | Completeness |
| Recalculating invoices, depreciation, or other amounts | Accuracy; valuation and allocation |
| Examining transactions just before and after year-end | Cutoff |
| Inspecting contracts, titles, and consignment agreements | Rights and obligations |
| Reviewing the aging schedule and cash collected after year-end | Valuation and allocation; collections after year-end can also support existence |
| Comparing note disclosures with debt agreements and reporting requirements | Classification and presentation |
Worked Examples of Audit Assertions
Cash: one balance, several representations
Assume Adam Company reports cash of $827,568 at December 31. Management’s representations include the existence of the deposits, the company’s rights to the cash, inclusion of all relevant accounts and transactions, and appropriate measurement and disclosure.
A bank confirmation and examination of the bank reconciliation may provide evidence about the reported balance. The auditor also needs procedures capable of identifying omitted accounts, evaluating reconciling items, and assessing restrictions. A restriction on cash may require particular classification or disclosure; physical or confirmed existence alone does not establish unrestricted availability.
Sales cutoff: a genuine sale recorded too early
Assume Lakeview Supply records a $12,000 credit sale on December 30. The goods ship on January 3, and the contract and applicable revenue recognition requirements establish that control transfers upon shipment. There are no other recognition issues.
The sale belongs in January. Recording it in December overstates December revenue and receivables by $12,000. Cutoff is the primary issue because the transaction is assigned to the wrong period. The auditor examines the contract, shipping evidence, and accounting entry. An invoice date alone does not establish the correct recognition date.
What about the cost side? If Lakeview also recorded cost of goods sold and reduced inventory on December 30, those entries are in the wrong period too. The goods were still in Lakeview’s warehouse on December 31, so they belong in year-end inventory.
Common CPA AUD Mistakes to Avoid
- Confusing existence with occurrence: existence generally concerns balances at a date; occurrence concerns transactions during a period.
- Confusing accuracy with valuation: a mathematically correct receivable balance may still require an allowance for credit losses.
- Confusing possession with rights: goods in the warehouse may belong to another party.
- Searching only recorded payables for omissions: completeness testing needs a population capable of revealing unrecorded obligations.
- Assuming one procedure addresses every assertion: relevant evidence for one objective may be insufficient for another.
- Applying testing shortcuts without assessing risk: asset overstatement and liability understatement are common teaching examples, but auditors design procedures for the assessed risks. Either assets or liabilities may be overstated or understated, and testing must address the relevant assertions.
Key Takeaways
- Audit assertions are management’s claims about the financial statements, and auditors gather evidence to test them.
- The AICPA (AU-C 315) splits assertions into transaction and account balance groups; the PCAOB (AS 1105) uses five broad categories. The underlying ideas are the same.
- Vouching (records to documents) tests existence or occurrence. Tracing (documents to records) tests completeness.
- Cutoff concerns the appropriate period; valuation concerns the appropriate amount; rights and obligations concerns the entity’s rights to assets and responsibility for liabilities.
- Start with what could go wrong, then name the assertion, then choose the evidence.
Practice Applying Audit Assertions
Identify the assertion most directly addressed, then expand the explanation. These are original study scenarios, not official CPA Exam questions.
1. Unrecorded liabilities
An auditor examines January payments and related invoices to identify December obligations omitted from accounts payable. Which assertion is primarily addressed?
Show answer and explanation
Completeness. The auditor is searching for obligations that should appear in the year-end records but are missing. Starting only with the payable listing would not identify liabilities omitted from that listing.
2. Goods held on consignment
An auditor inspects consignment agreements to determine whether goods in the warehouse belong in the company’s inventory. Which assertion is primarily addressed?
Show answer and explanation
Rights and obligations. The question concerns the company’s rights to the goods. Inspecting the goods may support existence, but their presence does not establish that the company holds the relevant rights.
3. Receivable collectibility
An auditor evaluates aging data, subsequent collections, and relevant expectations about customer payment to assess the allowance for credit losses. Which assertion is primarily addressed?
Show answer and explanation
Valuation and allocation. The objective is to evaluate the reported net amount of receivables. Establishing that customer balances exist does not determine whether the allowance is adequate.
Study Audit Assertions with Farhat Lectures
Continue with the Farhat Lectures Auditing Course for explanations of management assertions, audit evidence, risk assessment, and other auditing topics. Use the AUD CPA Test Bank to practice applying audit concepts.
To explore the teaching format, visit the free sample course. Some full-course lessons and practice resources require enrollment.
Already working through a review course? Farhat Lectures offers AUD supplemental courses built to go alongside Becker, Gleim, Surgent, and Miles.
Related reading: What Is GAAP?, Elements of Financial Statements, and Special Purpose Frameworks (OCBOA) Explained.
Frequently Asked Questions About Audit Assertions
Are audit assertions and management assertions the same?
In financial statement auditing, both terms generally refer to management’s representations about the statements. Management makes the representations, and the auditor evaluates the relevant assertions.
How many audit assertions are there?
It depends on the framework. The AICPA’s AU-C 315 lists six assertions for classes of transactions and six for account balances, and some names, such as completeness, appear in both groups. The PCAOB’s AS 1105 uses five broad categories. Older textbooks often show 13. This article uses eight study concepts that cover the same ground. On the exam, follow the framework the question uses and focus on what could go wrong.
Does confirming a receivable prove it will be collected?
No. Confirmation can provide evidence about a customer’s balance, but collectibility requires other relevant evidence. Existence and valuation are separate audit concerns.
What is an effective way to study audit assertions?
Describe the possible error first, identify the assertion, and explain how the proposed procedure would detect that error. This approach develops understanding beyond memorizing a list.
What are the five audit assertions?
The five audit assertions usually refer to the PCAOB’s categories in AS 1105: existence or occurrence, completeness, valuation or allocation, rights and obligations, and presentation and disclosure. They are used in audits of issuers, which are mostly public companies.
What is the difference between existence and occurrence?
Existence asks whether a balance, such as inventory or a receivable, is real at the balance sheet date. Occurrence asks whether a recorded transaction, such as a sale, actually happened during the period. Existence is about balances at a point in time, and occurrence is about transactions over a period.
What is the difference between vouching and tracing?
Vouching starts with a recorded entry and checks it against supporting documents, so it tests existence or occurrence. Tracing starts with source documents and follows them into the accounting records, so it tests completeness.
About the author: Professor Mansour Farhat, DBA, CPA, CIA, is a veteran accounting educator and the founder of Farhat Lectures. He holds a Doctor of Business Administration from Temple University and a Master of Accountancy from Bloomsburg University, and he teaches college students and CPA, CMA, and EA candidates. Learn more about Professor Mansour Farhat.
Responses