By the end of this chapter you'll be able to…

  • 1State the purposes of audit documentation under SA 230 and apply the experienced auditor test
  • 2State the assembly and retention rules, and who owns the audit file
  • 3Explain the documentation requirement for a change made after the final file is assembled
  • 4Distinguish the three windows of subsequent events and the auditor's obligation in each
  • 5Apply the adjusting/non-adjusting distinction to a subsequent event
  • 6Explain the respective responsibilities of management and the auditor for going concern
  • 7Identify going concern indicators across financial, operating and other categories
  • 8Explain what a material uncertainty related to going concern requires
  • 9Describe the overall review at completion and its components
  • 10Explain why written representations alone are never sufficient appropriate audit evidence
💡
Why this chapter matters in CMA Intermediate
Working papers are not a byproduct of the audit — SA 230's own purpose statement makes them evidence of the basis for the conclusion itself, tested against a specific, examinable standard: would an experienced auditor with no prior connection to this engagement understand what was done and why just from reading the file? Subsequent events split cleanly into three windows with genuinely different obligations, and confusing an active duty to search with the narrower duty to respond to a fact that happens to come to light is the single most common error in this area. Completion is where the whole audit sequence converges: every earlier chapter's evidence is finally weighed together to answer the one question the entire engagement has been building towards.

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.

Key formulas & results

Everything to memorise for the exam hall, in one card. Screenshot this for revision.

Documentation test: sufficient for an experienced auditor with no prior connection to the audit to understand procedures, evidence and conclusions
Final file assembly: ordinarily not more than 60 days after the date of the auditor's report
Retention: ordinarily not shorter than 7 years from the date of the auditor's report
Audit documentation is the property of the auditor, not the entity
Subsequent events window 1 (balance sheet date to report date): ACTIVE duty to search; adjusting events amend the statements, non-adjusting events require disclosure only
Subsequent events window 2 (after report date, before issuance): NO active duty to search, but must act on a fact that comes to light
Subsequent events window 3 (after issuance): NO active duty to search, but must consider revision if a fact comes to light
Going concern foreseeable future = ordinarily at least 12 months from the balance sheet date
Written representations alone NEVER provide sufficient appropriate audit evidence on their own
⚠️

Traps CMA Intermediate sets — and how to dodge them

These are the exact option-traps and misreads that cost marks under negative marking.

WATCH OUT
Treating the three subsequent events windows as one undifferentiated period with a single obligation
WATCH OUT
Believing the auditor has an active duty to search for subsequent events even after the date of the auditor's report
WATCH OUT
Confusing an adjusting event (amend the statements) with a non-adjusting event (disclose only)
WATCH OUT
Assuming the entity has an automatic right to the audit working papers
WATCH OUT
Deleting or discarding documentation, or failing to record who/when/why for a post-assembly change
WATCH OUT
Believing going concern is solely the auditor's responsibility rather than primarily management's, with the auditor evaluating management's assessment
WATCH OUT
Treating a going concern indicator in isolation as automatically meaning a material uncertainty exists, without considering management's mitigating plans
WATCH OUT
Relying on a management representation alone to support a matter capable of other corroboration

Exam-pattern practice

PYQ-style questions with full solutions. Work through them as a readiness check — mark yourself honestly and get your gap report at the end.

Readiness check

Are you exam-ready for Audit Documentation, Completion and Review?

15 problems from this chapter. Try each one, reveal the worked solution, mark yourself honestly — get your gap report at the end.

15 questions~11 min

5-minute revision

The whole chapter, distilled. Read this the night before the exam.

  • Documentation test: would an experienced auditor with no prior connection understand the file — write for a stranger, not future-self
  • Final file assembled within 60 days of the report date; retained for at least 7 years; owned by the auditor, not the entity
  • Any post-assembly change must be documented with reason, date and who made/reviewed it — never made silently
  • Window 1 (statements date to report date): ACTIVE search duty; adjusting events amend the statements, non-adjusting events need disclosure only
  • Window 2 (after report, before issuance): reactive only — act if a fact comes to light, no proactive search
  • Window 3 (after issuance): reactive only — consider revision if a fact comes to light
  • Going concern is management's assessment first; the auditor evaluates the appropriateness of that assessment, not a from-scratch prediction
  • Foreseeable future = at least 12 months from the balance sheet date
  • Going concern indicators: financial (liquidity/ratios), operating (key people, markets), other (legal, statutory breaches)
  • Indicators trigger further work and weighing against management's mitigating plans — presence alone doesn't equal a material uncertainty
  • Material uncertainty needs specific disclosure and a corresponding report section, distinct from opinion modification
  • Overall review: sufficient evidence overall, uncorrected misstatements individually AND in aggregate, final analytics, written representations
  • Written representations supplement other evidence — they never stand alone as sufficient appropriate evidence

