What is the completeness assertion?
The completeness assertion appears in all three assertion categories under ISA 315.A190: account balances at period end, classes of transactions during the period, and presentation and disclosure. It asks a single question: is anything missing? When management presents trade payables of EUR 3 million, completeness tests whether all obligations that existed at the reporting date have been included in that balance.
The defining feature of completeness testing is the direction: you start from a source outside the ledger and trace into it. Review subsequent payments after year-end and check whether the underlying liability was recorded at the balance sheet date. Examine goods received notes from late December and verify the corresponding payable was booked. Obtain supplier statements and reconcile them to the ledger. The direction is always external source to ledger — the opposite of existence testing (ISA 500.A31).
Completeness also applies to disclosures under ISA 315.A190(c), and this is frequently under-tested. The question is not just "are the numbers in the notes correct?" but "are all required disclosures present?" This means evaluating whether the entity has included every disclosure required by the applicable financial reporting framework — related party disclosures under IAS 24, contingent liability disclosures under IAS 37, segment reporting under IFRS 8, and so on.
Key Points
- Completeness tests whether anything is missing from the financial statements — unrecorded transactions, omitted balances, or absent disclosures.
- The direction of testing runs from external sources into the ledger — start from independent evidence and check whether the item was recorded. You cannot test completeness from the ledger because the ledger is the thing you suspect is incomplete.
- Completeness is the dominant assertion for liabilities and expenses because management's incentive is to understate obligations and costs, not overstate them.
- Disclosure completeness is a separate dimension and is consistently under-tested. It requires evaluating whether all disclosures required by the framework have been included, not just whether the disclosed amounts are correct.
Why it matters in practice
The FRC has flagged a recurring issue with the search for unrecorded liabilities — the most common completeness procedure. Teams perform the procedure but define it too narrowly. They review subsequent payments above materiality but ignore payments just below the threshold, or they limit the search to trade payables without considering accruals, provisions, or other obligations. A completeness test that only looks at one category of liability does not address completeness of the balance sheet as a whole.
Disclosure completeness is where the gap is widest. Teams verify that disclosed related party transactions are accurately described but do not evaluate whether all related party relationships and transactions have been disclosed (IAS 24 completeness). They check the contingent liability note for accuracy but do not assess whether other potential contingencies — from legal counsel letters, board minutes, or regulatory correspondence — should have been disclosed under IAS 37.86. The procedure tests accuracy of what is there, not completeness of what should be there.
Key standard references
- ISA 315.A190(a): Completeness as an assertion about account balances at period end.
- ISA 315.A190(b): Completeness as an assertion about classes of transactions during the period.
- ISA 315.A190(c): Completeness as an assertion about presentation and disclosure.
- ISA 500.A31: Directional testing — completeness requires testing from external sources into the ledger.
Related terms
Related reading
Frequently asked questions
Why does completeness testing start outside the ledger?
You cannot test completeness by starting from the ledger because the ledger is exactly the thing you suspect is incomplete. ISA 500.A31 requires the auditor to start from independent sources (subsequent payments, goods received notes, supplier statements) and trace back to determine whether items were recorded.
Is completeness only about account balances?
No. ISA 315.A190 splits completeness across all three assertion categories: account balances, transaction classes, and disclosures. Disclosure completeness is frequently under-tested — it requires evaluating whether all disclosures required by the applicable framework have been included.
How does completeness differ from cutoff?
Completeness asks whether an item is recorded at all. Cutoff asks whether it is recorded in the correct period. A December sale recorded in January fails cutoff. A December sale not recorded anywhere fails completeness. The two often overlap around year-end but ask different questions.