Key points
- A legal obligation arises from a contract, statute, court ruling, or regulatory order. It does not arise from the entity's voluntary conduct or past practice.
- Recognition requires the same criteria as any provision: present obligation from a past event, probable outflow (above 50%), a reliable estimate of the amount, and no right of reimbursement that eliminates the exposure.
- The existence of a legal obligation is usually easier to verify than a constructive obligation because a signed document or statutory text confirms it.
- Warranty provisions and environmental remediation mandated by law are among the most common legal obligations that auditors test on mid-market engagements.
What is a legal obligation?
We've seen this pattern on about half the mid-market engagements we've worked: the entity has a binding contract clause or a regulatory order sitting in the legal folder, but the provisions schedule carries the same number as last year (SALY) with no updated assessment. The file should tell a story of how the team confirmed the obligation still exists and whether the amount has changed. When it does not, review notes follow.
IAS 37.10 identifies a legal obligation as one that derives from a contract (through its explicit or implicit terms) or from legislation. Once a legal obligation exists, the entity applies the standard recognition test at IAS 37.14 : present obligation arising from a past event, probable outflow of resources, a reliable estimate of the amount, and no reimbursement asset that would offset it. If the probability gate fails, the entity either discloses a contingent liability or does nothing (when the outflow is remote).
For the auditor, the evidence trail is comparatively direct. A contract clause sets out the exposure. A statutory requirement identifies the obligation. ISA 500.9 requires that audit evidence be sufficient and appropriate, and for legal obligations the primary sources are external: signed agreements, legal opinions, regulatory notices, and correspondence from counsel obtained under ISA 501.10 . The judgment load is lighter than for a constructive obligation, where the auditor must assess whether the entity's behaviour has created a valid expectation in third parties. That said, measurement can still carry significant estimation uncertainty (particularly for long-tail warranty populations or environmental clean-up liabilities where the cash outflows stretch over a decade or more).
Worked example: Rossi Alimentari S.p.A.
Client: Italian food production company, FY2025, revenue EUR 67M, IFRS reporter. In March 2025, Italian environmental authorities (ARPA) inspected Rossi's processing facility near Parma and issued a remediation order for soil contamination caused by wastewater discharge. The order requires Rossi to complete remediation by December 2027. Rossi's environmental consultant estimates the total clean-up cost at EUR 1.8M to EUR 2.4M, with a most likely outcome of EUR 2.1M. No insurance coverage applies.
Step 1: identify the obligation type
The ARPA order is a legal instrument. The past event is the contamination from Rossi's operations. The obligation is legal, not constructive, because it arises from the operation of Italian environmental law (D.Lgs. 152/2006) and a specific regulatory order.
Step 2: assess probability of outflow
The order is legally binding. Non-compliance carries enforcement penalties. An outflow of resources is virtually certain, well above the "more likely than not" threshold.
Step 3: measure the provision
This is a single obligation with a range of outcomes. The most likely outcome is EUR 2.1M. The range extends from EUR 1.8M to EUR 2.4M, with the upper end reflecting the possibility of additional contamination discovered during excavation. Management selects EUR 2.1M as the best estimate per IAS 37.40 . The remediation timeline is 2.5 years. Discounting at a pre-tax rate of 3.2% (Italian government bond yield adjusted for the obligation's specific risk) produces a present value of approximately EUR 1.94M.
Step 4: verify measurement inputs
The environmental consultant's estimate rests on soil sampling results from April 2025 and comparable remediation costs at two Italian food-processing sites in the same region (completed 2022 and completed 2024). These external inputs are corroborated by Rossi's site-specific excavation plan. ISA 540.13 (b) requires the auditor to evaluate whether the data is relevant and reliable.
Conclusion: Rossi recognises a provision of EUR 1.94M (present value) at 31 December 2025 because the legal obligation is confirmed by a binding regulatory order and the outflow is virtually certain. The measurement rests on site-specific data corroborated by comparable remediation costs.
Why it matters in practice
- Teams sometimes fail to distinguish between the legal obligation itself and the measurement uncertainty around it. A binding court order or regulatory notice establishes that the obligation exists. The remaining question is how much. IAS 37.25 states that it is only in extremely rare cases that no reliable estimate can be made. Practitioners who defer recognition because the estimate is imprecise (while the legal instrument is unambiguous) misapply the standard. The obligation should be recognised with a best estimate, and the uncertainty disclosed.
- Discount rates on long-duration legal obligations are frequently either omitted or borrowed from the entity's weighted average cost of capital. IAS 37.47 specifies a pre-tax rate reflecting current market assessments of the time value of money and the risks specific to the liability. Using the entity's WACC overstates the discount (because WACC includes equity risk that does not apply to a provision) and understates the recognised amount.
- In our experience, the genuinely hard part is not confirming that a legal obligation exists. It is getting management to update the number. People grow attached to the provision figure they set in year one, and pushing back on a stale estimate feels adversarial when the relationship with the client is new. But the file should tell a story, and a story with the same number for three years running and no supporting narrative is a story that does not hold up under review.
Legal obligation vs constructive obligation
| Dimension | Legal obligation | Constructive obligation |
|---|---|---|
| Source | Contract, legislation, court order, or other operation of law | Entity's established pattern of past practice or published policies that create a valid expectation in third parties |
| Evidence for the auditor | Signed contracts, statutory text, court orders, regulatory notices, legal opinions | Board minutes, staff communications, press releases, history of similar payments |
| Judgment required | Lower on existence (legal instrument confirms it); can be high on measurement | High on both existence (did the entity create a valid expectation?) and measurement |
| Common examples | Warranty obligations per contract terms, environmental remediation mandated by statute, court-ordered damages, statutory redundancy payments | Restructuring announcements, established bonus practices, published environmental commitments without legal mandate, voluntary redundancy programmes |
| Derecognition trigger | Legal instrument is discharged or expires | Entity communicates withdrawal and affected parties accept it |
The distinction matters when the auditor designs procedures. For a legal obligation, the primary evidence is external (contracts and court documents). For a constructive obligation, the auditor must evaluate internal communications and historical patterns of behaviour to determine whether the entity created a reasonable expectation in third parties. Both can produce the same provision on the balance sheet, but the WPs look different.
Related terms
Related tools
Related reading
Frequently asked questions
How do I document a legal obligation in the audit file?
Record the legal instrument that creates the obligation (contract clause, statute, court order, or regulatory notice) and the date the obligation arose. Document the entity's basis for concluding that settlement is probable. IAS 37.85(a) requires disclosure of the nature of the obligation, so the audit file should contain the source document and enough context to support the disclosure wording.
Does a legal obligation always result in a provision?
No. A legal obligation meets only the first criterion of IAS 37.14. If the outflow is not probable (for example, a disputed contractual claim where legal counsel assesses the likelihood of payment as possible but not probable), the entity discloses a contingent liability instead. The legal nature of the obligation does not override the probability gate.
When should the auditor obtain an external legal opinion on a legal obligation?
ISA 501.10 requires the auditor to request that management instruct legal counsel to communicate directly with the auditor regarding litigation and claims. For material legal obligations where the amount or probability is uncertain, an external legal opinion provides the most persuasive evidence. The auditor evaluates the response under ISA 501.11 and considers a scope limitation if counsel refuses to respond.