The period between a reporting date and the completion or issuance of financial statements can bring important new information to light. A major customer may enter bankruptcy, a lawsuit may settle, a warehouse may be damaged by fire, or a refinancing may be completed. The controller must decide whether the event provides evidence about a condition that already existed at period-end, reflects a genuinely new condition, or requires a separate going-concern assessment.
These decisions affect estimates, disclosures, audit evidence and sometimes the basis on which financial statements are prepared. The terminology and assessment cut-off differ among US GAAP, IFRS and Canadian Accounting Standards for Private Enterprises (ASPE). A disciplined process helps avoid both late adjustments that are missed and post-period transactions that are incorrectly recorded in the prior year.
1. Establish the subsequent-events window
Start by documenting the reporting date and the date through which management must evaluate subsequent events. The end point is not necessarily the date the controller finishes the close workbook or sends a draft to the auditors.
- US GAAP: ASC 855 covers events after the balance-sheet date and before the financial statements are issued or are available to be issued. The applicable evaluation date depends on the entity and its reporting circumstances. SEC filers evaluate through the date the statements are issued; other entities generally evaluate through the date the statements are available to be issued. Non-SEC entities have related disclosure requirements concerning the evaluation date and whether the statements were issued or available to be issued.
- IFRS: IAS 10 covers events between the end of the reporting period and the date the financial statements are authorised for issue. The entity discloses the authorisation date and who gave the authorisation.
- Canadian ASPE: Section 3820 covers events after the financial statement date and before the financial statements are complete. Completion includes preparing the full statements and required disclosures, recording final adjusting entries, having no changes planned or expected, and obtaining approval under the entity’s process.
Record the relevant dates in the close calendar and technical accounting memo. For a Canadian private enterprise, do not assume the ASPE completion date is automatically the same as a board authorization date under IAS 10. For a US registrant, do not substitute an IFRS-style authorization date for the ASC 855 issuance analysis.
2. Separate evidence about an existing condition from a new event
The central accounting question is whether the later information provides additional evidence about a condition that existed at the reporting date, or instead indicates a condition that arose after that date.
An adjusting (recognized) event provides further evidence about a condition existing at period-end. The financial statements are adjusted to reflect that evidence. A non-adjusting (nonrecognized) event relates to a condition that arose after period-end. The prior-period amounts are not adjusted for that new condition, although disclosure may be required if the event is material under the applicable framework.
The date the information becomes known is not, by itself, decisive. A court settlement signed in February might provide evidence about a claim arising from events before December 31. Conversely, a new factory fire in February is generally a new condition, even if the resulting financial impact is substantial.
3. Apply the framework to practical controller scenarios
| Event discovered after year-end | Typical analysis | Controller action |
|---|---|---|
| Customer files for bankruptcy after year-end | May confirm severe financial difficulty that existed at the reporting date. | Reassess the year-end receivable and credit-loss allowance using evidence about the customer’s condition at year-end. |
| Lawsuit relating to pre-year-end conduct settles before statements are finalized | Settlement may provide additional evidence about the obligation existing at period-end. | Reassess the year-end loss contingency or provision under the relevant accounting guidance. |
| Major plant is destroyed by a new fire after year-end | Usually a new condition arising after the reporting date. | Do not write down the prior-year asset solely for the later fire; assess material subsequent-event disclosure and insurance implications. |
| New acquisition agreement signed after year-end | Usually a new transaction after the reporting date. | Do not recognize the acquisition in the prior period merely because it is significant; assess required disclosure. |
| Inventory sells below cost shortly after year-end | Could provide evidence of year-end condition, or reflect a later market change, depending on facts. | Examine age, damage, obsolescence, customer orders and market conditions at the reporting date. |
| New financing is arranged after year-end | Generally a new financing event, but may affect liquidity and going-concern analysis. | Assess disclosure and whether the financing changes the going-concern conclusion; do not automatically treat it as year-end cash or debt. |
These are starting points, not automatic conclusions. The underlying facts, other applicable accounting guidance and the reporting framework determine the final treatment.
4. Build an evidence-based assessment—not just an event log
A useful subsequent-events register records the date identified, description, affected entity and accounts, estimated financial exposure, source of information, condition date, framework analysis, adjustment or disclosure conclusion, reviewer and resolution date.
For each material item, ask:
- What condition or transaction caused the event?
- Did that condition exist at the reporting date?
- What new evidence became available, and what does it demonstrate about the reporting-date estimate?
- Does specific guidance elsewhere in the relevant accounting framework apply?
- Is an adjustment required, or is disclosure required because the event is non-adjusting?
- Does the event affect liquidity, debt compliance, insurance recovery, commitments or the going-concern assessment?
Retain contemporaneous support: customer correspondence, insolvency filings, legal letters, settlement agreements, insurance reports, board minutes, financing documents, subsequent sales reports and relevant operational data. A short memo should explain why the event relates—or does not relate—to a condition at the reporting date.
5. Revisit estimates and disclosures, not only journal entries
Subsequent information may require an adjustment to a recorded amount, but it can also change disclosures without changing recognized balances. Under IAS 10, for example, an entity updates disclosures about conditions existing at the reporting date in light of information received after the period. For material non-adjusting events, IAS 10 requires disclosure of the nature of the event and an estimate of its financial effect, or a statement that such an estimate cannot be made.
Under US GAAP, ASC 855 similarly requires disclosure of certain nonrecognized subsequent events when omission would make the statements misleading, including the nature of the event and an estimate of its financial effect or a statement that an estimate cannot be made. For Canadian ASPE, Section 3820 requires disclosure for specified non-adjusting events that cause significant changes to assets or liabilities in the subsequent period or may significantly affect future operations; disclosure includes the nature and, when practicable, estimated financial effect.
Do not treat the disclosure thresholds as identical. Apply the wording and materiality requirements of the framework used for the financial statements.
6. Give going concern a separate, explicit review
A subsequent event can be so significant that it challenges the appropriateness of preparing financial statements on a going-concern basis. Examples may include the loss of a critical funding source, a major customer failure, severe post-period operating deterioration or the withdrawal of essential financing.
Under IAS 10, if events after the reporting period indicate that the going-concern assumption is no longer appropriate, the financial statements are not prepared on a going-concern basis. Under US GAAP, going-concern assessment and disclosure are addressed by ASC 205-40, including conditions and events that raise substantial doubt and management’s plans. Canadian ASPE has its own going-concern requirements in Section 1400. A controller should therefore route severe liquidity and viability developments to management and the technical accounting lead immediately, rather than leave them in the routine disclosure checklist.
7. Coordinate the close, auditors and governance approvals
Assign owners across Finance, Treasury, Legal, Tax, Operations and Investor Relations. Require each function to report material developments through the defined evaluation cut-off. The controller should coordinate the register, challenge completeness and ensure the accounting conclusion is reflected consistently in the trial balance, consolidation, disclosures and audit support.
For multi-entity groups, document the reporting framework and completion or issuance timeline for each reporting package. A Canadian ASPE subsidiary reporting to a US GAAP parent may need a local statutory conclusion and a separate group reporting adjustment. Do not assume one memo automatically supports both sets of statements.
Controller’s subsequent-events close checklist
- Confirm the reporting date and applicable evaluation end date for each reporting framework.
- Obtain written confirmations from Legal, Treasury, HR, Operations and business leaders.
- Review post-period cash receipts, customer credit developments and inventory sales or disposals.
- Inspect new litigation developments, settlements, claims and regulatory correspondence.
- Review acquisitions, disposals, financing, covenant developments and major commitments.
- Assess each event as evidence of an existing condition or a new post-period condition.
- Record required adjustments and disclosures; document why other events need neither.
- Reassess going concern and liquidity where facts warrant.
- Obtain technical accounting and auditor review for significant or judgmental matters.
- Update the register through the required cut-off and retain final approval evidence.
Conclusion
A strong subsequent-events process is a controlled extension of the financial close. It ensures that later information is used appropriately to refine period-end estimates, that genuinely new events are not backdated into the prior period, and that material developments are communicated transparently. The most defensible conclusion is one that ties the event to its underlying condition, applies the correct reporting framework and is supported by dated evidence and independent review.
Authoritative and technical references
- FASB: Accounting Standards Update 2010-09, Subsequent Events (Topic 855).
- IFRS Foundation: IAS 10—Events after the Reporting Period.
- BDO Canada: ASPE Section 3820—Subsequent Events.
- CPA Canada: September 2023 CFE report, Appendix C—application of ASPE 3820.
- CPA Ontario: Subsequent-event considerations for private enterprises.
Disclaimer: This article is for general informational and educational purposes only. It is not accounting, audit, legal, tax or investment advice. Consult the current authoritative standards and qualified professional advisers when applying requirements to specific facts.
