FASB 5: Accounting for Contingencies Under ASC 450

FASB Statement No. 5, now codified as ASC Topic 450, tells companies how to account for contingent gains and losses — uncertain future events tied to something that has already happened. The core rule is a two-part test: a loss is recorded as a liability only when it is both probable and reasonably estimable. Everything else is either disclosed in the footnotes or left out entirely, depending on how likely the loss is. Gains get the opposite treatment and generally aren’t recognized until they’re realized.¹

What ASC 450 Covers

A contingency under ASC 450 is an existing condition involving uncertainty about a possible gain or loss, where the uncertainty will be resolved by some future event. The word “existing” does the work. The event creating the uncertainty must have already occurred by the balance sheet date. A company cannot accrue a loss for something that might happen later with no link to a past transaction or current condition.¹

A pending lawsuit is the textbook case. The company sold a product (past event), a customer was injured (existing condition), and the outcome of the litigation is unknown (future event that resolves it). The contingency exists now even though the verdict hasn’t landed.

The Two-Part Recognition Test

A loss contingency becomes an actual liability on the balance sheet only when both of these conditions are met:

It is probable that an asset has been impaired or a liability has been incurred as of the balance sheet date.
The amount of the loss can be reasonably estimated.²

Both. A loss that is probable but impossible to estimate stays off the balance sheet. A loss pegged at $5 million with only a reasonably possible likelihood also stays off. In either case the answer is disclosure, not accrual.

“Reasonably estimable” does not demand a single precise number. A range of outcomes is enough, which triggers a specific measurement rule covered below.

The Three Probability Buckets

ASC 450 sorts loss contingencies into three likelihood categories, and the treatment hinges on which one applies.

Probable: The future event confirming the loss is likely to occur. In practice most auditors and preparers treat this as roughly a 70 percent or higher likelihood, though the codification deliberately avoids assigning a specific percentage.¹
Reasonably possible: The chance is more than remote but less than likely. This is where contested items usually land.
Remote: The chance is slight.

That informal 70 percent threshold matters more than it looks. A company can face a lawsuit where management believes there’s a 60 percent chance of losing and still not be required to accrue the loss. Critics have long argued the bar is set too high, and the gap becomes sharpest in cross-border comparisons, which the IFRS section at the end addresses.

Measuring a Loss Within a Range

When a loss is probable and the company can only identify a range of possible amounts, ASC 450-20-30-1 sets the measurement rule. If one amount within the range is a better estimate than any other, that amount is accrued.³

If no single amount stands out, the company accrues the minimum of the range and discloses in the footnotes that the actual loss could exceed the recorded amount.² The conservatism built into U.S. GAAP shows up clearly here: the minimum-accrual rule means the balance sheet often understates the expected loss, and anyone reading only the liability line without the footnotes can miss the full exposure.

What Goes in the Footnotes

When a contingency doesn’t clear both recognition hurdles, the footnotes carry the information. The requirements split by probability level.

Probable but Not Estimable

If a loss is probable but the amount cannot be reasonably estimated, no liability appears on the balance sheet. The company must disclose the nature of the contingency and explain why it cannot estimate the loss. Even when a loss has been accrued, additional disclosure of the nature and amount may still be needed to keep the financial statements from being misleading.⁴

Reasonably Possible

This is the most common disclosure scenario. The footnotes must describe the nature of the contingency and include an estimate of the possible loss or range of loss. If an estimate cannot be made, the company must say so explicitly. Nothing is accrued, but the reader should walk away understanding the risk.⁴

Remote

Remote contingencies generally require no disclosure. The exception is certain guarantees under ASC 460, which require disclosure of their nature and the maximum potential future payments regardless of how unlikely a payout seems.⁵

How the Rules Apply in Practice

Litigation and Claims

Lawsuits generate the most judgment calls. The analysis starts with timing: the event giving rise to the claim must have occurred before the balance sheet date. A product liability suit filed in January over a product sold in November creates a contingency that existed at year-end, even if the complaint wasn’t served until after the books closed.

If the loss is probable and estimable, the company records a liability, often relying on legal counsel’s assessment. If it is reasonably possible, the company discloses. Most litigation disclosures land in that middle bucket, because few lawyers will tell their client a loss is probable while the case is still being contested. Companies frequently disclose that a loss is reasonably possible while adding that no reasonable estimate can be made, which gives investors very little to work with.

Product Warranties

Warranties are one of the few contingency types that almost always satisfy both recognition criteria from the start. The sale itself is the past event. The loss is probable because historical data shows that some fraction of products will need repair or replacement. The amount is estimable from past claim rates and average repair costs. The company accrues a warranty liability at the time of each sale, matching the estimated cost against the revenue just recorded.⁶

Uninsured Risks

