Completing the Audit: The Final Phase

Fieldwork gathers; completion judges. The completion phase is where the audit’s accumulated findings — tested controls, vouched transactions, challenged estimates, confirmed balances — are converted into the opinion through four evaluations: subsequent events (ISA 560 — what happened after year-end, and does it change the statements?), going concern (ISA 570 — can the entity continue, and is the basis and disclosure right?), uncorrected misstatements (ISA 450 — individually immaterial findings that aggregate into materiality, plus the qualitative factors), and written representations (ISA 580 — management’s formal acknowledgments, dated to the report).

This page is deliberately the phase overview, not the standards’ detail. Each ISA has its own page carrying the full treatment — subsequent events, going concern, misstatement evaluation, representations — and this page links to them rather than duplicating them. What this page adds is orchestration: how the pieces fit, in what order, evidencing what, under the deadline pressure that makes completion the audit’s most failure-prone phase.

The completion discipline: every finding evaluated (not filed), every loose end tied (the confirmation that never came, the estimate never quite challenged, the subsequent event never considered), the file showing an audit that finished deliberately. Reviewers read completion files for exactly this — the partner’s review evidenced, the EQR completed before dating, the subsequent-events procedures extended to the report date. An audit that merely stops — fieldwork done, report signed — has skipped its final phase, whatever the timetable said.

ISA 560 requires the auditor to consider events from the financial statements’ date to the report date — the subsequent-events window — performing procedures designed to identify events needing adjustment or disclosure. Adjusting events: conditions existing at year-end, confirmed afterward — the doubtful customer who liquidates in February (the provision was light), the lawsuit settling for more than provided. Non-adjusting events: conditions arising after year-end — the March fire, the April acquisition — disclosed where material, not adjusted.

Completion procedures: inquiry of management about subsequent events (with written representations covering them); reading minutes of meetings after year-end; reviewing the latest interim financial statements and management accounts; obtaining the lawyer’s updated letter; considering management’s own subsequent-event procedures. Where events are identified: adjusting events → require adjustment (or the opinion reflects the misstatement); non-adjusting material events → require disclosure.

The window extends to the report date — procedures performed near it, not at fieldwork’s end weeks earlier. Facts becoming known after the report date but before issuance trigger duties too: discuss with management, consider whether the statements need amendment, and where they are amended, extend procedures and consider dual-dating (the report’s original date plus the event’s date, limiting subsequent-event responsibility to that event). After issuance, the duties narrow but don’t vanish. The ISA 560 page carries the full standard; completion’s orchestration point is timing — the window stays open until the report is dated, and dating certifies it was watched.

ISA 570’s completion duties: evaluate management’s assessment of going concern — its process, its period (at least twelve months from the financial statements’ date), its assumptions — and conclude. The auditor challenges the forecasts where going-concern risk exists: the cash-flow projections’ financing assumptions (committed facilities or hoped-for refinancing?), the covenant compliance prospectively, the sensitivity to plausible downsides. Contrary evidence — the financing file’s diagnostics, post-year-end events — is weighed, not wished away.

Three conclusions: going-concern basis appropriate, no material uncertainty — unmodified opinion, with the assessment documented. Material uncertainty exists — adequate disclosure → unmodified opinion with a Material Uncertainty Related to Going Concern section; inadequate disclosure → qualified or adverse. Basis inappropriate (the entity will not continue) — adverse opinion, the statements’ fundamental premise wrong.

Completion’s orchestration: going concern is concluded late because its evidence arrives late — final forecasts, post-year-end financing events, the subsequent-events review’s findings all feed it. The ISA 570 page carries the standard’s full detail — indicators, procedures, reporting. This page’s point is placement: going concern is a completion judgment, made on completion evidence, by the partner, before dating — and its most common failure (inadequate forecast challenge under deadline pressure) is a completion failure, which is why the phase needs calendar protection.

Fieldwork finds misstatements; some get corrected, some don’t — and ISA 450 governs the rest. Accumulate: every uncorrected misstatement other than the clearly trivial, in the summary of uncorrected differences — factual, judgmental (the estimate’s reasonable range exceeded), and projected (sampling’s extrapolations). Communicate: to those charged with governance, with their individual and aggregate effect on the opinion, requesting correction — the communication that makes governance complicit in, or corrective of, the remaining misstatement.

Evaluate: individually and in aggregate against materiality — the individually immaterial items that sum to materiality are the classic trap — and qualitatively: the misstatement that turns profit to loss, meets or misses a trend, breaches a covenant, involves bias, or indicates fraud is material by nature whatever its size. Prior periods’ uncorrected misstatements’ carryover effects are considered (the iron curtain vs rollover methods — the evaluation’s technical layer).

Completion’s orchestration: the ISA 450 evaluation happens when all findings are in — it is inherently a completion procedure, because aggregation needs the complete set. The bias review belongs here too: do the judgmental misstatements pattern in one direction (the estimates all flattering profit)? — ISA 540’s bias indicators evaluated across the file. The ISA 450 page carries the detail; this page’s point is that the summary of uncorrected differences is the completion file’s quantitative conscience — the document proving the opinion considered everything found, not just everything corrected.

