Subsequent Events Training for Staff Accountants: Build ASC 855 Judgment From Year-End to Financial Statement Issuance

Last updated: September 3, 2026  |  35-minute read

What Is Subsequent Events Training for Staff Accountants?

Subsequent events training develops a staff accountant’s ability to evaluate information obtained after the balance-sheet date and determine whether that information changes the period-end numbers, requires disclosure only, or belongs entirely in the next reporting period.

ASC 855 divides subsequent events into two broad categories.

That is more precise than:

• “Did it happen before we issued?”
• “Did management know about it?”
• “Is the amount material?”
• “Does the event feel related to year-end?”

Timing matters. But the accounting hinges on the condition being evidenced.

This article connects directly to Contingency Accounting Training for Staff Accountants, CECL Training for Accountants, Income Tax Provision Training for Staff Accountants, Business Combination Accounting Training for Staff Accountants, and Fair Value Accounting Training for Staff Accountants.

Why ASC 855 Is a Judgment-Development Topic

I have practiced public accounting since 1990, founded my accounting firm in 1993, and helped grow Howard, Howard and Hodges from three people to approximately 50 staff. Since 2020, I have built SkillAbility around a recurring development issue: many staff accountants treat subsequent-events work as a final checklist completed after the “real” accounting is finished.

That reverses the importance of the process.

The issuance period can produce some of the strongest evidence about receivable collectibility, litigation exposure, inventory realizability, fair-value assumptions, going-concern conditions, tax positions, debt and liquidity, business combinations, asset impairment, and contingent gains or losses.

The skill is not memorizing “Type 1 vs. Type 2.” The skill is determining what the later event actually proves about the earlier reporting date.

What Is Current in ASC 855 in 2026?

KPMG’s current Financial Statement Presentation Handbook is dated September 2025 and includes a dedicated chapter on ASC 855 subsequent events. It remains current in 2026 and is effective immediately.

ASC 855’s core recognized-versus-nonrecognized framework has not been replaced in 2026. What changed is the environment in which staff have to apply it.

Chart: Where ASC 855 Judgment Concentrates

SkillAbility training heat map—not a FASB ranking. Actual risk depends on entity status, issuance timeline, estimates, litigation, financing, taxes, acquisitions, credit exposure, market movements, and whether financial statements are later revised or reissued.

The EVENT READY Framework

E — Establish the Correct Subsequent-Event Evaluation Window

Staff cannot evaluate subsequent events correctly until they know when the evaluation period ends.

SEC filers and relevant conduit bond obligors

ASC 855 generally requires an SEC filer—and a conduit bond obligor for conduit debt securities traded in a public market—to evaluate subsequent events through the date the financial statements are issued.

Other entities

Entities that are neither SEC filers nor qualifying conduit bond obligors generally evaluate subsequent events through the date the financial statements are available to be issued.

Do not assume “audit report date” is automatically the cutoff

The financial-statement issuance process depends on the entity’s governance, approvals, distribution, audit status, and reporting requirements.

The accounting team should document:

• entity status,
• required approvals,
• expected audit report date,
• board or owner approval date where relevant,
• financial statement distribution date,
• actual issued / available-to-be-issued date.

What Do “Issued” and “Available to Be Issued” Mean?

ASC 855 uses the terms deliberately.

Financial statements are issued

Financial statements are generally considered issued when they are widely distributed to shareholders and other financial statement users for general use and reliance in a GAAP-compliant form and format.

Financial statements are available to be issued

Financial statements are generally available to be issued when:

• they are complete in a GAAP-compliant form and format, and
• all approvals necessary for issuance have been obtained.

Those approvals can depend on the entity and may involve:

• management,
• board of directors,
• owners / significant shareholders,
• other governance requirements.

Private-company disclosure

A non-SEC filer generally discloses the date through which subsequent events were evaluated and whether that date represents:

• the date the financial statements were issued, or
• the date they were available to be issued.

That seemingly small disclosure is also a control: it forces management to identify the end of the evaluation period.

V + E + R — Recognized Subsequent Events

A recognized subsequent event provides additional evidence about a condition that existed at the balance-sheet date.

The later event helps management measure or confirm the year-end amount.

Classic example: litigation settlement

A lawsuit arose from pre-year-end conduct.

The company accrued $1.5M at December 31.

Before issuance, the case settles for $2.2M.

If the settlement provides additional evidence about the liability that already existed at December 31:

