When Is a Contingent Liability Recorded or Disclosed?

A contingent liability is recorded on the balance sheet only when two conditions are met at the same time: the loss is probable, and the amount can be reasonably estimated. If only one condition is met, or the risk is more than remote but not probable, the obligation moves to footnote disclosure instead. If the chance is only remote, generally nothing is required at all. These rules come from the FASB’s Accounting Standards Codification, primarily ASC 450-20.

The Two-Part Recording Test

Under ASC 450-20-25-2, a company must accrue a loss contingency by charging it to income when both of the following are true:

  • The loss is probable, meaning the event triggering the obligation is likely to occur based on available information.
  • The amount is reasonably estimable, meaning a specific dollar figure or a range of possible costs can be identified using available evidence.

Both boxes have to be checked at the same reporting date. A probable loss with no defensible dollar figure does not go on the balance sheet; it goes in the footnotes. An estimable loss that is not yet probable does the same. The pairing is deliberate. It keeps speculative figures out of reported liabilities while forcing genuine, quantifiable obligations onto the face of the financials rather than into fine print.

What “Probable” Means in Practice

The codification defines “probable” qualitatively as “the future event or events are likely to occur.” No percentage is attached. In practice, accounting professionals widely treat the threshold as roughly 75% or higher likelihood, and that informal consensus is how legal departments, controllers, and auditors evaluate pending lawsuits, regulatory actions, and similar exposures.

The standard sorts likelihood into three tiers: probable (likely), reasonably possible (more than remote but less than likely), and remote (slight chance). A loss sitting at, say, 60% likelihood would not qualify as probable under prevailing practice, even though a layperson would call it more likely than not. The practical result is that some genuine risks stay off the balance sheet and appear only in the footnotes.

One boundary is worth flagging. Companies reporting under International Financial Reporting Standards face a lower bar. IAS 37 defines “probable” as “more likely than not,” which effectively means anything above 50%. The same lawsuit can require an accrual under IFRS while remaining a footnote disclosure under U.S. GAAP. Anyone comparing statements across borders should keep that gap in mind.

Estimating the Loss Amount

Once a loss clears the probability threshold, the company needs a defensible dollar figure. Accountants look at historical loss patterns, settlement offers, expert valuations, and damage calculations from legal proceedings. The estimate does not need to be exact. A reasonable range satisfies the requirement.

A specific rule handles ranges. Under ASC 450-20-30-1, when a company identifies a range of possible losses but cannot determine which amount within that range is most likely, it accrues the low end of the range. If the legal team estimates a loss somewhere between $500,000 and $2 million with no particular amount more likely than another, $500,000 goes on the balance sheet. The remaining exposure up to $2 million gets disclosed in the footnotes so readers see the full picture.

This minimum-accrual rule is one of the more counterintuitive parts of contingent liability accounting. A company can report a $500,000 liability for a matter where actual exposure might reach four times that amount. Investors who scan only the balance sheet without reading the footnotes will miss the upper end of the range.

The Role of Legal Counsel

Auditors do not make legal judgments themselves. Under PCAOB auditing standards, the auditor’s primary tool for verifying management’s assessment of litigation risks is a formal inquiry letter sent to the company’s outside lawyers. The auditor asks management to authorize their attorneys to respond with an evaluation of the likelihood of an unfavorable outcome and, when possible, an estimate of the amount or range of potential loss.1PCAOB. AU Section 337 – Inquiry of a Client’s Lawyer Concerning Litigation, Claims, and Assessments

When a lawyer responds that inherent uncertainties make it impossible to evaluate the likelihood or estimate the range, the auditor treats the matter as not susceptible to reasonable estimation. The contingency does not disappear. It usually shifts to footnote disclosure rather than accrual. Lawyers understand this dynamic, and the language in response letters is carefully calibrated because it directly affects what appears in the financial statements.

When Footnote Disclosure Applies Instead

Footnote disclosure is the reporting mechanism for contingencies that fall short of the dual recognition threshold. Two situations trigger it:

  • Reasonably possible losses, where the chance of an unfavorable outcome is more than remote but less than probable. The footnote describes the contingency and either estimates the possible loss or range of loss or states that an estimate cannot be made.
  • Probable but not estimable losses, where the company believes it will likely lose but the amount is too uncertain to quantify. The footnote explains the situation and states that no estimate is currently available.

A footnote disclosure does not reduce net income or increase liabilities on the balance sheet. It alerts the reader. For many pending lawsuits and regulatory matters, though, the footnotes contain the most consequential information in the entire filing. The SEC has repeatedly pushed back on companies that provide boilerplate disclosure language without meaningful detail about specific contingencies.

When Nothing Needs to Be Recorded or Disclosed

Contingencies with only a remote chance of occurring require neither a balance sheet entry nor a footnote disclosure under ASC 450-20. The logic is straightforward. Including every far-fetched possibility would clutter financial statements without giving readers useful information. A frivolous lawsuit with no legal merit typically falls into this category.

The Guarantee Exception

Guarantees break this pattern. Under ASC 460, a company that issues certain types of guarantees must disclose the nature and terms of the guarantee regardless of how unlikely the loss may be. Even if the guarantor considers the chance of paying under the guarantee to be remote, the disclosure requirement still applies.2Financial Accounting Standards Board. Summary of Interpretation No 45

