ASC 855 governs subsequent events: how a company identifies, classifies, and reports things that happen after the balance sheet date but before the financial statements go out. The rule turns on a single question. Did the condition behind the event already exist at the balance sheet date? If yes, adjust the numbers. If no, the numbers stay put, but disclose the event when leaving it out would mislead the reader.
When the Evaluation Window Opens and Closes
The evaluation period begins the day after the balance sheet date. It closes on one of two dates, depending on the entity.
SEC filers and conduit bond obligors for publicly traded debt evaluate through the date the financial statements are issued. Financial statements are issued when they are widely distributed to shareholders and other users in a GAAP-compliant form. The SEC staff has clarified that for SEC filers, issuance generally occurs on the earlier of the date the statements are widely distributed or filed with the Commission. An earnings release does not count, because it is not in a form that complies with GAAP and GAAS.
Every other entity evaluates through the date the statements are available to be issued. That means complete in GAAP-compliant form with all necessary approvals obtained from management, the board, or significant shareholders. A private company that needs board sign-off before release can end up with a shorter evaluation window than an SEC filer whose filing deadline sits further out.
Non-SEC filers must disclose the date through which they evaluated subsequent events and state whether that date is the issuance date or the available-to-be-issued date. SEC filers are exempt from that disclosure, because the filing date is already on the public record.
Type 1 Events: Adjust the Financial Statements
A recognized subsequent event, called a Type 1 event, gives you better information about a condition that already existed at the balance sheet date. It sharpens an estimate management was already making when the books closed. The numbers get adjusted to reflect the better information.
Litigation is the classic case. If a lawsuit arose from events that occurred before year-end and settles afterward for a different amount than the accrued liability, the settlement figure informs the estimate that should have been recorded at the balance sheet date. Adjust the liability to the settlement amount.
Customer bankruptcy runs the same way when the trouble was already there. A customer whose receivable was outstanding at year-end files for bankruptcy before the statements are issued, and the bankruptcy reflects financial deterioration that predated the reporting date. The receivable and the allowance for doubtful accounts get adjusted to reflect the confirmed loss.
The condition-at-year-end test is what does the classification work, and it can flip the answer on facts that look identical on the surface. A customer whose bankruptcy grew out of pre-existing financial deterioration is Type 1. A customer whose bankruptcy was triggered by a February factory fire is not, because the fire created a new condition that did not exist at the balance sheet date.
Type 2 Events: Disclose but Do Not Adjust
A nonrecognized subsequent event, or Type 2 event, arises from conditions that did not exist at the balance sheet date. These are genuinely new developments. Because the condition was absent when the period closed, the financial statement balances stay as they are. The event goes in the footnotes when it is material enough that omitting it would make the statements misleading.
The FASB codification lists concrete examples:
- Debt or equity issuances after the balance sheet date, such as selling bonds or stock
- Business combinations completed after year-end, with Topic 805 requiring its own specific disclosures
- Destruction of assets by fire or natural disaster
- Changes in the fair value of assets, liabilities, or foreign exchange rates after the balance sheet date
- New commitments or guarantees representing significant contingent liabilities
- New litigation where the underlying events occurred entirely after the balance sheet date
A Type 2 disclosure must let the reader assess the potential financial impact. Include an estimate of the financial effect where one can be made. Where it cannot, say so explicitly. Silence on the number without an explanation falls short of the standard.
What the Footnotes Must Say
Non-SEC filers have two required disclosures under ASC 855-10-50-1: the date through which management evaluated subsequent events, and whether that date is the issuance date or the available-to-be-issued date. Both signal to readers exactly how far management’s review extended.
SEC filers skip the evaluation-date disclosure. For everyone, a Type 2 footnote needs to describe the nature of the event and give enough detail that a reader can gauge its potential effect. If an estimate is available, include it. If not, state that fact.
The ASC 450 Overlap
Loss contingencies under ASC 450 sit right on top of the subsequent events window, and this is where classification errors cluster. ASC 450 requires accruing a loss when it is probable that an asset was impaired or a liability was incurred at the balance sheet date and the amount can be reasonably estimated. Much of the evidence confirming those conditions surfaces during the subsequent events period.
Litigation that originated before the balance sheet date and settles during the window drives a Type 1 adjustment. The settlement amount informs the liability recognized at the balance sheet date. If a previously accrued contingent liability is settled for less than the recorded amount, reverse the liability to the extent it exceeds the settlement.
The mirror situation goes the other way. ASC 450 specifically addresses information available after the balance sheet date that indicates a liability was incurred after the balance sheet date. If a company guaranteed someone else’s debt after year-end and that debtor then went bankrupt, the guarantee obligation did not exist at year-end. The accrual condition is not met, so the event is Type 2 and gets disclosure rather than recognition.
Revised or Reissued Financial Statements Reopen the Window
When financial statements are revised to correct an error or to apply a change in accounting principle retrospectively, the subsequent events evaluation period reopens. The codification treats revised financial statements as reissued financial statements, so management must evaluate subsequent events again through the new issuance date.
The extended evaluation covers the gap between the original issuance date and the reissuance date. Events discovered in that gap run through the same Type 1 / Type 2 framework. If a newly discovered event relates to a condition that existed at the original balance sheet date, it may require restating previously reported figures. If it represents a new condition arising after the original balance sheet date, it goes in the reissued notes as a disclosure.
Non-SEC filers must disclose the evaluation dates for both the originally issued statements and the revised statements. SEC filers are exempt from that dual-date disclosure, consistent with the general exemption.
Going Concern Runs on the Same Clock
ASC 205-40 requires management to evaluate whether substantial doubt exists about the entity’s ability to continue as a going concern, and the evaluation runs through the same endpoint as the subsequent events window. Events that occur after the balance sheet date but before issuance feed directly into that analysis.
Losing a major customer contract in January, an unfavorable litigation ruling in February, or a debt covenant violation discovered before release can all raise going concern doubts even if the entity looked stable at year-end. An event that makes an anticipated future adverse condition more likely during the look-forward period, generally one year from the issuance date, also factors in. The same post-balance-sheet information that triggers a Type 2 disclosure can simultaneously drive going concern disclosures, or in extreme cases affect whether the statements should be prepared on a going concern basis at all.