Classic example: customer bankruptcy

A customer was already experiencing significant financial deterioration at December 31.

The customer files bankruptcy in February before issuance.

If the bankruptcy culminates a deterioration that existed at year-end, it can provide recognized subsequent-event evidence relevant to the year-end receivable allowance.

Other potential recognized-event examples

• settlement of an estimated liability tied to a pre-year-end condition,
• discovery of pre-year-end fraud or asset misappropriation,
• later evidence clarifying inventory realizability at year-end,
• information received after year-end that corroborates a condition embedded in a period-end fair-value estimate.

The underlying Topic still matters

ASC 855 tells the accountant whether later evidence belongs in the year-end analysis.

It does not replace:

• ASC 450 loss-contingency measurement,
• ASC 326 credit-loss measurement,
• ASC 820 fair-value measurement,
• ASC 740 tax rules,
• ASC 330 inventory rules,
• other Topic-specific recognition guidance.

E — Nonrecognized Subsequent Events

A nonrecognized subsequent event provides evidence about a condition that did not exist at the balance-sheet date but arose afterward.

Do not adjust the year-end financial statement amounts for that event.

ASC 855 examples include

• issuance of bonds or capital stock after year-end,
• a business combination occurring after year-end,
• litigation arising from an event that occurred after year-end,
• loss of a plant or inventory in a post-year-end fire or natural disaster,
• changes in estimated credit losses caused by conditions arising after year-end,
• changes in fair values or foreign-exchange rates after year-end.

Important does not mean recognized

Assume a company has $30M of inventory at December 31.

A warehouse burns down on January 20.

The fire did not exist at December 31.

Therefore, the December inventory is not written off merely because the financial statements are still open.

If material, the fire may require nonrecognized subsequent-event disclosure.

2026 tariff ruling example

Deloitte concluded that for reporting periods ending before the 2026 Supreme Court tariff ruling, the ruling itself was a nonrecognized subsequent event because the legal change occurred after the reporting date.

That is a useful training example:

E — Disclosure of Material Nonrecognized Subsequent Events

Nonrecognized does not mean “ignore.”

ASC 855 requires disclosure when a nonrecognized subsequent event is of such a nature that omitting it would make the financial statements misleading.

Required disclosure elements

When disclosure is required, include:

• the nature of the event, and
• an estimate of its financial effect, or
• a statement that such an estimate cannot be made.

Examples

• Material post-year-end acquisition
• Major debt or equity financing
• Destruction of a significant facility
• Major post-year-end litigation event arising from post-year-end conduct
• Material change in law
• Significant restructuring announced and initiated after year-end
• Material post-year-end fair-value or foreign-exchange movement, depending on facts and misleading-omission considerations

“Cannot estimate” should be supportable

A disclosure should not default to “the financial effect cannot be estimated” simply because the calculation is inconvenient.

Staff should ask:

• Can a range be estimated?
• Can a gross effect be estimated even if the net effect is uncertain?
• Is management still evaluating financing, insurance, or transaction structure?
• What information is missing?
• When should the estimate be refreshed?

N — Subsequent Evidence vs. Hindsight

This is one of the hardest practical ASC 855 distinctions.

Later information can be relevant without giving management permission to rewrite year-end assumptions using facts that did not exist at year-end.

Ask two questions

1. What condition existed at the measurement date?
2. Does the later information provide evidence about that condition—or does it reflect a genuinely new condition?

Example: December forecast vs. January customer cancellation

At December 31, the customer:

• was current on payments,
• had renewed its contract in November,
• had not indicated a plan to leave.

On January 20, the customer is acquired by a competitor and cancels the contract.

The January event may be economically significant.

But if the cancellation resulted from a new January acquisition, it may not be evidence that the December forecast was wrong.

Example: January bankruptcy after months of deterioration

At December 31, the customer:

• was 120 days past due,
• had lost its primary lender,
• was negotiating emergency financing.

On January 15, it files bankruptcy.

That later filing can be powerful evidence about collectibility at December 31.

Evidence map

Worked Example 1: Litigation Settlement After Year-End

Assume a December 31 year-end.

A customer lawsuit arose in September from alleged contract breaches that occurred during the year.

At December 31

• Outside counsel believes loss is probable.
• Best estimate: $1.8M.
• Company records $1.8M under ASC 450.

On February 10

Before the financial statements are issued, the company signs a settlement for $2.5M.

