Contingency Accounting Training for Staff Accountants: Build ASC 450 Judgment for Losses, Gains, and Disclosures

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

Last updated: September 2, 2026  |  34-minute read

What Is Contingency Accounting Training for Staff Accountants?

Contingency accounting training develops a staff accountant’s ability to convert uncertain legal, contractual, operational, insurance, and other events into the correct U.S. GAAP recognition, measurement, presentation, and disclosure conclusion.

ASC 450 defines a contingency around an existing condition, situation, or set of circumstances involving uncertainty that will ultimately be resolved by future events.

For loss contingencies, the accounting often begins with two questions:

If both conditions are met, the loss is generally accrued.

If a loss is only reasonably possible—or there is reasonably possible exposure beyond the amount already accrued—disclosure can be required.

If a loss is remote, specific ASC 450 disclosure generally is not required, although management still must consider whether omission would make the financial statements misleading.

Gain contingencies operate very differently.

This article connects directly to Income Tax Provision Training for Staff Accountants, CECL Training for Accountants, Business Combination Accounting Training for Staff Accountants, Revenue Recognition Training for Staff Accountants, and Workpaper Review Checklist.

Why Contingency Accounting 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 problem: staff often receive a litigation spreadsheet containing matter name, attorney, and one probability word—but little evidence connecting the word to the financial statements.

That is not enough for ASC 450.

The accountant has to understand:

• what event happened before the balance-sheet date,
• what obligation or asset impairment might already exist,
• whether the matter belongs in ASC 450,
• what counsel actually concluded,
• whether management’s assessment agrees with or differs from counsel’s view,
• whether a loss is estimable as one amount or a range,
• whether unrecorded loss above an accrual remains reasonably possible,
• whether insurance changes recovery accounting but not the underlying liability,
• and what changed after period end.

“Counsel says reasonably possible” is evidence.

It is not the complete accounting memo.

What Is Current in ASC 450 in 2026?

Deloitte’s current comprehensive Contingencies, Loss Recoveries, and Guarantees Roadmap is dated April 2025 and remains its current ASC 450/ASC 460 roadmap in 2026. Deloitte notes that the underlying ASC 450 guidance has remained substantially unchanged for decades, while questions continue because the standard requires significant judgment in scope, probability, estimation, recoveries, and disclosure.

KPMG’s current Contingencies, Commitments and Guarantees Handbook is dated September 2025 and is effective immediately. KPMG emphasizes that ASC 450 is a residual standard used when no more specific accounting guidance applies, and that probability assessments and estimation methodologies are central to the model.

Chart: Where ASC 450 Judgment Concentrates

SkillAbility training heat map—not a FASB ranking. Actual risk depends on matter type, legal posture, historical experience, claim volume, insurance terms, settlement dynamics, reporting entity status, and the specialized accounting Topics that may supersede ASC 450.

The CONTINGENCY READY Framework

C — Scope ASC 450 Before Applying Probability Words

ASC 450 is not the universal home for every uncertain amount.

It is often a residual standard.

That means staff should first ask whether another Topic contains more specific guidance.

That is why a strong contingency workpaper begins with:

Only after staff answer that question should they begin the probability analysis.

For related training, see Income Tax Provision Training for Staff Accountants, CECL Training for Accountants, and Business Combination Accounting Training for Staff Accountants.

T + I — Loss Contingencies: The ASC 450 Recognition Decision

A loss contingency is not recognized merely because a future payment is possible.

The accounting asks whether a loss has already been incurred as of the financial statement date and whether the amount is reasonably estimable.

Recognition gate

Both conditions matter

A loss may be probable but not reasonably estimable.

In that case, an accrual may not be possible, but disclosure can still be required.

A loss may also be reasonably estimable but only reasonably possible.

In that case, disclosure may be required without accrual.

The obligation has to exist as of the balance-sheet date

Staff should distinguish:

• a past event creating a present uncertainty,
• from a future event that would create the obligation only if it happens.

Examples of future events that generally do not create a present liability merely because management expects them to occur include:

