Audit assertions are the specific claims that a company’s management makes, explicitly or implicitly, about every number and disclosure in its financial statements. Auditors organize their entire examination around testing these claims, and the framework most widely used in practice groups them into three categories: assertions about account balances at period-end, assertions about transactions and events during the period, and assertions about presentation and disclosure. Each category contains its own subset of assertions, and each assertion answers a different question about whether the financial statements can be trusted.
What Management Is Actually Claiming
When a company publishes financial statements, its leadership is implicitly representing that the numbers are complete, accurate, properly categorized, and belong to the entity. Those implicit representations have formal names in auditing. Management owns the truthfulness of the representations. The auditor’s job is to gather enough evidence to confirm or contradict them.
Auditors don’t check every entry. They assess the risk of material misstatement at the assertion level for each significant account and disclosure, then design procedures accordingly.1Public Company Accounting Oversight Board. AS 2110 – Identifying and Assessing Risks of Material Misstatement High-risk assertions get more rigorous testing. Low-risk ones get less. Without this framework, audits would be either impossibly expensive or dangerously shallow.
Factors that push an assertion into higher-risk territory include account size and composition, susceptibility to fraud, transaction complexity, and whether significant estimates or judgments are involved.1Public Company Accounting Oversight Board. AS 2110 – Identifying and Assessing Risks of Material Misstatement Revenue carries a presumed fraud risk under PCAOB standards, so auditors must specifically design procedures around revenue assertions unless they can document why that presumption doesn’t apply.2Public Company Accounting Oversight Board. AS 2401 – Consideration of Fraud in a Financial Statement Audit
A Note on Competing Frameworks
Before working through the individual assertions, one boundary matters. PCAOB standards, which govern audits of U.S. public companies, define five broad assertions: existence or occurrence, completeness, valuation or allocation, rights and obligations, and presentation and disclosure.3Public Company Accounting Oversight Board. AS 1105 – Audit Evidence PCAOB does not split them into separate categories for balance sheet versus income statement items, and it does not list accuracy, cutoff, or classification as standalone assertions; those concepts are folded into the broader labels.
The International Standards on Auditing take a more granular approach. ISA 315 (Revised 2019) splits assertions into three categories — classes of transactions and events, account balances at period-end, and presentation and disclosure — and adds accuracy, cutoff, and classification as separate items. The AICPA standards used for private company audits in the U.S. follow the same structure. In practice, the underlying objectives are identical. The three-category framework is the one most useful for understanding what each assertion actually tests, so the sections below use it.
Assertions About Account Balances
These assertions focus on ending balances of assets, liabilities, and equity on the balance sheet at a specific date. The question at the heart of each one: do the reported figures accurately capture the company’s financial position on the closing date?
Existence
Existence is the claim that every asset, liability, and equity interest on the balance sheet actually exists on the reporting date. The risk runs in one direction: management overstating what the company has. Fictitious inventory, phantom receivables, and inflated cash balances all violate this assertion.
The classic test is external confirmation. Auditors send letters directly to customers asking them to verify outstanding receivable balances, and they confirm cash balances directly with the bank. For inventory, the auditor attends the physical count, selects items from the company’s listing to locate on the warehouse floor, and traces items found on the floor back to the listing. Each direction of that two-way check catches a different type of error.
Rights and Obligations
This assertion asks whether the company actually owns or controls the rights to its reported assets, and whether recorded liabilities are genuine obligations of the entity. A building can exist and be properly valued, but if the company doesn’t own it, listing it as an asset is wrong.
Auditors test rights and obligations by examining legal documents: property deeds, vehicle titles, patent registrations, loan agreements. For leased assets, the auditor reviews the lease terms to determine whether the arrangement qualifies for balance-sheet recognition. For intangibles, the auditor verifies that the entity holds the underlying copyrights, patents, or licensing agreements.
Completeness
Completeness is the mirror image of existence. Where existence asks “is this real?”, completeness asks “is anything missing?” The risk flips direction: the concern here is understatement, particularly for liabilities. A company trying to look healthier might fail to record obligations it actually owes.
That directional difference fundamentally changes how auditors design their tests. For existence, the auditor starts from the financial records and traces backward to supporting evidence. For completeness, the auditor starts from real-world source documents and traces forward into the records to see what may have been left out. For accounts payable, that means reviewing payments made after year-end and checking whether the underlying goods or services were received before the cutoff date. If they were, a liability should have been recorded.
Completeness testing also involves reviewing board meeting minutes for discussions of new debt, guarantees, or contingent liabilities. Under the codified guidance originally established by SFAS No. 5 (now ASC 450), an entity must record a contingent liability when it is probable that a loss has been incurred and the amount is reasonably estimable.4Financial Accounting Standards Board. Summary of Statement No 5 Failing to do so is one of the more common completeness violations auditors encounter.
Valuation and Allocation
Valuation and allocation is the claim that every balance sheet item is recorded at the right dollar amount, including any necessary adjustments like depreciation, amortization, or impairment write-downs. An asset can exist, be owned, and be booked, yet still be misstated if its carrying value is wrong.
For accounts receivable, the auditor evaluates the allowance for doubtful accounts by reviewing the aging schedule, historical write-off rates, and current economic conditions. For inventory, testing involves confirming that items are carried at the lower of cost or net realizable value, which requires the auditor to understand whether the company uses FIFO, LIFO, or another cost-flow method.
Goodwill has its own impairment analysis under ASC Topic 350. Current guidance requires entities to test goodwill for impairment at least annually by comparing the fair value of a reporting unit with its carrying amount.5Financial Accounting Standards Board. Goodwill Impairment Testing For complex fair-value measurements of investment securities or derivatives, auditors frequently bring in valuation specialists to independently assess management’s inputs and assumptions.
Assertions About Transactions and Events
Where balance sheet assertions cover a snapshot at a single date, transaction assertions cover everything that happened between two dates. These assertions apply to the revenues, expenses, and other economic events that flow through the income statement.
Occurrence
Occurrence is the transaction-level counterpart to existence. It confirms that recorded revenue, expenses, and other transactions actually happened and belong to the entity. The primary risk is fictitious revenue. A company might book sales that never took place to inflate its top line, which is why PCAOB standards treat improper revenue recognition as a presumed fraud risk.2Public Company Accounting Oversight Board. AS 2401 – Consideration of Fraud in a Financial Statement Audit
To test occurrence for revenue, an auditor selects a sample of recorded sales and traces each one back to customer shipping documents, signed purchase orders, and evidence of payment. For expenses, a common technique is the three-way match: the auditor verifies that the vendor invoice, the receiving report, and the original purchase order all correspond to the recorded payment. If any of the three pieces don’t align, the transaction gets flagged.
Completeness
Completeness for transactions asks whether every event that should have been recorded actually made it into the books. Where occurrence catches fake transactions, completeness catches missing ones. The risk is most acute for expenses, since management might delay recording costs to make profits look better than they are.
Directional testing applies here too. Instead of starting from recorded entries, the auditor starts from independent source documents and works forward. For purchases, that means selecting a sample of receiving reports and tracing them into the purchases journal to confirm a corresponding entry exists. For payroll, the auditor compares headcount from human resources records against the payroll register to check whether all employees are being accounted for. Analytical procedures also play a role. Comparing current-year revenue or expense patterns against prior-year figures and industry benchmarks can surface unexpected gaps that warrant deeper investigation.
Accuracy
Accuracy means recorded transactions reflect the correct dollar amounts. A sale might have occurred and been properly recorded in the right period, but if the extended price was miscalculated or a discount was applied incorrectly, the accuracy assertion is violated.
Auditors test accuracy by recalculating. For a fixed asset purchase, that means independently computing depreciation expense using the stated useful life, salvage value, and depreciation method. For revenue, it means rechecking sales tax, volume discounts, and rebates on a sample of large invoices. For interest expense, the auditor confirms the interest rate and principal balance against the loan agreement and recalculates the accrued interest independently.
Cutoff
Cutoff is about timing. Transactions must land in the correct accounting period, and improper cutoff is one of the easier ways to manipulate financial results. Pushing a December expense into January inflates this year’s profit. Pulling a January sale into December does the same thing.
Auditors test cutoff by examining transactions clustered around the year-end boundary, looking at entries recorded in the final days of the period and the first days of the next one. For sales, the key question is when control of the goods transferred to the customer, which under ASC 606 depends on factors like whether the customer can direct the use of and obtain the benefits from the asset. For inventory purchases, the auditor confirms that goods received before year-end have a corresponding payable recorded in the same period.
Classification
Classification addresses whether transactions landed in the right accounts. Numbers can be accurate and timely and still be misleading if they’re in the wrong category. The textbook example is recording a routine repair as a capital expenditure. Total spending is correct, but the income statement understates expenses while the balance sheet overstates assets.
Auditors test classification by reviewing a sample of journal entries to confirm that the debits and credits match the nature of the underlying transaction. Proper classification also matters for distinguishing operating expenses from non-operating items, since that distinction directly affects operating income. For stock-based compensation involving stock options and restricted stock units, ASC 718 governs how these awards are classified and measured, and misclassification can distort both compensation expense and equity balances.
Assertions About Presentation and Disclosure
The final category covers everything a company communicates in its footnotes and supplementary disclosures. Numbers can be perfectly accurate in the ledger and still mislead readers if the accompanying narrative is incomplete, unclear, or deceptive.
Occurrence, Rights, and Obligations
This assertion confirms that disclosed events actually happened and pertain to the entity. If a company discloses a material lawsuit in the footnotes, the auditor verifies that the legal action is real and currently involves the company. Primary evidence comes from external legal confirmations sent directly to outside counsel. The auditor also checks that disclosed related-party transactions actually involve the parties described.
Completeness of Disclosures
Completeness for disclosures means every footnote required by the applicable accounting framework has been included. Auditors work through a disclosure checklist to confirm nothing was omitted. For public companies, this includes compliance with Regulation S-X, which prescribes the form and content of financial statements filed with the SEC.6eCFR. 17 CFR Part 210 – Form and Content of and Requirements for Financial Statements
Accuracy and Valuation of Disclosures
The numbers in the footnotes need to be as accurate as the numbers in the primary statements. The auditor recalculates amounts disclosed in the notes and traces them back to the underlying records. Stated accounting policies also get scrutinized to confirm they describe the methods the company actually used, not aspirational descriptions of what it intended to do.
Classification and Understandability
Financial disclosures need to be clearly written and logically organized. This assertion goes beyond numerical accuracy into readability. Complex instruments shouldn’t be buried in vague language, and the required summary of significant accounting policies should appear as one of the first footnotes. The auditor reviews the notes for clarity and confirms that required terminology is applied consistently.
Why the Direction of Testing Matters
One of the most practical concepts in assertion testing is directional testing, and it trips up a surprising number of new auditors. The basic principle: the direction you trace evidence depends on which assertion you’re testing.
When testing existence or occurrence, you start from the financial records and work backward to the real world. You pick a recorded receivable and confirm the customer actually owes it. You pick a recorded sale and look for the shipping document. If something is in the books, prove it’s real.
When testing completeness, you reverse direction. You start from the real world and work forward into the records. You take a stack of receiving reports and check whether each one produced a journal entry. You review post-year-end cash disbursements and ask whether the underlying liability should have been booked before the cutoff. If something is real, prove it’s in the books.
Getting the direction wrong doesn’t just waste time. It means you’ve gathered evidence for the wrong assertion entirely. An auditor who selects recorded payables and confirms they’re valid has tested existence, not completeness. Completeness requires starting from outside the ledger.
What Happens When Assertions Fail
Undetected assertion failures end careers and sink companies. When a material misstatement makes it into published financial statements, the consequences reach well beyond an audit opinion.
The SEC regularly pursues enforcement actions against companies and executives who intentionally misstate assertions. In one 2024 case, the SEC charged a company and its CEO for improperly recognizing revenue on products that remained under the company’s control rather than being delivered to customers, a violation of the occurrence and cutoff assertions. The company paid a $175,000 penalty and the CEO paid $50,000, and the CEO was required to reimburse a cash bonus and stock awards received while the financial statements were misstated under the clawback provisions of Sarbanes-Oxley Section 304.7U.S. Securities and Exchange Commission. SEC Charges Microcap Issuer and CEO with Violations of the Antifraud Provisions for Improper Revenue Recognition and Reporting
That case was relatively small. In fiscal year 2024, the SEC reported enforcement actions involving financial misstatements that produced penalties and disgorgements in the tens and hundreds of millions of dollars. Macquarie paid roughly $80 million for overvaluing illiquid collateralized mortgage obligations, a valuation assertion failure. BF Borgers’ managing partner agreed to a $2 million penalty for fraud affecting hundreds of SEC filings.8U.S. Securities and Exchange Commission. SEC Announces Enforcement Results for Fiscal Year 2024 Every assertion in this article maps to a category of financial statement fraud that the SEC actively investigates.
Legal exposure typically includes violations of the Securities Act antifraud provisions, the Exchange Act’s reporting requirements, and the books-and-records and internal-controls provisions. For executives, the personal stakes include civil penalties, industry bars, and mandatory reimbursement of bonuses and stock sale profits received during the period of misstatement.