How auditors complete written representations, subsequent-event procedures, final communications, documentation, and report release steps.
Before issuing the auditor’s report, the engagement team must finish the procedures that connect audit evidence to report readiness. The final stage includes written representations, subsequent-event review, final communications, documentation completion, and resolution of open review notes. These steps are not formalities. They can reveal new evidence that changes adjustment, disclosure, or report conclusions.
AUD questions often test timing. The auditor’s report date, management representation letter date, subsequent-events responsibility, and documentation completion date each serve a different purpose.
flowchart LR
A["Financial statement date"] --> B["Subsequent-event procedures"]
B --> C["Written representations"]
C --> D["Final communications and review"]
D --> E["Auditor's report date"]
E --> F["File assembly and retention"]
Written representations are written confirmations from management and, when appropriate, those charged with governance. They confirm management’s responsibilities and specific representations relevant to the audit.
| Representation area | Why it matters |
|---|---|
| Financial statement responsibility | Management confirms responsibility for fair presentation |
| Internal control responsibility | Management confirms responsibility for controls relevant to financial reporting |
| Completeness of information | Management confirms all records, minutes, and information were provided |
| Fraud and noncompliance | Management confirms known or suspected fraud and illegal acts were disclosed |
| Related parties | Management confirms relationships and transactions were disclosed |
| Subsequent events | Management confirms events through the report date were evaluated |
| Uncorrected misstatements | Management acknowledges uncorrected items and its view of immateriality |
The representation letter is ordinarily dated the same date as the auditor’s report. If management refuses to provide required written representations, the auditor evaluates the effect as a scope limitation and considers whether withdrawal or a disclaimer is necessary.
Subsequent-event procedures cover the period after the financial statement date through the auditor’s report date. The auditor seeks evidence about events that may require adjustment or disclosure.
| Event type | Financial statement effect | Example |
|---|---|---|
| Recognized subsequent event | Adjust the financial statements because it provides evidence about conditions existing at year-end | Settlement of year-end litigation confirming the liability |
| Nonrecognized subsequent event | Disclose if necessary because it relates to conditions arising after year-end | Major acquisition after year-end |
| Later-discovered fact | Consider whether report dating, dual dating, reissuance, or other action is needed | Auditor learns after report release that evidence existed before report date |
Procedures include reading post-year-end minutes, inquiring of management and legal counsel, reviewing interim financial statements, inspecting significant post-year-end transactions, reading subsequent cash disbursements, and obtaining written representations.
The auditor’s report date should not be earlier than the date the auditor has obtained sufficient appropriate audit evidence, including evidence that the financial statements and disclosures are prepared and management has accepted responsibility.
If a subsequent event occurs after the original report date but before report release, the auditor may either extend all subsequent-event procedures to a new report date or dual-date the report for the specific event. Dual dating limits the auditor’s responsibility for later events to the specific disclosed event.
| Dating choice | Auditor responsibility |
|---|---|
| Single later report date | Extends subsequent-event responsibility through the later date for all events |
| Dual date | Extends responsibility only for the specific later event |
| Original date unchanged | Appropriate only when no later event requires additional dating responsibility |
Before release, the auditor completes required communications with management and those charged with governance. These may include significant findings, uncorrected misstatements, significant difficulties, disagreements with management, material weaknesses or significant deficiencies, independence matters, and other required communications.
The audit file should then be assembled and retained under applicable standards and firm policy. Public-company audits under PCAOB standards use a 45-day documentation completion period after report release. Other standards and firm policies may use different assembly periods, but the principle is the same: after the documentation completion date, additions are restricted and must be clearly documented.
Documentation completion is not an opportunity to create new audit evidence after the fact. Workpapers should show procedures performed, evidence obtained, conclusions reached, review completion, and report readiness.
Do not date the representation letter earlier than the auditor’s report date. It should cover the period through the report date.
Do not confuse recognized and nonrecognized subsequent events. Existing year-end conditions usually lead to adjustment; new post-year-end conditions usually lead to disclosure if material.
Do not assume dual dating extends responsibility for all subsequent events. It limits responsibility to the specific later event.
Do not treat documentation lockdown as permission to perform missing audit work after release. The file assembly period is for assembling and finalizing documentation, not replacing procedures.