• a future casualty,
• future enactment of proposed legislation,
• a future IPO,
• a future business combination.

What Do “Probable,” “Reasonably Possible,” and “Remote” Mean?

ASC 450 uses three probability categories:

Do not invent a “70% rule”

ASC 450 does not define “probable” using a numerical percentage.

A firm’s internal workflow can use structured probability bands to organize thinking, but staff should not present an internally invented percentage as though it came from the FASB.

Probability should be evidence-based

Relevant evidence can include:

• external or in-house counsel assessment,
• court rulings,
• claims history,
• settlement history,
• statutory or contractual language,
• available defenses,
• status of investigation,
• number and nature of claimants,
• similar prior cases,
• management’s planned response.

Probability is not static

A matter can move from:

—or move in the opposite direction as facts change.

The staff accountant’s job is to document what changed the conclusion.

I + N — Reasonably Estimable Losses and Range Measurement

Probability answers whether a loss should be recognized.

Estimability answers how much.

One best estimate

If one amount is the best estimate of the loss, accrue that amount when the recognition criteria are met.

Range of loss

If the loss is reasonably estimated as a range:

If no amount within the range is a better estimate than another:

That minimum is not an assertion that the final settlement will equal the minimum.

It is the required measurement when the entire range is supportable but no point is better than the others.

“Not reasonably estimable” should not become a convenience answer

Staff should ask:

• Can counsel estimate a range?
• Can management identify minimum exposure?
• Are similar historical settlements available?
• Is the uncertainty about liability or merely precision?
• Can components of the matter be estimated separately?
• Has the range narrowed since the prior period?

A range does not have to be precise to be useful.

Loss in excess of the accrual

Suppose the entity accrues $2 million because that is the best estimate.

If an additional loss of up to $5 million is reasonably possible, the disclosure analysis does not stop at the $2 million accrual.

The company should consider disclosure of reasonably possible additional exposure.

Worked Example 1: Litigation Range and Excess Exposure

A company is defending a contract claim arising from a transaction that occurred before year-end.

Outside counsel concludes:

• An unfavorable outcome is probable.
• Estimated loss range is $1.5M–$4.0M.
• $2.25M is a better estimate than any other amount in the range.

Now change one fact.

Counsel still concludes the loss range is $1.5M–$4.0M, but no point within the range is a better estimate.

The company should then evaluate whether the possible additional loss above $1.5M is at least reasonably possible and requires disclosure.

Review-ready evidence

• Matter chronology
• Counsel correspondence
• Probability conclusion
• Range support
• Reason for selected accrual
• Possible exposure above accrual
• Disclosure draft
• Subsequent-event update through issuance

G — Unasserted Claims Require Two Probability Questions

An entity can have a loss contingency even before a formal claim is filed.

Examples:

• known regulatory investigation,
• product defect likely to generate claims,
• known data incident before customers sue,
• environmental event before an agency assessment,
• conduct expected to prompt litigation.

Unasserted-claim analysis

Staff should identify:

1. Did a past event occur that could create a claim?
2. Is it probable that a claim will be asserted?
3. If asserted, is an unfavorable outcome probable?
4. Can the loss be reasonably estimated?

If assertion and unfavorable outcome are sufficiently probable and the loss is reasonably estimable, accrual can be required even though no complaint has been filed.

If a loss has been incurred and is at least reasonably possible, disclosure can also be required even when accrual is not appropriate.

Example

Management discovers before year-end that a product shipped during the year contains a defect.

No lawsuits have been filed.

Internal investigation indicates:

• the defect affected 5,000 units,
• customers have begun complaining,
• counsel expects formal claims,
• historical settlements provide a supportable range.

The absence of a filed complaint does not automatically mean “no contingency.”

Legal Counsel, Management Evidence, and Documentation

ASC 450 accounting often depends on legal interpretation.

Staff accountants should not try to become the lawyer.

They should become good translators between:

• legal facts,
• management’s assessment,
• accounting recognition,
• financial statement disclosure.

Questions for the contingency file

