Industry News & Expert Tips
Subsequent Events Under HKSA 560: A Practical Completion Review for Hong Kong Auditors
Practical audit procedures, evidence points, and documentation considerations for Hong Kong audit teams.
Practice Overview
Last updated: 16 September 2026
A well-designed subsequent-events review helps the audit team identify matters arising after the reporting date that may affect the financial statements, including their accounting, disclosure or the auditor’s conclusion. Under HKSA 560, the work should be planned and completed through the date of the auditor’s report, with procedures tailored to the entity’s risks, reporting timetable and likely sources of post-year-end information. At a high level, HKAS 10 distinguishes events that provide evidence of conditions existing at the reporting date from events that arise afterwards; the distinction informs whether an adjustment, disclosure or neither is appropriate.
For Hong Kong audit practices, quality commonly depends less on a generic checklist than on a disciplined completion process: a clear coverage period, focused enquiries, reliable follow-up evidence, timely escalation and a conclusion that is traceable in the file. This article is general professional technical education, not engagement-specific audit or legal advice. Auditors should apply professional judgment, consult current authoritative material and assess the facts and circumstances of each engagement.
Key Audit Issues
Defining the review period and keeping it current
A completion review can be incomplete when the team treats it as a year-end task rather than work that continues to the auditor’s report date. Changes to the expected signing timetable, delayed financial-statement approval or late information from management should trigger an update to the subsequent-events plan and the evidence obtained.
Completeness across dispersed information sources
Material events may sit outside the general ledger: financing negotiations, litigation, covenant breaches, customer failures, acquisitions or disposals, cyber incidents and fraud allegations may be known first to treasury, legal, operations or those charged with governance. Reliance on one management enquiry or a single post-year-end ledger scan can leave a completeness gap.
Distinguishing accounting adjustment from disclosure
The central judgment is whether the event gives further evidence of a condition that existed at the reporting date or indicates a condition arising afterwards. Weak files record the event but do not explain the linkage to reporting-date conditions, the quantitative and qualitative materiality assessment, or why the proposed financial-reporting treatment is appropriate.
Going concern, estimates and liquidity signals
Post-year-end developments may corroborate or challenge assumptions used in going-concern assessments, impairment analyses, expected credit loss estimates, provisions, fair values or forecasts. A favourable event after year end does not automatically resolve an earlier uncertainty, and an adverse event may require the team to revisit the evidence and disclosures supporting management’s assessment.
Late events, reporting implications and reviewability
Events discovered close to, or after, the auditor’s report date create heightened risks of unclear ownership, insufficient consultation and unsupported reporting decisions. The file should show when the matter became known, who evaluated it, the communications and actions taken, and how the final financial statements and auditor’s reporting considerations were resolved under the applicable standards.
Tailored Audit Procedures
Set the scope and refresh the risk assessment
Document the reporting date, the anticipated auditor’s report date, the financial-statement approval timetable and the post-year-end sources to be covered. Reassess the nature and extent of procedures for risks such as liquidity pressure, significant estimates, related-party activity, legal claims, covenant compliance and unusual transactions.
Make focused enquiries of management and those charged with governance
Ask about events, commitments, disputes, financing, breaches, restructurings, fraud or suspected fraud, significant customer or supplier developments, changes in forecasts and matters considered in preparing or approving the financial statements. Corroborate significant responses rather than treating enquiry alone as sufficient evidence.
Inspect governance records and current management information
Read relevant board, audit committee and shareholder meeting minutes available after the reporting date, and inspect post-year-end management accounts, cash-flow information, budgets and other reports used by management. Follow up decisions, variances and exceptional items that may indicate an event requiring evaluation.
Test selected post-year-end transactions and cash activity
Review selected subsequent receipts, payments, credit notes, sales returns, financing activity and journal entries with a focus on balances, estimates and cut-off risks identified in the audit. Link unusual or material items back to conditions at the reporting date and investigate whether they indicate an unrecorded liability, impaired asset, misstatement or disclosure matter.
Obtain external and contractual corroboration where relevant
For significant matters, inspect reliable underlying evidence such as executed financing agreements, lender correspondence, court documents, legal correspondence, settlement agreements, customer communications or valuation information. Evaluate the evidence in the context of the relevant assertion and management’s proposed accounting or disclosure.
Evaluate treatment, conclude and update through reporting
Assess each identified matter individually and in aggregate, including its effect on adjustments, disclosures, going concern and the audit conclusion. Agree final changes to the financial statements, perform any necessary additional procedures up to the auditor’s report date, obtain appropriate written representations as corroborative evidence, and document the rationale for the final conclusion.
Controls and Evidence to Consider
Post-year-end event register with accountable owners
Management can maintain a dated register of significant post-year-end developments, the responsible function, status, proposed accounting or disclosure treatment and escalation decisions. The auditor can use it as a starting point, reconcile it to other sources and retain evidence of follow-up on material items.
Disciplined close and review controls
Timely reconciliations, review of subsequent cash movements, cut-off monitoring, review of significant estimates and documented investigation of unusual journals provide evidence about conditions near the reporting date. Evidence should identify the preparer, reviewer, date and resolution of exceptions.
Governance reporting and escalation trail
Board or audit-committee packs, minutes, management representations, legal updates and communications on significant events can demonstrate that relevant developments were reported and considered. A clear escalation trail is especially important for liquidity, litigation, fraud, covenant and going-concern matters.
Reliable, contemporaneous support for the audit conclusion
The audit file should assemble the subsequent-events plan, enquiries, minutes reviewed, transaction testing, external documents, assessment of accounting and disclosure, materiality analysis, consultations and final sign-off. Cross-references to the completed financial statements should enable an experienced reviewer to understand what was identified, how it was evaluated and why the conclusion was reached.
Related Reading
Apply Technical Insight to Your Audit Workflow
EQC can discuss audit-quality priorities, documentation, inspection readiness, and Audit Program 4.1 (AP4.1) workflow support relevant to your practice.