Loss Contingency: Recognition, Disclosure, and IFRS Treatment

A loss contingency is a potential loss tied to an existing condition whose outcome depends on a future event that may or may not happen. Under ASC 450, you accrue one on the balance sheet only when both tests are met: it is probable that a loss has been incurred, and the amount can be reasonably estimated. If a contingency fails either test, it is not accrued, but it may still need to be described in the footnotes depending on how likely the loss is.

What Counts as a Loss Contingency

The defining feature is that the uncertainty stems from something that has already happened. A company sued over a product it already sold has a loss contingency. A company worried it might one day be sued over a product still in development does not, because no triggering condition yet exists.

Common examples include pending or threatened litigation, product warranty obligations, environmental cleanup costs, and guarantees of another party’s debt. Each involves a past event (the sale, the contamination, the guarantee) and an uncertain future resolution (the verdict, the claim, the cleanup bill, the default).

The Two-Part Accrual Test

A loss contingency is recorded on the balance sheet only when both conditions in ASC 450 are satisfied. 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.1Deloitte Accounting Research Tool. Deloitte Roadmap Contingencies, Loss Recoveries, and Guarantees – 2.3 Recognition When both hold, the journal entry debits an expense and credits a liability, so the income statement and balance sheet move together.

When one or both tests fail, the analysis shifts to disclosure. That is where the three likelihood categories decide what happens next.

Probable, Reasonably Possible, and Remote

ASC 450 sorts loss contingencies into three likelihood buckets, and each carries a different consequence.1Deloitte Accounting Research Tool. Deloitte Roadmap Contingencies, Loss Recoveries, and Guarantees – 2.3 Recognition The standard defines them qualitatively rather than by percentage, which is what makes the judgment hard in practice.

Probable

Probable means the future confirming event is likely to occur. Most preparers and auditors interpret this as roughly a 70 to 75 percent or greater likelihood, though the standard assigns no number.2Deloitte Accounting Research Tool. Differences Between U.S. GAAP and IFRS Accounting Standards A probable loss that is also reasonably estimable is accrued. Probable is the only category that triggers accrual.

Reasonably Possible

Reasonably possible means the chance of the loss is more than remote but less than likely. No accrual is required or permitted. The footnotes must describe the nature of the contingency and give an estimate of the possible loss or a range. If no estimate can be made, the disclosure must say so.

Remote

Remote means the chance is slight. A remote contingency generally requires neither accrual nor disclosure. There is a narrow exception for certain guarantees, covered further down.

How Much to Accrue

Once a contingency clears the probable threshold and qualifies for accrual, the measurement question turns on what management can say about the range of outcomes.

When One Amount Is the Better Estimate

If a single number within the range is a better estimate than any other, that amount is accrued.3Deloitte Accounting Research Tool. Deloitte Roadmap Contingencies, Loss Recoveries, and Guarantees – 2.4 Measurement If outside counsel views the most likely settlement of a lawsuit as $5 million within a range of $3 million to $8 million, the company records $5 million.

When No Point in the Range Is Better Than Another

Often management has a range but cannot identify any single point as more likely. In that case, GAAP requires accruing the minimum of the range.3Deloitte Accounting Research Tool. Deloitte Roadmap Contingencies, Loss Recoveries, and Guarantees – 2.4 Measurement For a $1 million to $5 million range with no best estimate, $1 million goes on the balance sheet. The footnotes must then disclose that additional loss up to the top of the range is reasonably possible.

When the Loss Is Probable but Not Estimable

Sometimes a loss is clearly probable but the amount cannot be pinned down, even as a minimum. No accrual is made. The footnotes must describe the contingency and state that an estimate is not possible.4FASB. Summary of Statement No. 5 This comes up regularly in early-stage litigation where damages theories are still developing.

What the Footnotes Have to Say

Disclosure carries the story the numbers alone cannot tell, and it is not optional even when an amount has been accrued.

For accrued contingencies, the footnotes must describe the nature of the obligation. The standard specifically calls for language such as “estimated liability” rather than “reserve,” which is reserved for a different accounting concept.5Deloitte Accounting Research Tool. Deloitte Roadmap Contingencies, Loss Recoveries, and Guarantees – 2.8 Disclosures If the accrual is the minimum of a range, the disclosure has to indicate the exposure to additional loss up to the top of that range.