• What is the nature of the matter?
• When did the underlying event occur?
• What is the current procedural status?
• What relief or damages are claimed?
• What defenses exist?
• Has counsel expressed a probability conclusion?
• Can counsel estimate one amount or a range?
• Has a settlement offer been made?
• Is management’s accounting conclusion consistent with counsel’s facts?
• What changed since last quarter?

Avoid wording games

A lawyer may use language that does not map perfectly to ASC 450 terminology.

Examples:

• “We cannot rule out an adverse result.”
• “Settlement is likely to be economically preferable.”
• “The claim has meaningful risk.”
• “We believe the company has strong defenses.”

The accountant may need clarification rather than forcing one phrase into a probability category.

Y — Loss-Contingency Disclosure Is Part of the Accounting Conclusion

Disclosure is not the consolation prize when an accrual is not recorded.

It is a separate recognition-and-transparency requirement.

Common disclosure situations

• A loss is reasonably possible but not probable.
• A probable loss cannot be reasonably estimated.
• An accrual has been recorded, but additional loss above the accrual is reasonably possible.
• A recognized contingency requires additional description to prevent the financial statements from being misleading.

Typical disclosure content

Depending on facts, disclosures can include:

• nature of the contingency,
• status of the matter,
• amount accrued when disclosure is needed for context,
• estimate of possible loss or range of loss,
• estimate of reasonably possible loss above accrual,
• statement that an estimate cannot be made when that conclusion is supportable.

“Cannot estimate” needs evidence

If management says it cannot estimate the reasonably possible loss, staff should document why.

Possible reasons may include:

• early procedural stage,
• unknown number of claimants,
• unresolved legal theory,
• uncertain damages methodology,
• insufficient settlement history,
• material facts still under investigation.

Then update the conclusion each period.

Disclosure should evolve

A litigation footnote should not remain identical for eight quarters if:

• a motion was denied,
• class certification occurred,
• settlement talks began,
• damages estimates changed,
• counsel’s probability assessment changed.

E — Insurance and Other Loss Recoveries Are Separate From the Underlying Liability

Insurance can reduce the economic cost of a loss.

It generally does not eliminate the accounting obligation to the claimant when the reporting entity remains the primary obligor.

Gross accounting mindset

For litigation:

Then separately:

Probable recovery up to the recognized loss

A probable recovery of a previously recognized financial statement loss can generally be recognized as an asset up to the amount of that recognized loss, subject to the applicable recovery model and evidence.

Recovery above the recognized loss

Expected proceeds above the recognized loss are not simply “more recovery.”

The excess can be a gain contingency.

Example

A fire destroys equipment with a recognized financial statement loss of $800,000.

Management expects insurance proceeds of $1.1M.

If recovery is probable and sufficiently supported:

• up to $800,000 can be evaluated under the loss-recovery model,
• the additional $300,000 represents a potential gain and follows the gain-contingency model.

That $300,000 generally has a higher recognition threshold.

Contested insurance claims

If the insurer disputes coverage, staff should not assume recovery is probable simply because the policy exists.

Evidence can include:

• written carrier acknowledgment,
• coverage confirmation,
• legal opinion on enforceability,
• history of similar claim payments,
• absence or resolution of coverage disputes.

N — Gain Contingencies: Do Not Recognize Income Before Realization

Gain contingencies are intentionally asymmetric with loss contingencies.

ASC 450 generally does not permit recognition of a gain merely because management believes realization is probable.

Core principle

Substantially all uncertainties generally need to be resolved and the gain realized or realizable.

Examples

• Plaintiff litigation award under appeal
• Insurance proceeds exceeding a previously recognized loss
• Government reimbursement subject to unresolved eligibility
• Settlement receivable before an enforceable agreement exists
• Recovery dependent on future performance requirements

When can the gain become recognizable?

Examples of stronger realization evidence can include:

• executed settlement agreement creating an enforceable claim to cash,
• insurer confirmation that all contingencies are resolved and payment is due,
• cash received with no refund/clawback condition,
• another claim to cash that is no longer contingent.

Gain contingency disclosure

