Contingent liabilities are potential financial obligations whose existence depends on the outcome of an uncertain future event, and under U.S. GAAP you must either record them on the balance sheet, describe them in the footnotes, or leave them off entirely, depending on how likely the loss is and whether you can put a number on it. The rule that governs this, ASC 450, sets a two-part test for accrual: the loss must be probable, and the amount must be reasonably estimable. Miss either prong and the obligation moves to disclosure or drops out of the statements altogether. The rest of the work — measurement, tax treatment, SEC reporting, and ongoing reassessment — flows from that starting point.
The Three Likelihood Categories
ASC 450 sorts every potential obligation into one of three buckets based on probability, and the classification drives everything that follows.
Probable means the future event is likely to occur. The codification does not attach a percentage to the word, but practitioners and the FASB’s own guidance on going-concern assessments treat the threshold as roughly 70 percent or higher. Reasonable professionals disagree on exactly where the line falls. What matters is that probable demands considerably more than a coin flip.
Reasonably possible covers the middle ground: the chance of occurrence is more than slight but does not rise to likely. This is the bucket where auditors and lawyers argue the longest, because the boundary between reasonably possible and probable is inherently subjective. A pending lawsuit where the plaintiff has some evidence but has not cleared summary judgment often lands here.
Remote means the chance is slight. Most remote contingencies disappear from the financial statements entirely. One important exception: guarantees of another party’s debt must be disclosed even when the likelihood of having to pay is remote. That rule, codified in ASC 460, catches many companies off guard.
What Hits the Balance Sheet and What Lives in the Footnotes
Both conditions of the two-part test must be met before anything is accrued. If a loss is probable and reasonably estimable, the company records a liability on the balance sheet and a corresponding expense on the income statement, reducing net income for that period.
When a potential obligation is reasonably possible, no liability is recorded. Instead, the footnotes describe the nature of the risk, an estimate of the possible loss or a range of losses, and the factors that will ultimately resolve the uncertainty. If no estimate can be made, the footnote must say so. The same footnote treatment applies when a loss is probable but the amount cannot be reasonably estimated.
Remote contingencies generally require no disclosure, which keeps financial statements from drowning in unlikely scenarios. Guarantees under ASC 460 are the main exception. A guarantor must disclose the nature of each guarantee, how it arose, the events that would trigger payment, and the maximum potential amount of future payments, regardless of how unlikely payment seems. A parent company that guarantees a subsidiary’s $10 million credit line cannot ignore it because the subsidiary is financially healthy today.
Estimating the Dollar Amount
Recording a contingent liability requires more than concluding a loss is probable. You also need a number. Financial teams pull from internal data, historical patterns, actuarial analysis, and expert opinions to build that figure. When the analysis points to a single most likely amount, that figure gets recorded.
More often the result is a range. ASC 450 handles ranges with a conservative bias: if one amount within the range appears to be a better estimate than the others, that amount is recorded. If no single figure stands out, the company records the minimum of the range. This floor approach avoids overstating liabilities while still recognizing that an obligation exists. Investors reading the balance sheet should understand that the recorded figure may represent the low end of what the company actually expects to pay.
Complex contingencies often require present-value calculations. A remediation liability that will pay out over the next decade may be discounted to reflect current dollars, supported by documented assumptions about timing and discount rates. Those assumptions have to withstand audit scrutiny, so how the number was built matters as much as the number itself.
Common Examples
Pending and Threatened Litigation
Lawsuits are the most visible source of contingent liabilities. When a company is sued for patent infringement, breach of contract, or product liability, legal counsel evaluates the strength of the opposing claim, the likely range of damages, and the probability of an unfavorable outcome. A $500,000 judgment on appeal still needs assessment: if the appeals court is likely to uphold it, the company records the liability. If the outcome could go either way, the range gets footnote disclosure.
Litigation contingencies are subjective because lawyers and accountants think about probability differently. Legal counsel may resist calling a loss probable until a case is nearly lost, while auditors push for earlier recognition. This tension is where contingent liability accounting earns its reputation for judgment calls.
Product Warranties
Selling a product with a repair or replacement guarantee creates an obligation to cover future defects. The company estimates total warranty cost at the time of sale, using historical return rates and average repair costs, and records that estimated liability immediately. This matches the warranty expense to the revenue from the sale rather than waiting for customers to actually return products. A company selling electronics with a one-year warranty might estimate $50 per unit in expected repair costs, multiply by units sold, and record the aggregate figure as a warranty liability.
Guarantees and Liquidated Damages
Guarantees of third-party debt are a common source of exposure that many companies underestimate. When a corporation guarantees a loan for a subsidiary or business partner, it takes on the full balance if the borrower defaults. Under ASC 460 these guarantees require footnote disclosure even when payment is remote, including the maximum potential future payment.
Liquidated damages clauses in construction contracts create a different kind of contingency. A contract might specify a penalty for each day a project runs past its deadline, and federal procurement rules require construction contracts to describe the daily rate, covering estimated inspection costs and other expenses tied to the delay. These obligations require ongoing monitoring, because every day of slippage increases the potential liability.
Environmental and Asset Retirement Obligations
Environmental cleanup obligations are among the hardest contingent liabilities to estimate. When a company operates on contaminated land or uses hazardous materials, remediation costs may unfold over years or decades. ASC 410-30 applies when contamination stems from normal operations, while sudden events like spills or accidents may fall under the general ASC 450 framework.
Recognition still follows the two-prong test, but the standard addresses a situation that trips up many companies: at early stages of remediation, some cost components are not estimable. That does not excuse the company from recording anything. The estimable components serve as a surrogate for the minimum of the overall liability range. You cannot wait for perfect information before recognizing an environmental obligation. Asset retirement obligations under ASC 410-20 work similarly, covering legal obligations to decommission or restore a site at the end of its useful life, even when the timing is uncertain.
Self-Insurance and IBNR Claims
Companies that self-insure for workers’ compensation, health benefits, or general liability face a specific type of contingent liability: claims incurred but not yet reported. These IBNR claims must be accrued if it is probable that losses occurred before the balance sheet date and the amount can be reasonably estimated, typically through actuarial analysis of historical claims data. What you cannot do is accrue expected future losses before they happen. Recording a general reserve “in lieu of insurance” is not permitted under ASC 450. Accruing for events that have already occurred but haven’t surfaced is required; setting money aside for events that might happen next quarter is not.
Contingent Gains Are Treated Differently
The treatment of potential gains is deliberately asymmetric. Under ASC 450-30, a gain contingency must not be recorded in the financial statements even if realization is considered probable. The reasoning is straightforward: booking a gain before it materializes could mislead investors into thinking the company has resources it does not yet have.
A company awaiting a favorable court ruling on a patent dispute cannot book the expected damages award until the cash is actually received or the outcome is virtually certain. The potential gain may be disclosed in footnotes, but the disclosure must avoid misleading implications about the likelihood of realization. In practice, the footnote describes the nature of the contingency, the parties involved, and the expected timeline for resolution without projecting a dollar figure with unwarranted confidence. The result is a built-in pessimistic bias in financial statements: bad news gets recorded earlier than good news.
Book Accrual Does Not Mean a Tax Deduction
Recording a contingent liability on the balance sheet does not mean you get to deduct it on the tax return. The IRS applies a separate test under Section 461(h) of the Internal Revenue Code that is stricter than the accounting standard. The all-events test requires that all events establishing the fact of the liability have occurred and that the amount can be determined with reasonable accuracy. There is a third hurdle: economic performance must also take place before the deduction is allowed.1Office of the Law Revision Counsel. 26 USC 461 – General Rule for Taxable Year of Deduction
Economic performance generally occurs when the company actually pays or provides the services or property that gave rise to the liability. For tort and workers’ compensation claims, economic performance happens when payments are made to the injured party, not when the liability is accrued on the books. A company that records a $2 million litigation accrual in 2025 but does not settle until 2027 cannot deduct that $2 million until 2027. A narrow exception exists for recurring items where economic performance occurs within 8½ months after the close of the tax year, but it does not apply to material or non-recurring contingencies.1Office of the Law Revision Counsel. 26 USC 461 – General Rule for Taxable Year of Deduction
The gap between book and tax treatment creates a temporary difference that shows up as a deferred tax asset. Companies that fail to track it accurately end up with incorrect tax provisions, and both auditors and the IRS flag those quickly.
Extra Disclosure Requirements for Public Companies
Publicly traded companies face reporting obligations that go beyond GAAP’s footnotes. SEC Regulation S-K Item 103 requires registrants to describe any material pending legal proceedings, including the court or agency involved, the date the case was filed, and the relief sought. Environmental proceedings get special treatment: they must be disclosed if the amount exceeds 10 percent of current assets, if a governmental authority is involved, or if the case is otherwise material to the company’s financial condition.2eCFR. 17 CFR 229.103 – Item 103 Legal Proceedings
Contingent obligations also have to be discussed in Management’s Discussion and Analysis. Under the amended Item 303(b), companies must discuss commitments and contingent obligations arising from off-balance-sheet arrangements if they have, or are reasonably likely to have, a material effect on financial condition, liquidity, or results of operations. This disclosure is required even when the arrangement results in no liability on the balance sheet.3U.S. Securities and Exchange Commission. Management’s Discussion and Analysis, Selected Financial Data, and Supplementary Financial Information
The SEC staff has warned that a blanket statement calling a contingency “not expected to be material” does not satisfy disclosure requirements when there is at least a reasonable possibility that an unrecognized loss could be material to an investor’s decision. In that situation, the company must either disclose the estimated additional loss or range of loss, or explicitly state that no estimate can be made.4U.S. Securities and Exchange Commission. Codification of Staff Accounting Bulletins – Topic 5
Reassessing Contingencies Every Period
Contingent liabilities do not freeze at the balance sheet date. Events that occur after the reporting period but before the financial statements are issued can change classification and measurement. If an unfavorable court ruling comes down after year-end but the underlying lawsuit existed at the balance sheet date, the company must adjust its financial statements to reflect the new information. A case previously classified as reasonably possible might become probable, or a settlement amount might differ from the accrued figure. Either way, the statements get restated to reflect what was true about the obligation at year-end, even if the confirming event happened later.
Events that create entirely new contingencies after the balance sheet date do not result in retroactive adjustments. A lawsuit filed in January over an incident that occurred in January does not affect the prior December financial statements. If the new event is significant enough that omitting it would make the statements misleading, the company must disclose it in the footnotes without adjusting the numbers.
SEC filers must evaluate subsequent events through the date their financial statements are issued. Non-public entities evaluate through the date statements are available to be issued, which is generally earlier. Every reporting period, management must reassess existing contingencies, evaluate new information, and update accruals and disclosures accordingly.
A Note for Companies Reporting Under IFRS
Companies reporting under International Financial Reporting Standards follow IAS 37 instead of ASC 450, and the differences matter. Under IFRS, probable means “more likely than not,” which is anything above 50 percent. Under U.S. GAAP, probable means roughly 70 percent or higher. A contingency that falls between 50 and 70 percent likelihood would be recorded as a liability under IFRS but only disclosed in footnotes under U.S. GAAP.
Measurement rules also diverge. When a company faces a range of possible outcomes under IAS 37, it uses the best estimate of the expenditure required to settle the obligation. For a large population of similar items, IAS 37 calls for an expected-value calculation that weights all possible outcomes by their probabilities. For a single obligation, the most likely outcome often serves as the best estimate, though the company must still consider whether other outcomes skew the distribution higher or lower. When a continuous range of equally likely outcomes exists, IAS 37 uses the midpoint. U.S. GAAP records the minimum of a range when no single amount is more likely. The same underlying facts can produce different balance sheet figures depending on which framework applies.