What is the presentation and disclosure assertion?
ISA 315.A190(c) breaks presentation and disclosure into four sub-assertions: occurrence and rights and obligations (disclosed events actually happened and pertain to the entity), completeness (all required disclosures are included), classification and understandability (information is appropriately described, classified, and clearly expressed), and accuracy and valuation (amounts and other data in disclosures are correct).
ISA 700.13(b) links these assertions directly to the auditor's opinion: the auditor concludes whether the financial statements are "presented fairly, in all material respects" — which encompasses not just the face of the statements but every note, accounting policy, and supplementary disclosure. A clean opinion implicitly covers all four sub-assertions for every material disclosure.
In practice, most audit teams test disclosures using a checklist that confirms whether each required note is present. This addresses completeness but leaves three sub-assertions untested. A note can be present (completeness satisfied) but contain the wrong amount (accuracy fails), describe a transaction in misleading terms (understandability fails), or include an event that did not actually occur (occurrence fails). Each sub-assertion requires its own procedures.
Key Points
- Covers notes, policies, the face of the statements, and supplementary disclosures. Every piece of information presented in the financial statements falls under this assertion category.
- Most files under-test disclosures vs. balances. Teams allocate the majority of testing effort to balance sheet and income statement line items while treating disclosures as a completion-phase formality.
- Technically present but buried fails understandability. A disclosure that exists but is written in a way that obscures the substance of the transaction does not satisfy classification and understandability.
- Inspection findings have been increasing since 2021. AFM, FRC, PCAOB, and NBA reports all show year-on-year increases in disclosure-related deficiencies.
Why it matters in practice
The AFM has specifically called out the tick-box approach to disclosure testing as insufficient. Teams complete a disclosure checklist during the final review phase and treat it as evidence that presentation and disclosure assertions have been addressed. But ISA 330.6 requires the auditor to design and perform further audit procedures whose nature, timing, and extent are responsive to the assessed risks at the assertion level — including disclosure assertions. A checklist designed after the audit is essentially complete cannot be responsive to risks identified during planning.
Teams also frequently fail to test the accuracy of amounts within disclosure notes. A related party transactions note may list the correct parties (occurrence) and include all required transactions (completeness), but if the monetary amounts are transposed or aggregated incorrectly, the disclosure is materially misstated. The auditor needs to trace amounts in notes back to the underlying ledger entries and supporting documents with the same rigour applied to balance sheet testing. IAS 1.10 requires a complete set of financial statements including notes — and the opinion covers the notes as much as the primary statements.
Key standard references
- ISA 315.A190(c): Four sub-assertions for presentation and disclosure — occurrence and rights and obligations, completeness, classification and understandability, accuracy and valuation.
- ISA 700.13(b): The auditor's opinion on whether the financial statements are presented fairly, in all material respects.
- ISA 330.6: Requirement to design and perform further audit procedures responsive to assessed risks at the assertion level.
- IAS 1.10: Components of a complete set of financial statements, including notes comprising material accounting policy information and other explanatory information.
Related terms
Related reading
Frequently asked questions
What are the four sub-assertions within presentation and disclosure?
ISA 315.A190(c) breaks them into: occurrence and rights and obligations (disclosed events happened and pertain to the entity), completeness (all required disclosures are included), classification and understandability (information is described and classified appropriately), and accuracy and valuation (amounts and descriptions are correct).
Why are disclosure findings increasing?
Inspection findings on disclosure testing have increased year-on-year across AFM, FRC, PCAOB, and NBA reports since 2021. The main cause is that teams treat disclosures as a completion-phase tick-box exercise rather than designing assertion-level procedures during planning, as ISA 330.6 requires.
Is a disclosure checklist sufficient for testing?
A checklist catches missing disclosures (completeness) but does not test whether present disclosures are understandable (classification) or whether amounts within notes are correct (accuracy). Separate procedures are needed for each sub-assertion. A note can be present but contain a transposition error that makes a figure materially wrong.