Gain contingencies can require or merit disclosure.

But wording should avoid implying that realization is more certain than it actually is.

Useful disclosure can describe:

• nature of potential gain,
• remaining uncertainties,
• relevant parties,
• timeline,
• amount or range if supportable.

C — Subsequent Events Can Change the Year-End Contingency Conclusion

The contingency file does not stop at the balance-sheet date.

Staff must evaluate relevant events through the date the financial statements are issued or available to be issued.

Recognized subsequent event

If post-balance-sheet information provides additional evidence about a condition that existed at the balance-sheet date, it can change the year-end accrual.

Example: litigation settlement

December 31:

• lawsuit arose from events before year-end,
• company accrued $2.0M.

February 10, before issuance:

• company settles for $3.1M.

If the settlement provides additional evidence about the year-end liability, the year-end estimate generally should reflect that evidence.

Nonrecognized subsequent event

If the event creating the loss occurs after the balance-sheet date, do not backdate the loss.

Examples:

• new lawsuit arising from January conduct,
• fire occurring in January,
• new law enacted after year-end that creates a new obligation.

Disclosure can still be required if omission would be misleading.

Gain contingencies remain asymmetric

A favorable litigation resolution after year-end generally does not become a recognized year-end gain simply because it occurs before issuance.

That is one of the reasons staff should not apply subsequent-event logic symmetrically to gains and losses.

Warranties, Guarantees, Environmental Matters, and Other Scope Traps

Several recurring balance-sheet items can look like ordinary ASC 450 matters but require additional guidance.

Product warranties

Assurance-type warranty obligations can involve ASC 450 estimation, but the related revenue arrangement and service-type warranties can also intersect with ASC 606.

Staff should identify:

• what the warranty promises,
• whether it provides a service beyond assurance,
• historical claim frequency,
• severity,
• product changes,
• recall activity.

Guarantees

ASC 460 can require initial recognition and disclosures for certain guarantees even when the probability of payment is remote.

Do not default every guarantee to ordinary ASC 450 loss-contingency logic.

Environmental matters

Environmental obligations can fall under ASC 410 and related guidance.

ASC 450 concepts can still matter in certain areas, but staff should first identify whether specialized environmental or asset-retirement guidance applies.

Income tax matters

Uncertain tax positions are governed by ASC 740—not ASC 450.

For staff development, pair this topic with Income Tax Provision Training for Staff Accountants.

Credit losses

Expected nonpayment of receivables or other in-scope credit assets follows ASC 326.

Pair this topic with CECL Training for Accountants.

Business combinations

Contingencies acquired in a business combination have special ASC 805 recognition and measurement considerations.

Pair this topic with Business Combination Accounting Training for Staff Accountants.

Worked Example 2: Litigation, Insurance Recovery, and Possible Gain

Assume a company faces litigation arising from a pre-year-end event.

Underlying loss

Counsel concludes:

• Unfavorable outcome is probable.
• Best estimate of loss is $3.0M.
• Reasonably possible total loss extends to $4.5M.

The company should also evaluate disclosure of up to $1.5M of reasonably possible additional loss.

Insurance

The company’s insurer confirms:

• the claim is covered,
• $2.4M reimbursement is payable under the policy,
• the carrier does not contest the claim.

If recovery is probable:

Do not net the underlying $3.0M liability to $600,000 merely because insurance is expected.

Now add a possible extra recovery

The policy may reimburse another $800,000 depending on a disputed coverage interpretation.

That additional amount is not automatically recognized.

To the extent expected proceeds would exceed a previously recognized loss or otherwise represent a gain, the higher gain-contingency recognition threshold applies.

What the reviewer should see

A Quarter-End Contingency Close Workflow

Build one controlled contingency register

Suggested fields:

• Matter ID
• matter name
• matter type
• underlying event date
• asserted / unasserted
• legal counsel
• procedural status
• applicable accounting Topic
• probability assessment
• best estimate / range
• amount accrued
• reasonably possible excess exposure
• insurance / recovery status
• gain-contingency component
• disclosure required?
• subsequent events
• last updated
• reviewer

