Provisions in Accounting Under IAS 37: Recognition and Measurement

Provisions in accounting under IAS 37 are liabilities of uncertain timing or amount, and the standard requires you to recognize one only when a past event has created a present obligation, an outflow of resources is more likely than not, and the amount can be reliably estimated. Miss any of those three tests and the item either becomes a contingent liability disclosed in the notes or drops off the financial statements entirely. The standard exists to stop companies from smoothing earnings by quietly building reserves in good years and releasing them in bad ones.¹

The Three Recognition Conditions

A provision goes on the balance sheet only when all three conditions are satisfied.²

A present obligation, legal or constructive, arising from a past event.
A probable outflow of economic resources to settle that obligation, meaning greater than 50 percent likely.
A reliable estimate of the amount.

Fail any one and there is no provision. If the outflow is only possible rather than probable, the item is reclassified as a contingent liability and disclosed in the notes.¹

Legal Versus Constructive Obligations

A legal obligation flows from a contract, legislation, or another enforceable source. A constructive obligation is subtler: the entity’s own conduct has created a valid expectation in others that it will follow through.¹

The illustrative examples published with the standard make this concrete. An oil company operating where no environmental legislation exists still has a constructive obligation to clean up contamination if it has a widely published environmental policy and a track record of honoring it. A retailer that routinely refunds dissatisfied customers, even with no legal duty to do so, has created a constructive obligation through established practice.³ Public behavior and published commitments can bind a company as firmly as a signed contract for accounting purposes.

What Does Not Qualify

One trap catches people repeatedly: future operating losses cannot be recognized as a provision. There is no past obligating event for losses that have not yet occurred, so the first test fails. The standard prohibits it explicitly.¹

How to Measure the Provision

Once recognition is settled, the amount recorded is the best estimate of the expenditure required to settle the obligation at the reporting date. How you arrive at that estimate depends on what you are provisioning for.

Expected Value or Most Likely Outcome

For a large population of similar items, such as warranty claims across thousands of units sold, the expected value method applies: weight each possible outcome by its probability and add them. For a single obligation like a lawsuit or a one-off regulatory fine, the most likely individual outcome is usually the best estimate.⁴

When a range of outcomes exists and no single amount stands out as more likely, IAS 37 directs you to use the midpoint of the range.⁴

Risk Adjustments Without Padding

Management must factor in the risks and uncertainties surrounding the estimate, including cost overruns and unexpected complications. Those adjustments are not an invitation to inflate the number. Deliberately overstating a provision distorts financial health just as much as understating one, and the standard warns explicitly against creating excessive provisions or intentionally overstated liabilities.

Discounting When Settlement Is Distant

Where the time value of money is material, the provision is discounted to present value. The discount rate must be a pre-tax rate reflecting current market assessments of the time value of money and the risks specific to the liability.⁴ In practice, this often starts with a risk-free government bond yield and is adjusted for factors like the duration and liquidity of the obligation.⁵ On a long-duration obligation like a 30-year mine decommissioning, getting the rate wrong can shift the reported figure by tens of millions.

Future Events

Anticipated changes in legislation or technology that could reduce settlement cost are factored in only when those changes are virtually certain.⁴ Speculation that a new regulation might lower cleanup costs five years out does not justify reducing today’s provision.

Information surfacing between the reporting date and the date the statements are authorized for issue may still require an adjustment. If it relates to conditions that existed at the reporting date, IAS 10 treats it as an adjusting event and the provision must be updated accordingly.⁶

Reviewing Provisions at Each Reporting Date

A provision is not a set-and-forget entry. Every provision must be reviewed at each reporting date and the carrying amount adjusted to the current best estimate. If an outflow is no longer probable, the provision is reversed entirely. This ongoing reassessment is where auditors focus, because the judgment involved is inherently subjective.

Reimbursements From Third Parties

An insurer or another third party may reimburse some or all of the settlement cost. IAS 37 permits a separate asset for the expected reimbursement, but only when recovery is virtually certain. That is a much higher bar than the “more likely than not” test used for the provision itself. The reimbursement asset also cannot exceed the amount of the provision.¹

