What is Constructive Obligation?
IAS 37.10 defines a constructive obligation as one that derives from an entity's actions where, by an established pattern of past practice, published policies, or a sufficiently specific current statement, the entity has indicated to other parties that it will accept certain responsibilities, and as a result has created a valid expectation that it will discharge those responsibilities. The definition matters because it extends IAS 37's recognition criteria beyond contracts and legislation.
The recognition test is the same as for any provision: a present obligation from a past event, probable outflow of resources, and a reliable estimate (IAS 37.14). What differs is the evidence. For a legal obligation, the auditor looks at contracts, statutes, or court rulings. For a constructive obligation, the auditor looks at board minutes, press releases, internal communications to staff, and historical behaviour. ISA 540.13(b) requires the auditor to evaluate whether the data supporting the estimate is relevant and reliable. When the obligation's existence rests on management's stated intentions rather than a signed contract, that evaluation carries more judgment.
IAS 37.72 adds a specific gate for restructuring: a constructive obligation arises only when the entity has both a detailed formal plan and has raised a valid expectation in those affected by starting implementation or announcing the plan's main features.
Key Points
- A constructive obligation exists when the entity has created a valid expectation in affected parties that it will act, even without a legal requirement to do so.
- Recognition requires both a reliable estimate of the outflow and a probability threshold above 50% that the outflow will occur.
- Restructuring announcements are the most common trigger; IAS 37.72 sets detailed conditions before a restructuring constructive obligation exists.
- Failing to recognise a constructive obligation understates liabilities and overstates profit in the period the obligation crystallises.
Worked example: Schäfer Elektrotechnik AG
Client: German electronics manufacturer, FY2025, revenue €310M, IFRS reporter. In November 2025, Schäfer's board approves a plan to close its Leipzig facility (140 employees) and consolidate production in Stuttgart. The finance team asks whether a provision is required at 31 December 2025.
Step 1 — Assess whether a detailed formal plan exists
The board resolution specifies the location to be closed, the number of affected employees (140), the expected closure date (Q2 2026), the estimated redundancy payments (€4.2M based on German statutory severance and Schäfer's established Sozialplan practice), and the estimated lease termination cost (€0.9M for early exit of the Leipzig lease).
Documentation note: obtain the board resolution dated 18 November 2025 and verify it contains the elements required by IAS 37.72(a): the business concerned, the principal locations affected, approximate number of employees who will be compensated, the expenditures to be undertaken, and the timeline.
Step 2 — Assess whether a valid expectation has been created
On 25 November 2025, Schäfer issued an internal communication to all Leipzig staff detailing the closure plan and announcing the start of consultations with the works council (Betriebsrat). By 31 December 2025, initial Sozialplan negotiations are under way.
Documentation note: file the internal staff communication (dated 25 November 2025) and works council meeting minutes as evidence that the entity raised a valid expectation per IAS 37.72(b). Compare the timeline to confirm the announcement occurred before the reporting date.
Step 3 — Measure the provision
Schäfer estimates the total restructuring cost at €5.1M (€4.2M redundancy plus €0.9M lease exit). The redundancy estimate uses the entity's established severance formula, which has been applied consistently in two prior facility closures (2018 and 2021). The lease exit cost is based on the contractual early-termination clause.
Documentation note: record the €5.1M best estimate per IAS 37.36. Cross-reference the severance calculation to the Sozialplan formula and the two prior closures for consistency. Record the lease termination penalty from the Leipzig lease agreement, clause 14.2.
Step 4 — Evaluate the probability threshold
The board resolution is approved, staff have been notified, and works council consultations are active. Reversal at this stage would damage Schäfer's credibility with employees and regulators. The outflow is probable.
Documentation note: document the probability assessment, noting that implementation has commenced and reversal is not realistic given the stage of works council engagement.
Conclusion: Schäfer recognises a restructuring provision of €5.1M at 31 December 2025 because the IAS 37.72 conditions (detailed formal plan plus valid expectation in affected parties) are both satisfied before the reporting date, and the estimate is traceable to contractual terms and established practice.
Why it matters in practice
Teams frequently recognise a restructuring provision based on a board decision alone, without verifying that the entity has communicated the plan to affected parties. IAS 37.72(b) requires a valid expectation to have been created before the reporting date. A board resolution that remains confidential at year-end does not meet this condition, regardless of how detailed the plan is.
Practitioners sometimes confuse a constructive obligation with a business intention. An entity that has historically provided ex gratia redundancy payments but has not announced a current plan, and has no pattern specific to the current situation, does not have a constructive obligation. IAS 37.17 is clear that a management decision alone does not create a present obligation unless it has been communicated in a sufficiently specific manner to those affected.
Constructive obligation vs [legal obligation](/glossary/legal-obligation)
| Dimension | Constructive obligation | Legal obligation |
|---|---|---|
| Source | Entity's own actions: past practice, published policies, specific announcements | Contract, legislation, or other operation of law |
| Evidence for the auditor | Board minutes, staff communications, press releases, history of similar payments | Signed contracts, statutory requirements, court orders, legal opinions |
| Judgment intensity | High: requires assessment of whether a "valid expectation" exists in affected parties | Lower: the obligation's existence is usually determinable from the legal instrument |
| Common examples | Restructuring announcements, established bonus practices, published environmental remediation commitments, customer refund policies with no contractual basis | Warranty obligations per contract terms, statutory redundancy payments, tax liabilities, court-ordered damages |
| Derecognition trigger | Entity communicates that it will no longer honour the commitment (and affected parties accept this) | Legal instrument is discharged, expires, or is cancelled |
The distinction affects audit strategy. For a legal obligation, the auditor can confirm existence through external legal confirmation or contract inspection. For a constructive obligation, existence depends on the entity's communications and behaviour, which means the auditor relies more heavily on inquiry, inspection of internal documents, and evaluation of past practice under ISA 500.
Related terms
Frequently asked questions
How do I document a constructive obligation in the audit file?
Record the specific evidence that creates the valid expectation: the board resolution, staff communications, published policies, or pattern of past practice. IAS 37.85(b) requires disclosure of the nature of the obligation, so the audit file should contain enough detail to support both the recognition decision and the disclosure.
Does a constructive obligation apply outside restructuring?
Yes. Restructuring is the most common example, but constructive obligations also arise from published environmental remediation policies, established bonus payment patterns, and public commitments to customer remediation programmes. IAS 37.10 does not limit constructive obligations to any single type of event. The entity's history of honouring similar commitments is the deciding factor.
When does a constructive obligation stop being recognised?
IAS 37.59 requires the entity to review provisions at each reporting date and adjust them to reflect the current best estimate of expenditure. If the obligation is no longer probable (for instance, the restructuring plan is formally abandoned and affected parties are informed), the provision is reversed. The auditor verifies that the reversal is supported by evidence of changed circumstances, not by a quiet management decision to defer.