That single register should drive both accounting and disclosure support.

ASC 450 Self-Review Checklist Before Manager Review

• Did I identify the accounting Topic that governs each matter?
• Did I avoid applying ASC 450 to income-tax uncertainty governed by ASC 740?
• Did I avoid applying ASC 450 to credit losses governed by ASC 326?
• Did I identify acquired contingencies that require ASC 805 analysis?
• Did I identify guarantees that may require ASC 460?
• Did I identify customer refunds/variable consideration that may belong in ASC 606?
• Did I identify environmental/ARO matters subject to ASC 410?
• Did I identify the underlying past event or existing condition?
• Did I confirm the event existed by the financial statement date?
• Did I distinguish a present contingency from a future event that would create an obligation only if it occurs?
• Did I define the unit of account / matter consistently?
• Did I identify whether claims should be evaluated individually or as a population?
• Did I identify asserted claims?
• Did I identify unasserted claims and investigations?
• Did I obtain current management status for each material matter?
• Did I obtain or reconcile current legal-counsel information?
• Did I identify differences between management’s assessment and counsel’s facts?
• Did I evaluate whether additional clarification from counsel is required?
• Did I classify loss likelihood as probable, reasonably possible, or remote?
• Did I avoid inventing a FASB percentage threshold for “probable”?
• Did I support the probability conclusion with actual evidence?
• Did I compare the probability conclusion with prior periods?
• Did I explain what changed from the prior period?
• Did I determine whether an unfavorable outcome is probable as of the balance-sheet date?
• Did I determine whether the amount of loss is reasonably estimable?
• If one amount is the best estimate, did I accrue that amount?
• If a range exists, did I determine whether one amount is a better estimate than another?
• If no amount is better, did I accrue the minimum amount in the range?
• Did I avoid using the midpoint of a range without support?
• Did I support the high and low ends of the range?
• Did I challenge “cannot reasonably estimate” conclusions?
• Did I document why a range cannot currently be estimated when applicable?
• Did I reassess whether estimation became possible as the matter progressed?
• Did I evaluate reasonably possible loss above an amount already accrued?
• Did I quantify the excess exposure when reasonably estimable?
• Did I prepare disclosure when loss is reasonably possible?
• Did I prepare disclosure when a probable loss cannot be reasonably estimated?
• Did I evaluate whether disclosure is needed for a recognized accrual to avoid misleading statements?
• Did I update disclosure language for current procedural developments?
• Did I avoid copying stale legal boilerplate from prior periods?
• Did I disclose the nature of the contingency?
• Did I disclose an estimate or range of possible loss when required and estimable?
• If no estimate can be made, did I support that statement?
• Did I identify unasserted claims arising from known past events?
• Did I evaluate whether assertion of an unasserted claim is probable?
• Did I evaluate whether an unfavorable outcome would be probable if asserted?
• Did I estimate the unasserted-claim loss where appropriate?
• Did I consider disclosure for unasserted matters that are at least reasonably possible?
• Did I identify insurance policies or indemnifications related to each loss?
• Did I account for the underlying liability independently from insurance recovery?
• Did I avoid netting an insurer’s expected payment against the primary obligation without appropriate basis?
• Did I assess whether realization of the loss recovery is probable?
• Did I obtain carrier confirmation where available?
• Did I identify disputed coverage or reimbursement terms?
• Did I identify whether legal advice is needed on policy enforceability?
• Did I limit recognized loss-recovery assets to the applicable previously recognized loss?
• Did I identify proceeds in excess of recognized loss as a potential gain contingency?
• Did I avoid recognizing a gain merely because realization is probable?
• Did I determine whether substantially all gain uncertainty has been resolved?
• Did I identify an executed settlement agreement or enforceable claim to cash where applicable?
• Did I identify clawback or refund conditions that prevent realization?
• Did I prepare gain-contingency disclosure without overstating likelihood or amount?
• Did I identify claims contingent on future performance?
• Did I avoid recognizing such gains before the remaining contingency is resolved?
• Did I identify settlements occurring after the balance-sheet date but before issuance?
• Did I determine whether those settlements provide evidence about conditions existing at year-end?
• Did I adjust year-end losses for recognized subsequent events where appropriate?
• Did I identify new post-year-end events that should not be backdated?
• Did I consider disclosure for material nonrecognized subsequent events?
• Did I avoid recognizing a favorable gain contingency as a year-end gain solely because it resolved before issuance?
• Did I reconcile beginning contingency accruals to prior-period financial statements?
• Did I reconcile additions to expense?
• Did I reconcile settlements and payments?
• Did I reconcile reversals or estimate changes?
• Did ending accruals tie to the balance sheet?
• Did recognized loss-recovery assets tie to the balance sheet?
• Did contingency expense tie to the income statement?
• Did I consider presentation classification of settlement or recovery amounts?
• Did the disclosure population match the legal/claims register?
• Did I identify matters omitted from the disclosure population and document why?
• Did I identify product warranty obligations and the applicable accounting guidance?
• Did I identify guarantees and required ASC 460 recognition/disclosure?
• Did I identify commitments that may require ASC 440 or other disclosure?
• Did I identify environmental obligations subject to specialized guidance?
• Did I distinguish business interruption proceeds from property-loss recovery where relevant?
• Did I track changes in probability and estimate through the issuance date?
• Did I document material judgments in language a reviewer can follow?
• Can another accountant reconstruct the matter chronology from the file?
• Can another accountant explain why the matter is accrued, disclosed, both, or neither?
• Can another accountant explain separately the loss, recovery, gain, and subsequent-event conclusions?

