Skip to content

Audit and Assurance · Assertions and audit evidence

Financial Statement Assertions in Audit Explained

Updated 11 October 2026 · Fact-checked

Financial statement assertions are the claims management makes, implicitly or explicitly, about the figures and disclosures in the financial statements. They cover classes of transactions, account balances and presentation. Auditors use them to spot where misstatement could occur, then design procedures that test each assertion at risk.

Understand Financial Statement Assertions

When directors sign financial statements, they claim many things. Sales are real. Receivables exist. Nothing is left out. Assets belong to the company. These claims are assertions. You cannot audit "the accounts" in one go, so ISA 315 (Revised 2019) sets out assertions as specific claims you can test one by one. ISA 500 deals with the audit evidence you gather to support them.

Assertions are grouped in three sets. The first set is for classes of transactions and events in the period (income statement items): occurrence, completeness, accuracy, cut-off and classification. The second set is for account balances at the period end (statement of financial position): existence, rights and obligations, completeness, accuracy, valuation and allocation, and classification. The third set is for presentation and disclosure: occurrence and rights and obligations, completeness, classification and understandability, and accuracy and valuation.

The key idea is direction. Occurrence and existence test for overstatement: is there anything recorded that should not be? Completeness tests for understatement: is anything missing? So revenue and assets are usually at risk of overstatement, while liabilities and expenses are usually at risk of understatement. The direction depends on the scenario, so think about who gains from the misstatement. For example, management may overstate liabilities or expenses to smooth profits, which puts existence or occurrence at risk. Assets or revenue may also be understated, which puts completeness at risk.

Assertions drive the audit. At risk assessment, you ask which assertion could be wrong for each material item. At the procedures stage, you choose tests that give evidence on that assertion. A test that proves existence of inventory tells you nothing about its valuation.

The difference students search for: existence asks whether the asset is physically or legally there at the date. Rights and obligations asks whether the entity owns or controls it (or owes the liability). Inventory held on consignment can exist in the warehouse yet fail rights.

Key rules to remember

Assertions about classes of transactions and events
Occurrence, Completeness, Accuracy, Cut-off, Classification
Used for the income statement and period transactions.
Assertions about account balances at period end
Existence, Rights and obligations, Completeness, Accuracy/valuation and allocation, Classification
Used for the statement of financial position.
Assertions about presentation and disclosure
Occurrence and rights and obligations, Completeness, Classification and understandability, Accuracy and valuation
Used for notes and how items are presented.
Direction of testing
Occurrence/existence → usually overstatement; Completeness → usually understatement
The direction depends on the scenario incentives. Management may, for example, overstate liabilities to smooth profits. Use this to choose the starting point of a test (ledger to document, or document to ledger).
Test direction rule
Existence: ledger → physical item or document. Completeness: document or physical item → ledger
Getting the direction wrong loses marks in procedure answers. Analytical procedures can also give evidence on completeness.

How to solve Financial Statement Assertions questions

Use this method for any question that asks you to identify assertions, link them to risks or design procedures.

  1. 1Identify the item (for example revenue, inventory, a provision) and whether it is a transaction class, a balance or a disclosure.
  2. 2List the assertions that apply to that category. Do not use the balance list for an income statement item.
  3. 3Decide which assertion is most at risk from the scenario facts: pressure to overstate profit, weak controls, estimates, year-end timing.
  4. 4State the risk in terms of the assertion, for example: revenue may be overstated, so occurrence is at risk.
  5. 5Choose a procedure that gives evidence on that assertion and say which direction you test.
  6. 6Name the procedure precisely: inspect, observe, inquire, confirm, recalculate, reperform or analytical procedure. Say what you inspect and why.
  7. 7Link the procedure back to the assertion in your final sentence so the marker sees it.

Quickest way: Overstatement or understatement, then pick the test

When to use it: Use it in Section A and B objective questions, and when you have little time in a written answer.

  1. Ask: is the risk that something is recorded but not real, or real but not recorded? Use the scenario incentives to decide. Assets and revenue are usually overstated, but not always.
  2. Recorded but not real: occurrence (transactions) or existence (balances). Test from the ledger to evidence.
  3. Real but not recorded: completeness. Test from evidence to the ledger.
  4. Wrong period near the year end: cut-off.
  5. Right amount but wrong figure or estimate: accuracy, or valuation and allocation.
  6. Wrong account or heading: classification.
  7. Ownership or legal claim in question: rights and obligations.

