What Is a Constructive Obligation in Accounting?

A constructive obligation in accounting is a liability that arises from an entity’s own conduct rather than from a contract or a statute: through an established pattern of past practice, a published policy, or a sufficiently specific current statement, the entity has signaled that it will accept certain responsibilities, and outside parties now have a valid expectation that it will follow through. Under IFRS, it is recognized as a provision on the balance sheet once three tests are met at the same time: a past event has created a present obligation, an outflow of economic resources is more likely than not, and the amount can be reliably estimated. Those criteria come from IAS 37.¹

What Makes an Obligation Constructive

IAS 37 defines a constructive obligation through two linked conditions. The entity has signaled to outside parties that it will accept certain responsibilities, and those parties now have a valid expectation that the entity will follow through.¹ The signal can take three forms: an established pattern of past practice, a published policy, or a sufficiently specific current statement by management.

Take a retailer that has, for years, allowed customers to return merchandise for a full refund well past the written return window. Customers have come to rely on that practice. The retailer’s consistent behavior has created a constructive obligation for those returns, even though no written policy promises them. Compare that with a CEO mentioning at a conference that the company “hopes to do more for the community next year.” Hope is not a commitment, and no reasonable outsider would treat it as one.

Management’s private intent is never enough on its own. The obligation crystallizes only when the intent becomes visible to the people who would be affected by it. A board resolution to fund a voluntary severance package, kept in the minutes but never communicated to employees, does not create a constructive obligation. Once the company announces the package to staff, it does.

How It Differs From a Legal Obligation

A legal obligation gives a third party the power to force performance, typically through a court or a regulator. It comes from a contract, a statute, or another operation of law. A constructive obligation is self-imposed. The enforcement mechanism is reputational and commercial rather than judicial: if the entity walks back a commitment its stakeholders relied on, it risks losing customers, employees, or community goodwill.

An environmental example illustrates the split. If the EPA orders a company to decommission a contaminated factory site, the resulting cleanup liability is legal. If that same company has a published environmental policy committing it to remediate nearby waterways, and local residents have come to expect that work, the cleanup cost is constructive. Both end up on the balance sheet once the recognition criteria are met.²

The distinction matters for timing. A legal obligation usually has a clear triggering event: the contract is signed, the regulation takes effect. A constructive obligation can build gradually through repeated behavior, making the “when” question harder to pin down. That ambiguity is exactly why auditors pay close attention to it.

The Three Recognition Tests Under IAS 37

IAS 37 paragraph 14 sets out three conditions that must be satisfied simultaneously before an entity records a provision. If any one is missing, the obligation stays off the balance sheet, though it may still need disclosure as a contingent liability.¹

A Present Obligation From a Past Event

The entity must have a present obligation arising from a past “obligating event.” For a constructive obligation, the obligating event is whatever action created the valid expectation: announcing the restructuring plan, maintaining the return policy for the hundredth time, or publishing the environmental remediation commitment. The test is practical rather than legalistic. Could the entity walk away from the expenditure today without significant consequences? If the answer is no, a present obligation exists.

A Probable Outflow of Resources

It must be probable that settling the obligation will require the entity to give up cash, inventory, services, or another economic resource. Under IAS 37, “probable” means more likely than not, a probability greater than 50 percent. For a single obligation, this assessment is straightforward. For a class of similar obligations such as product warranties, IAS 37 says you assess the group as a whole: even if the likelihood that any individual claim gets filed is low, it may still be probable that some outflow will be needed to settle the class collectively.¹

A Reliable Estimate of the Amount

The entity must be able to quantify the obligation with enough reliability to put a number on the balance sheet. Precision is not required; a reasonable range supported by historical data, market information, or expert judgment is enough. A commitment too vague or speculative to measure does not qualify, no matter how probable the outflow. IAS 37 notes that cases where no reliable estimate is possible are “expected to be extremely rare.”

All three tests must be satisfied at the same point in time. A company-wide bonus announcement, for example, becomes a recognized constructive obligation only at the moment the announcement is made (creating the present obligation), the payout is more likely than not (probable outflow), and the total cost can be reasonably calculated (reliable estimate).

Restructuring: The Clearest Real-World Case

Restructuring is the scenario where constructive obligation recognition matters most in practice. IAS 37 sets out specific conditions: a constructive obligation to restructure arises only when the entity has both a detailed formal plan and has raised a valid expectation in the affected parties that the restructuring will happen.³

The detailed formal plan must identify at least the following:

The business or division affected
The principal locations involved
The approximate number and functions of employees whose roles will be terminated
The expenditures the restructuring will require
The timeline for when implementation will begin

Having a plan on paper is necessary but not enough. The entity must also start implementing the plan or announce its main features to those affected, in enough detail that employees, customers, and suppliers can reasonably conclude the restructuring is going ahead.³ A board decision made in December does not create an obligation at year-end if nothing has been communicated externally by that date.

Timing discipline matters. If the entity announces a restructuring but plans to start implementation years from now, the announcement is unlikely to create a valid expectation, because stakeholders can reasonably assume the entity still has time to change its mind. The implementation window needs to be short enough that significant changes to the plan would be impractical.

Measuring the Provision