100-Point ASC 450 Readiness Scorecard

Suggested readiness bands

• 90–100: Ready to own defined recurring contingency workstreams with normal manager/legal/technical review.
• 82–89: Generally review-ready; targeted coaching remains in estimation, unasserted claims, or recovery/gain distinctions.
• 72–81: Controlled ownership with manager checkpoints before recognition and disclosure conclusions are finalized.
• Below 72: Continue structured ASC 450 practice.

Override the numerical score for concealed legal matters, unsupported probability changes, intentional delay of accrual, manipulated loss ranges, premature gain recognition, improper netting of insurance, or disclosure designed to obscure material exposure.

A 30/60/90-Day Contingency Accounting Training Plan

Days 1–30: Train the decision tree

Give staff scenarios with:

• probable + estimable loss,
• probable + not estimable,
• reasonably possible loss,
• remote loss,
• one best estimate,
• a range with no best estimate.

Days 31–60: Add legal and insurance facts

Require staff to:

• reconcile counsel language to accounting terminology,
• identify unasserted claims,
• separate liability from insurance recovery,
• quantify possible loss above the accrual,
• draft disclosure.

Days 61–90: Cross the boundaries

Add matters that initially look like ASC 450 but belong in:

• ASC 740,
• ASC 326,
• ASC 460,
• ASC 805,
• ASC 606.

Use Scenario-Based Training for Accountants so staff practice deciding when they should stop and escalate rather than force every uncertainty into ASC 450.

15 Realistic ASC 450 Training Scenarios

1. Counsel says “possible,” management says “probable”

Staff identifies the factual disagreement, obtains clarification, and documents why the accounting conclusion follows the available evidence.

2. Range of $2M–$8M with no best point

Staff accrues $2M—not the midpoint—and evaluates reasonably possible additional exposure.

3. Range of $2M–$8M with $5M as the best estimate

Staff accrues $5M.

4. Probable but no reasonable estimate

No arbitrary accrual is invented. Staff prepares robust disclosure and documents why estimation is not currently possible.

5. Reasonably possible lawsuit with no accrual

Staff prepares the required disclosure instead of concluding “no entry means no work.”

6. Unasserted product claim

A known defect and customer complaints make future claims likely. Staff evaluates assertion, unfavorable outcome, estimation, and disclosure.

7. Insurance policy exists but carrier denies coverage

Staff does not recognize a recovery asset merely because the policy exists.

8. Insurance recovery exceeds the recognized loss