The mere existence of an uninsured risk, such as fire, earthquake, or flood, does not create a contingency that can be recorded. Before the event happens, no liability has been incurred and no asset has been impaired. A company cannot accrue a loss for a hypothetical fire just because it dropped its insurance policy. Recognition comes only after the event occurs.

Environmental Remediation

Environmental cleanup is one of the most complex applications, and ASC 410-30 layers specific guidance on top of the general contingency rules. The probability test has two elements: a claim or assessment has been asserted (or is likely to be asserted) that the company is responsible for remediation because of a past event, and it is probable the outcome will be unfavorable. The standard creates a strong presumption of an unfavorable outcome whenever a company is associated with a contaminated site, meaning it arranged for disposal of hazardous substances there, transported hazardous materials to the site, or is a current or former owner or operator.⁷

In practice, the probability threshold is generally considered met once a company receives a notice letter from the EPA identifying it as a potentially responsible party. A company doesn’t have to wait for the EPA, though. Internal environmental studies or other information revealing contamination tied to operations can be enough to trigger recognition on their own.⁷ Environmental liabilities are measured independently from any potential recovery, so the full liability is recorded first and any insurance or cost-sharing claim is evaluated separately.

Gain Contingencies Work Differently

The rules for potential gains are deliberately lopsided. Under ASC 450-30, a gain contingency should usually not be recognized before the gain is realized, even if the gain is considered probable.⁸ The reasoning is straightforward conservatism: recording income before it materializes risks misleading investors.

The standard says gain contingencies “usually should not” be recognized, not that they are absolutely prohibited. In rare cases a gain may be recognized when it becomes realizable, meaning substantially all uncertainties about it have been resolved. In practice this almost never happens before the gain is fully settled, which is why most accountants treat the rule as a near-total ban.⁹

Footnote disclosure of a gain contingency is allowed, but the language has to be managed to avoid implying the gain is a sure thing. A company waiting on a favorable patent ruling, for instance, might disclose the existence of the case without suggesting it expects to collect.

Insurance Recoveries and Other Reimbursements

When a company records a loss contingency and expects to recover some or all of it from an insurance carrier or third party, it cannot simply net the expected recovery against the liability. The liability and the recovery are evaluated independently.¹⁰

A company can record a receivable for an expected recovery, but only when collection is probable, and the receivable cannot exceed the total recognized losses. Any expected recovery above the actual losses or related costs is treated as a gain contingency and faces the higher recognition bar described above.¹⁰

If the recovery claim is itself the subject of litigation, such as an insurer denying coverage, there is a rebuttable presumption that recovery is not probable. Strong evidence is required to overcome that presumption and book the receivable. SEC staff has also taken the position that when a party is actively contesting its indemnification obligation, registrants should presumptively not record a recovery asset; those that do must disclose the contested amount and explain their reasoning.

How IFRS Differs

Companies reporting under International Financial Reporting Standards follow IAS 37 instead of ASC 450, and two differences stand out. The probability threshold is lower under IFRS. “Probable” there means more likely than not, essentially anything above 50 percent, compared with the roughly 70 percent threshold applied under U.S. GAAP.¹¹ That 20-point gap means IFRS financial statements will recognize some provisions as liabilities that U.S. GAAP companies only disclose in footnotes.

The measurement rule also differs. When a range of outcomes exists and no single amount is a better estimate, U.S. GAAP requires accruing the minimum of the range. IFRS requires the midpoint.¹¹ Combined with the lower recognition threshold, IFRS tends to produce larger and earlier contingency accruals, so the same underlying legal exposure can look quite different depending on which framework a company reports under.

1
Deloitte Accounting Research Tool. Contingencies, Loss Recoveries, and Guarantees – 2.3 Recognition
2
FASB. Contingencies Topic 450 – Disclosure of Certain Loss Contingencies
3
Deloitte Accounting Research Tool. Contingencies, Loss Recoveries, and Guarantees
4
Deloitte Accounting Research Tool. Contingencies, Loss Recoveries, and Guarantees – 2.8 Disclosures
5
Deloitte Accounting Research Tool. Contingencies, Loss Recoveries, and Guarantees – 5.5 Disclosure Requirements
6
Deloitte Accounting Research Tool. Contingencies, Loss Recoveries, and Guarantees – 5.3 Initial Recognition and Measurement Provisions of ASC 460
7
Deloitte Accounting Research Tool. Recognition of Environmental Remediation Liabilities
8
Deloitte Accounting Research Tool. Contingencies, Loss Recoveries, and Guarantees – 3.1 Overview
9
Deloitte Accounting Research Tool. Contingencies, Loss Recoveries, and Guarantees – 3.3 Application of the Gain Contingency Model
10
Deloitte Accounting Research Tool. Contingencies, Loss Recoveries, and Guarantees – 4.3 Loss Recovery and Gain Contingency Models
11
Deloitte Accounting Research Tool. Differences Between U.S. GAAP and IFRS Accounting Standards