SOCPA Auditing common mistakes
SOCPA Auditing · Understand the traps and how to avoid them.
Writing audit procedures as vague assurances ('check the invoices are valid', 'ensure controls are adequate') instead of stating the assertion tested, the population, the sample selection, and the evidence that would satisfy it.
Candidates memorise that procedures exist but never practise converting them into testable steps, so under time pressure they default to reassurance language that an examiner cannot mark as a procedure.
What to do instead
Drill a fixed template for every procedure: assertion → population and source → selection method → what is inspected or recomputed → what constitutes an exception. Rewrite ten past procedure answers into this template and self-mark against each of the four elements.
Confusing the three tiers of assurance engagement (reasonable, limited, and related-services such as agreed-upon procedures and compilations) - for example, describing a review as giving 'reasonable assurance' or stating that an AUP engagement expresses any opinion at all.
The engagement types are learned as a list of names rather than as a matrix of evidence, assurance level, and form of report, so the distinctions collapse under exam pressure.
What to do instead
Build a one-page matrix with rows for audit, review, AUP, and compilation, and columns for level of assurance, nature of procedures, independence required, and the exact wording of the conclusion. Redraw it from memory until it is exact.
Preparing or adjusting individual ledger entries correctly but failing to carry the effect through to the statement of financial position, statement of profit or loss, and disclosure notes, so the final statements do not articulate.
Candidates treat each adjustment as an isolated journal and never build the habit of tracking the double entry through to the face of the statements and the notes.
What to do instead
For every adjustment, write the journal, then state in one line its effect on each affected statement line and any required disclosure. Finish each question by reconciling profit to closing retained earnings as a check.
Applying the wrong measurement basis to a classification question - for example, measuring a financial liability at fair value through profit or loss when amortised cost applies, or expensing borrowing costs that qualify for capitalisation.
Standards are recalled by topic heading rather than by the decision tree that selects the measurement model, so the candidate picks a familiar basis instead of the one the facts require.
What to do instead
Practise classification-first: for each item, state the classification (e.g., amortised cost vs. FVTPL, qualifying asset vs. not), cite the criterion that drives it, and only then compute. Keep a decision-tree sheet per standard and use it on every practice question.
Computing variances arithmetically correctly but labelling them with the wrong sign or failing to explain the operational cause, so favourable and adverse are reversed or the variance is left as a number with no interpretation.
Candidates focus on the formula and skip the convention (standard minus actual, price versus usage) and the narrative the examiner is actually testing.
What to do instead
Before calculating, write the sign convention at the top of the answer and state which figure is standard and which is actual. After each variance, add one sentence naming a plausible operational cause and who is accountable for it.
Treating fixed costs as product costs in marginal-costing decisions, or using absorption profit to make a short-term accept/reject decision, and mis-handling limiting-factor ranking by ranking on unit contribution instead of contribution per unit of the scarce resource.
Absorption costing is the default taught first, and the scarcity-ranking rule is memorised as a phrase rather than applied to the constraint given in the scenario.
What to do instead
For every decision question, first classify each cost as fixed or variable and identify the scarce resource explicitly. Rank products by contribution per unit of that resource, and reconcile marginal profit to absorption profit separately.
Computing tax on an individual or entity by applying the headline rate to total income, ignoring the progressive brackets, exemptions, allowable deductions, and the ordering of reliefs and losses.
Candidates learn rates as single numbers and do not rehearse the step-by-step computation sequence that the law prescribes.
What to do instead
Memorise and practise a fixed computation ladder (gross income → exemptions → allowable deductions → taxable base → bracket application → reliefs/credits → final liability) and run at least five full computations per tax type using the ladder before attempting mixed questions.
Mixing up the tax point, the filing deadline, and the payment deadline, or applying the wrong registration threshold, so procedural questions are answered with a plausible but incorrect date or figure.
Procedural rules are skimmed as background reading while computational practice dominates study time, so dates and thresholds are remembered only approximately.
What to do instead
Build a single reference table of tax points, filing dates, payment dates, thresholds, and penalties for each tax type, and test yourself on it weekly until recall is exact. Flag any figure you cannot state with confidence for re-reading of the primary source.
Answering a commercial-law scenario by naming a general principle ('the contract is void', 'the agent had authority') without applying the specific statutory or case-law test to the facts given, and without addressing the counter-argument.
Candidates revise law as definitions to be recited rather than as tests to be applied, and run out of time before structuring an applied answer.
What to do instead
Use a strict IRAC structure on every scenario: identify the precise legal issue, state the rule and its source, apply the rule element by element to the named facts, then conclude. Allocate marks explicitly to the application step and always write the strongest opposing argument before concluding.
Treating threats to independence and other ethical requirements as a list to be named, rather than identifying the specific threat type in the scenario, evaluating its significance, and proposing a safeguard - or failing to recognise when no safeguard can reduce the threat to an acceptable level.
Ethics is revised as vocabulary (self-interest, self-review, familiarity) and candidates do not practise the evaluate-and-respond step, nor the situations where the engagement must be declined.
What to do instead
For each scenario, name the threat, state which specific interest creates it, judge significance against the facts, then propose a concrete safeguard or state that the engagement must be refused. Practise at least one 'no safeguard available' case per area of the code so the exception is recognised.