Audit Documentation, Completion and Review
Weightage: Chapter 6 of ICAI's Paper 5 syllabus, roughly 10 marks. The "document" and "evaluate at completion" stages of the audit sequence — where the audit's individual pieces of evidence become one coherent conclusion.
Audit documentation — SA 230
Audit documentation is the record of audit procedures performed, relevant audit evidence obtained, and conclusions the auditor reached — commonly called working papers.
Purpose: it provides evidence of the auditor's basis for a conclusion about the achievement of the overall objectives of the audit, and evidence that the audit was planned and performed in accordance with the SAs and applicable legal and regulatory requirements. Additional purposes include: assisting the engagement team to plan and perform the audit; assisting members of the team responsible for supervision to direct, supervise and review audit work; enabling the team to be accountable for its work; retaining a record of matters of continuing significance to future audits; enabling quality control reviews and inspections; and enabling external inspections.
The examinable test: documentation should be sufficient to enable an experienced auditor, having no previous connection with the audit, to understand the nature, timing and extent of procedures performed, the results and evidence obtained, and significant matters and the conclusions reached — this "experienced auditor test" is the standard against which the adequacy of a working paper file is judged, and it is precisely why a competent auditor writes documentation for a stranger to understand, not merely for their own future reference.
Assembly and retention: the auditor must assemble the final audit file on a timely basis, ordinarily not more than 60 days after the date of the auditor's report. Audit documentation is the property of the auditor — the entity has no automatic right to it, though the auditor may, at discretion, make portions available to the client. Retention period: for an audit of financial statements, ordinarily not shorter than 7 years from the date of the auditor's report (or, if later, the group auditor's report where applicable).
Changes after assembly — after the final file is assembled, documentation is not deleted or discarded before the end of the retention period; where a change is necessary after assembly (for instance, correcting an administrative matter), it must be documented, regardless of its nature, along with when and by whom it was made and reviewed, and the specific reasons for it.
Subsequent events — SA 560
Subsequent events are events occurring between the date of the financial statements and the date of the auditor's report, and facts that become known to the auditor after the date of the auditor's report. This chapter treats these as two distinct windows with different obligations, and confusing them is the single most common error:
Window 1 — between the balance sheet date and the date of the auditor's report. The auditor has an active duty to perform procedures designed to identify events in this period that may require adjustment of, or disclosure in, the financial statements — reading minutes of meetings, inquiry of management, reviewing the entity's latest available interim financial information. This connects directly to the adjusting/non-adjusting distinction from Paper 1's AS 4: an adjusting event requires the financial statements themselves to be amended; a non-adjusting event requires disclosure only.
Window 2 — after the date of the auditor's report but before the financial statements are issued. The auditor has no obligation to actively search for further events, but if a fact becomes known to the auditor that, had it been known at the date of the report, might have caused the auditor to amend the report, the auditor must discuss the matter with management and take appropriate action (which may include a new or amended report).
Window 3 — after the financial statements have been issued. Similarly, no active duty to search, but where a fact becomes known that would have caused amendment had it been known earlier, the auditor considers whether the financial statements need revision and discusses with management, potentially leading to a revised set of financial statements and a new auditor's report.
Going concern — SA 570
Going concern is a fundamental assumption in preparing financial statements (Paper 1's AS 1 material, examined here from the audit side) — the entity is assumed to continue in operation for the foreseeable future, ordinarily meaning at least twelve months from the balance sheet date, with neither intention nor necessity to liquidate or cease operations.
Management's responsibility is to assess the entity's ability to continue as a going concern when preparing the financial statements. The auditor's responsibility is to obtain sufficient appropriate audit evidence about the appropriateness of management's use of the going concern basis and to conclude whether a material uncertainty exists that requires disclosure.
Indicators of going concern doubt — financial indicators (net liability position, negative operating cash flows, adverse key financial ratios, inability to pay creditors on due dates), operating indicators (loss of key management, loss of a major market or franchise, labour difficulties), and other indicators (pending legal proceedings that may result in claims the entity cannot satisfy, non-compliance with capital or statutory requirements).
A material uncertainty related to going concern — where events or conditions identified, individually or collectively, may cast significant doubt on the entity's ability to continue as a going concern, and where, having considered management's plans, the auditor concludes a material uncertainty exists, this requires specific disclosure in the financial statements and a corresponding, specifically worded section in the auditor's report.
Completion and final review
The overall review at the end of the audit brings together all the individual pieces of evidence gathered throughout the engagement and asks the question every prior chapter has been building towards: taken as a whole, does the evidence support the opinion the auditor is about to give?
This includes: evaluating whether sufficient appropriate audit evidence has been obtained (SA 200's own standard, applied here as the final checkpoint); evaluating the effect of uncorrected misstatements, both individually and in aggregate, against materiality; performing final analytical procedures on the financial statements as a whole, to assess whether they are consistent with the auditor's understanding of the entity; and obtaining written representations from management on matters the auditor cannot otherwise corroborate.
Written representations are required as audit evidence, but SA 580 is explicit that they do not, on their own, provide sufficient appropriate audit evidence about any of the matters they address — they supplement, and are corroborated by, other evidence gathered, never substituting for it.
Documenting review itself
Just as the underlying audit work is documented, the review of that work by more senior team members is itself documented — who reviewed what, when, and what (if anything) was identified and resolved — because supervision and review are themselves part of what the "experienced auditor" reading the file later needs to be able to see evidence of, connecting directly back to SA 230's documentation purpose.
