IAS 37 Provisions, Contingent Liabilities

Updated 1 April 2026 · Reviewed by IFRS Buddy Editorial Team

When should a provision be recognised under IAS 37?

U
IFRS

IAS 37 Provisions, Contingent Liabilities — Core Rule

A provision must be recognised as a liability when three conditions are met simultaneously: (1) an entity has a present obligation (legal or constructive) as a result of a past event, (2) it is probable that an outflow of resources will be required to settle the obligation, and (3) a reliable estimate can be made of the amount of the obligation (IAS 37.14).

How IAS 37 Provisions, Contingent Liabilities Works

  • Present obligation test: The obligation must arise from a past event (the "obligating event"), not from future actions or management intention alone. A legal obligation results from statute, contract, or court ruling; a constructive obligation arises when an entity has created a valid expectation in others (e.g. a public commitment or established practice) that it will assume responsibility (IAS 37.10, IAS 37.13). The key is that the entity has little discretion to avoid the settlement.
  • Probability threshold: IAS 37.23 states that a provision is recognised only when the outflow of resources is "more likely than not" — meaning probability exceeds 50%. This is a higher bar than mere possibility. If probability is ≤50%, the obligation is disclosed as a contingent liability under IAS 37.86, not recognised in the statement of financial position.
  • Reliable measurement: The amount recognised must be a reliable estimate of the best estimate of the expenditure required to settle the obligation (IAS 37.36). For a single obligation, this is the most likely amount; for a large population of similar items, the expected value (probability-weighted average) is used (IAS 37.40). The estimate must reflect both the direct costs of settlement and, where appropriate, incremental costs associated with the event.
  • Timing of recognition: The provision is recognised at the date when the obligating event occurs and the three criteria are satisfied, not when the payment is expected. This means a provision can exist long before cash outflow (IAS 37.26).
  • Presentation and disclosure: The provision is shown in the statement of financial position as a separate liability, with movements (opening balance, additions, reversals, settlement, unwinding of discount) detailed in the notes (IAS 37.84). If a provision relates to a discontinued operation, segment, or specific project, it may be presented separately or detailed by class.
  • Subsequent measurement and changes: A provision is remeasured at each reporting date. If the obligation decreases, the provision is reversed by crediting the expense line initially debited (IAS 37.58). Where the passage of time is a significant factor, the provision is discounted to present value, and the unwinding of the discount is recognised as finance costs (IAS 37.45).

IAS 37 Provisions, Contingent Liabilities — Practical Example

A manufacturing company has a legal obligation under environmental law to decommission a factory at the end of its 10-year lease. Management estimates the decommissioning will cost €2,000,000 in 10 years' time. The obligation is virtually certain (probability 95%+). The risk-adjusted discount rate is 5% per annum.

Present value of the obligation = €2,000,000 ÷ (1.05)^10 = €1,227,830

At initial recognition (Year 1, end of period):

AccountDr (€)Cr (€)
Decommissioning expense1,227,830
Provision for decommissioning1,227,830

At the end of Year 2, the unwinding of the discount (5% × €1,227,830 = €61,392) is recognised as a finance cost:

AccountDr (€)Cr (€)
Finance costs61,392
Provision for decommissioning61,392

The carrying amount of the provision is now €1,289,222. This process repeats annually until settlement.

IAS 37 Provisions, Contingent Liabilities — Common Pitfalls

  • Confusing constructive obligations with intentions: Many entities reserve for restructuring costs when a plan exists internally, but no announcement has been made to affected parties. Under IAS 37.72, a provision for restructuring is recognised only when the entity has a detailed plan and has started implementation or announced the plan to those affected — mere board approval is insufficient.
  • Underestimating probability: Practitioners sometimes assume that if a claim has been filed (e.g. litigation), the outflow is probable. However, IAS 37.23 requires judgment; legal advice on the strength of the claim is essential. A weak legal position may justify disclosure as a contingent liability rather than a provision.
  • Using expected value incorrectly for single items: IAS 37.40 allows expected value for many similar items (e.g. warranty claims), but for a single major obligation, the most likely outcome should be used (IAS 37.39). Averaging probabilities across discrete scenarios is a common error in single-obligation cases.

IAS 37 Provisions, Contingent Liabilities — Key Paragraphs

  • IAS 37.14 — the three recognition criteria (definition of a provision)
  • IAS 37.23 — the probability threshold (more likely than not)
  • IAS 37.36–40 — measurement: best estimate, most likely vs. expected value
  • IAS 37.45 — discounting to present value and finance cost unwinding
  • IAS 37.72–73 — restructuring provisions (constructive obligation timing)
  • IAS 37.86–89 — contingent liabilities (disclosure when criteria not met)

Related Topics

IAS 37 Constructive ObligationIAS 37 Contingent Liability DisclosureIAS 37 Onerous ContractsIAS 37 Restructuring Provisions