How misstatements work in audit
Every audit file ends with a schedule of uncorrected misstatements, and at most firms the conversation about that schedule is the most uncomfortable part of completion. You've found differences. Management doesn't want to adjust. The partner needs to decide whether the aggregate crosses the line. Getting this wrong in either direction is a real problem: push too hard on immaterial items and you damage the client relationship, let too many slide and you risk an opinion that doesn't hold up.
ISA 200.13 (i) defines misstatement broadly. It covers factual errors, incorrect classification, missing disclosures, and application of non-compliant accounting policies. ISA 450.5 requires accumulating all misstatements except clearly trivial ones, and ISA 450.11 requires evaluating uncorrected misstatements individually and in aggregate. Prior-period uncorrected misstatements carry forward and must be considered in the current year's evaluation.
What actually happens on most engagements is that teams are good at ticking and bashing their way through testing, finding the differences, and logging them. Where the file tends to fall down is on the evaluation. In our experience, the summary of uncorrected misstatements (SoUM) gets populated correctly, but the conclusion paragraph reads like a template rather than an actual assessment of whether these specific misstatements, in this direction, affecting these line items, could influence the decisions of these users. The file should tell a story about why the aggregate is or isn't material. Too often it just states the number.
Governed by ISA 450 paragraph 4(a) and ISA 200 paragraph 13(i).
Key points
- A misstatement can arise from error, fraud, incorrect application of accounting policies, or inadequate disclosure
- The auditor's opinion addresses whether statements are free from material misstatement, not all misstatement
- Individually immaterial misstatements must still be accumulated because their aggregate may be material
- Uncorrected misstatements from the prior year carry forward and affect the current year's evaluation
Worked example: Brennan Construction Ltd
Irish construction company, FY2024, revenue EUR 48M, IFRS. Materiality EUR 480K, performance materiality (PM) EUR 340K, clearly trivial EUR 17K.
Four misstatements found during testing:
- EUR 62K duplicate invoice (factual misstatement)
- EUR 95K warranty provision understatement (judgmental misstatement)
- EUR 28K classification error where lease expense was posted to the wrong line item (classification misstatement)
- EUR 78K projected from sampling (projected misstatement)
Aggregate: EUR 263K (55% of materiality), all in the same direction (overstate profit). The team requests correction of the factual and classification items and communicates the remainder to those charged with governance. At this point, the engagement manager needs to step back and consider the pattern. Four misstatements, all overstating profit, suggests a directional bias that warrants discussion in the completion memo even though the aggregate sits below materiality.
What reviewers get wrong
- Accumulating all types on the same schedule without distinguishing factual, judgmental, projected, and classification misstatements. ISA 450 .A3 distinguishes between types because they carry different levels of certainty. A factual misstatement is definite. A projected misstatement involves estimation. Lumping them together on a single line makes the evaluation paragraph harder to write and easier to challenge.
- Dropping PY uncorrected misstatements from the current-year evaluation. ISA 450 .A6 requires consideration of prior-period misstatements that still affect the current period. At firms like ours, the easiest way to catch this is a standing item on the completion checklist that forces the team to pull forward last year's SoUM and confirm each line has either reversed or been re-included in the current-year SoUM.
- Template conclusions on the SoUM. "The aggregate of uncorrected misstatements is not material" is not an evaluation. The file should explain why the aggregate isn't material: the direction, the accounts affected, the qualitative nature of the items, and whether any individual item is close to PM. I've seen files where the aggregate was 70% of materiality and the conclusion was still one sentence. That's a tick box exercise, not professional judgment.
- Not reassessing the clearly trivial threshold when materiality is revised downward. If mat drops at completion, the clearly trivial threshold drops with it. Misstatements that were previously excluded from the SoUM may now need to be accumulated.
Misstatement vs materiality
| Dimension | Misstatement | Materiality |
|---|---|---|
| What it is | Difference between reported and required | Threshold above which misstatement influences decisions |
| ISA reference | ISA 450.4 (a), ISA 200.13 (i) | ISA 320.2 , ISA 320.10 |
| Set by whom | Identified by auditor during testing | Determined by auditor at planning |
Related terms
Related tools
Related reading
Frequently asked questions
Does the auditor need to find every misstatement?
No. The auditor's job is to determine whether uncorrected misstatements, individually or in aggregate, are material to the financial statements as a whole. Misstatements below the clearly trivial threshold need not be accumulated.
Do prior-year uncorrected misstatements affect the current year?
Yes. ISA 450.A6 requires the auditor to consider prior-period uncorrected misstatements that still affect the current period's financial statements in the current year's evaluation.