The settlement relates to the same pre-year-end conduct.

Under ASC 855, the settlement can provide additional evidence about the liability that existed at December 31.

What should the staff accountant document?

• Underlying breach date
• Lawsuit chronology
• Original ASC 450 estimate
• Settlement date
• Why the settlement confirms the year-end condition
• Revised journal entry
• Disclosure impact

Change the facts

Assume instead that the conduct giving rise to litigation occurred on January 15.

The February settlement would not create a December 31 liability because the underlying condition did not exist at year-end.

It could still require disclosure if material.

Customer Bankruptcy: Subsequent Event or New Credit Condition?

A post-year-end bankruptcy is a classic ASC 855 training scenario because the answer depends on what caused the bankruptcy.

Recognized fact pattern

At year-end:

• $900,000 receivable
• customer seriously delinquent
• credit rating deteriorated
• known lender withdrawal
• severe liquidity problems

Customer files bankruptcy two weeks later.

The filing can corroborate conditions that already existed at year-end.

The year-end ASC 326 allowance should consider that evidence.

Nonrecognized fact pattern

At year-end:

• customer financially healthy,
• payments current,
• no known liquidity problems.

In January, a catastrophic event destroys the customer’s only operating facility, causing bankruptcy.

The bankruptcy may reflect a new post-year-end condition rather than preexisting year-end credit deterioration.

That is exactly why ASC 855 training has to focus on the condition, not the calendar.

For the underlying credit-loss model, see CECL Training for Accountants.

Fair Value and Market Movements After Year-End

Post-year-end prices are often tempting evidence.

ASC 855 requires discipline about the measurement date.

General rule

A fair-value measurement as of December 31 should reflect market-participant assumptions and conditions that existed on December 31.

A January price movement caused by January information generally should not be backdated.

But later transactions can still provide evidence

Suppose an illiquid private investment is valued at December 31.

A sale closes January 8.

Staff should ask:

• Were transaction negotiations substantially complete by December 31?
• Did the January closing merely formalize preexisting terms?
• Did January bring new information or changed market conditions?
• Was the transaction orderly?
• Does the transaction reflect the same unit of account?

If the January transaction provides evidence about December 31 conditions, it may inform the period-end valuation.

If it reflects new January circumstances, it is not a basis for changing December fair value.

For the underlying valuation principles, see Fair Value Accounting Training for Staff Accountants.

Tax Developments After Year-End: ASC 855 Is Not the Only Rule

Tax accounting demonstrates why ASC 855 cannot be applied by analogy without checking the governing Topic.

Change in tax law or rate

ASC 740 generally requires effects of a tax-law or tax-rate change to be recognized in the period that includes the enactment date.

If the law is enacted after year-end, the prior-year tax provision generally is not adjusted merely because the financial statements remain open.

Disclosure under ASC 855 may still be relevant if the effect is material.

Uncertain tax-position settlement

ASC 740 has specialized guidance that can produce a result different from a general ASC 855 analogy.

For example, a post-year-end tax litigation settlement related to a pre-year-end position is not necessarily recognized in the prior-year financial statements under ASC 740 even though an ordinary litigation settlement under ASC 450 might be recognized under ASC 855.

For the underlying tax model, see Income Tax Provision Training for Staff Accountants.

Post-Year-End Business Combinations, Debt, and Equity Financing

Some of the most material subsequent events do not change year-end recognition at all.

Business combination after year-end

A business combination that occurs after the balance-sheet date is a classic nonrecognized subsequent event.

The acquisition did not exist at year-end merely because negotiations were underway.

However, ASC 805 can require specific disclosures about a material business combination occurring after year-end.

For the acquisition accounting itself, see Business Combination Accounting Training for Staff Accountants.

Debt or equity issuance after year-end

Issuing bonds, borrowing under a new financing arrangement, or issuing stock after the balance-sheet date generally reflects a post-year-end transaction rather than a transaction that should be recorded at year-end.

But the financing can still matter to:

• liquidity disclosures,
• going-concern analysis,
• debt classification under Topic-specific guidance,
• subsequent-event disclosure,
• pro forma or SEC reporting requirements.

Do not use ASC 855 to override specialized debt rules

Post-year-end refinancing, waiver, covenant, and classification questions can be highly fact-specific under ASC 470 and related guidance.

Staff should route the matter to the applicable debt accounting literature before concluding that a later financing event retroactively changes year-end classification.