Staff separates the loss-recovery portion from the potential gain portion.

9. Plaintiff wins a court judgment but defendant appeals

Staff evaluates whether an unfavorable outcome is probable and what the judgment means for accrual/range—not simply assume appeal eliminates recognition.

10. Company wins a lawsuit before issuance

Staff does not automatically recognize the gain at prior year-end merely because resolution occurred before issuance.

11. Settlement after year-end confirms prior condition

Staff updates the year-end loss estimate when the settlement is recognized subsequent-event evidence about a preexisting liability.

12. New casualty occurs after year-end

Staff does not accrue it at year-end but considers subsequent-event disclosure.

13. Uncertain tax position put on the litigation register

Staff routes it to ASC 740 rather than ASC 450.

14. Customer refund reserve treated as litigation contingency

Staff evaluates ASC 606 refund/variable-consideration guidance first.

15. Guarantee assessed as remote, so no disclosure is drafted

Staff recognizes that ASC 460 can require disclosures even when payment likelihood is remote.

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 Contingency Accounting Training Mistakes

Mistake 1: Apply ASC 450 to every uncertain amount

Staff use probability labels before determining whether a more specific Topic controls.

Mistake 2: Convert probability words into fake percentages

Internal conventions are presented as though they are FASB thresholds.

Mistake 3: Use the midpoint of every range

The ASC 450 best-estimate/minimum rule is ignored.

Mistake 4: Treat “not estimable” as permanent

The matter develops, but estimation conclusions are never refreshed.

Mistake 5: Ignore unasserted claims

No formal lawsuit exists, so a known pre-year-end exposure disappears from the register.

Mistake 6: Net insurance against the liability

The company’s obligation to the claimant and its recovery from the insurer are collapsed into one number.

Mistake 7: Recognize a gain because it is probable

Loss-contingency probability logic is applied symmetrically to gains.

Mistake 8: Copy last quarter’s disclosure

Material legal developments occur but the footnote never changes.

Mistake 9: Stop monitoring at year-end

A settlement or ruling before issuance is missed.

Mistake 10: Let the legal letter replace the accounting workpaper

Counsel’s evidence is not connected to recognition, measurement, disclosure, recovery, and subsequent events.

How SkillAbility Builds Contingency Accounting Capability

BASE — Loss-contingency execution

• Scope
• past events
• probability categories
• reasonable estimation
• range measurement
• basic disclosure

MAPS — Evidence and cross-functional judgment

• Legal-counsel integration
• unasserted claims
• excess exposure
• insurance recoveries
• gain contingencies
• subsequent events

SUMMIT — Reviewer and governance readiness

• Challenge probability changes
• challenge range methodology
• review complex recovery arrangements
• coordinate legal, insurance, tax, and technical accounting
• review guarantees and commitments
• review disclosures
• coach staff without rewriting every matter memo

Frequently Asked Questions About Contingency Accounting Training

What is ASC 450?

ASC 450 is the U.S. GAAP Topic covering contingencies, including general guidance for loss contingencies and gain contingencies when another Topic does not provide more specific accounting.

When is a loss contingency accrued?

A loss contingency is accrued when it is probable that a loss has been incurred as of the financial statement date and the amount of the loss can be reasonably estimated.

What does probable mean under ASC 450?

Probable means the future event or events are likely to occur. ASC 450 does not prescribe a numerical percentage threshold for “probable.”

What does reasonably possible mean?

Reasonably possible means the chance of occurrence is more than remote but less than likely. A reasonably possible loss generally is disclosed rather than accrued solely on that basis.

What does remote mean?

Remote means the chance of occurrence is slight. Specific ASC 450 loss-contingency disclosure generally is not required for remote matters, though misleading omission still should be considered.

What happens when a loss is probable but cannot be reasonably estimated?

An accrual generally cannot be measured, but disclosure can be required. The company should explain the contingency and, where relevant, why an estimate cannot currently be made.

How is a loss range measured under ASC 450?

If one amount in the range is a better estimate than another, that amount is accrued. If no amount is a better estimate, the minimum amount in the range is accrued.

