A contingent liability under IFRS is an uncertain obligation that stays off the balance sheet and lives in the notes to the financial statements. IAS 37 draws a hard line: an obligation becomes a recognized provision only when all three tests are satisfied at once — a past event has created a present obligation, an outflow of economic resources is more likely than not, and the amount can be reliably estimated.1IFRS Foundation. IAS 37 Provisions, Contingent Liabilities and Contingent Assets Fail any one of those tests and the item is a contingent liability: disclosed, not recognized. Get the line wrong and the financial statements are materially misstated.
Two Categories, Two Accounting Treatments
IAS 37 sorts uncertain obligations into two buckets, and the treatments diverge sharply.1IFRS Foundation. IAS 37 Provisions, Contingent Liabilities and Contingent Assets A provision is a liability of uncertain timing or amount that clears all three recognition criteria. It sits on the balance sheet as a recognized liability, with a matching expense in the income statement. A contingent liability is everything that falls short. It never touches the balance sheet.
Contingent liabilities themselves come in two forms. The first is a possible obligation where you don’t yet know whether a real obligation exists at all — a lawsuit where liability hasn’t been established, for example. The second is a present obligation that fails recognition because the outflow isn’t probable or the amount can’t be reliably estimated. Either way, the treatment is note disclosure only.
Classification is not permanent. An item disclosed as a contingent liability last quarter can become a recognized provision this quarter if the facts move. Management reassesses at every reporting date, and the moment all three criteria line up, the obligation moves from the notes to the balance sheet.
The Three Recognition Criteria
All three must be satisfied simultaneously. If any one fails, the obligation stays in the notes.1IFRS Foundation. IAS 37 Provisions, Contingent Liabilities and Contingent Assets
Present Obligation From a Past Event
The entity must have a present obligation, meaning it has no realistic alternative to settling it. The obligation can be legal, created by contract, statute, or regulation, or it can be constructive. A constructive obligation arises when the entity’s own pattern of behavior, published policies, or specific statements create a valid expectation in other parties that it will act. A manufacturer that has publicly committed to a voluntary product recall has a constructive obligation even without a regulatory order.
The past event triggering the obligation is sometimes called the obligating event. If none has occurred, there is nothing to recognize, no matter how likely a future obligation looks. A company cannot record a provision for an environmental cleanup law that has been proposed but not enacted, even if passage seems certain.
Probable Outflow of Resources
Under IAS 37, “probable” means more likely than not — a probability above 50 percent.1IFRS Foundation. IAS 37 Provisions, Contingent Liabilities and Contingent Assets That threshold is lower than many people assume. A 51 percent chance of paying is enough to require recognition, provided the other two criteria hold. If probability sits around 40 percent, the outflow is only possible, and the obligation is a contingent liability requiring disclosure. If the chance is remote, no disclosure is required at all.
This is the criterion that shifts most often. A pending lawsuit might start at a 30 percent chance of loss and jump to 60 percent after an unfavorable court ruling. That single reassessment flips the obligation from disclosure to recognition.
Reliable Estimate of the Amount
Even when the first two tests are met, the entity must be able to make a reliable estimate of the cost. IAS 37 takes a pragmatic view here. In all but the most extreme cases, the entity should be able to determine a range of possible outcomes and use that range to arrive at an estimate. The standard says inability to estimate should be extremely rare.
When a reliable estimate genuinely cannot be made, the obligation is treated as a contingent liability and disclosed rather than recognized. The notes must then explain why measurement was impossible.
What Goes in the Notes
When an obligation fails one of the criteria but the possibility of an outflow isn’t remote, IAS 37 requires note disclosure. The standard is prescriptive about content:1IFRS Foundation. IAS 37 Provisions, Contingent Liabilities and Contingent Assets
- A description of the nature and source of the contingent liability, specific enough for a reader to understand the underlying event, such as a pending lawsuit or an unresolved regulatory claim.
- An estimated financial effect, presented as a single figure or a range. If quantification is impossible, the notes must state that explicitly and explain why.
- The uncertainties affecting the amount or timing of any potential outflow, with enough detail for investors to model the risk.
- Any potential reimbursement from a third party, such as insurance. Reimbursements are presented separately and are never netted against the contingent liability.
One narrow exception applies. If disclosing the details would seriously prejudice the entity in an ongoing dispute, specific information can be withheld. Even then, the entity must disclose the general nature of the dispute and the reason for the omission. Auditors and regulators scrutinize these omissions heavily.
Classification Changes Over Time
Reassessment is required at every reporting date, and it can move an obligation in either direction. Take a lawsuit where legal counsel initially estimates a 40 percent chance of loss. Because the outflow is possible but not probable, the entity discloses it as a contingent liability, including the nature of the case and an estimated range of loss. Six months later, the opposing party wins a key procedural motion and counsel revises the estimate to 65 percent. The obligation immediately converts to a recognized provision, with a journal entry debiting an expense and crediting the provision liability.
The traffic runs both ways. A contingent liability can be dropped entirely if the probability of outflow becomes remote — for instance, after the opposing party withdraws its claim.
Warranty obligations follow a similar arc for new products. A company launching a product with no warranty history may lack the data for a reliable estimate. During that early period, the warranty obligation is a contingent liability, disclosed but not recognized because measurement is not yet reliable. As claims data accumulates, the expected value method becomes workable and the obligation transitions to a recognized provision.1IFRS Foundation. IAS 37 Provisions, Contingent Liabilities and Contingent Assets
Events After the Reporting Date
Information that surfaces after the balance sheet date, but before the financial statements are authorized for issue, can change classification. Under IAS 10, if the new information provides evidence about a condition that already existed at the reporting date, it is an adjusting event and the statements must be updated.
If a court rules against the entity in January on a lawsuit that was pending at December 31, the ruling is evidence of a condition that existed at year-end. Assuming the other criteria are met, the entity recognizes a provision in the December 31 financial statements even though the ruling arrived later. A completely new claim that arises after year-end and has no connection to conditions at the reporting date is a non-adjusting event: disclose in the notes, no adjustment to the numbers.
Contingent Assets Are Not the Mirror Image
IAS 37 treats potential gains asymmetrically. Contingent assets are never recognized on the balance sheet unless the inflow of economic benefits is virtually certain — a threshold significantly higher than the more-likely-than-not standard used for provisions.1IFRS Foundation. IAS 37 Provisions, Contingent Liabilities and Contingent Assets Once an inflow reaches virtual certainty, it is no longer contingent and is simply recognized as an asset.
Below that threshold, a contingent asset is disclosed in the notes only when an inflow is more likely than not. If an inflow is merely possible or remote, no disclosure is required. IFRS is deliberately conservative here, preventing premature recognition of gains that may never arrive while ensuring likely losses are captured early.
Where IFRS Differs From US GAAP
Anyone reading IFRS financials alongside US GAAP financials should know the recognition bars are not the same. Under IFRS, probable means more likely than not, above 50 percent. Under US GAAP (ASC 450), probable means “likely to occur,” generally interpreted around 70 percent or higher. The same lawsuit assessed at a 55 percent chance of loss would produce a recognized provision under IFRS but only a footnote disclosure under US GAAP.
Other differences compound the gap:
- When a range of outcomes is equally probable, IFRS uses the midpoint; US GAAP uses the minimum. IFRS provisions therefore tend to be larger for the same underlying exposure.
- IFRS requires discounting provisions to present value when the time effect is material. US GAAP generally prohibits discounting loss contingencies unless timing and amounts are fixed or reliably determinable.
- IFRS requires a provision when a contract becomes loss-making. US GAAP has no general onerous-contract requirement, though specific industry guidance exists.
- IFRS fully recognizes constructive obligations as a basis for provisions. US GAAP recognizes them only where specific codification topics explicitly require it.
An entity moving from US GAAP to IFRS should expect to recognize provisions earlier, and often at higher amounts, for many of the same uncertain obligations.