Identify And Classify Subsequent Events - CPA Far

SECTION 1

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.

1963 • SAS No. 1 (AU Section 560)

The AICPA's auditing standards first codified guidance on subsequent events, establishing a conceptual split between events that provide additional evidence about conditions existing at the balance sheet date and events that provide evidence about conditions arising after that date.

2003 • FASB Statement No. 150 Era

As high-profile corporate failures (Enron, WorldCom) exposed financial reporting weaknesses, pressure mounted for the FASB to issue explicit accounting (not just auditing) guidance on subsequent events, including clearer disclosure requirements.

2009 • SFAS 165 / ASC 855 Issued

The FASB issued Statement No. 165, Subsequent Events, later codified as ASC 855, providing the first authoritative accounting standard (as distinct from auditing standard) on the topic under U.S. GAAP. The standard defined two types—recognized and non-recognized—and required disclosure of the date through which subsequent events had been evaluated.

2010 • ASU 2010-09 Amendment

The FASB issued ASU 2010-09 to remove the requirement for SEC filers to disclose the date through which subsequent events had been evaluated, responding to concerns about potential confusion with SEC filing dates. Non-SEC filers retained this disclosure obligation.

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.

SECTION 2

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)

Events that provide additional evidence about conditions that existed at the balance sheet date. These events require adjustment of the financial statements. Example: settlement of litigation for a claim that was pending at year-end.

Non-Recognized Subsequent Events (Type II)

Events that provide evidence about conditions that did not exist at the balance sheet date but arose subsequently. These events are disclosed in the notes but do not require adjustment. Example: a major casualty loss from a fire occurring in January when the balance sheet date is December 31.

Evaluation Period

The window during which management must assess subsequent events extends from the balance sheet date through the date the financial statements are issued (for SEC filers) or are available to be issued (for non-SEC filers).

The 'Condition Existed' Test

The critical classification criterion is whether the underlying condition or cause of the event was already present as of the balance sheet date. If yes → Type I (recognize). If no → Type II (disclose only, if material).

✦

KEY TAKEAWAY

Think of the balance sheet date as a photograph of a scene. A Type I event is like developing the photograph and realizing a detail you could not see clearly is now in sharper focus—the subject was already in the frame. A Type II event is like something new entering the scene after the shutter clicked—it was never in the original frame. You adjust the photograph for the first case (re-develop for clarity), but you simply attach a note for the second (informing the viewer of what happened afterward).

SECTION 3

Visual Explanation — The Subsequent Events Decision Framework

The flowchart above illustrates the decision framework under ASC 855. Start with the occurrence of an event after the balance sheet date, verify it falls within the evaluation period, and then apply the central diagnostic: did the underlying condition exist at the balance sheet date? A 'yes' answer leads to Type I recognition (adjustment); a 'no' answer leads to Type II treatment (note disclosure if material).

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.

SECTION 4

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

Comparison of Type I and Type II Subsequent Events Under ASC 855

SECTION 5

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.

This timeline and classification map situates common subsequent events within the evaluation period and assigns each to Type I or Type II. Note the special cases at the bottom: going concern evaluations follow their own codification guidance (ASC 205-40), and stock dividends/splits after the balance sheet date trigger retroactive adjustment of per-share amounts under ASC 855-10-25, even though they are technically new events.

⚠

CPA Exam Tip

The CPA exam frequently tests the stock dividend/split exception. A stock split occurring after year-end but before financial statement issuance requires retroactive adjustment of all per-share amounts (EPS, dividends per share) presented in the financial statements, even though the split is a new event. This is codified in ASC 855-10-25 and is one of the most commonly missed points on FAR.

SECTION 6

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.

Scenario A — Settlement of Pending Litigation

1
Step 1 — Identify the Event

On February 10, 20X5, Meridian settles a product liability lawsuit for $2.4 million. The lawsuit was filed against Meridian in August 20X4, and at December 31, 20X4, Meridian had accrued a loss contingency of $1.8 million under ASC 450 because the loss was deemed probable and reasonably estimable.
2
Step 2 — Apply the Condition-Existed Test

