01 / 21

Subsequent Events
Identify & Classify

Master the two types of subsequent events under ASC 855: recognize which conditions existed at the balance sheet date and which arose after.

CPA FAR

What Are Subsequent Events?

Subsequent events are events or transactions that occur after the balance sheet date but before the financial statements are issued (or available to be issued). They may provide additional evidence about conditions that existed at the balance sheet date or arise from conditions that did not exist at that date.

The Evaluation Window

Balance Sheet Date Dec 31 Subsequent Event Evaluation Period F/S Issued (or Available) Mar 15 No further evaluation

Two Types: Recognized vs. Non-Recognized

Type I: Recognized
Conditions existed at the balance sheet date. The subsequent event provides additional evidence. Financial statements are adjusted.
Type II: Non-Recognized
Conditions did not exist at the balance sheet date. The event arose after. Financial statements are not adjusted but may require disclosure.

The Core Rule Under ASC 855

Event occurs after B/S date Did condition exist at B/S date? YES NO Type I: Recognized Adjust the financial statements Type II: Non-Recognized Disclose (if material) Do not adjust

Type I: Recognized Events

Type I events provide additional evidence about conditions that already existed at the balance sheet date. Because the underlying condition was present, the financial statements must be adjusted to reflect the new information.

1
Settlement of litigation: A lawsuit was pending at year-end and settles in January for a specific amount.
2
Bankruptcy of a customer: A receivable existed at year-end; the customer declares bankruptcy in February, confirming uncollectibility.
3
Loss on inventory: Inventory was on hand at year-end; a subsequent sale below cost confirms the loss existed.

Type II: Non-Recognized Events

Type II events arise from conditions that did not exist at the balance sheet date. They represent new developments after year-end. The financial statements are not adjusted, but if the event is material, note disclosure is required.

1
Fire or natural disaster: A warehouse burns down in January; the loss did not exist at Dec 31.
2
Business combination: An acquisition closes in February; no obligation existed at year-end.
3
Issuance of debt or equity: New bonds issued in January create obligations that did not exist at year-end.

Key Distinction: Same Event, Different Types

The same category of event can be Type I or Type II depending on when the underlying condition originated. Litigation is a classic example:

Lawsuit Filed Before Year-End
Settled after year-end for a known amount. The condition (the lawsuit) existed at the B/S date. This is Type I: adjust the F/S.
Lawsuit Filed After Year-End
A new lawsuit is filed in January arising from a January event. The condition did not exist at the B/S date. This is Type II: disclose only.

Disclosure Requirements

Type I
No separate disclosure is needed because the financial statements themselves are adjusted to reflect the event.
Type II
Disclose the nature of the event and an estimate of its financial effect (or state that an estimate cannot be made).
Date Disclosure
Entities must disclose the date through which subsequent events were evaluated, and whether that date is the issued or available-to-be-issued date.

How to Apply the Framework

1
Identify the event: Determine what occurred after the balance sheet date but before the F/S issuance date.
2
Trace the condition: Ask: "Did the underlying condition exist at the balance sheet date?"
3
Classify the event: If yes, it is Type I (recognized). If no, it is Type II (non-recognized).
4
Determine treatment: Type I: adjust the financial statements. Type II: disclose if material.
5
Document the evaluation date: Disclose the date through which subsequent events were evaluated.

Example 1: Customer Bankruptcy

Scenario: On December 31, Apex Corp. had a \( \$500{,}000 \) accounts receivable from Beta Inc. On February 10 (before F/S issuance), Beta Inc. files for bankruptcy and notifies Apex that it cannot pay.

Dec 31 Receivable exists $500,000 Feb 10 Beta files bankruptcy Mar 15 F/S issued

Example 2: Warehouse Fire

Scenario: Apex Corp. had inventory valued at \( \$2{,}000{,}000 \) on December 31. On January 20, a fire destroyed the entire warehouse. F/S are issued March 15.

Dec 31 Inventory intact $2,000,000 Jan 20 Fire destroys warehouse Mar 15 F/S issued

Example 3: Inventory Sale Below Cost

Scenario: On December 31, Gamma Inc. holds inventory recorded at cost of \( \$800{,}000 \). On January 15, Gamma sells the inventory for \( \$600{,}000 \). Market conditions had been declining throughout December.

Analysis
The market decline existed at Dec 31. The January sale merely confirms the lower net realizable value. The condition (market decline) was present at the B/S date.
Conclusion
Type I (Recognized). Write down inventory by \( \$200{,}000 \) to reflect the lower of cost or NRV at December 31.

Example 4: Debt Issuance in January

Scenario: On January 25, Delta Corp. issues \( \$10{,}000{,}000 \) in bonds to fund a planned expansion. The board authorized the issuance on January 10. The December 31 F/S are issued March 1.

Analysis
No bond obligation existed at Dec 31. The authorization and issuance both occurred after the B/S date. This is a new condition arising in January.
Conclusion
Type II (Non-Recognized). Do not adjust F/S. If material, disclose the bond issuance and its financial implications in the notes.

Common Mistakes to Avoid

Confusing Discovery with Origin
The date you learn about a condition is not the same as the date it existed. Always trace back to the origin.
Adjusting for Type II Events
New conditions after year-end are never adjusted in the F/S. They are disclosed only if material.
Wrong Evaluation Window
SEC filers use the issuance date, not the available-to-be-issued date. Using the wrong endpoint can miss or include events incorrectly.

Summary Comparison Table

Type I (Recognized) Type II (Non-Recognized)
Condition at B/S Date Existed Did not exist
F/S Treatment Adjust Do not adjust
Disclosure Not separately required Required if material
Examples Lawsuit settled, bad debt confirmed Fire, acquisition, new debt
Mnemonic "Existed: Adjust" "New: Note it"

Question 1 of 5

An entity's year-end is December 31. On February 5, a customer who owed \( \$200{,}000 \) at year-end declares bankruptcy. The financial statements have not yet been issued. How should this event be treated?

Question 2 of 5

A company's December 31 financial statements are issued on March 10. On January 28, a major earthquake destroys a production facility. What type of subsequent event is this?

Question 3 of 5

Which of the following is the critical question to determine whether a subsequent event is Type I or Type II?

Question 4 of 5

On January 15, a company settles a lawsuit that was filed against it in October of the prior year. The settlement amount was \( \$3{,}000{,}000 \). The December 31 financial statements have not been issued. What should the company do?

Question 5 of 5

An SEC filer has a December 31 year-end. The financial statements are issued on February 28 and were available to be issued on February 15. Through which date must the entity evaluate subsequent events?