Warranty and defects liability provisions · IAS 37 / IFRS 15

In plain words

After handover, the contractor usually must fix defects, often for 12 months. The question is whether this warranty is a cost to provide for or a separate service. A standard warranty that only confirms the work meets specifications needs a provision for expected repair costs. If the client could buy it separately, or it offers extra service, part of the price is deferred and recognised over the warranty period.

Why it matters

Confusing an assurance-type defects liability obligation (an IAS 37 cost provision) with a service-type extended warranty (a separate IFRS 15 performance obligation requiring transaction price allocation) leads to either overstating current-period revenue by failing to defer a portion of the price, or overstating current-period cost by over-providing for what is really a distinct paid service, both misstate margin in the period of substantial completion versus the defects liability period.

Diagnostic questions

Does the customer have the option to purchase the warranty separately, or does it provide a service beyond simply assuring the works comply with agreed specifications? If the warranty is assurance-type (the standard defects liability period), is a provision being recognized under IAS 37 based on probability-weighted expected rectification costs rather than a single worst-case estimate? If any element is service-type, has a portion of the transaction price been allocated to it as a separate performance obligation and deferred? Is there reliable historical defect-rate data across similar completed contracts to support the estimate?

Recognition

Determine the nature of the warranty: does the customer have the option to purchase the warranty separately, or does it provide a service beyond simply assuring the work complies with agreed specifications? If yes to either, it is (or includes) a service-type warranty.
For an assurance-type warranty (the default for standard defects liability/maintenance periods that merely confirm the completed work meets specifications), account for it under IAS 37: recognize a provision for the expected cost of rectification as the related revenue is recognized, not deferred as a separate performance obligation.
For a service-type warranty, or the service component of a combined warranty, allocate a portion of the transaction price to it as a separate performance obligation and recognize that portion of revenue over the warranty/service period.
Where a single warranty combines both elements and cannot be reasonably separated, account for the combined warranty as a single performance obligation under IFRS 15. 5. Reassess the provision each period against actual defect rectification experience across the population of completed contracts.

Measurement

Measure the assurance-type warranty provision using probability-weighted expected rectification costs derived from historical defect rates across the population of similar completed contracts, not a single worst-case scenario; discount if the effect of the time value of money is material given the length of the defects liability period. Measure the service-type warranty performance obligation's allocated transaction price using its standalone selling price (observable price if sold separately, or an estimated cost-plus-margin/adjusted market assessment approach if not).

Presentation & disclosure

Disclose: (1) the warranty provision balance and movements (additions, utilization, releases, unwinding of discount) separately from other provisions; (2) the accounting policy distinguishing assurance-type from service-type warranties; (3) the amount of transaction price allocated to service-type warranty performance obligations and its expected recognition timing; (4) key assumptions in estimating the provision (historical defect rates, cost per rectification); (5) nature and expected timing of outflows for the assurance-type warranty.

Common mistakes

Treating every contractual defects liability period as automatically a service-type warranty requiring transaction price deferral, when most are standard assurance-type provisions under IAS 37
conversely, failing to identify a genuinely separately-priced extended maintenance package as a distinct performance obligation
estimating the warranty provision using a single worst-case cost assumption rather than a probability-weighted estimate across the portfolio
not updating the provision rate as actual defect experience emerges from completed projects
releasing the entire warranty provision at the end of the defects liability period without evidence that no further claims will arise.

Simple example

A contractor completes a SAR 100,000,000 building contract with a standard 12-month assurance-type defects liability period; based on historical experience across similar contracts, expected rectification costs are estimated at 0.8% of contract value, i.e. SAR 800,000, recognized as the related revenue is recognized (at completion, for simplicity in this example).
Journal entry at completion:
Dr Warranty expense (cost of sales) 800,000
Cr Provision for warranty/defects liability 800,000
During the defects liability period, actual rectification costs of SAR 550,000 are incurred:
Dr Provision for warranty/defects liability 550,000
Cr Cash / accounts payable 550,000
At the end of the defects liability period, the unused SAR 250,000 provision is released as no further claims are expected:
Dr Provision for warranty/defects liability 250,000
Cr Warranty expense (cost of sales) 250,000

Professional judgment

The assurance-versus-service-type distinction can be genuinely unclear for maintenance or defects-liability arrangements that go beyond pure defect rectification to include periodic preventive servicing, the key question (does it provide a service in addition to assurance the goods comply with specifications) requires reading the actual scope of works in the defects liability clause, not just its label. Building a credible probability-weighted provision rate requires a sufficiently large and comparable population of completed, closed-out contracts; for a contractor with few large, heterogeneous projects, historical rates from one project may not be a reliable predictor for another with different specifications, subcontractors, or site conditions.

Source basis

IAS 37 / IFRS 15 · Provisions, Contingent Liabilities and Contingent Assets / Revenue from Contracts with Customers

Paragraph references

IFRS 15.B28–B33IAS 37.14

Verified against the official standard texts used in the IFRS Expert skill.

IAS 37 Provisions, Contingent Liabilities and Contingent Assets

Issued: September 1998 · Effective: 1 July 1999

IFRS 15 Revenue from Contracts with Customers

Issued: 28 May 2014 · Effective: 1 January 2018

Related issues

Educational and navigation content only. Not professional advice. Does not reproduce official IFRS/IAS text. Consult the authoritative standards and qualified professionals; professional judgment may still be required.