A — Going Concern, Liquidity, and Subsequent Events

Going concern is one of the most important areas where events after year-end can matter even when they are not recognized as ordinary year-end transactions.

ASC 205-40 requires management to evaluate whether conditions and events, considered in the aggregate, raise substantial doubt about the entity’s ability to continue as a going concern for the relevant one-year look-forward period measured from the date the financial statements are issued—or available to be issued when applicable.

That creates a broader horizon than December 31

Examples of post-year-end events relevant to going concern can include:

• loss of a major customer,
• loss of critical financing,
• new borrowing obtained,
• equity infusion,
• default or covenant breach,
• major litigation judgment,
• facility loss,
• severe supply disruption,
• restructuring or cost-reduction plan.

A post-year-end financing may be a nonrecognized subsequent event for ordinary transaction accounting but still be highly relevant to whether management’s plans alleviate substantial doubt.

Keep two questions separate

One event can produce:

• no year-end journal entry,
• a subsequent-event disclosure, and
• a major going-concern conclusion.

Current 2026 context

Deloitte’s 2026 financial-reporting alerts continue to emphasize that fast-moving geopolitical, tariff, liquidity, and operating developments may affect both subsequent-event disclosures and going-concern analysis.

Y — Reissued and Retrospectively Revised Financial Statements

The subsequent-events process becomes more complex when previously issued financial statements are later reissued or retrospectively revised.

Do not automatically reopen every historical number

ASC 855 generally does not require an entity to recognize events or transactions that occurred after the original financial statements were issued or available to be issued merely because the statements are later reissued in comparative form.

But other accounting requirements can require retrospective revision.

Examples of retrospective revision can include

• discontinued operations,
• changes in reportable segments,
• certain changes in accounting principle,
• stock splits or similar retrospective presentation matters, depending on the applicable guidance.

In those situations, staff need to understand:

• what changed retrospectively,
• what new subsequent-event evaluation is required,
• whether new information is an error under ASC 250 rather than a subsequent event,
• which disclosure dates are required for a non-SEC filer.

Non-SEC filer date disclosures

When non-SEC-filer financial statements are revised, ASC 855 can require disclosure of both:

• the date through which subsequent events were evaluated in the originally issued / available-to-be-issued statements, and
• the date through which they were evaluated for the revised financial statements.

Reissuance is a reviewer topic

Staff should not independently decide that an event discovered during a reissuance is:

• a new subsequent event,
• a prior-period error,
• or a retrospective presentation adjustment.

That classification can change the financial statements materially and usually warrants manager or technical-accounting review.

Worked Example 2: One Year-End, Six Subsequent Events

Assume a private manufacturing company has a December 31 year-end and its financial statements become available to be issued on March 15.

The accounting package should not be one checklist

It should contain six mini-analyses:

1. event chronology,
2. condition at December 31,
3. recognized / nonrecognized conclusion,
4. underlying accounting Topic,
5. journal entry or disclosure effect,
6. going-concern / broader-reporting effect.

An Issuance-Period Subsequent-Event Workflow

Build one controlled subsequent-event register

Suggested fields:

• Event ID
• date identified
• event date
• business owner
• source of information
• related balance / estimate
• condition at balance-sheet date
• recognized / nonrecognized
• governing accounting Topic
• journal-entry effect
• disclosure effect
• going-concern effect
• materiality
• reviewer
• final resolution

That register should remain open until the actual issuance or available-to-be-issued cutoff.

ASC 855 Self-Review Checklist Before Manager Review

