Key Takeaways
- A provision hits the balance sheet; a contingent liability stays in the notes as a disclosure item.
- The dividing line is probability: "more likely than not" (above 50%) triggers provision recognition.
- The entity reassesses every contingent liability at each reporting date to determine whether the outflow has become probable enough to reclassify as a provision.
- Misclassifying in either direction creates a material misstatement of liabilities that affects the auditor's opinion.
What is IAS 37 Provision vs Contingent Liability?
| Dimension | Provision | Contingent liability |
|---|---|---|
| Where it appears | Recognised as a liability on the balance sheet (IAS 37.14) | Disclosed in the notes only (IAS 37.27) |
| Probability of outflow | Probable (more likely than not, i.e. above 50%) | Possible but not probable, or amount cannot be reliably estimated |
| Measurement | Best estimate of expenditure required to settle, discounted if material (IAS 37.36, 37.45) | No balance sheet amount; entity discloses estimated financial effect (IAS 37.86) |
| Reassessment | Adjusted at each reporting date to reflect the current best estimate (IAS 37.59) | Reviewed each reporting date; reclassified to provision if probability increases above the threshold (IAS 37.98) |
| What the auditor tests | Estimation method, probability inputs, discount rate, completeness of the provision population | Completeness of disclosure, probability classification, risk that a contingent liability should have been reclassified |
| Documentation the auditor needs | Management's calculation, supporting evidence for the probability assessment, discount rate source | Legal opinions, correspondence, board minutes supporting the "possible but not probable" conclusion |
Decision rule: Recognise a provision when an outflow is probable and the amount can be estimated reliably. Disclose a contingent liability when the outflow is possible but not probable, or when a reliable estimate cannot be made.
When the distinction matters on an engagement
The probability assessment is the hinge, and it rarely sits at a comfortable distance from the threshold. A lawsuit where counsel calls the outcome "roughly even" forces the preparer to pick a side. IAS 37.23 treats "probable" as more likely than not, which means a 51% likelihood produces a recognised liability on the balance sheet, while a 49% likelihood produces a note disclosure with no balance sheet effect. The difference in reported liabilities can be material.
Auditors face this boundary most often with litigation, tax disputes, environmental claims, and regulatory penalties. ISA 540.13(a) requires the auditor to evaluate whether the entity's method for arriving at the probability assessment is appropriate. When management classifies four pending claims as contingent liabilities and none as provisions, the auditor needs to test each classification individually against the available evidence (legal opinions, historical settlement rates, regulatory correspondence) rather than accepting the batch classification at face value.
Worked example: Rossi Alimentari S.p.A.
Client: Italian food production company, FY2025, revenue EUR 67M, IFRS reporter. At 31 December 2025, Rossi faces two unresolved matters arising from the same product recall in August 2025.
Step 1 — Recognise the provision (Matter A)
A class of 38 retailers has filed claims totalling EUR 2.1M for spoiled inventory. Rossi's external counsel assesses an adverse outcome as probable, estimating the likely settlement at EUR 1.6M based on documented damage reports and precedent from a similar Italian food-safety case in 2022. Settlement is expected within 9 months. The three IAS 37.14 criteria are met: a past event exists (the product recall), the outflow is probable, and a reliable estimate is available. Rossi recognises a provision of EUR 1.6M classified as a current liability.
Step 2 — Disclose the contingent liability (Matter B)
The regional health authority has opened an investigation into Rossi's quality control processes. If the authority finds a systemic failure, fines of up to EUR 4M could apply. Rossi's counsel assesses the likelihood of a finding of systemic failure as possible but not probable, noting that the recall was limited to a single batch and Rossi's HACCP records are otherwise clean. IAS 37.86 requires Rossi to disclose the nature of the investigation, an estimate of the financial effect (up to EUR 4M), the uncertainties around timing and outcome, and the possibility of reimbursement (none expected). Rossi does not recognise a liability on the balance sheet for this matter.
Conclusion: the same product recall produces a recognised provision (EUR 1.6M for the retailer claims) and a disclosed contingent liability (up to EUR 4M for the regulatory investigation). If Rossi had classified both matters as contingent liabilities, liabilities on the balance sheet would be understated by EUR 1.6M. If Rossi had recognised provisions for both, it would have recorded EUR 5.6M against a matter where the regulatory outflow is not probable.
Why it matters in practice
The FRC's 2022/23 annual review of corporate reporting identified contingent liability disclosures as a recurring weakness, finding that entities frequently provided generic language without the entity-specific detail required by IAS 37.86 (nature of the claim, estimated financial effect, uncertainties, reimbursement possibility). When the auditor accepts boilerplate disclosure, the contingent liability note fails to meet IAS 37.86 even if the classification itself is correct.
Teams sometimes apply a single probability assessment across a group of related claims rather than evaluating each individually. IAS 37.24 permits the expected-value approach for a large population of obligations, but this applies to measuring the provision amount, not to determining whether each matter crosses the probable/possible threshold in the first place. A portfolio of 20 lawsuits can contain matters that split across both categories.
Related terms
Frequently asked questions
What is the difference between a provision and a contingent liability under IAS 37?
A provision is a recognised liability on the balance sheet because the outflow of resources is probable and the amount can be estimated reliably (IAS 37.14). A contingent liability is disclosed in the notes only because the outflow is possible but not probable, or the amount cannot be measured reliably (IAS 37.27). The dividing line is the probability assessment: above 50% triggers recognition, below it triggers disclosure.
Can a contingent liability become a provision during the year?
Yes. IAS 37.98 requires the entity to reassess contingent liabilities at each reporting date. If an outflow that was previously assessed as possible becomes probable (for instance, because a court ruling shifts the likelihood), the entity reclassifies the matter and recognises a provision measured at the best estimate under IAS 37.36. The auditor verifies that the reclassification is supported by updated evidence, not by a change in management's preference.
What happens if a provision turns out to be unnecessary?
IAS 37.59 requires the entity to review provisions at each reporting date. If the outflow is no longer probable, the entity reverses the provision through profit or loss. If the probability drops from “probable” to “possible,” the entity derecognises the provision and discloses a contingent liability instead. The auditor evaluates whether the reversal is supported by changed circumstances (a court dismissal, for example) rather than by optimistic reassessment.