For reasonably possible contingencies, the footnotes must describe the contingency and give an estimate of the possible loss or range of loss, or state that no estimate can be made. Analysts read these disclosures closely because they flag risks the balance sheet does not yet carry.

The Guarantee Exception

ASC 460 carves out certain loss contingencies that must be disclosed no matter how remote the chance of paying out. The common thread is a guarantee, an arrangement where the company has agreed to step in if a third party fails to perform.6Deloitte Accounting Research Tool. Deloitte Roadmap Contingencies, Loss Recoveries, and Guarantees – 5.5 Disclosure Requirements The arrangements caught by this rule include:

  • Guarantees of another party’s debt, including indirect guarantees
  • Standby letters of credit issued by commercial banks
  • Agreements to repurchase receivables or related property that have been sold or assigned
  • Any other arrangement that functions substantively like a guarantee

The point is to let financial statement users see the total exposure, even where the probability of an actual payout is low.

Gain Contingencies Work Differently

A gain contingency, such as a potential favorable lawsuit outcome, is treated in the opposite direction. Gain contingencies cannot be recognized in the financial statements until they are actually realized.7Deloitte Accounting Research Tool. Application of the Gain Contingency Model The asymmetry reflects the conservative bias in financial reporting: losses come in as soon as they are probable and estimable, while gains wait until the money is in hand.

Events After the Balance Sheet Date

The balance sheet date does not end the analysis. Events that happen between year-end and the issuance of the financial statements can change the contingency picture, and the treatment depends on whether the event confirms a condition that already existed or reflects a new one.

If a lawsuit that was pending at year-end settles for a specific amount before the statements are issued, that settlement is evidence about a condition that existed at the balance sheet date. The financial statements are adjusted to reflect the settlement amount.8Deloitte Accounting Research Tool. Deloitte Roadmap Contingencies, Loss Recoveries, and Guarantees – 2.9 Subsequent-Event Considerations These are recognized, or Type 1, subsequent events.

If a new lawsuit is filed after year-end based on events that also happened after year-end, the condition did not exist at the balance sheet date. The financials are not adjusted, though the event may need footnote disclosure to keep the statements from misleading users.9PwC Viewpoint. Types of Subsequent Events These are nonrecognized, or Type 2, events. Miscategorizing a settlement of a pre-existing lawsuit as Type 2 leaves the balance sheet understated.

Insurance Recoveries

When a company accrues a loss and expects to recover some of it through insurance, the recovery can be recorded at the same time, but only if the recovery itself is probable. The receivable is capped at the amount of loss already recognized.10Deloitte Accounting Research Tool. Deloitte Roadmap Contingencies, Loss Recoveries, and Guarantees – 4.3 Loss Recovery and Gain Contingency Models Filing a claim alone does not make the recovery probable; the carrier must not be contesting payment, and the payment cannot be subject to refund.

Any expected recovery beyond the recognized loss becomes a gain contingency and faces the higher realization threshold. And when the insurance claim is itself in litigation because the carrier has denied coverage, there is a rebuttable presumption that recovery is not probable. In plain terms, a company fighting its insurer over coverage cannot assume it will collect.

How IFRS Handles the Same Question

Companies reporting under IFRS use IAS 37 instead of ASC 450, and two differences push IFRS toward earlier and larger recognition.

The probability threshold is lower. Under U.S. GAAP, “probable” is interpreted as roughly 70 percent or greater. Under IFRS, “probable” means “more likely than not,” which is anything above 50 percent.2Deloitte Accounting Research Tool. Differences Between U.S. GAAP and IFRS Accounting Standards A loss that a GAAP preparer treats as only reasonably possible and puts in the footnotes may clear the IFRS bar and require balance sheet recognition.

Measurement of a range also differs. When outcomes are equally likely, GAAP requires the minimum; IFRS requires the midpoint. For a $2 million to $10 million range with no best estimate, a GAAP filer records $2 million while an IFRS filer records $6 million. The gap can be material for entities that report under both frameworks or that switch between them.