Year-end audit work does not stop on the balance-sheet date. Events occurring after that date can confirm conditions that already existed, reveal conditions that arose later, or even require the auditor to reconsider a report that has already been signed. For Indian statutory audits, the core audit guidance is ICAI's SA 560, Subsequent Events, supported by ICAI's Implementation Guide to SA 560.
What is a subsequent event in an audit?
SA 560 defines subsequent events broadly as events occurring between the date of the financial statements and the date of the auditor's report, together with facts that become known to the auditor after the date of the auditor's report. The standard therefore covers more than the familiar period between year-end and audit signing.
The accounting question and the audit question should be separated. The applicable financial-reporting framework determines whether an event requires adjustment or disclosure. SA 560 determines what the auditor must do to obtain evidence that the required accounting or disclosure treatment has been reflected appropriately and how the auditor responds to important facts discovered later.
Adjusting versus non-adjusting events: the practical distinction
SA 560 notes that financial-reporting frameworks ordinarily distinguish between two broad types of post-balance-sheet events: those providing evidence about conditions that existed at the financial-statement date, and those providing evidence about conditions arising after that date. In practice, this distinction drives the adjustment-versus-disclosure analysis under the applicable accounting framework.
Example: suppose a customer owed a material receivable at 31 March and enters insolvency shortly after year-end. If the later development provides evidence about financial difficulty that already existed at 31 March, management should assess whether the year-end receivable measurement needs adjustment under the applicable accounting framework. By contrast, if a warehouse is destroyed by an unrelated fire after year-end, the event may represent a condition arising later; the accounting framework may call for disclosure rather than changing the year-end asset measurement, depending on materiality and the applicable requirements.
What must the auditor do before signing the report?
SA 560 requires procedures designed to identify events between the financial-statement date and the auditor's-report date that require adjustment or disclosure. The procedures should extend to the auditor's-report date, or as near to it as practicable, and their nature and extent should reflect the auditor's risk assessment.
The standard specifically includes understanding management's process for identifying subsequent events, asking management and where appropriate those charged with governance about relevant events, reading minutes of post-year-end meetings and asking about matters where minutes are not yet available, and reading the latest subsequent interim financial statements if available.
Depending on risk, useful additional work can include reviewing later accounting records and bank statements, reading budgets and cash-flow forecasts, following up litigation with legal counsel, examining subsequent receipts from customers, and considering later developments affecting estimates, provisions, asset recoverability or going concern.
A practical subsequent-events audit checklist
- Set the review window: identify the financial-statement date, approval date and planned auditor's-report date.
- Understand management's process: determine who identifies post-year-end events and how they are escalated.
- Read later minutes: inspect board, audit committee and relevant management minutes and inquire about meetings not yet minuted.
- Review later financial information: inspect interim accounts, major journal entries, cash-flow information and material post-year-end transactions where relevant.
- Follow open matters: revisit litigation, guarantees, borrowings, contingencies, estimates, provisions and doubtful receivables.
- Ask targeted questions: consider new commitments, borrowings, guarantees, asset acquisitions or disposals, capital or debt issues, major losses, unusual adjustments and developments affecting going concern.
- Evaluate treatment: determine whether identified events have been adjusted or disclosed as required by the applicable financial-reporting framework.
- Obtain representations: SA 560 requires written representation that events requiring adjustment or disclosure have been adjusted or disclosed.
What if a fact emerges after the auditor's report is signed?
The auditor does not have a continuing obligation to perform audit procedures after the auditor's-report date. But that does not mean a significant later-discovered fact can be ignored. If, before the financial statements are issued, the auditor learns a fact that might have caused the report to be amended had it been known earlier, SA 560 requires the auditor to discuss it with management and, where appropriate, those charged with governance, determine whether the financial statements need amendment, and ask how management intends to address it.
If management amends the financial statements, the auditor performs necessary procedures on the amendment and, subject to the circumstances addressed by the standard, extends subsequent-event procedures to the date of the new auditor's report and issues a new report. SA 560 also permits restricted procedures and an additional date in specified circumstances where the framework allows an amendment to be restricted to the particular subsequent event.
What if the financial statements have already been issued?
Again, there is no general obligation to keep auditing indefinitely. However, if a fact becomes known after issuance that might have changed the auditor's report had it been known on the report date, the auditor must discuss the matter, determine whether amendment is needed, and inquire how management will respond. Where management amends the statements, SA 560 requires procedures on the amendment and review of management's steps to inform recipients of the previously issued financial statements.
If management refuses necessary action, the standard requires the auditor to take appropriate steps to seek to prevent future reliance on the auditor's report, subject to the auditor's legal rights and obligations.
Common mistakes in subsequent-events work
- Treating subsequent-events review as a last-day management-representation exercise instead of performing substantive procedures.
- Checking only events before board approval while overlooking the auditor's-report date as the key end point for required pre-signing procedures.
- Assuming every post-year-end event changes year-end numbers instead of distinguishing evidence of an existing condition from a genuinely new condition.
- Failing to connect later cash receipts, legal developments or customer distress back to year-end estimates and asset recoverability.
- Assuming the auditor has no responsibility at all once the report is signed; SA 560 contains specific responses for significant facts discovered before or after issuance.
Practical takeaway
A strong subsequent-events review is a structured bridge between the balance-sheet date and the auditor's report. Build a dated checklist, obtain evidence from minutes and later financial information, revisit estimates and contingencies, and document why each material event requires adjustment, disclosure or neither. For authoritative requirements and practical illustrations, use ICAI's SA 560 together with its Implementation Guide.
