Skip to content

Audit and Assurance · Audit procedures

Financial Statement Assertions and Audit Evidence for ACCA Audit and Assurance

Updated 11 October 2026 · Fact-checked

Assertions are the claims management makes in the financial statements, such as that items exist, are complete and are properly valued. ISA 315 (Revised 2019) uses them to assess risk. To answer a question, name the assertion at risk, then give a procedure that directly tests it.

Understand Financial Statement Assertions and Evidence

When management prepares financial statements, it is making claims. A receivables balance of ₹50,00,000 claims that the customers exist, that they owe the money, and that the amount is correctly stated. These claims are called assertions. The auditor's job is to gather evidence on whether each claim is true.

ISA 315 (Revised 2019) groups assertions into three categories. The first covers classes of transactions and events for the period, such as sales and expenses. The second covers account balances at the period end, such as receivables and inventory. The third covers presentation and disclosure, which is how items are shown and described in the financial statements. The ISA describes these as categories of assertions the auditor may use, not a fixed set, so the exact wording can vary.

Assertions guide the audit. You identify what could go wrong for each assertion (a risk of material misstatement), then design procedures that give evidence on that assertion. A procedure that tests existence will not tell you about completeness. For these two, evidence goes in opposite directions: to test existence, you start from the accounting records and trace to the physical item; to test completeness, you start from the physical item or an independent source and trace to the records. This direction rule applies to existence/occurrence and completeness only. Other assertions, such as accuracy, valuation and cutoff, use procedures like recalculation, agreeing to invoices or confirmation.

Under ISA 315 (Revised 2019), assertions for transactions are: occurrence, completeness, accuracy, cutoff and classification. For balances: existence, rights and obligations, completeness, and accuracy, valuation and allocation. For presentation and disclosure: occurrence and rights and obligations, completeness, classification and understandability, and accuracy and valuation. ACCA exam answers usually use the familiar names, so link each procedure clearly to one named assertion.

Key rules to remember

Assertions for classes of transactions and events
Occurrence | Completeness | Accuracy | Cutoff | Classification
Apply to income statement items for the period, such as sales, purchases and payroll.
Assertions for account balances at the period end
Existence | Rights and obligations | Completeness | Accuracy, valuation and allocation
Apply to statement of financial position items such as inventory, receivables and payables.
Assertions for presentation and disclosure
Occurrence and rights and obligations | Completeness | Classification and understandability | Accuracy and valuation
Test that items are properly described, grouped and disclosed in line with the reporting framework.
Direction of testing
Existence/occurrence: records → item. Completeness: item → records
This rule applies to existence/occurrence and completeness only. For existence/occurrence (overstatement) test from records to evidence; for completeness (understatement) test from evidence to records. Other assertions, such as accuracy, valuation and cutoff, use recalculation, agreeing to invoices or confirmation.
Typical risk direction
Assets and income: overstatement risk. Liabilities and expenses: understatement risk
This is a starting point. Always consider the scenario, as incentives can reverse it.

How to solve Financial Statement Assertions and Evidence questions

Use this method for any question that asks you to link assertions, risks and audit procedures.

  1. 1Identify the item (for example inventory, payables, sales) and whether the question is about a transaction class, a balance or a disclosure.
  2. 2Pick the assertion that the scenario or requirement points to. Look for words such as exist, missing, valued, cut-off, owned.
  3. 3State the risk in one sentence: what could be wrong, and in which direction (overstated or understated).
  4. 4Choose a procedure that tests that assertion directly, using the correct direction of testing.
  5. 5Name the type of evidence and procedure, such as inspection, observation, external confirmation, recalculation, reperformance or inquiry.
  6. 6Say what the result would show, so the examiner sees the procedure produces relevant evidence.
  7. 7Check each procedure is matched to a single assertion. Do not give a general test such as 'review the ledger'.

Quickest way: Assertion, direction, procedure

When to use it: Use in Section A and B objective questions or when you have a few minutes for a written part.

  1. Underline the key word: exist, complete, value, owned, cut-off, classified.
  2. Match it to the assertion: exist = existence or occurrence, missing = completeness, value = valuation or accuracy, owned = rights and obligations.
  3. For existence/occurrence and completeness only, decide direction: overstated means test from records to evidence; understated means test from evidence to records. For other assertions, choose a procedure such as recalculation, agreeing to invoices or confirmation.
  4. Write one procedure naming the document, the population and the purpose.

