Subsequent Event Disclosure Periods and Reissuance Considerations

FAR coverage of subsequent event evaluation windows, issuance dates, availability for issuance, and reissuance considerations.

ASC 855 requires management to evaluate events after the balance sheet date through the date the financial statements are issued or available to be issued. The evaluation window matters because an event inside the window may require recognition or disclosure, while an event after the window is usually outside the financial statements being issued.

FAR questions often test the cutoff date. The answer depends on whether the entity is an SEC filer, a non-SEC filer, or is reissuing previously issued financial statements.

Evaluation Window

The evaluation window begins after the balance sheet date and ends on the relevant issuance date.

Entity or situation Evaluation endpoint Meaning
SEC filer or public company filing financial statements Date the financial statements are issued The date statements are filed or otherwise widely distributed so users can rely on them
Non-SEC filer or private company Date the financial statements are available to be issued The date all approvals are complete and no further steps are needed before distribution
Reissued statements with no revision for later events Original issuance or available-to-be-issued date The evaluation period is not automatically reopened
Revised or restated statements Depends on the revision and disclosure being updated Management evaluates whether the revision affects subsequent-event disclosures and dates

The date of the auditor’s report is not automatically the subsequent-event endpoint. It may be close to the endpoint in practice, but the accounting analysis focuses on issued or available-to-be-issued financial statements.

Issued Versus Available To Be Issued

Public and private entities use different wording because their release process differs.

Term Usually applies to Practical meaning FAR trap
Issued Public entities and SEC filers Financial statements have been distributed or filed so users can rely on them Do not stop evaluation at board approval if statements are not yet issued
Available to be issued Private entities and non-SEC filers Statements are complete, approvals are obtained, and management can distribute them Do not wait for every user to receive the statements

Private-company statements may be available to be issued before they are actually placed in every lender or owner portal. Once management has all required approvals and no further impediments remain, the evaluation period generally ends.

Timeline Logic

    flowchart LR
	    A["Balance sheet date"] --> B["Subsequent event evaluation window"]
	    B --> C{"Financial statements issued or available to be issued?"}
	    C -->|No| D["Continue evaluating later events"]
	    C -->|Yes| E["Evaluation period ends"]
	    E --> F{"Statements later reissued?"}
	    F -->|No| G["Use original evaluation date disclosure"]
	    F -->|Yes| H["Assess reissuance rules and disclose original and reissue context"]

Within the evaluation window, management still applies the recognized versus nonrecognized event analysis. A recognized event adjusts the statements because it confirms a condition at the balance sheet date. A nonrecognized event is disclosed if material because it arose after the balance sheet date.

Required Date Disclosure

Financial statements should disclose the date through which subsequent events were evaluated. This disclosure tells users the endpoint of management’s review.

Disclosure point Why it matters
Evaluation date Shows the last date considered for subsequent-event recognition and disclosure
Basis for the date Clarifies whether statements were issued or available to be issued
Reissuance date, when applicable Helps users distinguish the original evaluation period from later republication
Whether statements were updated for later events Prevents users from assuming a reissue automatically updates all subsequent-event evaluation

For a material nonrecognized subsequent event inside the evaluation window, the note should describe the nature of the event and estimate the financial effect if possible. If the effect cannot be estimated, the disclosure should say so.

Reissuance Considerations

Reissuance means previously issued financial statements are issued again, often because they are provided to another user, included in another filing, or revised for a correction. Reissuance does not automatically reopen the subsequent-event evaluation period for all events after original issuance.

Reissuance scenario Usual treatment
Statements reissued without revision Do not recognize or disclose events that occurred after original issuance unless required by the reissue context
Statements revised to correct an error Update the statements for the correction and consider whether subsequent-event disclosures related to the correction must be updated
Statements reissued with added disclosure Clarify what has changed and whether later events have been evaluated
Statements included in a later filing Follow the applicable reporting requirements and clearly identify the evaluation date used

