Historical Context & Motivation
Financial statements are prepared as of a specific date, yet the world does not pause while auditors and management finalize their reports. The period between the balance sheet date and the date on which financial statements are issued (or are available to be issued) can span weeks or even months—a window during which economically significant events may occur. The accounting profession has long recognized that ignoring these events would undermine the reliability and relevance of reported figures, potentially misleading investors, creditors, and regulators who depend on those statements for capital-allocation decisions.
The formal treatment of subsequent events evolved alongside the broader development of generally accepted accounting principles in the United States. Early pronouncements by the American Institute of Certified Public Accountants (AICPA) established the conceptual foundation, but it was not until the Financial Accounting Standards Board (FASB) issued dedicated guidance that a codified, two-category framework became authoritative for all U.S. GAAP reporters. Understanding this history clarifies why the distinction between the two types of subsequent events matters so much on the CPA exam and in professional practice.
The central question ASC 855 resolves is deceptively simple: when something happens after the balance sheet date but before financial statements are issued, should the entity adjust the numbers already on the financial statements, or should it merely disclose the event in the notes? Answering this question correctly is essential for the FAR section of the CPA exam and is a recurring area of professional judgment in practice.
Core Principles & Definitions
ASC 855 defines subsequent events as events or transactions that occur after the balance sheet date but before financial statements are issued or are available to be issued. The standard classifies these events into exactly two categories, each carrying distinct accounting consequences. The entire framework rests on a single diagnostic question: did the condition giving rise to the event already exist at the balance sheet date?
Recognized Subsequent Events (Type I)
Non-Recognized Subsequent Events (Type II)
Evaluation Period
The 'Condition Existed' Test
Visual Explanation — The Subsequent Events Decision Framework
As the diagram illustrates, the classification hinges entirely on the temporal origin of the underlying condition, not the timing of the event itself. Both Type I and Type II events occur within the same calendar window—between the balance sheet date and the issuance date—yet they receive fundamentally different accounting treatments. This distinction reflects the accrual-basis principle that financial statements should faithfully represent the economic conditions that existed as of the reporting date, while simultaneously ensuring users are informed of material developments that alter the entity's risk profile going forward.
How It Works — Identification and Evaluation Process
Step 1 — Determine the Evaluation Period
The evaluation period begins on the balance sheet date and ends on the date the financial statements are issued (for SEC filers) or available to be issued (for all other entities). 'Issued' means the financial statements are widely distributed to shareholders and other financial statement users in a form and format that complies with GAAP. 'Available to be issued' means the financial statements are complete in a form and format that complies with GAAP and have obtained the necessary approvals from management. This distinction matters because a non-SEC entity's evaluation window may close earlier than the actual distribution date, which affects the scope of events it must evaluate.
Step 2 — Identify Events Within the Window
Management must implement procedures designed to surface material events that occur during the evaluation period. In practice, this involves reviewing post-period bank reconciliations, reviewing minutes of board meetings held after the balance sheet date, examining legal correspondence for litigation developments, and confirming the status of significant receivables and inventory. The auditor's procedures complement management's evaluation, but primary responsibility rests with management.
Step 3 — Apply the Classification Test
For each identified event, management asks the critical question: Did the condition giving rise to this event exist at the balance sheet date? If the answer is yes, the event is Type I (recognized) and the financial statements must be adjusted to reflect the new information. If the answer is no, the event is Type II (non-recognized), and the entity discloses the nature of the event and an estimate of its financial effect (or states that an estimate cannot be made) in the notes to the financial statements, provided the event is material.
Step 4 — Determine the Accounting Response
| Attribute | Type I — Recognized | Type II — Non-Recognized |
|---|---|---|
| Condition origin | Existed at the balance sheet date | Arose after the balance sheet date |
| F/S adjustment | Yes — adjust amounts in the statements | No — do not adjust reported amounts |
| Note disclosure | Update existing disclosures as needed | Disclose the nature and financial effect (if material) |
| Typical examples | Litigation settlement, bankruptcy of a customer with a year-end receivable, realization of a loss on inventory | Natural disaster, issuance of debt or equity, business combination, loss from fire |
Detailed Classification — Common Scenarios
One of the most challenging aspects of subsequent events on the CPA exam is correctly classifying specific fact patterns. The scenarios below represent the most commonly tested situations. For each, the key is tracing the underlying condition back to or after the balance sheet date.
Worked Example — Classifying and Accounting for Subsequent Events
Meridian Corp. has a December 31, 20X4 fiscal year-end. Its financial statements are issued on March 5, 20X5. During the subsequent events evaluation period, the following events occur. We will classify each and determine the appropriate accounting treatment.
U.S. GAAP vs. IFRS — Subsequent Events Treatment
While the CPA exam primarily tests U.S. GAAP under ASC 855, FAR candidates should understand that IFRS addresses subsequent events under IAS 10, Events After the Reporting Period. The two frameworks are conceptually aligned—both use a two-category model based on whether the condition existed at the reporting date—but they differ in terminology and in certain specific requirements.
| Attribute | U.S. GAAP (ASC 855) | IFRS (IAS 10) |
|---|---|---|
| Terminology | Recognized (Type I) / Non-recognized (Type II) | Adjusting events / Non-adjusting events |
| Evaluation end date | Date F/S are issued (SEC) or available to be issued (non-SEC) | Date F/S are authorized for issue |
| Dividends declared post-period | Disclosed in notes (Type II) | Explicitly non-adjusting; disclosed but NOT recognized as a liability |
| Date disclosure requirement | SEC filers: not required; Non-SEC: disclose date | Must disclose the date F/S were authorized for issue |
| Going concern | Evaluated under ASC 205-40 separately | IAS 10 specifically states: do not prepare F/S on going concern basis if events indicate entity is not a going concern |
Connections to Related Standards and Advanced Topics
Subsequent events do not exist in isolation within the codification. Several other ASC topics intersect with ASC 855, and understanding these connections is critical for applying judgment on the CPA exam and in practice. The most significant intersections involve loss contingencies (ASC 450), going concern (ASC 205-40), and fair value measurement (ASC 820).
| Related Topic | Interaction with Subsequent Events |
|---|---|
| ASC 450 — Contingencies | A contingency that was 'reasonably possible' at year-end may become 'probable' due to a subsequent event. If the underlying condition existed at B/S date, this is Type I and requires adjustment (recognize the loss). If the contingency arises from a new post-period event, it is Type II (disclosure only). |
| ASC 205-40 — Going Concern | Management evaluates going concern for a one-year look-forward period from the F/S issuance date. If subsequent events (e.g., loss of a major customer, loan default) raise substantial doubt, management must disclose plans and may need to modify the going concern assessment, even though the events arose post-period. |
| ASC 820 — Fair Value | Post-period market declines may provide evidence that a year-end fair value estimate was overstated (Type I if the decline reflects conditions existing at period-end) or may represent new market conditions (Type II). Professional judgment is required to determine whether the decline is indicative of a pre-existing impairment. |
| ASC 855-10-25 — Stock Splits | A stock split or stock dividend after B/S date but before issuance requires retroactive adjustment of all per-share data (EPS, dividends per share). This is a unique rule within ASC 855 because it requires a financial statement adjustment for what would otherwise be a Type II event. |
Looking forward, the evolving complexity of financial instruments, the acceleration of real-time reporting expectations, and the increasing globalization of capital markets will continue to challenge the subsequent events framework. As integrated reporting and more frequent interim disclosures become standard practice, the evaluation period may narrow, but the fundamental classification principle—tracing the origin of the condition—will remain the bedrock of this area of financial reporting.
Practice Problems
Summary — Subsequent Events Under ASC 855
Under ASC 855, subsequent events are events or transactions occurring after the balance sheet date but before financial statements are issued or available to be issued. They are classified into two categories based on one critical question: did the condition exist at the balance sheet date? Type I (recognized) events provide additional evidence about conditions existing at that date and require adjustment of the financial statements. Type II (non-recognized) events arise from new conditions and require note disclosure only (if material).
Key exceptions include stock splits and stock dividends after the balance sheet date, which require retroactive adjustment of per-share amounts even though they represent new events. Going concern evaluations follow ASC 205-40 but may be triggered by subsequent events. The IFRS equivalent (IAS 10) uses similar logic under the labels 'adjusting' and 'non-adjusting' events. Non-SEC filers must disclose the date through which subsequent events were evaluated, while SEC filers are exempt from this requirement under ASU 2010-09. Mastering these distinctions is essential for success on the FAR section of the CPA exam.