ICAEW Assurance common mistakes
ICAEW Assurance · Understand the traps and how to avoid them.
Answering scenario questions with generic textbook definitions of audit risk, materiality or assertions instead of applying them to the named client, its industry and the figures given.
Candidates memorise definitions during revision and then reproduce them under time pressure, because it feels safer than committing to a judgement about the specific entity; ICAEW scenario stems are long and the temptation is to write everything known about the topic.
What to do instead
Before writing, underline the client name, industry, key ratios and any stated risk factors in the scenario, then force every paragraph to start with a sentence naming the client and the specific fact relied on. Practise by re-answering past scenarios where each mark-bearing point must cite a figure or fact from the stem; if a sentence would be true for any company, delete it.
Treating 'identify and explain' questions as pure identification, listing risk factors or deficiencies as bullet points with no explanation of the effect on the financial statements or the audit approach.
Under exam time pressure candidates count bullets as marks and stop once they have a list, missing that the verb 'explain' carries marks for the consequence, mechanism or audit response, not the label alone.
What to do instead
Use a fixed two-part sentence structure for every point: state the issue, then 'this means that...' linking it to misstatement risk, an assertion, or a specific audit procedure. When practising, mark your own answers against the verb in the requirement and rewrite any bullet that lacks a consequence clause.
Confusing the direction of risk when analysing ratios, for example saying a rising gross margin percentage increases the risk of overstated profit without explaining the mechanism, or mislabelling a fall in receivables days as a worsening of credit control.
Ratio analysis is often learned as formulas and trend directions rather than as a causal chain from business event to account balance to assertion, so candidates state the movement but not what it implies for misstatement.
What to do instead
For each ratio, rehearse a three-step chain: what changed, which account and assertion it affects, and whether the risk is over- or understatement. Work through a set of practice calculations and write the audit implication for each before checking; explicitly test both directions (increase and decrease) so the causal logic, not the memorised direction, drives the answer.
Describing audit procedures at too high a level ('test the balance', 'review the ledger', 'obtain comfort') rather than specifying the population, the source document, the assertion addressed and what would constitute evidence.
Procedural knowledge is often held as topic headings from study manuals, and candidates have not practised converting a heading into an executable instruction that another auditor could perform.
What to do instead
Write every procedure in a four-slot format: assertion addressed, population or sample, action and source document, and expected evidence or exception. For example, instead of 'test receivables', write 'for a sample of year-end trade receivables, agree to signed sales invoices and shipping documentation to test occurrence, and inspect post-year-end cash receipts to test valuation'. Self-check by asking whether a junior could perform the procedure from your wording alone.
Ignoring the requirement to consider materiality, performance materiality and clearly trivial thresholds when designing procedures, or applying a single percentage mechanically without adjusting for qualitative factors such as director remuneration, covenants or regulatory thresholds.
Materiality is taught with benchmark percentages, so candidates apply the arithmetic and stop, forgetting that the scenario usually plants a qualitative factor (loan covenant, bonus target, related-party balance) that should change the judgement.
What to do instead
In every planning question, write a short materiality memo: benchmark chosen and why, percentage, computed amount, performance materiality and clearly trivial threshold, plus one sentence on qualitative factors from the stem. Practise identifying covenant and remuneration triggers in scenarios and stating how they lower the threshold for specific balances.
Mixing up the components of the audit risk model, for example describing inherent risk as detection risk, or claiming the auditor controls inherent risk rather than assessing it.
The model is learned as a formula (audit risk = inherent x control x detection) and candidates recite the formula without mapping each component to who controls it and how it responds to the risk assessment.
What to do instead
Build a one-page table with the three components, who influences each, and the audit response each drives; inherent and control risk are assessed, detection risk is managed by the nature, timing and extent of procedures. Then answer three or four scenario questions where you must classify a given risk factor before writing the response.
Failing to distinguish tests of controls from substantive procedures, and answering a controls question with substantive testing or vice versa.
Both appear in the same scenarios and candidates default to substantive procedures because they are easier to describe, without checking whether the requirement asks about operating effectiveness of controls or about detecting material misstatement.
What to do instead
Annotate the requirement before answering: circle 'controls', 'substantive', 'analytical' or 'test of details'. For controls, write procedures that involve inspection of evidence of operation, enquiry combined with observation, or reperformance, and state the control being tested. For substantive work, state the assertion and the evidence source.
Writing conclusions that do not follow from the evidence discussed, for example concluding an opinion is unmodified while the body of the answer has identified a material uncorrected misstatement, or failing to state the effect on the audit report.
Candidates treat the conclusion as a formality and write the standard wording, rather than tracing the misstatement's materiality and pervasiveness through to the correct opinion type and reporting implication.
What to do instead
Practise a decision tree: is the misstatement material, and if so is it pervasive? Map each combination to unmodified, qualified, adverse or disclaimer, and to the corresponding paragraph placement. Always finish an evaluation question with two sentences: the opinion type and the reason, plus any additional report matter such as a key audit matter or emphasis paragraph.
Managing time badly: over-writing the first requirement until it consumes half the exam, then leaving later requirements with bullet fragments or unanswered.
Candidates write until they run out of knowledge rather than out of marks, because they cannot judge how much depth a requirement carries and fear missing easy marks in the first question.
What to do instead
Before writing, allocate minutes per requirement in proportion to marks and write the allocation at the top of the answer. Use a strict rule of one distinct mark-bearing point per mark plus a small buffer, then move on. In practice, use a timer and stop mid-sentence when the allocation expires to build the habit of leaving and returning.
Answering ethics and independence questions with a general statement that independence must be maintained, instead of identifying the specific threat, evaluating its significance and stating safeguards or the appropriate action.
Ethics is revised as principles rather than as a threat-and-safeguard framework, so candidates recognise that a situation is sensitive but cannot name the threat category or the required response.
What to do instead
Use a fixed structure for every ethics scenario: identify the threat (self-interest, self-review, advocacy, familiarity, intimidation), say why it arises in this scenario, assess significance using the specific facts, then state safeguards or decline the engagement. Practise by classifying ten short scenarios into threat categories before writing any evaluation.