FASB Statement No. 5, now codified as ASC Topic 450, tells companies how to account for uncertain future events that could produce a gain or a loss. The core of the standard is a two-part test for losses: if a loss is both probable and reasonably estimable, record it as a liability on the balance sheet; if it is only reasonably possible, disclose it in the footnotes; if it is remote, generally do nothing. Gains work the other way. They usually stay off the books until they are realized, no matter how likely they look.
What Qualifies as a Contingency
Under ASC 450, a contingency is an existing condition involving uncertainty about a possible gain or loss that will be resolved by some future event. The word “existing” carries the weight. The event that created the uncertainty must already have happened by the balance sheet date. A hypothetical future problem with no connection to a past transaction is not a contingency and cannot be accrued.1Deloitte Accounting Research Tool. Contingencies, Loss Recoveries, and Guarantees – 2.3 Recognition
A pending lawsuit is the standard illustration. The company sold a product, a customer says they were injured, and litigation is underway. The past event and the current condition are both in place; only the outcome remains uncertain. That is a contingency. The mere possibility of an uninsured fire, by contrast, is not: no event has occurred, no asset has been impaired, and no liability has been incurred. Recognition waits until something actually happens.
The Three Probability Categories
ASC 450 sorts loss contingencies into three likelihood buckets, and the accounting treatment turns entirely on which one applies.
- Probable: the future event confirming the loss is likely to occur. The codification does not fix a percentage, but preparers and auditors typically treat probable as roughly 70 percent or higher.1Deloitte Accounting Research Tool. Contingencies, Loss Recoveries, and Guarantees – 2.3 Recognition
- Reasonably possible: more than remote, less than likely. This is the middle bucket where most contested items sit.
- Remote: the chance is slight.
That informal 70 percent threshold has real consequences. A company can face a lawsuit management believes it will lose 60 percent of the time and still keep the exposure off the balance sheet. Whether that reads as prudent or too permissive depends on your view, but the number is worth knowing because it shapes how U.S. financial statements look compared with those prepared under IFRS.
When a Loss Gets Recorded
A loss contingency becomes a liability on the balance sheet only when two conditions are both satisfied at the reporting date. First, it must be probable that an asset has been impaired or a liability incurred. Second, the amount of the loss must be reasonably estimable.2FASB. Contingencies Topic 450 – Disclosure of Certain Loss Contingencies
Both conditions have to be met at the same time. If a loss is probable but no one can put a reasonable number on it, no liability is recorded and the company discloses instead. If the amount is easy to pin down but the likelihood is only reasonably possible, again no accrual. “Reasonably estimable” does not mean pinpoint precision. A defensible range is enough, which sets up the measurement rule that follows.
Measuring the Loss When Only a Range Is Available
When a loss is probable and the company can identify a range of possible amounts, ASC 450-20-30-1 supplies the rule. If one amount inside the range is a better estimate than any other, that amount is accrued.3Deloitte Accounting Research Tool. Contingencies, Loss Recoveries, and Guarantees If no single point in the range stands out, the company accrues the minimum of the range and discloses in the footnotes that the actual loss could be higher.2FASB. Contingencies Topic 450 – Disclosure of Certain Loss Contingencies
The conservatism built into U.S. GAAP shows up plainly here. Accruing the low end of a range means the balance sheet often understates the expected outcome, and a reader who only looks at the liability line without checking the footnotes can miss the full exposure.
Disclosure Requirements by Probability Level
When a loss does not clear both hurdles for balance sheet recognition, the footnotes carry the load. What has to be said depends on where the contingency falls.
Probable but Not Estimable
No liability appears on the balance sheet. The company must disclose the nature of the contingency and explain why the amount cannot be estimated.1Deloitte Accounting Research Tool. Contingencies, Loss Recoveries, and Guarantees – 2.3 Recognition Even when a loss has been accrued, disclosure of its nature and amount may still be needed to keep the statements from being misleading.4Deloitte Accounting Research Tool. Contingencies, Loss Recoveries, and Guarantees – 2.8 Disclosures
Reasonably Possible
This is the most common disclosure scenario. The footnotes must describe the contingency and include an estimate of the possible loss or range of loss. If no estimate can be made, the company must say so explicitly. Nothing hits the balance sheet, but a reader should still finish the footnote understanding the risk.4Deloitte Accounting Research Tool. Contingencies, Loss Recoveries, and Guarantees – 2.8 Disclosures
Remote
Remote contingencies generally require no disclosure. One exception matters: certain guarantees that fall under ASC 460 require disclosure of their nature and the maximum potential future payments no matter how unlikely a payout looks.5Deloitte Accounting Research Tool. Contingencies, Loss Recoveries, and Guarantees – 5.5 Disclosure Requirements
How the Framework Plays Out in Practice
Litigation and Claims
Lawsuits generate more judgment calls than any other contingency category. The analysis begins with timing. The event giving rise to the claim must have occurred before the balance sheet date, though the complaint itself can be filed later. A product liability suit filed in January over a product sold in November creates a contingency that existed at year-end.
Where does the loss usually land? Most of the time, in the reasonably possible bucket. Few outside lawyers will label a live case “probable” for their own client while it is still being contested, and any written evaluation of potential liability carries its own risk of being treated by an opposing party as an admission. The typical result is a footnote saying a loss is reasonably possible but no reasonable estimate can be made, which gives investors little to work with.
Product Warranties
Warranties are one of the few contingencies that almost always meet both recognition criteria from day one. The past event is the sale, which creates the obligation. The loss is probable because history shows some fraction of products will need repair. The amount is estimable from past claim rates and average repair costs. The company records a warranty liability at the time of each sale, matching estimated warranty cost against the revenue it just recognized.6Deloitte Accounting Research Tool. Contingencies, Loss Recoveries, and Guarantees – 5.3 Initial Recognition and Measurement Provisions of ASC 460
Uninsured Risks
The existence of an uninsured risk does not create a contingency. Before a fire, earthquake, or flood actually occurs, no liability has been incurred and no asset has been impaired. A company that drops its insurance cannot accrue a loss for the possibility of a future disaster. Recognition waits until the event happens.
Gain Contingencies
The rules for potential gains are deliberately asymmetric. Under ASC 450-30, a gain contingency should usually not be recognized before the gain is realized, even when the gain looks probable.7Deloitte Accounting Research Tool. Contingencies, Loss Recoveries, and Guarantees – 3.1 Overview The reasoning is straightforward conservatism: booking income before it materializes risks misleading users of the financial statements.
The language is “usually should not,” not “may not.” In rare cases a gain contingency may be recognized once substantially all uncertainties have been resolved, but in practice that almost never happens before the gain is fully settled, which is why most accountants treat the rule as a near-total bar.8Deloitte Accounting Research Tool. Contingencies, Loss Recoveries, and Guarantees – 3.3 Application of the Gain Contingency Model Footnote disclosure is permitted, but the wording has to be handled carefully so it does not imply the gain is a sure thing. A company waiting on a favorable patent ruling can describe the case without suggesting it expects to collect.
Where U.S. GAAP and IFRS Part Ways
Companies reporting under IFRS follow IAS 37 rather than ASC 450, and two differences matter for anyone reading across the two frameworks.
The first is the probability threshold. Under IFRS, “probable” means more likely than not, essentially anything above 50 percent. Under U.S. GAAP, the effective bar sits around 70 percent or higher.9Deloitte Accounting Research Tool. Differences Between U.S. GAAP and IFRS Accounting Standards That gap means IFRS statements will recognize some provisions as liabilities that a U.S. GAAP company would only disclose.
The second is measurement. When a range of outcomes exists and no single amount is a better estimate, U.S. GAAP accrues the minimum. IFRS accrues the midpoint.9Deloitte Accounting Research Tool. Differences Between U.S. GAAP and IFRS Accounting Standards Taken together, the lower threshold and higher midpoint measurement generally produce larger and earlier accruals under IFRS. The same underlying legal exposure can look meaningfully different on paper depending on which framework the company reports under.