The lawsuit was pending at the balance sheet date; the condition (the legal obligation) clearly existed as of December 31, 20X4. The February settlement provides additional evidence about the amount of that pre-existing condition.

Classification: Type I — Recognized Subsequent Event
3
Step 3 — Determine the Accounting Response

Meridian must adjust its December 31, 20X4 financial statements. The loss contingency accrual should be increased from $1.8 million to $2.4 million, and the corresponding litigation expense on the income statement should be increased by $600,000. The related disclosure note for litigation should be updated to reflect the settlement.

Adjusting entry: Dr. Litigation Expense $600,000 / Cr. Litigation Liability $600,000

Scenario B — Fire Destroys a Production Facility

1
Step 1 — Identify the Event

On January 18, 20X5, a fire destroys Meridian's eastern production facility. The uninsured loss is estimated at $8 million. The facility was fully operational and undamaged at December 31, 20X4.
2
Step 2 — Apply the Condition-Existed Test

The fire is a new event; the condition (the fire and resulting destruction) did not exist at the balance sheet date. The facility was intact on December 31, 20X4.

Classification: Type II — Non-Recognized Subsequent Event
3
Step 3 — Determine the Accounting Response

Meridian does not adjust its December 31, 20X4 balance sheet or income statement. However, because the loss is material, Meridian must disclose the nature of the event (fire at the eastern facility), the estimated financial effect ($8 million uninsured loss), and any expected insurance recovery in the notes to the financial statements.

No adjusting entry — note disclosure only

SECTION 7

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

Key Differences Between ASC 855 and IAS 10

✦

KEY TAKEAWAY

The conceptual framework is nearly identical under both GAAP and IFRS—think of them as two editions of the same textbook written in slightly different dialects. The most testable difference is the dividends declared after the reporting period: under IAS 10, dividends declared after the reporting date are explicitly prohibited from being recognized as a liability at period-end, while U.S. GAAP treats this as a standard Type II disclosure. Also note the IFRS requirement to disclose the authorization date in all cases.

SECTION 8

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.

Intersections Between ASC 855 and Related Codification Topics

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.

SECTION 9

Practice Problems

Question 1: CONCEPTUAL

Explain the fundamental distinction between a Type I (recognized) subsequent event and a Type II (non-recognized) subsequent event under ASC 855. What single criterion drives the classification?

Show answer

The fundamental distinction rests on whether the underlying condition or cause of the event existed at the balance sheet date. A Type I (recognized) subsequent event provides additional evidence about a condition that was already present at the balance sheet date, and the financial statements must be adjusted to incorporate this new evidence. A Type II (non-recognized) subsequent event arises from a condition that did not exist at the balance sheet date; it represents a genuinely new development. Type II events are not reflected in the reported financial statement amounts but, if material, must be disclosed in the notes. The single driving criterion is temporal origin: did the condition exist at the balance sheet date, or did it arise afterward?

Question 2: BASIC CALCULATION

Apex Inc. has a December 31, 20X4 year-end. At year-end, Apex had accrued a litigation liability of $500,000 for a pending lawsuit. On February 3, 20X5 (before financial statements are issued on March 10, 20X5), the lawsuit is settled for $750,000. What adjustment, if any, should Apex record in its December 31, 20X4 financial statements?

Show answer

This is a Type I (recognized) subsequent event because the litigation was pending at the balance sheet date—the underlying condition (the legal obligation) existed as of December 31, 20X4. The February settlement provides additional evidence about the amount of that pre-existing liability. Apex should increase its litigation liability from $500,000 to $750,000, recording an additional $250,000 in litigation expense. The adjusting journal entry is: Dr. Litigation Expense $250,000 / Cr. Litigation Liability $250,000. The settlement amount should be reflected in the December 31, 20X4 financial statements, and the litigation disclosure note should be updated accordingly.

Question 3: INTERMEDIATE

