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. Under IAS 37, you recognize one as a provision on the balance sheet when three conditions are satisfied at the same reporting date: 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.¹ US GAAP handles the same idea more narrowly, so the timing of recognition can shift depending on which framework the entity reports under.

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 the form of an established pattern of past practice, a published policy, or a sufficiently specific current statement by management.

The “valid expectation” element is what separates a real obligation from a vague aspiration. If a retailer has for years accepted customer returns well past its written return window, customers have come to rely on that practice. The retailer has created a constructive obligation for those returns even though no written policy promises them. Compare that with a CEO telling a conference audience 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.

Internal intent is never enough. The obligation crystallizes only when intent becomes visible to the people who would be affected. 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 package is announced to staff, it does.

How a Constructive Obligation Differs From a Legal One

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

Take an environmental example. If the EPA orders a company to decommission a contaminated factory site, the cleanup cost is a legal obligation. If the 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 a constructive obligation. Both end up on the balance sheet if the recognition criteria are met.²

Timing is where the two diverge. A legal obligation usually has a clean triggering event: the contract is signed, the regulation takes effect. A constructive obligation can build gradually through repeated behavior, which makes the “when” question harder to pin down and is one reason auditors scrutinize it so closely.

The Three Recognition Criteria Under IAS 37

IAS 37 paragraph 14 requires three conditions to be met at the same time before an entity records a provision for a constructive obligation. If any one is missing, the item stays off the balance sheet, though it may still require disclosure as a contingent liability.¹

A Present Obligation From a Past Event

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

Probable Outflow of Resources

Settling the obligation must probably require the entity to give up cash, inventory, services, or some other economic resource. Under IAS 37, “probable” means more likely than not, which translates to a probability greater than 50 percent. For a single obligation the assessment is straightforward. For a class of similar obligations like product warranties, you assess the group as a whole: even if the chance any individual claim gets filed is low, it may well 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 doesn’t 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 instance, becomes a recognized constructive obligation only once the announcement has been made (creating the present obligation), the payout is more likely than not, and the total cost can be reasonably calculated.

When the Criteria Are Not Met

Not every potential obligation ends up on the balance sheet. When an outflow 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. It is disclosed in the notes to the financial statements, unless the possibility of any outflow is remote.²

That creates three possible outcomes 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.

Classification can shift. A contingent liability disclosed one quarter may become a recognized provision the next if new facts push the probability above the threshold, which is why entities reassess at each reporting date.

How US GAAP Treats the Same Concept

If the entity reports under US GAAP rather than IFRS, treatment is noticeably narrower. US GAAP has no general provision for constructive obligations the way IAS 37 does. Instead, 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 it is probable a liability has been incurred at the financial statement date and the amount can be reasonably estimated.⁴ The word “probable” does similar work in both frameworks, but the threshold differs. 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. That gap means 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 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.

Restructuring highlights the practical gap. Under IAS 37, announcing a detailed restructuring plan to the people affected can create a constructive obligation that is recognized immediately. Under US GAAP’s 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 therefore often recognize restructuring provisions later than their IFRS counterparts.

Restructuring: Where This Comes Up Most

Restructuring is the setting where constructive obligation recognition matters most in practice under IFRS. IAS 37 says a constructive obligation to restructure arises only when the entity has both a detailed formal plan and has raised a valid expectation in affected parties that the restructuring will happen.⁶

The detailed formal plan has to 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.
When implementation will begin.

A plan on paper is necessary but not sufficient. 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 an announcement sets implementation years into the future, it probably won’t 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 and Updating the Provision

Once all three recognition criteria 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 covers 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.² A $1 million environmental cleanup expected in five years is recorded today at a present value 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. This is one more area where IFRS and US GAAP diverge: ASC 450 does not generally require discounting of loss contingencies.

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. These adjustments happen in the period 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.²

Why the Tax Deduction Does Not Follow Automatically

Recognizing a constructive obligation for financial reporting purposes does not by itself 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 still depends on a future event, such as 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. 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
Deloitte Accounting Research Tool. Appendix A – Differences Between US GAAP and IFRS Accounting Standards
4
FASB. Contingencies Topic 450 Disclosure of Certain Loss Contingencies
5
Deloitte Accounting Research Tool. 2.4 Measurement
6
IFRS Foundation. Indicative Drafting – IAS 37 Staff Paper