A lawsuit, damaged asset, or disputed claim does not produce an automatic journal entry. At the reporting date, you need to know what condition exists, how likely the loss is, and whether the company can estimate it. Those facts determine whether the company records a loss, discloses the uncertainty, or does neither under the general loss-contingency model.
Learn the loss-contingency model before using the decision tree
Read Use the loss-contingency matrix first. It separates the condition date, qualitative probability, reasonable estimation, recognition, and disclosure. Then read Measure ranges and control disclosure to connect a recognized amount with possible additional exposure.
The decision tree below is a review tool after those lessons. The Ridgeway material is a worked example. Independent practice appears after the complete explanation.
Confirm that ASC 450 applies
Do not send every estimate to ASC 450. First distinguish a loss contingency from a routine accrued liability, assurance warranty, commitment, guarantee, gain contingency, and a matter governed by more specific guidance.
A loss contingency involves an existing condition, situation, or set of circumstances that creates uncertainty about a possible loss. One or more future events will resolve that uncertainty. The reporting-date condition matters even when later evidence helps the company estimate it.
Separate a routine accrual
A known service already received can create an accrued liability even when the invoice has not arrived. Uncertainty alone does not make every estimate a loss contingency.
Identify a commitment
An executory purchase commitment can require disclosure or Topic-specific accounting without meeting the loss-contingency recognition test.
Route a warranty
An assurance warranty follows the applicable warranty guidance. A service warranty can instead be a performance obligation under ASC 606.
Check guarantees separately
ASC 460 can require recognition and disclosure for a guarantee even when the contingent payment appears remote. Do not use the general remote-loss shortcut first.
After you confirm that the loss-contingency guidance applies, keep recognition, measurement, and disclosure in order. A failed recognition condition does not end the analysis.
Answer four questions in order
Decide whether the loss meets both accrual conditions
Start after you identify an existing reporting-date condition within the loss-contingency guidance.
- Test likelihood at the reporting date
Does the available information indicate that a loss was probable at the reporting date?
Yes - Decide whether you can estimate the loss
Can the company reasonably estimate the amount of the loss?
Yes
Did the relevant condition exist at the reporting date?
Identify the event, claim, damage, obligation, or other condition and the period to which it relates. Do not begin with the settlement date.
Does the company recognize a loss?
ASC 450-20-25-2 requires accrual when available information indicates that a loss was probable at the reporting date and the company can reasonably estimate the amount.
What amount does the company accrue?
Under ASC 450-20-30-1, use the amount in the range that is a better estimate than the other amounts. If no amount is a better estimate, accrue the minimum amount in the range.
What does the company disclose?
ASC 450-20-50-3 requires disclosure when there is at least a reasonable possibility of a loss or an additional loss and the stated conditions apply. ASC 450-20-50-4 calls for the nature of the contingency and an estimate of the possible loss or range, or a statement that the company cannot make that estimate.
Match your assessment to the reporting outcome
| What you conclude at the reporting date | What the company records | What you must check for disclosure |
|---|---|---|
| Probable loss and reasonably estimable amount | Accrue the estimated loss. | Consider the nature of the contingency and any possible additional loss. |
| Accrual condition not met, but loss is at least reasonably possible | Do not accrue under the loss-contingency test. | Disclose the nature and estimate of possible loss or range, or state that the estimate cannot be made. |
| Loss is remote | Do not accrue under the general loss-contingency test. | The general loss-contingency disclosure is usually not required, but check specific exceptions and other applicable guidance. |
This table is a route into the analysis, not a substitute for the complete guidance. Review ASC 450-20-25-2, 30-1, and 50-1 through 50-8 with the facts and any Topic-specific requirements.
If the company must accrue the loss, the next question is how much to record. Do not create precision that the available evidence does not support.
Use the supported amount in the range
At December 31, Ridgeway Manufacturing concludes that a covered loss is probable. Its evidence supports a range of $240,000 to $400,000. No amount in the range is a better estimate than another.
Ridgeway accrues $240,000, the minimum amount in the range. The company then evaluates disclosure of the nature of the contingency and the possible additional exposure. It does not record the midpoint merely because the midpoint looks balanced.
Use the contingency range measurement page for the full boundary.
Worked example: Follow the checked Ridgeway product claim through recognition, measurement, entry, disclosure support, and later evidence.
Measurement can also depend on information received after year end. The date of the new evidence does not, by itself, decide which period it affects.
Use later evidence only for an existing condition
A settlement after year end can supply evidence about a condition that existed at the reporting date. A new event after year end does not create a prior-period liability merely because it occurs before the statements are issued. Ask what condition the later information describes and when that condition existed.
Losses require timely recognition when the conditions are met. Possible gains need a different boundary because early recognition could report income that the company never receives.
Do not recognize a possible gain too soon
A possible gain does not become income merely because management believes that collection is probable. Premature recognition can report income that the company never realizes. Keep the matter out of income until recognition is appropriate under the governing guidance, and use care when disclosure could imply that realization is assured.
Read gain contingency, then test the mistaken claim that a gain contingency mirrors a loss accrual.
A public filing can show how one company presents a recorded loss and possible additional exposure. It cannot reveal every private fact behind management's judgments.
Compare the recorded loss with possible additional exposure
Microsoft's 2025 Form 10-K reports $541 million of aggregate legal liabilities at June 30, 2025. Note 14 also reports that adverse outcomes beyond the recorded amounts could reach about $600 million in aggregate and were reasonably possible.
The filing shows why the recorded liability and possible additional loss belong in the same analysis. It does not give an outside reader enough private evidence to recreate management's probability assessments for each matter. Read Microsoft's complete 2025 Form 10-K and find Note 14 before drawing a conclusion from the two amounts.
Practice after you finish the contingency lessons
The Ridgeway worked case uses a January report that supplies evidence about a December condition. Start the independent attempt by changing the condition date itself. Then reconstruct the authority trail so another person can check your answer.
Optional practice
Decide what a January incident changes
Apply the reporting-date boundary when the loss-producing condition arises after year end.
Optional practice
Build the ASC 450 research trail
Connect the supplied facts to exact recognition, measurement, disclosure, and later-evidence paragraphs.
Optional practice
Classify the outcome
Apply likelihood, estimation, recognition, and disclosure to a new fact pattern.
Optional practice
Measure and disclose the range
Connect the recorded amount with remaining exposure and note disclosure.
Check your reasoning
Test whether no accrual means no disclosure
See why a failed recognition test does not end the disclosure analysis.
Check your reasoning
Test whether a lawsuit automatically means accrue
Identify the reporting-date evidence that the filing of a claim does not supply by itself.
Check your reasoning
Test whether no estimate means zero loss
Keep the recognition condition, measurement evidence, and disclosure requirement separate.
Check your reasoning
Test whether remote always means no disclosure
Check guarantees and other specific guidance before relying on the general loss-contingency result.
For a longer sequence, continue to Current liabilities, refinancing, and contingencies. Use the versioned ASC 450 contingencies source record to see the paragraph set reviewed for this material.
Carry the decision model into another Topic
You can now identify the reporting-date condition, test both accrual requirements, measure a supported amount, and complete the disclosure analysis. Return to Complete every accounting decision if you need to separate recognition from measurement or disclosure. Then continue to Turn a customer contract into reported revenue to apply the same discipline to a larger accounting model.