Common mistakes in Financial Statement Assertions

  • Using existence for an income statement item such as sales.

    Students remember existence as the main assertion and apply it everywhere.

    Fix: Existence is a balance assertion. For sales, the matching assertion is occurrence.

  • Treating existence and rights and obligations as the same.

    Both relate to assets and both seem to ask whether the asset is "there".

    Fix: Existence is whether it is there. Rights is whether it is the entity's. Use the example of goods held on consignment, assets subject to a legal charge, or goods sold but still recorded in inventory.

  • Testing completeness from the ledger.

    Students pick a sample of recorded items because it is easy.

    Fix: Completeness needs a start outside the ledger, such as goods received notes or post year-end payments, traced into the records. Analytical procedures can also give evidence on completeness.

  • Listing assertions without linking them to the scenario.

    Students recite the list from memory.

    Fix: Pick the one or two assertions most at risk and give the reason from the facts given.

  • Confusing cut-off with completeness.

    Both can lead to items missing from the period.

    Fix: Cut-off is about the right period for a transaction. Completeness is about whether anything is omitted altogether.

  • Giving vague procedures such as "check the invoices".

    Students do not say what is checked against what.

    Fix: State the document, the comparison and the purpose, for example agree a sample of recorded sales to dispatch notes to confirm occurrence.

Worked examples

Example 1

Section B style: During the audit of a retailer, you find that the finance director receives a bonus linked to profit. Which assertion is most at risk for revenue, and give one procedure to test it.

Show the solution
  1. The item is revenue, a class of transaction.
  2. The bonus gives an incentive to overstate profit, so the risk is revenue recorded that did not happen.
  3. That is the occurrence assertion.
  4. Test from the ledger to evidence: select a sample of sales recorded near and during the year.
  5. Agree each to the customer order, dispatch note and invoice to confirm the sale happened.

Answer: Occurrence is most at risk. Select a sample of recorded sales and agree them to orders and dispatch notes.

Example 2

Section C style: A company has material trade payables at the year end. Management is under pressure to meet a bank covenant. Identify the assertion most at risk and describe two procedures.

Show the solution
  1. Payables are an account balance. A covenant gives an incentive to understate liabilities.
  2. The key assertion is completeness, because liabilities may be omitted.
  3. Procedure 1: Obtain supplier statements at the year end and reconcile them to the payables ledger, investigating differences. This tests from external evidence to the ledger.
  4. Procedure 2: Review payments made after the year end and goods received notes from around the year end. Trace each into the payables ledger to confirm that the liability is recorded. This tests completeness, because it starts outside the ledger and looks for omitted liabilities.
  5. Separate note, not part of the answer above: comparing the dates on the goods received notes with the period in which each purchase was recorded gives evidence on cut-off for purchases.

Answer: Completeness of payables is most at risk. Reconcile supplier statements to the ledger, and trace post year-end payments and goods received notes into the payables ledger to confirm all liabilities are recorded.

Exam tips

  • Always name the assertion in your answer. Markers give credit for the link between risk, assertion and procedure.
  • Use the correct assertion set. Occurrence and cut-off apply to transactions. Existence and rights apply to balances.
  • In objective questions, check the direction first. Overstatement usually points to occurrence or existence, understatement to completeness, but check the scenario incentives.
  • In written answers, give procedures that state the document and the direction of test. Avoid one-word procedures.
  • Read scenario hints: incentive to inflate profit, consignment stock, year-end timing or estimates all point to a specific assertion.

Financial Statement Assertions in other exams

The same ground in other exams, if you are preparing for more than one or want another angle on it.

Financial Statement Assertions: frequently asked questions

What is the difference between existence and rights and obligations?

Existence asks whether an asset, liability or equity interest exists at the date. Rights and obligations asks whether the entity holds the rights to the asset or owes the obligation. Inventory on consignment may exist but not belong to the entity.

Which assertions are used for the income statement?

Assertions about classes of transactions and events apply: occurrence, completeness, accuracy, cut-off and classification. Balance assertions such as existence are for the statement of financial position.

How do I link audit procedures to assertions?

First decide which assertion is at risk from the scenario. Then choose a procedure that gives evidence on that assertion and test in the right direction. State the link in your answer.

Is completeness tested from the ledger or to the ledger?

Completeness is tested to the ledger. You start with an independent source, such as goods received notes or supplier statements, and trace it into the records to find omissions.