Obligation Types the Standard Singles Out

Three categories come up often enough that IAS 37 gives them dedicated rules.

Onerous Contracts

A contract is onerous when the unavoidable costs of meeting the obligations exceed the economic benefits expected from it.¹ The provision is measured at the lower of the cost of fulfilling the contract or the penalties and compensation payable for walking away.

The 2022 amendment clarified that the “cost of fulfilling” a contract includes not just incremental costs like direct labor and materials but also an allocation of other directly related costs, such as depreciation on equipment used to perform the work. Before booking the onerous-contract provision, any impairment loss on assets dedicated to the contract must be recognized first.

Restructuring

Recognizing a restructuring provision requires a detailed formal plan identifying the businesses concerned, the locations affected, and the approximate number of employees who will be compensated for termination. The plan on paper is not enough on its own: the entity must also raise a valid expectation among those affected that the restructuring will happen, by starting to implement it or announcing its main features.¹

Costs related to ongoing operations are excluded. Retraining or relocating staff who will continue with the company are not restructuring costs, even if they only arise because of the restructuring. The provision covers obligations flowing directly from exiting a business or closing a location, not the cost of adapting what remains.

Decommissioning and Environmental Restoration

Long-lived assets like oil platforms, mines, and chemical plants often carry an obligation to restore the site or remove equipment at end of life. The provision is recognized when the initial damage or installation occurs, not years later when the cleanup begins. These obligations typically involve large sums and complex assumptions about future labor, regulation, and discount rates.

IFRIC 1 governs later changes in the estimate. Revisions to the timing or amount of decommissioning costs, or changes in the market discount rate, require corresponding adjustments to both the provision and the related asset.⁷ Over an asset’s life, these re-estimates can happen many times.

Where Provisions Stop and Contingent Liabilities Begin

When a potential obligation fails the recognition test, it may still belong in the notes as a contingent liability. IAS 37 puts contingent liabilities into two buckets: possible obligations whose existence depends on uncertain future events, and present obligations that are not recognized because an outflow is not probable or the amount cannot be reliably estimated.¹

Disclosure is required unless the possibility of an outflow is remote. For each class of contingent liability, the entity discloses the nature of the obligation and, where practicable, an estimate of the financial effect, the uncertainties around amount or timing, and the possibility of any reimbursement.⁴ If the possibility is remote, no disclosure is required.

The result is a three-tier framework. Probable outflow: recognize a provision. Possible outflow: disclose a contingent liability. Remote outflow: do nothing.

Disclosure Requirements

For each class of provision, the entity provides a reconciliation of the movement during the period: opening carrying amount, new provisions recognized, amounts used against the provision, amounts reversed as no longer needed, the unwinding of any discount, and the closing balance.⁴

Each class also needs a narrative covering the nature of the obligation, the expected timing of outflows, major uncertainties about amount or timing, and key assumptions about future events. Where discounting has a material effect, the discount rate used must be disclosed. Any recognized reimbursement asset is disclosed separately.

In extremely rare cases, disclosing the required information could seriously prejudice the entity’s position in a dispute. IAS 37 permits an exemption, but the entity must still disclose the general nature of the dispute and explain why the information has been withheld.⁴ This is genuinely rare, and auditors will push back hard on any attempt to invoke it without strong justification.

1
IFRS. IAS 37 Provisions, Contingent Liabilities and Contingent Assets
2
IFRS Foundation. IAS 37 Provisions, Contingent Liabilities and Contingent Assets
3
IFRS Foundation. IAS 37 Provisions, Contingent Liabilities and Contingent Assets Illustrative Examples
4
IFRS Foundation. IAS 37 Provisions, Contingent Liabilities and Contingent Assets
5
IFRS Foundation. Provisions – Discount Rates Application Guidance
6
IFRS Foundation. IAS 10 Events After the Reporting Period
7
IFRS. IFRIC 1 Changes in Existing Decommissioning, Restoration and Similar Liabilities