Delta Corp. (a non-SEC filer) has a December 31, 20X4 year-end. On January 25, 20X5, a major customer representing 30% of Delta's accounts receivable files for bankruptcy. On February 15, 20X5, an earthquake damages Delta's headquarters, resulting in $5 million of uninsured losses. Delta's financial statements are available to be issued on March 20, 20X5. Classify each event and describe the required accounting treatment, including any disclosure obligations specific to non-SEC filers.

Show answer

Event 1 (customer bankruptcy): This is a Type I event. The accounts receivable existed at December 31, 20X4, and the customer's financial deterioration leading to bankruptcy was a condition developing at or before year-end. The January bankruptcy provides additional evidence confirming that the receivable was impaired at the balance sheet date. Delta should adjust its allowance for doubtful accounts to reflect the probable uncollectible amount on the customer's balance. Event 2 (earthquake): This is a Type II event. The earthquake is a new condition that arose after the balance sheet date. Delta should not adjust its financial statement amounts but must disclose the nature of the event and the estimated $5 million financial effect in the notes. As a non-SEC filer, Delta must also disclose the date through which subsequent events have been evaluated (March 20, 20X5) and indicate that this is the date the financial statements were available to be issued, per ASU 2010-09.

Question 4: APPLIED

Orion Corp. (an SEC registrant) has a December 31, 20X4 year-end and issues its financial statements on February 28, 20X5. On January 10, 20X5, Orion's board declares a 2-for-1 stock split effective January 20, 20X5. Separately, on February 1, 20X5, Orion completes the acquisition of a competitor for $40 million. Describe the accounting treatment for each event in Orion's December 31, 20X4 financial statements. How, if at all, should per-share data be affected?

Show answer

Event 1 (stock split): Although a stock split occurring after the balance sheet date is technically a new event (Type II), ASC 855-10-25 requires that all per-share data presented in the December 31, 20X4 financial statements be retroactively adjusted to reflect the 2-for-1 split. This means earnings per share, dividends per share, and any other per-share disclosures must be computed using the post-split share count. This is a specific exception to the general Type II non-adjustment rule. Event 2 (business combination): The acquisition is a Type II event—it represents a new condition that arose after the balance sheet date. Orion does not adjust its December 31, 20X4 balance sheet or income statement amounts. However, because a $40 million acquisition is almost certainly material, Orion must disclose the nature of the acquisition and its estimated financial effect in the notes. As an SEC filer, Orion is not required under ASC 855 to disclose the date through which subsequent events were evaluated, although SEC regulations may impose separate disclosure requirements.

Question 5: CRITICAL THINKING

Vega Corp. holds a portfolio of mortgage-backed securities measured at fair value at December 31, 20X4. Between January 1 and February 20, 20X5 (the date the financial statements are issued), the market experiences a significant downturn, and the fair value of the portfolio declines by 25%. Vega's management argues this is a Type II event because the market decline occurred in 20X5 and therefore no adjustment is required. The auditor is not convinced. Evaluate both perspectives and recommend the appropriate treatment, explaining how professional judgment should be applied under ASC 855 in conjunction with ASC 820 (Fair Value Measurement).

Show answer

This scenario requires careful application of professional judgment at the intersection of ASC 855 and ASC 820. Management's position is defensible only if the market decline was caused by genuinely new conditions arising in 20X5 (e.g., a sudden geopolitical crisis in January). However, if evidence suggests that credit deterioration, increasing default rates, or weakening housing fundamentals were already developing at December 31, 20X4—and the January-February market decline merely reflected the market's belated recognition of those pre-existing conditions—then the decline constitutes additional evidence of conditions existing at the balance sheet date (Type I). The auditor should examine whether credit metrics, delinquency rates, and macroeconomic indicators at year-end already pointed to impairment. Under ASC 820, fair value reflects market conditions at the measurement date. If the subsequent decline provides evidence that the December 31 fair value was already overstated because of pre-existing deterioration, the year-end valuation should be adjusted downward. If the decline is truly attributable to a new post-period shock, disclosure rather than adjustment is appropriate. In practice, most significant market declines reflect a combination of both pre-existing and new factors, requiring management and auditors to exercise significant judgment and thoroughly document their rationale.

SUMMARY

Summary — Subsequent Events Under ASC 855

Summary

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.