Financial statement assertions in one place
The ISA 315 (Revised 2019) assertions for transactions, balances and disclosures, what each means, and how naming them shapes every audit test.
By Achekam · · 5 min read · For Accountants & audit firms in South Africa, Nigeria, Kenya
Ask a first-year trainee what a procedure is for and the answer is often "to test receivables". Ask what about receivables, and the room goes quiet. The missing half of the answer is the assertion: the specific thing about a figure that could be wrong, and that the procedure is meant to give evidence on.
Assertions are the vocabulary that links risk assessment to audit work. A file that uses them well reads like an argument: here is what could be wrong, here is the test aimed at it, here is what we found. A file that ignores them reads like a list of activities. This article sets them out in one place, grouped as ISA 315 (Revised 2019) groups them, and shows how to put them to work on an audit in South Africa, Nigeria or Kenya.
Why assertions exist
ACCA describes the financial statement assertions as the assertions implicit when the directors state that the financial statements give a true and fair view: attributes that must be true if the statements are to give that view. When directors sign a statement of financial position showing trade receivables, they are implicitly claiming that those customers exist, that they owe the amounts shown, that nothing owed is missing, that the amounts are stated at what is likely to be collected, and that the balance is properly described.
The auditor tests those implicit claims where the risk of them being wrong is significant. ACCA's technical article on financial statement assertions explains each one under ISA 315 (Revised 2019), with examples of tests, and works well as pre-reading for a training session.
ISA 315 (Revised 2019) groups the assertions in two families, those about classes of transactions and events for the period and those about account balances at the period end, and each family covers the related disclosures.
Classes of transactions and events
These apply to the income statement and to movements during the year: sales, purchases, payroll, depreciation.
- Occurrence. ACCA explains that occurrence means the transactions and events recorded or disclosed have occurred and pertain to the entity. A sale that never happened, or one that belongs to the owner's other company, fails occurrence.
- Completeness. Every transaction that should have been recorded has been. Unrecorded sales or unrecorded expenses fail it.
- Accuracy. Amounts and other data have been recorded correctly.
- Cut-off. Transactions are recorded in the right period.
- Classification. Transactions are recorded in the proper accounts.
- Presentation. ACCA explains this as transactions and events being appropriately aggregated or disaggregated and clearly described, with related disclosures relevant and understandable in the context of the applicable framework.
Account balances
These apply at the reporting date, to assets, liabilities and equity.
- Existence. The asset or liability is real. ACCA lists physical verification of non-current assets, circularisation of receivables and payables, and the bank letter as tests relevant to existence.
- Rights and obligations. ACCA explains that the entity holds or controls the rights to its assets, and that its liabilities are its own obligations. A vehicle in the register that belongs to a director fails this.
- Completeness. Everything that should be recorded is recorded. ACCA notes that a completeness test starts from the underlying documents and traces them to the ledger, so that none has been missed.
- Accuracy, valuation and allocation. ACCA explains that assets, liabilities and equity interests are included at appropriate amounts, with any resulting valuation or allocation adjustments properly recorded. Receivables impairment and stock write-downs live here.
- Classification and presentation apply as above: the right accounts, sensible aggregation, clear description.
Presentation and disclosure
Disclosures are where assertions are most often forgotten. A note can have every figure right and still fail presentation: a related-party balance buried in "other receivables", a contingent liability described so vaguely that a reader would miss it, or accounting policies copied in for transactions the entity does not have. ACCA's description of presentation gives a reviewer three questions for each note. Is the aggregation sensible? Is the description clear? Is the disclosure relevant and understandable to a reader of these statements?
Naming the assertion in each step in Achekam
Assertions only help if they are written where the work happens. In Achekam, each work item lists the procedures to perform and the documents required, and a step is marked done only with a written response and its documents, or set aside with a reason. Steps are never deleted. That structure rewards assertion-led wording. Write the assertion into the step itself, for example "Completeness of trade payables: trace supplier statements and goods received notes from after year end to the payables ledger", and the written response has to address it.
The papers can then be read by statement line. The Working Paper Control Centre shows the engagement's file as an index with progress by status, and can group the same papers by preparer, reviewer, risk or statement line; Lead Schedules opens the statement-line view. Looking down one line, a reviewer can see whether the work beneath it covers the assertions that matter for that balance, or whether everything is aimed at existence and nothing at completeness. For how those choices flow from the risk assessment, see risk assessment under ISA 315 and linking risks to procedures.
Common balances and their main assertions
The assertions that most often carry the risk for familiar balances. Treat this as a starting point, not a replacement for the risk assessment on the file.
| Balance or class | Assertions that usually matter most | A test aimed at them |
|---|---|---|
| Revenue | Occurrence, cut-off | Trace recorded sales back to delivery notes; examine dispatches either side of year end |
| Trade receivables | Existence, valuation | Confirm balances with customers; review receipts after year end and the ageing |
| Inventory | Existence, valuation | Attend the count; compare cost with recent selling prices |
| Property, plant and equipment | Existence, rights, completeness | Inspect assets; examine title documents; review repairs and maintenance for items that should have been capitalised |
| Trade payables and accruals | Completeness, cut-off | Search for unrecorded liabilities in payments and invoices after year end |
| Bank and cash | Existence, completeness | Bank confirmation; reperform the reconciliation |
| Loans | Completeness, obligations, presentation | Lender confirmation; read the agreement for covenants and security |
| Related-party disclosures | Completeness, presentation | Compare minutes and declared interests with the note |
The repairs test in that table comes straight from ACCA, which explains that reviewing repairs and maintenance expenditure can reveal items omitted from non-current assets, giving evidence of completeness.
A simple discipline makes all of this stick: before anyone writes a procedure, they write the assertion it serves. If they cannot name one, the procedure probably does not belong on the file.
General guidance only, not advice on your own circumstances. Tax and payroll rules change: check the current position with the authority or your adviser.
