Audit Assertions for Expenses: The Six Types and Their Risks

Audit assertions for expenses are the specific claims a company’s management makes about every expense recorded in the financial statements, and auditors design their testing around them one by one. Six assertions apply to expense transactions: occurrence, completeness, accuracy, cutoff, classification, and presentation. Each targets a different way an expense figure can go wrong, which is why auditors ask for different documents and run different procedures depending on which assertion they’re testing.

Why Expenses Get Six Assertions

The PCAOB standard for public company audits groups assertions into five broader categories: existence or occurrence, completeness, valuation or allocation, rights and obligations, and presentation and disclosure.1Public Company Accounting Oversight Board. AS 1105 Audit Evidence When those categories are applied to transactions that happen over a reporting period rather than balances sitting at a point in time, they break into the six more granular assertions used for expenses.

The split matters because the risks are different. A balance-sheet item might not exist. An expense transaction might never have happened at all, might have happened but landed in the wrong year, might sit in the wrong account, or might carry the wrong dollar figure. Each assertion isolates one of those failure points so the audit response can be targeted.

Occurrence: Did the Expense Actually Happen?

The occurrence assertion is management’s claim that every recorded expense reflects a real transaction that belongs to the company during the reporting period. The risk is overstatement — fictitious or inflated expenses that reduce reported income. That risk climbs when management is under pressure to reduce taxable income, or when controls over vendor setup are loose enough for someone to create a fake vendor and route payments to themselves.

Auditors test occurrence by working backward from what’s already in the books. They pull a sample of recorded expenses from the general ledger and trace each one to its supporting documents: the approved vendor invoice, the purchase order, a receiving report showing goods actually arrived, and evidence of payment. The paper trail has to confirm that the company received something of value, that a real vendor provided it, and that the charge belongs to the entity being audited rather than a related party or a personal expense. This vouching direction, starting from the recorded entry and working back to the source, is the signature procedure for occurrence testing. Working the other direction tests a different assertion.

Completeness: Are Any Expenses Missing?

Completeness is the mirror image of occurrence. Here, management is claiming that every expense that should have been recorded actually was. The risk is understatement: expenses left out, whether deliberately or by accident, making net income look higher than it should. When a company wants to impress investors or hit an earnings target, omitting expenses is one of the most direct ways to inflate the bottom line.

The primary procedure is the search for unrecorded liabilities, and it appears in nearly every audit. The auditor works in the opposite direction from occurrence testing — starting from external evidence that an expense might exist and tracing forward to see whether it made it into the books.

In practice, that means examining large vendor payments made in the first month or two after the fiscal year-end. If a company paid a vendor $200,000 in January, the auditor looks at the invoice date and receiving report to determine whether the goods or services were actually received before December 31. If they were, the expense belongs in the prior year and should have been accrued. Auditors also compare current-year accruals for recurring costs like payroll, utilities, and warranty claims against prior-period amounts and contractual obligations to see if anything looks suspiciously low. Board minutes and legal counsel correspondence can surface commitments or litigation that should have triggered an accrual but didn’t. A lot of adjusting entries originate here.

Accuracy: Are the Amounts Right?

The accuracy assertion claims that recorded expense amounts are mathematically correct and properly calculated. A transaction can be real and recorded in the right period yet still carry the wrong dollar figure. Errors in allocation, computation, or currency conversion all fall under accuracy.

Auditors test accuracy through recalculation. For depreciation, the auditor independently recomputes the charge using the company’s stated method, useful life, and salvage value, then compares the result to what was recorded. For foreign-currency expenses, the auditor verifies that the correct exchange rate was applied. Allocated costs like shared overhead or insurance get scrutinized to confirm the allocation formula was applied consistently and the inputs are accurate. The recorded amount also has to match the underlying invoice or contract. A transposition that turns $15,300 into $13,500 is an accuracy failure even though the transaction is otherwise legitimate.

Cutoff: Was It Recorded in the Right Period?

Cutoff is management’s claim that every expense landed in the correct fiscal year. The risk is period manipulation: recording a legitimate expense in the wrong year to shift results between periods. A company wanting to boost current-year earnings might push a December expense into January. One wanting to reduce next year’s tax burden might pull a January expense into December.

Cutoff testing focuses on the days immediately surrounding the fiscal year-end. The standard procedure is to examine the last several receiving reports before year-end and trace the corresponding invoices to confirm they were recorded in the current period’s payable ledger. The auditor then flips to the other side of the line, looking at the first disbursements and invoices recorded in the new period to verify the underlying goods or services weren’t actually received before the cutoff date. An expense recorded in the wrong period distorts both years’ income statements, overstating one and understating the other.

