SA 705 governs how an auditor chooses among three types of modified opinion — qualified, adverse, or a disclaimer of opinion — based on two genuinely independent questions: how material is the actual or possible effect of the matter, and is that effect confined to specific, identifiable elements of the financial statements or pervasive across them. The two questions combine into a simple grid, and the common error is treating materiality alone as the deciding factor when pervasiveness is doing equally important work in the standard's logic.
The decision grid
| Material but not pervasive | Material and pervasive | |
|---|---|---|
| Misstatement identified (auditor has sufficient evidence, and knows the effect) | Qualified opinion — "except for..." | Adverse opinion — the financial statements do not give a true and fair view |
| Unable to obtain sufficient appropriate evidence (auditor doesn't know the effect, only that it could be significant) | Qualified opinion — "except for the possible effects of..." | Disclaimer of opinion — the auditor does not express an opinion at all |
Why "pervasive" is doing real work, not just intensifying "material"
Pervasive doesn't mean "very material" — it's a separate test entirely, asking whether the effects are not confined to specific elements, or if confined, represent a substantial proportion of the financial statements, or relate to disclosures fundamental to users' understanding. A single, large, clearly isolated misstatement (an overstated receivable balance, fully quantified) can be material without being pervasive — it gets a qualified opinion naming the specific account. A smaller, poorly scoped problem affecting the reliability of the whole revenue recognition process across every segment of the business can be pervasive even if its precise rupee effect is harder to pin down.
An auditor unable to obtain sufficient evidence about a matter they cannot even reasonably bound — where the possible range of effect is unknown rather than merely large — should lean toward a disclaimer rather than a qualified opinion, since the pervasiveness test applies to the possible effects of undetected misstatements, not only confirmed ones.
What has to be in the report itself
- A "Basis for Qualified/Adverse Opinion" (or "Basis for Disclaimer of Opinion") section, describing the matter in enough detail that a reader understands exactly what the modification is about.
- For a qualified or adverse opinion, a reasonably specific quantification of the financial effect where it's practicable to state one.
- The opinion paragraph itself, placed and worded per SA 700's structure but modified to reflect the specific type chosen.
- For a disclaimer, an explicit statement that the auditor does not express an opinion, and specific wording that avoids language elsewhere in the report (such as in an Other Matter paragraph) that could be read as providing some level of assurance despite the disclaimer.
How we think about this
The grid exists so the choice of opinion type is derived from an explicit assessment against both axes, documented in the file, rather than arrived at by a feeling that "this seems serious enough for adverse" — a reviewer should be able to see the materiality and pervasiveness conclusion stated separately, not inferred from the final opinion chosen.
This is practical guidance written for audit teams, not an authoritative statement of any standard or statute. Standards, forms and timelines change. Check the current text issued by the ICAI and the relevant authority before relying on anything here in an audit file.
Related resources
- Audit workflow & automationSA 700: forming an opinion, and what "true and fair" actually requires concluding onFinishing every planned procedure isn't the same as forming an opinion. SA 700 is the step that happens after the checklist, not instead of it.
- Audit workflow & automationSA 706: emphasis of matter and other matter paragraphs, and when each appliesBoth paragraphs sit inside an unmodified opinion. The difference is what they're pointing at — something already in the financial statements, or something outside them.
- Audit workflow & automationSA 570: going concern, and when it actually changes the audit reportMost going-concern evaluations end exactly where they should: no material uncertainty, no change to the report. The standard is about the minority of cases where that's not true.
Free tools, no signup
Each one reads a file entirely in your browser — or, for two of them, just answers a few questions — and nothing is ever uploaded.
- Purchase register checkDuplicate payments, round-sum amounts, weekend-dated invoices, incomplete records.
- GSTR-2B reconcilerMatches your purchase register against GSTR-2B — missing invoices either side, amount mismatches.
- Bank reconciliation checkerMatches your cash book against a bank statement — what's outstanding on each side.
- Fixed asset register checkDuplicate asset codes, missing location or useful life, negative net book value.
- Payroll red-flag scannerBank accounts shared across employees, and records missing an ID, PAN or salary.
- CARO applicability checkerAnswer a few questions about the company and see which CARO 2020 clauses likely apply.
- MSME payment delay checkerMSME-flagged invoices paid — or still unpaid — beyond the 45-day Section 22 limit.
- Related-party transaction screenerTransactions above a threshold you set with no approval reference, grouped by counterparty.
- Depreciation useful life checkerCompares a useful life in use against the Schedule II, Part C indicative figure.
- Materiality calculatorOverall and performance materiality against PBT, revenue, assets or equity, with reasoning shown.
- Sample size calculatorStatistical sample size for a test of controls or a substantive test of detail.