CMA Intermediate question blueprint

How this topic is asked, tier by tier — so you can prep to the pattern.

Typical weightage: 10

Exam-hall strategy

Battle-tested tips from mentors and toppers for this topic under the sectional clock.

  1. Cite SA 230, SA 560, SA 570 or SA 580 explicitly wherever their specific subject matter is being discussed
  2. Always name which of the three subsequent events windows a fact pattern falls into before stating the auditor's obligation
  3. State the adjusting/non-adjusting classification and give the reason (evidence of a condition existing at the balance sheet date, or not) explicitly
  4. Frame going concern answers as management assesses, the auditor evaluates — never reverse the two roles
  5. Weigh going concern indicators against mitigating plans explicitly rather than concluding a material uncertainty from indicators alone
  6. State that written representations supplement rather than substitute for other evidence whenever they appear in a scenario

Beyond the exam

Where this skill shows up in the job you're competing for — and in life.

The experienced auditor test is the actual standard appli…

The experienced auditor test is the actual standard applied by quality control reviewers and regulatory inspectors examining real audit files after the fact

The 60-day assembly deadline and 7-year retention rule ar…

The 60-day assembly deadline and 7-year retention rule are hard compliance requirements every audit firm's file management system is built around

Subsequent events review

Subsequent events review, particularly reading post-year-end board minutes and management inquiry, is a standard, late-stage procedure performed just before every audit report is signed

Going concern assessment became a subject of intense real…

Going concern assessment became a subject of intense real-world scrutiny following corporate collapses where a clean audit opinion was issued shortly before a company failed, driving much of the current detail in SA 570

Where else this topic is tested

Prepare once, score in every exam that asks it.

CA Final Paper 3 — Advanced Auditing, Assurance and Professional Ethics, where SA 570 and going concern reporting are developed in far greater depth
CS Executive — Secretarial Audit, Compliance Management and Due Diligence
CMA Intermediate — Cost and Management Audit
ACCA Audit and Assurance, where ISA 230, ISA 560, ISA 570 and ISA 580 are examined in near-identical terms

Questions aspirants ask

Pulled from the Q&A community and mentor sessions.

Because the file remains the primary evidence of what was done, and disputes, regulatory inspections, or quality reviews can arise years after an audit opinion is issued, sometimes triggered by matters that only come to light later, such as a fraud eventually discovered or litigation alleging the audit was deficient. The retention period ensures the auditor's own record of the work performed, the evidence obtained and the professional judgements made remains available to be examined, defended, or learned from for a meaningful period after the engagement concludes, rather than being available only while the matter is fresh and then lost.

Typically through the ordinary channels by which any professional becomes aware of relevant news: continuing contact with the client on other matters, industry news, a client voluntarily informing the auditor of a significant development, or a subsequent regulatory or legal filing coming to the auditor's attention in the ordinary course. The absence of an active search duty does not mean the auditor ignores information that does reach them; it means the auditor is not required to proactively investigate or make fresh inquiries specifically to hunt for such facts once the report has been issued, a materially lighter obligation than the active procedures required in the first window.

Yes, and this is a genuinely nuanced area of professional judgement rather than a binary test. Even where the auditor finds a mitigating plan credible enough that no modification of the audit opinion is warranted, the auditor may still conclude that a material uncertainty exists and requires specific disclosure, if the underlying situation remains genuinely uncertain, dependent on future events such as whether a refinancing actually completes on the terms currently contemplated, rather than fully resolved. The disclosure of a material uncertainty, with a corresponding section in the auditor's report, is a distinct outcome from an unqualified opinion with no such disclosure, and is also distinct from a modified opinion; it sits as a middle position specifically designed for exactly this kind of genuinely uncertain, but not necessarily fatal, situation.
Header Logo