Contingent liabilities under GAAP are governed by ASC 450, which sorts each potential loss by likelihood and then applies a two-part test: accrue the loss on the balance sheet only if it is both probable and reasonably estimable, disclose it in the footnotes if it is reasonably possible or if it is probable but cannot be quantified, and generally do nothing if the chance is remote. Two questions drive every decision in this area. How likely is the loss? And can you put a number on it?
The Three Likelihood Tiers
ASC 450 places every loss contingency into one of three buckets, and the classification decides everything that follows.
A loss is probable when the future event confirming it is likely to occur. The codification defines this as “likely to occur” without attaching a percentage, though practitioners commonly read it as roughly a 70% or greater chance. A loss is reasonably possible when the chance is more than remote but less than likely. A loss is remote when the chance is slight.
The standard deliberately avoids numerical thresholds. Management has to exercise judgment based on the facts: opinions from legal counsel, the posture of ongoing litigation, historical outcomes in similar disputes, and the company’s own experience all feed the assessment. This is where the process gets subjective, and it is where companies most often run into trouble with regulators.
When a Loss Must Be Recorded on the Balance Sheet
Accrual is required when both conditions are met: the loss is probable and the amount can be reasonably estimated. Both prongs. A loss that is almost certain but impossible to quantify does not get recorded on the balance sheet, though it still needs footnote disclosure. A loss you can estimate to the penny but that is only reasonably possible also stays off the balance sheet.
The mechanics are straightforward. The company debits an expense account, such as litigation expense or estimated loss, and credits an accrued liability for the same amount. That accrual hits the income statement immediately, reducing net income in the period the loss becomes probable and estimable. The point of this treatment is to alert investors before cash actually leaves the company.
Timing matters more than most preparers realize. The accrual does not wait for a final court judgment or a signed settlement. Once management concludes both conditions are met, the obligation goes on the books that period. In large class-action cases, companies often build statistical models from prior court rulings and the size of the claimant pool to reach a reasonable estimate well before any resolution.
Estimating the Loss When a Range Exists
Real contingencies rarely produce a single clean number. Management usually arrives at a range, and ASC 450 gives a two-step rule for that situation. If one amount within the range is a better estimate than any other, accrue that amount. If no single figure stands out as more likely, accrue the minimum of the range.
The minimum-of-the-range rule trips people up because it feels counterintuitive. Suppose a company estimates a settlement will cost somewhere between $500,000 and $2 million and cannot identify a most-likely figure. It records $500,000 on the balance sheet. The remaining exposure up to $2 million gets disclosed in the footnotes. The logic is practical. The inability to fix a precise figure should not let the company record nothing when some loss is clearly probable.
Footnote Disclosure Requirements
A loss contingency that does not qualify for accrual may still need to appear in the footnotes. Disclosure is required in two situations: when a loss is reasonably possible, whether or not it is estimable, and when a loss is probable but cannot be reasonably estimated. Remote contingencies generally need no disclosure, with one significant exception for guarantees discussed below.
The disclosure must describe the nature of the contingency and provide either an estimate of the possible loss, a range of the possible loss, or a statement that no estimate can be made. Vague language does not satisfy the standard. For a government investigation into potential environmental violations, the disclosure should explain the nature of the investigation, the regulations at issue, and the company’s current assessment of the potential financial exposure.
Investors often rely on these notes more than the balance sheet itself to understand a company’s risk profile. A company might have no accrued litigation liability but disclose $200 million in reasonably possible losses across pending lawsuits. That information changes how the company is valued, which is precisely why the standard requires it.
Unasserted Claims
Claims that have not been formally filed yet catch companies off guard. ASC 450 sets a more forgiving threshold here than for existing litigation. A company need not disclose an unasserted claim unless two conditions are both met: it is probable that a claim will be asserted, and there is a reasonable possibility the outcome will be unfavorable.
If no potential claimant has shown any awareness of a possible claim, there is no disclosure obligation regardless of the underlying facts. But once the company becomes aware that a claim is likely to be brought, management must assess the likelihood of assertion, the probability of an unfavorable outcome, and whether any resulting loss can be reasonably estimated. If all the pieces line up and a loss is both probable and estimable, the company must accrue even though no complaint has been filed. Waiting for the summons is not a defense.
Gain Contingencies and Insurance Recoveries
GAAP treats gains and losses asymmetrically. Losses must be recognized as soon as they are probable and estimable, but gain contingencies cannot be recorded until the gain is realized or realizable. A company expecting to win a $50 million patent infringement case cannot book that gain even if victory looks virtually certain. The gain stays off the balance sheet until the money is received or the company holds an asset readily convertible to a known amount of cash.
The rationale is conservatism. Premature recognition of gains inflates net income with assets that may never materialize. If a gain contingency is highly likely, management may disclose it in the footnotes, but the language must avoid creating a misleading impression of certainty. A favorable trial court ruling under appeal is the textbook example.
Insurance proceeds tied to a recognized loss sit in a middle ground. A recovery can be recognized as an asset when realization is probable, which requires strong evidence. Direct confirmation from the insurer that it agrees with the claim is the clearest path. Without that, the company needs a legal opinion that the claim under the policy is enforceable and that the loss events are covered. If the claim is the subject of litigation between the company and the insurer, there is a rebuttable presumption that realization is not probable. Any recovery amount that exceeds the previously recognized loss crosses into gain contingency territory and faces the higher threshold.
Guarantees Follow a Different Rule
Guarantees do not follow the ASC 450 model, and applying ASC 450 thinking to a guarantee is a common error. Under ASC 460, a guarantor must recognize a liability at the inception of a guarantee at fair value, even if the likelihood of ever having to pay is remote.
The reasoning is that issuing a guarantee creates a noncontingent stand-ready obligation. The guarantor has committed to perform if certain triggering events occur, and that commitment has value regardless of whether the trigger is ever pulled. Someone would have to be paid to assume the obligation, and that willingness-to-pay is itself evidence of a liability.
Disclosure requirements are extensive even when no payment seems likely. A guarantor must disclose the approximate term, how the guarantee arose, the triggering events, the current risk assessment, and the maximum potential amount of future undiscounted payments. If there is no cap on potential payments, that fact must be stated. If the maximum cannot be estimated, the company must explain why. This is the major exception to the general rule that remote contingencies need no disclosure.
Environmental Remediation Liabilities
Environmental cleanup obligations have their own layer of guidance under ASC 410-30, built on top of the general ASC 450 framework. These liabilities are notoriously hard to estimate because remediation can span decades and involve multiple responsible parties, but the standard does not let difficulty become an excuse for inaction.
ASC 410-30 identifies specific milestones at which the company must reassess its estimate. Each typically brings better information: identification as a potentially responsible party, receipt of a unilateral administrative order, participation in a remedial investigation and feasibility study, completion of the feasibility study, issuance of a record of decision by the EPA, and the remedial design and operation phases. By the completion of the feasibility study, both a minimum remediation cost and the company’s allocated share are generally reasonably estimable.
If total remediation cost cannot be estimated, the company must still evaluate individual components. If any single component is reasonably estimable, that figure becomes the minimum in the range and must be accrued. Total uncertainty is not a permitted excuse for recording nothing.
Subsequent Events
Events happening after the balance sheet date but before the financial statements are issued can change how a contingency is reported. ASC 855 draws a line between two types, and the distinction turns on when the underlying conditions arose.
Recognized Subsequent Events
If the events giving rise to the loss occurred before the balance sheet date, new information obtained after year-end must be reflected in the financial statements. A company defends a lawsuit that arose during the fiscal year, then settles for $3 million after year-end but before the statements are issued. That settlement amount should be used to estimate the liability as of year-end because it provides additional evidence about conditions that existed at the balance sheet date.
Nonrecognized Subsequent Events
If the triggering event itself occurred after the balance sheet date, the company does not adjust the prior-period statements. A fire that destroys a warehouse in January, for a company with a December 31 year-end, is a nonrecognized subsequent event. The loss happened after the reporting period, so it does not belong on the year-end balance sheet. If the event is significant enough that omitting it would mislead readers, the company must disclose it in the footnotes with an estimate of the financial impact.
Companies must evaluate subsequent events through the date the financial statements are issued or available to be issued, and must disclose that evaluation date so readers know the cutoff.
Deferred Tax Consequences of Accruals
Book accrual of a loss contingency almost never produces an immediate tax deduction. Under 26 U.S.C. § 461, a tax deduction for a liability requires that the all-events test be met: all events establishing the fact of the liability have occurred, and the amount can be determined with reasonable accuracy. On top of that, economic performance must have occurred, which for most contingent liabilities means the company has actually paid the obligation or performed the related service.1Office of the Law Revision Counsel. 26 U.S. Code 461 – General Rule for Taxable Year of Deduction
The timing gap between book recognition and tax deductibility creates a deferred tax asset. The company has a liability on its balance sheet that has no tax basis because the deduction has not been taken yet, producing a deductible temporary difference. When the company eventually pays the settlement or remediation cost, it takes the tax deduction, and the deferred tax asset reverses. A $10 million loss accrual at a 21% corporate tax rate generates a $2.1 million deferred tax asset, partially offsetting the hit to the balance sheet.
Where IFRS Reporters Land Differently
Companies reporting under IFRS use IAS 37, and two differences can produce materially different balance sheets from identical facts. First, the recognition threshold is lower. IAS 37 requires a provision when an outflow is more likely than not, meaning anything above 50%. US GAAP interprets probable as roughly 70% or greater. A lawsuit with a 60% chance of an unfavorable outcome requires a balance sheet accrual under IFRS but only footnote disclosure under US GAAP. Second, when no single amount in a range is more likely than another, US GAAP records the minimum while IFRS records the midpoint. For a range of $1 million to $5 million with no best estimate, a US GAAP reporter accrues $1 million and an IFRS reporter accrues $3 million.
Enforcement Risk from Getting It Wrong
The SEC treats contingency accounting seriously, and enforcement actions in this area tend to involve delayed accruals used to manage earnings. In one notable case, the agency found that Healthcare Services Group improperly delayed recording anticipated litigation losses that should have been accrued when the company entered settlement agreements, at which point the losses were both probable and estimable. In some periods, timely accrual would have caused the company to miss analyst earnings-per-share estimates by as little as a penny. The company paid a $6 million civil penalty. Civil penalty authority under 15 U.S.C. § 78u-2 is tiered and adjusted annually for inflation.2Office of the Law Revision Counsel. 15 U.S.C. 78u-2 – Civil Remedies in Administrative Proceedings3U.S. Securities and Exchange Commission. Adjustments to Civil Monetary Penalty Amounts (2025) Beyond the penalties themselves, restatements damage investor confidence, invite shareholder litigation, and draw continued regulatory attention.
The companies that handle contingency accounting well treat it as an ongoing risk management process, with regular communication between legal counsel, finance, and the audit committee. The ones that end up on the receiving end of enforcement actions tend to have treated it as someone else’s problem until it was too late.