Classification: Was It Recorded in the Right Account?

The classification assertion claims that each expense was recorded in the correct general ledger account. A misclassified expense might not change total net income, but it distorts individual line items in ways that mislead anyone analyzing the statements. It can also create real tax problems.

The highest-stakes classification question in expense auditing is whether a cost should be expensed immediately or capitalized as an asset. Federal tax law draws a hard line. Under the Internal Revenue Code, ordinary and necessary business expenses, including routine repairs and maintenance, are deductible in the year they’re incurred.2Office of the Law Revision Counsel. 26 U.S. Code 162 – Trade or Business Expenses But amounts paid for permanent improvements or betterments that increase a property’s value must be capitalized, meaning they get added to the asset’s cost basis and depreciated over time rather than deducted immediately.3Office of the Law Revision Counsel. 26 U.S. Code 263 – Capital Expenditures The IRS tangible property regulations provide a framework for making the distinction, recognizing that the line between a deductible repair and a capitalizable improvement has long been one of the trickiest calls in tax accounting.4Internal Revenue Service. Tangible Property Final Regulations

Incorrectly expensing a $500,000 building improvement as a repair wipes that amount off current-year income in one shot instead of spreading it across decades of depreciation. The income statement, balance sheet, and tax return are all wrong. Auditors test classification by reviewing the nature of significant expenditures, examining invoices and work orders for language that suggests improvement rather than maintenance, and comparing the company’s capitalization policy against how individual transactions were actually treated.

Presentation: Properly Shown and Disclosed?

The presentation assertion is the one most people overlook. Management is claiming that expenses are appropriately grouped, labeled, and disclosed in the financial statements and accompanying notes. A company could record every expense accurately, in the right account and right period, yet still violate this assertion by burying a material item inside an unrelated line or failing to break out a significant cost that investors would want to see separately.

Auditors test presentation by evaluating whether expense totals are aggregated or disaggregated at the right level. Employee compensation expense, for instance, should typically be broken out in the notes to show wages, pension costs, and payroll taxes as separate components. Unusual or nonrecurring items need to be identified clearly rather than blended into operating costs where they’d distort trend analysis. The presentation assertion also covers the adequacy of footnote disclosures, particularly for contingent liabilities. When a company faces pending litigation or other loss contingencies, accounting standards require disclosure of the nature of the contingency and either an estimate of the possible loss or a statement explaining why no estimate can be made.

Where the Assertions Concentrate Risk

Some expense areas hit multiple assertions at once, which is why they draw heavier scrutiny. Related-party expenses are the clearest example. A transaction with a company insider, an affiliated entity, or a family member of an executive can fail occurrence and accuracy if the company overpays a consulting firm owned by the CEO’s spouse, fail presentation if the relationship isn’t disclosed, and fail classification if the payments are buried in generic operating expense accounts. These transactions are harder to evaluate because they don’t arise from arm’s-length negotiation, so the usual market-based reasonableness checks don’t work as well.

PCAOB standards require auditors to understand the company’s process for identifying related parties and authorizing transactions with them.5Public Company Accounting Oversight Board. AS 2410 Related Parties For each related-party transaction that requires disclosure, the auditor must examine the underlying documentation, evaluate whether the stated business purpose makes sense, and determine whether the transaction was properly authorized under the company’s own policies. Board minutes get reviewed for evidence of dealings management may not have flagged.

What Management Should Have Ready

Companies that maintain clean, organized expense documentation give auditors what they need to test each assertion without expanding scope. Before fieldwork begins, the following records should be readily accessible:

  • Vendor invoices and purchase orders. Every recorded expense should trace to an approved invoice, ideally matched to a purchase order and receiving report. This three-way match is the backbone of occurrence testing.
  • Approval documentation. Clear records of who authorized each expense and whether it fell within their approval authority. Expenses over threshold amounts should show evidence of the required higher-level sign-off.
  • A written capitalization policy. This should define the dollar threshold and criteria for capitalizing expenditures versus expensing them. Auditors test individual transactions against this policy during classification testing.
  • Accrual support. Workpapers showing how year-end accruals for payroll, utilities, warranty costs, and other recurring expenses were calculated. Auditors compare these against prior periods and contractual terms during completeness testing.
  • Related-party records. Documentation identifying all related parties, the business purpose of each transaction, and evidence of board authorization where required.
  • Period-end receiving reports. The reports from the last few days of the fiscal year and the first few days of the new year are the direct evidence for cutoff testing.

Each of these ties back to one or more of the six assertions. When the documentation is there, testing confirms what the ledger already says. When it isn’t, the auditor’s risk assessment changes and testing expands, which is what a well-run expense process is designed to avoid.