The main FAR trap is assuming that a May reissuance of March financial statements means management must evaluate every event through May. The original evaluation date often remains the anchor unless the statements are revised in a way that requires updated subsequent-event disclosure.

Example: Private Company Reissuance

Assume a private company has a December 31 year-end. Management obtains all approvals and the financial statements are available to be issued on March 15. In April, the company reissues the same statements to a new lender without revising the statements.

The subsequent-event evaluation period generally ended on March 15. Events occurring after March 15 are not automatically added to the reissued statements. If the statements are revised for a material error, management must evaluate whether the correction affects subsequent-event disclosures and explain the reissue context.

Common Pitfalls

Pitfall Better FAR reasoning
Using the audit report date as the automatic endpoint Use issued or available-to-be-issued date under ASC 855
Ending a private-company evaluation when fieldwork ends Continue until statements are available to be issued
Treating reissuance as a full reopening of all later events Reissuance does not automatically reopen the evaluation period
Omitting the evaluation date disclosure Users need to know the date through which subsequent events were evaluated
Confusing event classification with evaluation period First decide whether the event is inside the window, then classify recognized or nonrecognized
Ignoring material Type 2 events inside the window Do not adjust, but disclose if material

Key Takeaways

  • Subsequent events are evaluated after the balance sheet date through issuance or availability for issuance.
  • Public entities generally evaluate through the date financial statements are issued.
  • Private entities generally evaluate through the date financial statements are available to be issued.
  • Financial statements should disclose the date through which subsequent events were evaluated.
  • Reissuance does not automatically reopen the evaluation period for all later events.

Disclosure Periods Knowledge Check

### For an SEC filer, subsequent events are generally evaluated through which date? - [x] The date the financial statements are issued or filed - [ ] The balance sheet date - [ ] The date the audit team begins fieldwork - [ ] The date the first draft is prepared > **Explanation:** Public-company financial statements are evaluated through the date they are issued, such as the filing date. ### For a private company, subsequent events are generally evaluated through which date? - [x] The date the financial statements are available to be issued - [ ] The date cash receipts are closed for the month - [ ] The date the tax return is filed - [ ] The date the bank first requests financial statements > **Explanation:** Private entities evaluate events through the date statements are complete, approved, and available for distribution. ### What disclosure tells users the endpoint of management's subsequent-event review? - [x] The date through which subsequent events were evaluated - [ ] The depreciation method used for fixed assets - [ ] The number of audit staff assigned - [ ] The date inventory was purchased > **Explanation:** ASC 855 requires disclosure of the date through which subsequent events were evaluated. ### A private company reissues unchanged March financial statements to a new lender in May. What is the usual effect on the subsequent-event evaluation period? - [x] The original available-to-be-issued date generally remains the evaluation endpoint - [ ] The evaluation period automatically extends through May for all events - [ ] All post-March events must be recognized - [ ] No subsequent-event disclosure is allowed > **Explanation:** Reissuing unchanged statements does not automatically reopen the evaluation period for all later events. ### Which event is inside the subsequent-event evaluation window? - [x] An event after year-end but before statements are issued or available to be issued - [ ] An event before the beginning of the fiscal year - [ ] An event after the evaluation endpoint with no reissuance issue - [ ] An event planned for the next fiscal year but not yet occurring > **Explanation:** The subsequent-event window runs after the balance sheet date through issuance or availability for issuance. ### What is the correct sequence for analyzing a later event? - [x] Determine whether it is inside the evaluation window, then classify it as recognized or nonrecognized - [ ] Recognize every event first, then decide whether it occurred - [ ] Disclose only unfavorable events - [ ] Ignore the issuance date and focus only on management intent > **Explanation:** The evaluation window determines whether ASC 855 applies; then the event is classified based on whether the underlying condition existed at the balance sheet date.
Revised on Monday, June 15, 2026