Common mistakes in Financial Statement Assertions and Evidence

  • Testing the wrong direction, such as tracing from ledger to delivery notes to prove completeness of sales.

    Students remember a procedure but not which assertion it supports.

    Fix: For completeness, start from an independent source (goods despatched notes) and trace to the ledger. For existence or occurrence, start from the ledger and trace to supporting documents.

  • Listing assertions without linking a procedure to each one.

    The question says 'identify assertions', and students stop there.

    Fix: Always follow the assertion with a specific test and the evidence it will produce.

  • Confusing transaction assertions with balance assertions, such as using 'occurrence' for inventory at the year end.

    The names sound similar and the lists are partly overlapping.

    Fix: Occurrence is a transaction assertion (and is part of the combined disclosure assertion, occurrence and rights and obligations). Cutoff is also a transaction assertion. Existence is the balance equivalent of occurrence. Rights and obligations is a balance assertion, and it also appears in disclosure as occurrence and rights and obligations. Decide which category you are testing first.

  • Using 'check the balance is right' as a procedure.

    Students describe the objective instead of the action.

    Fix: Describe an action: inspect, recalculate, confirm, observe, reperform, or compare to a source document.

  • Treating valuation, accuracy and cutoff as the same thing.

    All involve getting the number right.

    Fix: Cutoff is about the period. Accuracy is about the right amount for the transaction. Valuation is about carrying value, such as net realisable value or recoverability.

  • Ignoring the scenario and giving a textbook list.

    Students memorise tables.

    Fix: Use facts from the scenario, for example a new customer, a late invoice or slow-moving stock, to choose the assertion and tailor the test.

Worked examples

Example 1

The audit client, a distributor, has inventory of ₹80,00,000 at the year end. Describe one audit procedure for each of the existence, completeness and valuation assertions for inventory.

Show the solution
  1. Existence: the risk is that recorded inventory does not physically exist. Attend the inventory count and select items from the count records to inspect physically on the shelves. This goes from records to items.
  2. Completeness: the risk is that items on hand are not recorded. Select items from the warehouse floor and trace them to the count sheets and final inventory listing. This goes from items to records.
  3. Valuation: the risk is that inventory is carried above the lower of cost and net realisable value. Select a sample of lines, agree cost to supplier invoices, and compare with post year-end selling prices to check that NRV is not below cost.
  4. Link each test to its assertion in the answer.

Answer: Existence: select items from the count sheets and inspect them physically in the warehouse. Completeness: trace items from the floor to the count sheets and listing. Valuation: agree cost to supplier invoices and compare to post year-end selling prices for NRV.

Example 2

A retail client's payables ledger shows trade payables of ₹30,00,000. The auditor is concerned that liabilities may be understated. Identify the assertion most at risk and describe two procedures.

Show the solution
  1. The risk is that liabilities exist but are not recorded. The assertion at risk is completeness of payables.
  2. Direction: start from an independent or external source and trace to the ledger, because understatement is the concern.
  3. Procedure 1: obtain supplier statements for key suppliers, including those with zero or low balances, and reconcile them to the payables ledger. Investigate any differences. Supplier statements are external evidence.
  4. Procedure 2: review payments made after the year end and goods received notes dated before the year end. Trace each to the ledger to check that liabilities relating to pre year-end goods or services are recorded. This tests completeness of payables.
  5. Goods received notes and the client's payment listing are internal records, so their reliability depends on the client's controls. Cross-check them to bank statements or to supplier invoices.
  6. Cutoff is a separate assertion and needs its own test. Check that goods and invoices around the year end are recorded in the correct period, for example by comparing the dates of the last goods received notes before and the first after the year end with the period in which the related invoices are recorded.

Answer: Assertion: completeness of payables. Procedures: reconcile supplier statements (external evidence), including low-balance suppliers, to the ledger; and trace post year-end payments and pre year-end goods received notes to the ledger to check that the related liabilities are recorded. Goods received notes and the payment listing are internal records, so cross-check them to bank statements or supplier invoices. Test cutoff separately by checking that goods and invoices around the year end are recorded in the correct period.

Exam tips

  • Write the assertion name in your answer. Markers award marks for the link between assertion and procedure.
  • In Section B OT cases, read the requirement for the key word and match it to one assertion before looking at the options.
  • In a written answer, use one line per procedure: assertion, test, and evidence source.
  • Use scenario facts to justify the risk, such as rapid growth or unusual year-end sales.
  • Do not give both directions of a test for one assertion. Choose the correct one and explain why.

Financial Statement Assertions and Evidence 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 and Evidence: frequently asked questions

What are the assertions in ISA 315 for ACCA AA?

They are grouped into those for classes of transactions and events, those for account balances, and those for presentation and disclosure. Transactions include occurrence, completeness, accuracy, cutoff and classification. Balances include existence, rights and obligations, completeness, and accuracy, valuation and allocation.

What is the difference between existence and completeness?

Existence asks whether recorded assets, liabilities or equity interests really exist. Completeness asks whether everything that should be recorded has been recorded. Existence mainly addresses overstatement of recorded items, and completeness mainly addresses understatement through omitted items.

How do I link procedures to assertions in the exam?

Name the assertion, state the risk, and give a specific action such as inspect, confirm, recalculate or trace. Make sure the direction of the test matches the assertion. Use details from the scenario.

Do assertions for transactions differ from those for balances?

Yes. Transaction assertions cover the period and include occurrence, cutoff and classification. Balance assertions cover the year-end position and include existence and rights and obligations. Some, like completeness, appear in both sets.