• Did I determine whether the entity is an SEC filer, qualifying conduit bond obligor, or another entity?
• Did I identify the correct subsequent-event evaluation cutoff?
• Did I distinguish financial statements issued from available to be issued?
• Did I document the approvals necessary for the financial statements to be available to be issued?
• For a non-SEC filer, did I prepare the required disclosure of the date through which subsequent events were evaluated?
• Did I state whether that date was the issuance date or the date the financial statements were available to be issued?
• Did I keep the subsequent-event process open through the actual cutoff rather than an estimated cutoff?
• Did I identify all material events occurring after the balance-sheet date?
• Did I identify the source and date of each event?
• Did I identify the business owner for each event?
• Did I determine what condition existed at the balance-sheet date?
• Did I distinguish the event date from the date the underlying condition began?
• Did I document facts existing before the balance-sheet date?
• Did I document facts arising only after the balance-sheet date?
• Did I avoid classifying an event solely because it occurred before issuance?
• Did I classify each material event as recognized or nonrecognized?
• For a recognized event, did I explain why it provides additional evidence about a condition existing at year-end?
• For a nonrecognized event, did I explain why the underlying condition arose after year-end?
• Did I identify the accounting Topic governing the underlying recognition or measurement?
• Did I avoid using ASC 855 as a replacement for ASC 450 loss-contingency guidance?
• Did I avoid using ASC 855 as a replacement for ASC 326 credit-loss guidance?
• Did I avoid using ASC 855 as a replacement for ASC 740 tax guidance?
• Did I avoid using ASC 855 as a replacement for ASC 820 fair-value guidance?
• Did I identify ASC 805 requirements for post-year-end business combinations?
• Did I identify ASC 470 implications for debt classification/refinancing questions?
• Did I identify ASC 205-40 going-concern implications?
• Did I identify ASC 606 or ASC 842 implications where relevant?
• For recognized events, did I update the correct period-end estimate rather than simply record the subsequent transaction date?
• Did I reconcile the estimate change to the source evidence?
• Did I distinguish later evidence from hindsight?
• Did I avoid inserting facts that did not exist at the measurement date into the year-end estimate?
• Did I identify whether a post-year-end litigation settlement relates to pre-year-end conduct?
• Did I update a pre-year-end litigation accrual when the settlement provides better evidence?
• Did I avoid recognizing litigation arising from post-year-end conduct at year-end?
• Did I identify customer bankruptcies occurring before issuance?
• Did I determine whether the customer’s financial deterioration existed at year-end?
• Did I distinguish bankruptcy caused by a new post-year-end event from a culmination of pre-year-end deterioration?
• Did I update the ASC 326 allowance when later evidence supports year-end credit deterioration?
• Did I identify post-year-end customer collections relevant to year-end estimates?
• Did I apply any Topic-specific elections or practical expedients before using collection evidence?
• Did I identify inventory information received after year-end?
• Did I determine whether later inventory realization evidence reflects a preexisting condition?
• Did I identify post-year-end fair-value transactions or market data?
• Did I determine whether the later market information reflects year-end conditions or new market conditions?
• Did I avoid backdating January market movements to December without measurement-date support?
• Did I identify foreign-exchange rate changes occurring after year-end?
• Did I avoid adjusting year-end balances for post-year-end FX changes unless they provide evidence about a preexisting measurement condition under applicable guidance?
• Did I identify tax-law or tax-rate changes enacted after year-end?
• Did I apply ASC 740’s enactment-date requirements rather than general ASC 855 analogy?
• Did I identify settlements of uncertain tax positions after year-end?
• Did I check ASC 740’s specialized subsequent-measurement guidance before adjusting year-end tax balances?
• Did I identify post-year-end business combinations?
• Did I avoid recording a post-year-end acquisition in the prior-year financial statements?
• Did I prepare ASC 805 subsequent-acquisition disclosures when applicable?
• Did I identify post-year-end debt issuances?
• Did I identify post-year-end equity issuances?
• Did I evaluate required nonrecognized-event disclosure for material financing?
• Did I separately evaluate the financing in the going-concern analysis?
• Did I identify post-year-end fires, disasters, or physical asset losses?
• Did I avoid writing off year-end assets for a disaster that occurred only after year-end?
• Did I disclose a material post-year-end disaster when omission would be misleading?
• Did I identify post-year-end legal or regulatory changes?
• Did I determine whether the law or ruling created a new condition after year-end?
• Did I avoid backdating new legal conditions into the prior period?
• Did I evaluate whether a material nonrecognized event requires disclosure?
• Did the disclosure describe the nature of the event?
• Did the disclosure include an estimate of the financial effect when estimable?
• If no estimate was provided, did I document why an estimate cannot be made?
• Did I challenge unsupported “cannot estimate” language?
• Did I consider whether a range or partial estimate could be disclosed?
• Did I identify events relevant to going-concern conditions?
• Did I update management’s one-year going-concern assessment for post-year-end events?
• Did I distinguish an ASC 855 recognition conclusion from an ASC 205-40 going-concern conclusion?
• Did I consider post-year-end financing as part of management’s going-concern plans?
• Did I identify covenant, default, or refinancing developments requiring specialized debt guidance?
• Did I escalate debt-classification questions rather than rely on general ASC 855 logic?
• Did I identify whether financial statements will be retrospectively revised?
• Did I distinguish reissuance from ordinary comparative presentation?
• Did I identify whether a later-discovered issue is a subsequent event or an ASC 250 error?
• For revised non-SEC financial statements, did I disclose both required subsequent-event evaluation dates where applicable?
• Did I identify changes in reportable segments or discontinued operations that require retrospective revision?
• Did I identify stock splits or other retrospective presentation matters under applicable guidance?
• Did I reconcile recognized subsequent-event entries to the GL?
• Did I reconcile nonrecognized-event disclosures to the subsequent-event register?
• Did I reconcile legal subsequent events to the contingency register?
• Did I reconcile credit events to the CECL workpaper?
• Did I reconcile tax events to the tax provision workpaper?
• Did I reconcile acquisition events to the transaction/accounting team?
• Did I reconcile financing events to treasury and debt schedules?
• Did I reconcile going-concern events to management’s liquidity forecast?
• Did I obtain final updates from legal counsel before issuance?
• Did I obtain final updates from treasury before issuance?
• Did I obtain final updates from tax before issuance?
• Did I obtain final updates from sales/collections on major customers?
• Did I obtain final updates from operations on significant asset events?
• Did management perform a final subsequent-event inquiry near the actual issuance cutoff?
• Did the auditor/management representation process align with the same cutoff?
• Did I document who reviewed each material event?
• Can another accountant trace each material event from source → year-end condition → ASC 855 classification → Topic-specific accounting → journal entry/disclosure?
• Can another accountant explain why no year-end adjustment was made for each material nonrecognized event?