Does ASC 450 require the midpoint of a loss range?

No. Under U.S. GAAP, the midpoint is not the default. The best estimate is used, or the minimum of the range when no amount is better than another.

What is an unasserted claim?

An unasserted claim is a potential claim or assessment that has not yet been formally asserted. A known past event can still require accrual or disclosure when claim assertion and an unfavorable outcome meet the applicable probability and estimation thresholds.

Can insurance be netted against a litigation liability?

Generally, the underlying loss contingency is evaluated independently from the insurance recovery because the entity typically remains the primary obligor to the claimant.

When can an insurance recovery be recognized?

A recovery related to a previously recognized loss can generally be recognized when realization is probable, subject to the specific recovery model and evidence. Amounts above the recognized loss can be gain contingencies.

Can a probable gain contingency be recognized?

Usually not. Gain contingencies generally are not recognized merely because realization is probable; substantially all uncertainty generally must be resolved and the gain realized or realizable.

When is a litigation settlement after year-end recognized?

If the litigation arose from events that existed before the balance-sheet date and the settlement before issuance provides additional evidence about the year-end liability, it can require adjustment of the year-end estimate.

Is a favorable court decision after year-end recognized as a year-end gain?

Usually not merely because it occurs before issuance. Gain contingencies are rarely recognized as subsequent events because premature gain recognition is specifically constrained.

What should a loss-contingency disclosure include?

Depending on facts, disclosure can include the nature of the matter, an estimate or range of possible loss, possible loss above an accrual, or a statement that an estimate cannot be made when supportable.

Does ASC 450 apply to uncertain tax positions?

No. Uncertain income-tax positions are governed by ASC 740.

Does ASC 450 apply to credit losses on receivables?

Financial assets within ASC 326 use the applicable credit-loss model rather than the general ASC 450 loss-contingency model.

Does ASC 450 apply to guarantees?

Some guarantees are subject to ASC 460, which can impose initial recognition and disclosure requirements that differ from ordinary ASC 450 contingency accounting.

How often should contingencies be reassessed?

Material contingencies should be refreshed each reporting period and monitored through the financial-statement issuance date for relevant subsequent events.

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

A review-ready staff accountant can scope the matter, identify the past event, support probability and estimation, measure ranges correctly, identify unasserted and excess exposure, separate insurance recovery from gains, evaluate subsequent events, and reconcile the register, GL, and disclosures.

Current Research and Authority Resources

• Deloitte — Contingencies, Loss Recoveries, and Guarantees Roadmap, April 2025
• Deloitte — On the Radar: Contingencies, Loss Recoveries, and Guarantees
• KPMG — Contingencies, Commitments and Guarantees Handbook, September 2025
• Google Search Central — Optimizing for Generative AI Features

ASC 450 can intersect with ASC 460 guarantees, ASC 440 commitments, ASC 740 income taxes, ASC 326 credit losses, ASC 805 business combinations, ASC 606 revenue/refund obligations, ASC 410 environmental and asset-retirement obligations, ASC 855 subsequent events, insurance and industry-specific guidance. Verify current authoritative literature and transaction-specific facts for live work.

The Bottom Line

Contingency accounting training should not produce staff who know three probability labels.

It should produce accountants who can defend the evidence chain behind recognition and disclosure.

Scope the uncertainty before applying ASC 450.

Identify the past event and existing condition.

Support probable, reasonably possible, or remote with evidence.

Separate probability from estimability.

Use the best estimate—or the minimum of the range when no amount is better.

Do not ignore unasserted claims.

Disclose reasonably possible exposure above an accrual.

Evaluate insurance recovery separately from the underlying loss.

Do not recognize contingent gains merely because they are probable.

Monitor settlements and other events through issuance.

Keep the legal register, GL, recovery schedules, and disclosures synchronized.

That is CONTINGENCY READY.

Protect Knowledge. Develop People. Scale the Firm.

To staff who can explain the uncertainty before review has to reconstruct it,

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, insurance, regulatory, SEC, litigation, or other professional advice.