This exception covers a wide range of arrangements, including indemnification agreements, standby letters of credit, and guarantees of another entity’s debt. A parent company guaranteeing a subsidiary’s loan must disclose that guarantee even if the subsidiary is financially healthy and default seems extremely unlikely. The rationale is that guarantee obligations represent a fundamentally different kind of risk than ordinary contingencies because they involve a direct promise to a third party.

Unasserted Claims Have Their Own Rule

Not every potential liability comes with a formal demand or lawsuit. A company may know it has exposure that no one has filed on yet, such as an environmental contamination discovered internally or a product defect that could generate future lawsuits. These unasserted claims follow their own disclosure logic.

If no potential claimant has shown any awareness of a possible claim, disclosure is not required unless both of the following are true: it is probable that a claim will eventually be asserted, and there is a reasonable possibility that the outcome would be unfavorable. If assertion is not probable, neither accrual nor disclosure is needed. If assertion is probable, the company then evaluates the likely outcome and either accrues (if probable and estimable) or discloses (if reasonably possible or not estimable).

Gain Contingencies Are Not Recorded the Same Way

The accounting treatment for potential gains and potential losses is deliberately asymmetric. A probable loss gets recorded on the balance sheet. A probable gain does not. Under ASC 450-30, gain contingencies should not be recognized in the financial statements before realization, meaning the company actually receives the money or asset. Even if a company is virtually certain to win a lawsuit for damages, it cannot book the expected recovery as revenue until the cash arrives or the judgment is final and collectible.

The reasoning is conservatism. Overstating assets and income is treated as more dangerous to financial statement users than overstating liabilities. Gain contingencies may be disclosed in the footnotes, but the codification warns against language that might mislead readers into thinking realization is certain.

How Post-Balance-Sheet Events Change the Answer

Financial statements are not frozen the moment the reporting period ends. Under ASC 855, companies must consider information that becomes available after the balance sheet date but before the financial statements are issued. If that new information reveals that a loss existed as of the balance sheet date, the company adjusts its financials retroactively.

A common example: a company assesses a pending lawsuit as reasonably possible at year-end. In February, before the annual report is filed, the court rules against the company. Because the underlying conditions existed at the balance sheet date, the company goes back and records the liability as of year-end. The February ruling is treated as additional evidence about a condition that already existed, not as a new event.

The reverse also applies. If a company accrued a contingent liability at year-end and then settled the matter for less before the financials were issued, it adjusts the accrual down to the settlement amount. The key question is always whether the subsequent event provides evidence about conditions at the balance sheet date or reflects genuinely new circumstances that arose afterward. Only the former triggers an adjustment.

Book Recording Does Not Equal a Tax Deduction

Recording a contingent liability on the balance sheet under GAAP does not automatically create a tax deduction. The Internal Revenue Code imposes a separate timing rule called the economic performance requirement. Under 26 U.S.C. § 461(h), an accrual-method taxpayer cannot treat a liability as incurred for tax purposes until economic performance has occurred, regardless of what the financial statements show.3Office of the Law Revision Counsel. 26 USC 461 General Rule for Taxable Year of Deduction

What counts as economic performance depends on the type of liability. For tort claims and workers’ compensation obligations, economic performance occurs when the company actually makes payment, not when it accrues the estimated liability.4eCFR. 26 CFR 1.461-4 – Economic Performance A company that accrues a $3 million litigation liability in 2025 but pays the settlement in 2027 cannot deduct the $3 million until 2027 for tax purposes. This creates a temporary difference between the book value and the tax basis of the liability, which in turn generates a deferred tax asset on the balance sheet.

There is a limited exception for recurring items. If the all-events test is met during the tax year, economic performance occurs within 8½ months after year-end, the item recurs regularly, and accruing it in the earlier year produces a better match against income, the taxpayer can deduct it before economic performance is complete.3Office of the Law Revision Counsel. 26 USC 461 General Rule for Taxable Year of Deduction Warranty expenses often qualify because they recur predictably and are settled within months. Litigation settlements rarely do.

What Happens When Companies Get It Wrong

Getting contingent liability accounting wrong is not an abstract compliance issue. The SEC has brought enforcement actions specifically targeting companies that delayed recording or disclosing loss contingencies.

In 2021, the SEC issued an order against Healthcare Services Group (HCSG) for failing to accrue or disclose anticipated losses from pending litigation in multiple quarters during 2014 and 2015. The company had internally determined it would seek settlements ranging from $2.5 million to $8 million on various cases, making the losses both probable and estimable. Instead of recording them when the conditions were met, HCSG delayed the accruals to later quarters. The result: HCSG reported earnings per share that met analyst consensus estimates in the quarters where accruals were omitted. Had it accrued on time, it would have missed those estimates by as much as 25%.5U.S. Securities and Exchange Commission. In the Matter of Healthcare Services Group Inc

The SEC found violations of multiple provisions of the Securities Act and the Exchange Act. The case illustrates a pattern the agency watches for: small accrual delays that conveniently allow companies to hit earnings targets. Even a one-cent difference in earnings per share can be treated as material if it determines whether a company meets or misses market expectations.

Beyond enforcement actions, companies and their officers can face civil penalties, and investors who relied on misstated financials may have a right of rescission that forces the company to return their investment plus interest.6U.S. Securities and Exchange Commission. Consequences of Noncompliance The bottom line for anyone applying the rule: the question of when to record versus disclose is answered on the date the two conditions are met, not on the date it is convenient to recognize the hit.