100-Point ASC 855 Readiness Scorecard

Suggested readiness bands

• 90–100: Ready to own the subsequent-events workstream with normal manager/technical review.
• 82–89: Generally review-ready; targeted coaching remains in cross-topic issues, reissuance, or estimate evidence.
• 72–81: Controlled ownership with checkpoints on recognized/nonrecognized and disclosure conclusions.
• Below 72: Continue structured ASC 855 practice.

Override the score for deliberately stopping the evaluation early, concealing material post-year-end events, backdating new conditions to manipulate results, withholding recognized evidence, or omitting a material nonrecognized event to avoid disclosure.

A 30/60/90-Day Subsequent Events Training Plan

15 Realistic ASC 855 Training Scenarios

1. Bankruptcy after year-end, deterioration before year-end

Staff treats the bankruptcy as recognized evidence relevant to the year-end credit-loss estimate.

2. Bankruptcy caused by a new January catastrophe

Staff identifies a new post-year-end condition rather than automatically adjusting the year-end allowance.

3. Pre-year-end lawsuit settles above the accrual

Staff updates the year-end liability when the settlement provides better evidence about the existing obligation.

4. Lawsuit arises from January conduct

No year-end liability is created; staff evaluates nonrecognized disclosure.

5. Warehouse burns in January

Staff does not write off December inventory or PP&E because the fire arose after year-end.

6. Major acquisition closes in February

Staff does not record the acquisition at December 31 but evaluates ASC 805 and ASC 855 disclosure.

7. Company issues $20M of debt in February

Staff treats the issuance as a post-year-end transaction while separately evaluating disclosure, liquidity, going concern, and debt guidance.

8. Private-company valuation closes shortly after year-end

Staff determines whether the transaction corroborates year-end market conditions or reflects new post-year-end facts.

9. New tax law is enacted in January

Staff applies ASC 740 enactment-date guidance and does not simply adjust December taxes under general ASC 855 logic.

10. Tax audit settles after year-end

Staff checks ASC 740’s specialized rule rather than assuming the result follows ordinary litigation accounting.

11. Major customer cancels because of a January acquisition

Staff distinguishes a new January event from evidence about December operations.

12. Major customer cancellation confirms December negotiations

If cancellation terms were substantially decided before year-end, staff evaluates whether the later action confirms a preexisting condition.

13. New geopolitical conflict erupts after year-end

Staff evaluates it as a nonrecognized event for periods ending before the conflict unless particular effects evidence conditions already present.

14. Financial statements are complete but board approval is still pending

A private-company team keeps the subsequent-event window open until all approvals needed for issuance are obtained.

15. Prior-year financial statements are retrospectively revised

Staff escalates whether later information is a reissuance disclosure issue, retrospective presentation matter, or ASC 250 error.