Once all three recognition tests are satisfied, the provision is measured at the best estimate of what it will cost to settle the obligation at the reporting date. Best estimate means the amount the entity would rationally pay to settle or transfer the obligation, taking risks and uncertainties into account.²

Where a provision involves a large number of similar items, such as warranty claims or return obligations, the best estimate is typically calculated using an expected-value approach: weighting each possible outcome by its probability and summing the results. For a single obligation, the most likely individual outcome may be the best estimate, although the entity still considers other possible outcomes that could push the final cost higher or lower.

IAS 37 requires the provision to be discounted to its present value.² If a $1 million environmental cleanup is expected in five years, the entity records a present-value amount today that is lower than $1 million. Over time the discount unwinds and the provision grows toward the settlement amount, with the unwinding recognized as a finance cost in the income statement.

Estimates are revisited at every reporting date. If the expected cost increases, the entity records additional expense. If it decreases, the provision is partially reversed, improving that period’s earnings. Adjustments happen in the period the new information becomes available, not retroactively. IAS 37 also prohibits provisions for future operating losses, since no present obligation exists for losses that haven’t happened yet.²

When the Tests Are Not Met

Not every possible obligation ends up on the balance sheet. When the outflow of resources is possible but not probable, or when the amount cannot be reliably estimated, IAS 37 classifies the item as a contingent liability. A contingent liability is not recognized in the statement of financial position. Instead, the entity discloses it in the notes to the financial statements, unless the possibility of any outflow is remote.²

That creates a three-tier outcome for any potential constructive obligation:

Probable outflow and reliably estimable: recognize a provision on the balance sheet.
Possible but not probable, or not reliably estimable: disclose as a contingent liability in the notes.
Remote possibility of outflow: no recognition and no disclosure required.

The classification can shift over time. A contingent liability disclosed one quarter may become a recognized provision the next if new facts push the probability above the threshold. Entities need to reassess at each reporting date.

How US GAAP Handles the Same Idea

If your entity reports under US GAAP rather than IFRS, the treatment is notably narrower. US GAAP does not have a general provision for constructive obligations the way IAS 37 does. Constructive obligations are recognized only when a specific topic in the FASB Accounting Standards Codification requires it.⁴

The closest analog is ASC 450, which governs loss contingencies. Under ASC 450-20-25-2, a loss contingency is accrued when two conditions are met: it is probable that a liability has been incurred at the financial statement date, and the amount can be reasonably estimated.⁵ “Probable” does similar work in both frameworks, but the threshold is materially different. Under US GAAP, probable means “likely to occur,” generally interpreted as a likelihood above roughly 70 percent. Under IFRS, the bar is just above 50 percent. An obligation can qualify for recognition under IFRS well before it qualifies under US GAAP.

Measurement also diverges. When US GAAP produces a range of possible loss amounts and no single figure within the range is a better estimate than any other, ASC 450-20-30-1 requires the entity to accrue the minimum amount in the range.⁶ Under IAS 37, the entity uses its best estimate, which for large populations of similar items typically means an expected-value calculation that can land well above the minimum. ASC 450 also does not generally require discounting.

The restructuring area highlights the practical gap. Under IAS 37, announcing a detailed restructuring plan to the people affected can create a constructive obligation recognized immediately. Under ASC 420, a liability for exit or disposal costs is recognized only when it is actually incurred, not when management commits to a plan. A board resolution to restructure, standing alone, does not create a present obligation under ASC 420, because the entity has not yet transferred an economic benefit to anyone. US GAAP entities often recognize restructuring provisions later than their IFRS counterparts.

Tax Treatment Is Not Automatic

Recognizing a constructive obligation for financial reporting does not automatically create a tax deduction. Under US federal tax rules, an accrued expense is deductible only after the all-events test under IRC Section 461(h) is satisfied. That test requires three things: all events establishing the liability have occurred, the amount can be determined with reasonable accuracy, and economic performance has taken place.

The first prong is where most constructive obligations hit a wall. A liability must be fixed and determinable to satisfy the all-events test. If the obligation is still contingent on a future event, say, customers actually submitting return requests or terminated employees actually claiming their severance, the liability may not be fixed for tax purposes even though it qualifies for accrual under IAS 37 or ASC 450. Courts have consistently held that anticipated claims not yet filed are contingent and do not satisfy the test.

A recurring-item exception exists for expenses where the all-events test is met by year-end and economic performance occurs within roughly eight and a half months after the close of the tax year. To qualify, the expense must be recurring, and the entity must have consistently treated similar items the same way in prior years. The exception relaxes the timing of economic performance but does not excuse the entity from proving the liability is fixed and the amount is estimable.

The practical result is a timing difference between the book provision and the tax deduction, often creating a deferred tax asset that unwinds as the obligation is actually settled.

1
IFRS Foundation. International Accounting Standard 37 Provisions, Contingent Liabilities and Contingent Assets
2
IFRS Foundation. IAS 37 Provisions, Contingent Liabilities and Contingent Assets
3
IFRS Foundation. Indicative Drafting – IAS 37 Staff Paper
4
Deloitte Accounting Research Tool. Appendix A – Differences Between US GAAP and IFRS Accounting Standards
5
FASB. Contingencies Topic 450 Disclosure of Certain Loss Contingencies
6
Deloitte Accounting Research Tool. 2.4 Measurement