ISA 580 requires written representations from management (and, where appropriate, those charged with governance): acknowledging responsibility for the financial statements; confirming all relevant information was provided and transactions recorded; supporting significant judgments — the estimate’s assumptions, the going-concern assessment’s basis, subsequent events’ completeness, related-party disclosures’ completeness. Dated as near as practicable to the report date — they speak to the report date’s evidence.

Their evidential status is precisely defined: necessary audit evidence, never a substitute for other procedures. The representation about the estimate’s reasonableness does not replace challenging it; the completeness representation does not replace the unrecorded-liability search. And doubt about their reliability — inconsistency with other evidence, evasiveness in their preparation — contaminates all management-provided evidence, triggering reconsideration of risk assessments and procedures.

Refusal to provide requested representations is a scope matter: the auditor considers its effect, communicates with governance, and evaluates the reporting consequences — the refusal itself is evidence about management’s integrity. Completion’s orchestration: representations are obtained late (they cover the subsequent-events window and the final judgments) but prepared for throughout (the difficult representations — going concern, estimates, fraud knowledge — are discussed early, not sprung at signing). The ISA 580 page carries the standard; this page notes the discipline — representations evidence the close, they don’t substitute for the audit.

Completion’s quality gates, in order. The engagement team’s review: work reviewed by senior staff, with significant judgments and significant risks reviewed before the report date — ISA 220 (Revised)’s requirement, planned from the strategy phase. The partner’s review and conclusion: the partner satisfies themselves the evidence supports the opinion, completion procedures were performed, and the report may be dated — the signature’s precondition, not its accompaniment.

The engagement quality review (ISQM 2): for engagements requiring it — listed-entity audits and others the firm’s criteria capture — the EQR reviewer’s evaluation of significant judgments must be complete before the report is dated. Not concurrent, not after: before. The dating rule enforces it — a report dated before the EQR completed is a quality-management breach whatever the review later concludes.

Dating discipline: the report date certifies sufficient appropriate evidence — including subsequent-events procedures to that date, representations dated accordingly, and all quality reviews complete. Subsequent events after dating but before issuance: ISA 560’s duties (discuss, consider amendment, dual-date where amended). The orchestration point: these gates are sequential and non-compressible — review, then EQR, then dating, each certifying readiness for the next. Deadline pressure compresses them at the opinion’s peril; the partner who protects the gates protects the opinion.

The completion file tells the story of the finish: the subsequent-events work (procedures, findings, conclusions — the window watched to the report date); the going-concern evaluation (management’s assessment challenged, conclusion reached, reporting decided); the summary of uncorrected misstatements (accumulated, communicated, evaluated — the aggregate view with qualitative factors); the written representations (obtained, dated, consistent with other evidence); the review trail (who reviewed what, when — the significant judgments’ review evidenced); the EQR (where required — completed before dating, its conclusions recorded).

Reviewers read completion for deliberateness: does the file show findings evaluated or merely filed? Was the going-concern conclusion evidenced or asserted? Did subsequent-events procedures reach the report date? The rushed finish has a documentary signature — thin completion sections, review dates clustered impossibly, the EQR dated after the report — and inspectors read signatures.

UAE completion notes: multi-authority filing deadlines mean the report date must serve the earliest deadline while preserving the gates — plan the completion calendar backwards from the filing date, protecting review and EQR time. Subsequent events in the UAE context include post-year-end regulatory developments and group restructuring announcements — the inquiry net cast accordingly. And the representations’ Arabic/English bilingual reality: ensure the signed representations match what was discussed, in the language of discussion — the formality of representations depends on their being understood, not just signed.

Completion questions test orchestration — markers route each scenario fact to its ISA. The subsequent-event scenario (the post-year-end fire, the customer liquidation, the lawsuit settlement): classify (adjusting vs non-adjusting — conditions at year-end?), state the procedure (inquiry, minutes, interim statements, lawyer’s letter), conclude (adjust or disclose; opinion consequences if refused). Always extend procedures to the report date — the answer that stops at fieldwork’s end misses ISA 560’s window.

The going-concern scenario (breached covenant, refused refinancing, forecast assumptions): identify indicators, describe the ISA 570 evaluation (challenge forecasts, financing assumptions, sensitivity), conclude (no uncertainty / material uncertainty with disclosure / inappropriate basis) with the reporting consequence of each. The misstatement scenario: aggregate the uncorrected items, apply qualitative factors, conclude on materiality — showing the aggregate view, not item-by-item dismissal.

The representations scenario: the refused representation — scope implications, governance communication, reporting consequences; the inconsistent representation — reliability doubt contaminating other evidence. Traps: dating the report before the EQR completes; treating representations as substitutes for procedures; evaluating misstatements only quantitatively; and forgetting dual-dating for post-report-date amendments. The exam sentence: route each fact to its ISA (560/570/450/580), extend to the report date, gate review before dating — completion as orchestration, standards as instruments.