What CPA Firms Should Measure

Connect these measures to your Staff Accountant Competency Checklist, Accounting Employee Development Plan, Workpaper Review Checklist, and Accountants Shifting From Preparers to Reviewers.

Common Subsequent Events Training Mistakes

Mistake 1: “Before issuance” means adjust year-end

Timing is treated as the recognition criterion instead of the condition existing at the balance-sheet date.

Mistake 2: Complete the checklist before the evaluation period ends

The form is signed while material events can still occur.

Mistake 3: Use hindsight

January market, customer, or operating information is inserted into December estimates without proving that it reflects December conditions.

Mistake 4: Ignore material Type 2 events

“No journal entry” is interpreted as “no disclosure.”

Mistake 5: Use ASC 855 instead of the governing Topic

Tax, debt, CECL, fair value, or acquisition rules are overridden by a generic subsequent-event analogy.

Mistake 6: Ignore going concern because an event is nonrecognized

A post-year-end event can be nonrecognized and still materially affect the one-year liquidity assessment.

Mistake 7: Treat all customer bankruptcies the same

The team never asks whether credit deterioration existed at year-end.

Mistake 8: Backdate a post-year-end fire

A material disaster is recorded in the prior year instead of disclosed as a new condition.

Mistake 9: Use the wrong cutoff for a private company

The audit report or draft date is assumed to be the available-to-be-issued date without evaluating required approvals.

Mistake 10: Reissue statements without reopening the right controls

Revised financial statements are treated as a mechanical formatting exercise rather than a separate reporting event.

How SkillAbility Builds Subsequent-Event Capability

BASE — Event classification

• ASC 855 evaluation window
• issued vs available to be issued
• recognized vs nonrecognized
• basic disclosure
• event chronology

MAPS — Cross-topic judgment

• Litigation
• CECL / customer bankruptcies
• fair value
• tax
• business combinations
• financing
• going concern

SUMMIT — Issuance and reviewer readiness

• Own the subsequent-event register
• challenge hindsight
• review material disclosures
• coordinate legal, tax, treasury, valuation, and transaction teams
• manage reissuance / retrospective revision
• complete final issuance-date signoff
• coach staff without repeating every inquiry

Frequently Asked Questions About Subsequent Events Training

What is ASC 855?

ASC 855 is the U.S. GAAP Topic governing subsequent events—events or transactions occurring after the balance-sheet date but before financial statements are issued or available to be issued.

What is a recognized subsequent event?

A recognized subsequent event provides additional evidence about a condition that existed at the balance-sheet date. The financial statements are adjusted to reflect that evidence.

What is a nonrecognized subsequent event?

A nonrecognized subsequent event provides evidence about a condition that did not exist at the balance-sheet date but arose afterward. The prior-period amounts are not adjusted, but material disclosure can be required.

What is the difference between Type 1 and Type 2 subsequent events?

“Type 1” is common shorthand for recognized subsequent events and “Type 2” for nonrecognized subsequent events. The ASC 855 analysis still focuses on whether the underlying condition existed at the balance-sheet date.

How long do SEC filers evaluate subsequent events?

SEC filers generally evaluate subsequent events through the date the financial statements are issued.

How long do private companies evaluate subsequent events?

Entities that are neither SEC filers nor relevant conduit bond obligors generally evaluate subsequent events through the date their financial statements are available to be issued.

What does “available to be issued” mean?

Financial statements are generally available to be issued when they are complete in a GAAP-compliant form and format and all approvals necessary for issuance have been obtained.

Do private companies disclose the subsequent-event evaluation date?

Generally yes. A non-SEC filer discloses the date through which subsequent events were evaluated and whether that date was the issuance date or the date the financial statements were available to be issued.

Does every event before issuance change the year-end financial statements?

No. Only events providing additional evidence about conditions that existed at the balance-sheet date are recognized in the prior-period financial statements.

Is a post-year-end litigation settlement a recognized subsequent event?

It can be when the events giving rise to the litigation occurred before year-end and the settlement provides better evidence about the liability existing at the balance-sheet date.

Is a post-year-end fire a recognized subsequent event?

Generally no when the fire occurred after year-end. A material post-year-end fire is a classic nonrecognized event that may require disclosure.

Is a customer bankruptcy after year-end recognized?

