Audit Evidence, Completion and Review — Case Studies

Why this chapter has no new standards, only new demands

Every standard this chapter draws on — SA 500 on audit evidence generally, SA 501 on specific considerations for selected items, SA 505 on external confirmations, SA 510 on initial engagements and opening balances, SA 530 on audit sampling, SA 550 on related parties, SA 560 on subsequent events, SA 570 on going concern, and SA 580 on written representations — was already examined at Intermediate level in full definitional depth, and the method chapter's opening note flagged exactly this cluster as one where Final level tests application, not recall. This chapter accordingly introduces no new standard; its purpose is to show, through worked examples, precisely what "application at professional depth" actually looks like when these standards are woven together into a single, realistic scenario rather than tested one at a time.

Reliability hierarchy applied under pressure

The Intermediate-level reliability hierarchy for audit evidence — evidence obtained directly by the auditor is more reliable than evidence obtained indirectly; evidence from independent external sources is more reliable than evidence generated internally; written evidence is more reliable than oral evidence; original documents are more reliable than photocopies or facsimiles — is tested at Final level specifically in scenarios engineered to create tension between two pieces of evidence of differing reliability that point in different directions. A Final-level answer must resolve this tension explicitly: where a highly reliable piece of evidence (an external bank confirmation) and a less reliable piece of evidence (an internal management schedule) conflict, the auditor does not simply average the two or defer to whichever is more convenient — the auditor investigates the discrepancy, and the more reliable source generally, though not automatically or unconditionally, carries greater weight in resolving it, unless specific circumstances (such as evidence the external source itself may be unreliable in this particular instance) suggest otherwise.

External confirmations under genuinely difficult conditions

Non-responses and alternative procedures. Where a confirmation request under SA 505 receives no response, the auditor performs alternative procedures — examining subsequent cash receipts for a receivable confirmation, for instance — and a Final-level scenario typically makes these alternative procedures themselves imperfect or incomplete, requiring you to assess whether the alternative evidence obtained is genuinely sufficient, or whether the non-response itself should be treated as a scope limitation with reporting consequences if no adequate alternative evidence can be obtained at all.

Exceptions and their investigation. A confirmation response that disagrees with the recorded amount is not, on its own, evidence of a misstatement — it requires investigation, since the discrepancy could reflect a timing difference (goods in transit, a payment not yet recorded by one party), a genuine error on either side, or a more serious issue; a Final-level scenario typically presents a specific discrepancy and asks you to work through which of these explanations the additional facts given actually support.

Related parties: the standard most prone to management concealment

SA 550's core challenge, tested repeatedly at Final level, is that related party relationships and transactions are inherently susceptible to being concealed or misrepresented by management, since a related party transaction on non-arm's-length terms is precisely the kind of transaction management might have an incentive to disguise as an ordinary, unrelated transaction. A Final-level scenario typically embeds a related party relationship the auditor was not directly told about, requiring you to identify the specific indicators in the fact pattern (unusual terms, a transaction with no clear business rationale, an intermediary entity whose ownership traces back to a related individual) that should have prompted the auditor's professional scepticism, and the specific audit procedures — reviewing shareholder registers, minutes of board and shareholder meetings, and inquiring specifically of those charged with governance about related party relationships management may not have volunteered — that address this heightened risk of concealment.

Subsequent events across the entire window, applied precisely

The three subsequent events windows from Intermediate — between the reporting date and the date of the auditor's report (an active duty to perform procedures identifying such events); between the report date and the date the financial statements are issued (no active duty, but if the auditor becomes aware of a fact through some other means, the auditor must act on it); and after the financial statements are issued (a duty arising only if the auditor becomes aware of a fact that existed at the report date and might have caused a modified opinion) — are tested at Final level through scenarios that deliberately blur which specific window a described event actually falls within, requiring you to identify the precise date the auditor became aware of the event, the precise date the financial statements were issued, and only then determine which of the three distinct duty levels genuinely applies.

Going concern: the sharpest professional judgement in this cluster

The auditor's responsibility is evaluative, not diagnostic. The auditor does not determine whether an entity will actually fail — the auditor evaluates whether management's own going concern assessment, and the disclosures accompanying it, are appropriate given the entity's specific circumstances, a distinction Final-level scenarios test by presenting facts where an entity is genuinely troubled but management's disclosure is (or is not) adequate to that trouble, requiring you to assess the disclosure's adequacy specifically, not merely the entity's underlying financial health.

Indicators versus a definitive conclusion. A Final-level scenario typically presents several indicators simultaneously — recurring operating losses, a working capital deficiency, loss of a key customer, denial of trade credit by suppliers — and expects you to weigh them together, considering also any specific, credible mitigating factors management has identified (a committed refinancing, an asset disposal plan with a signed buyer), rather than mechanically concluding that the mere presence of any indicator automatically means a material uncertainty exists; the professional judgement lies precisely in weighing indicators against mitigating factors on the specific facts given, not in applying a mechanical checklist.

Written representations: necessary, never sufficient, alone

SA 580's central point, worth restating precisely because Final-level scenarios test it directly: written representations are necessary audit evidence — the auditor cannot conclude the audit without obtaining them — but they are never, on their own, sufficient appropriate audit evidence about any specific matter to which they relate; a written representation from management confirming a specific accounting judgement does not substitute for the auditor's own independent corroborating evidence on that same judgement, and a scenario presenting a written representation as the auditor's sole evidence for a material item should prompt you to flag this as inadequate, not sufficient, evidence.

SA 510: initial audit engagements

For a first-year audit, the auditor must obtain sufficient appropriate audit evidence about whether the opening balances contain misstatements that materially affect the current period's financial statements, and whether appropriate accounting policies reflected in the opening balances have been consistently applied in the current period — where the prior period was audited by a different auditor, this typically involves reviewing that predecessor auditor's working papers (where permission is granted and professional and legal considerations permit) and performing specific audit procedures directly on the opening balances themselves, precisely because a first-year auditor cannot simply assume the entity's own opening figures are correct without some genuine, independent verification, given the auditor had no direct involvement in establishing them.

Why this chapter rewards worked practice over further reading

Because this chapter tests the application of already-known standards rather than teaching new ones, the single most effective preparation strategy is working through varied, layered case studies specifically designed to create the kind of ambiguity and tension between competing pieces of evidence that a real audit genuinely presents, rather than re-reading the underlying standards' text, which you should already know cold from Intermediate-level preparation. Treat every practice problem in this chapter as training for exactly the professional judgement — resolving conflicting evidence, weighing indicators against mitigating factors, recognising when written representation alone is not enough — that this paper's case-study format is specifically built to test.