Glossary · Audit & Assurance
Subsequent Events in Audit
Definition
Subsequent events are events that happen after the balance sheet date, up to the date of the auditor's report and sometimes after it, that may require the financial statements to be adjusted or a disclosure to be added. The auditor has to look for them, because accounts signed in July still need to reflect what was known about the position at 31 March.
At a glance
- Category
- Audit & Assurance
- Main provision
- SA 560
- In this entry
- How it works in an audit Where the law or the standard sets it · A simple example
In detail
01 How it works in an audit
Accounting standards split subsequent events into two kinds:
- Adjusting events give more evidence about conditions that already existed at the balance sheet date. The figures change. Example: a customer who owed money at 31 March goes bankrupt in May.
- Non-adjusting events relate to conditions that arose after the balance sheet date. The figures stay, but a material event is disclosed. Example: a fire destroys a warehouse in June.
The auditor's work runs through three windows:
- Up to the date of the report
the auditor actively looks for events, by reading board minutes, later management accounts and legal letters, reviewing receipts and payments after year end, and asking management directly.
- After the report but before the accounts are issued
the auditor no longer searches, but must act if a fact comes to its attention.
- After the accounts are issued
the same, if a fact comes to light that would have changed the report.
Management confirms in the representation letter that all such events have been dealt with.
The provision
02 Where the law or the standard sets it
The auditor's duties are set out in SA 560, Subsequent Events, issued by ICAI. The accounting treatment comes from the accounting standard on events after the reporting period that the company follows. SA 560 requires the auditor to perform procedures covering the period from the date of the financial statements to the date of the auditor's report, such as inquiries of management, reading minutes and reading the latest interim financial statements, and to obtain a written representation from management that all such events have been adjusted or disclosed. After the report date the auditor has no duty to perform further procedures, but if a fact that might have changed the report comes to light before the financial statements are issued, the auditor discusses it with management and decides whether the statements need amending.
Worked example
03 A simple example
An example, not advice on your facts.
A company's year ends on 31 March and the audit report is dated 15 July. On 20 June, a court decides a long-running case against the company and awards damages of ₹1.2 crore. The case existed at 31 March, so the decision is evidence of a condition that already existed: the company records a provision in the March accounts. Had the case started only in June, it would be disclosed but not provided for.
In detail
04 Why it matters to a company
Between year end and the audit report, management should keep a list of significant events: big customer losses, legal outcomes, fires, acquisitions, large borrowings. Telling the auditor early avoids late adjustments and last-minute changes to the report.
Need help with subsequent events in an audit? See our Standards on Auditing (SAs) guide.
Review and sources
Sources: ICAI Checklist on Standards on Auditing (22 Jun 2023): SA 560 title.