It depends on the cause. Bankruptcy can provide recognized evidence when it culminates financial deterioration existing at year-end. Bankruptcy caused by a genuinely new post-year-end event can be nonrecognized.

Are market-price changes after year-end recognized?

Ordinary post-year-end changes in fair values or market prices generally are nonrecognized. Later transactions can still be relevant when they provide evidence about conditions that existed at the measurement date.

Is a business combination after year-end recognized in the prior year?

No. A post-year-end business combination is generally a nonrecognized subsequent event, although ASC 805 may require specific disclosures.

Is post-year-end debt or equity financing recognized at year-end?

Generally the financing transaction itself is not recorded at the prior year-end. It can still affect subsequent-event disclosure, liquidity, going concern, and Topic-specific debt or equity analysis.

Does a new tax law enacted after year-end adjust the prior-year tax provision?

Generally no. ASC 740 recognizes the effect of a tax-law or tax-rate change in the period that includes the enactment date. Material post-year-end enactment can still require disclosure.

Can a tax settlement after year-end be treated like an ordinary litigation settlement?

Not automatically. ASC 740 contains specialized guidance for uncertain tax positions, so staff should apply that Topic rather than assuming the general ASC 450/855 litigation model controls.

What must be disclosed for a material nonrecognized subsequent event?

ASC 855 generally requires disclosure of the nature of the event and an estimate of its financial effect—or a statement that such an estimate cannot be made—when omission would make the financial statements misleading.

Can a nonrecognized subsequent event affect going concern?

Yes. A post-year-end event can require no year-end journal entry yet still materially affect management’s ASC 205-40 going-concern assessment and related disclosures.

What happens when previously issued financial statements are revised?

Reissued or retrospectively revised financial statements can require additional ASC 855 analysis, revised evaluation-date disclosures for non-SEC filers, and consideration of whether later-discovered information is an ASC 250 error or another retrospective accounting matter.

How do you know when a staff accountant is review-ready for ASC 855?

A review-ready staff accountant can establish the evaluation cutoff, prove the condition existing at year-end, classify recognized versus nonrecognized events, update estimates without hindsight, apply the governing Topic, prepare disclosure, assess going concern, and complete an issuance-date evidence trail.

Current Research and Authority Resources

• KPMG — Financial Statement Presentation Handbook, September 2025 (includes ASC 855 subsequent events)
• Deloitte — Subsequent Events: Issuance, Reissuance, and SEC Reporting Considerations
• Deloitte — ASC 855 Subsequent-Event Considerations for Loss Contingencies
• Deloitte — ASC 855 Subsequent Events in CECL Accounting
• Deloitte — 2026 Middle East Conflict Financial Reporting Considerations
• Deloitte — 2026 Supreme Court Tariff Ruling Accounting Considerations
• Google Search Central — Optimizing for Generative AI Features
• Google Search Central — Generative AI Performance Reports

ASC 855 frequently intersects with ASC 450 contingencies, ASC 326 credit losses, ASC 740 income taxes, ASC 805 business combinations, ASC 820 fair value, ASC 470 debt, ASC 205-40 going concern, ASC 606 revenue, ASC 842 leases, ASC 330 inventory, ASC 250 accounting changes/errors, and SEC reporting requirements. Verify current authoritative literature and transaction-specific facts for live work.

The Bottom Line

Subsequent events training should not produce staff who ask whether anything happened after year-end.

It should produce accountants who can explain what the later event proves about the reporting date.

Establish the correct evaluation cutoff.

Identify what condition actually existed at year-end.

Recognize later evidence about existing conditions.

Do not backdate genuinely new post-year-end conditions.

Use the governing accounting Topic for measurement.

Preserve the measurement date and avoid hindsight.

Disclose material nonrecognized events when omission would mislead.

Include the financial effect—or say why it cannot be estimated.

Evaluate going concern even when no year-end journal entry is required.

Keep the subsequent-event register open through the actual issuance cutoff.

Reopen the right controls when financial statements are revised or reissued.

That is EVENT READY.

Protect Knowledge. Develop People. Scale the Firm.

To staff who know what later evidence means before review has to reconstruct the timeline,

Vincent Howard, CPA
Managing Partner, Howard, Howard and Hodges
SkillAbility for Accounting Firms

© 2026 SkillAbility for Accounting Firms. This article provides general educational information and does not replace client-specific U.S. GAAP, audit, tax, legal, SEC, regulatory, valuation, financing, transaction-advisory, or other professional advice.