Liquidated damages for delay as variable consideration reducing the transaction price · IFRS 15

In plain words

Contracts usually charge the contractor a fixed amount per day of delay, called liquidated damages, often up to a cap. The question is whether to wait until the client actually deducts them. Liquidated damages are variable consideration, so once a delay is probable, the contractor estimates the expected damages, net of any extension of time likely to be granted, and reduces revenue, rather than booking a penalty expense later. The estimate is updated each period.

Why it matters

Booking liquidated damages only when formally deducted by the employer from a certified payment (rather than estimating and reflecting them as a reduction of transaction price as soon as a delay obligation is probable) overstates revenue and margin in the periods leading up to the deduction, giving a false impression of on-track performance right up until the cash impact suddenly appears.

Diagnostic questions

Is the project tracking behind the contractual completion or milestone dates in a way that makes a liquidated-damages exposure probable rather than merely possible? Is there a reliable basis, such as the current schedule or a formal delay analysis, to estimate the net number of delay days and the resulting LD amount? Are there approved, or likely-to-be-approved, extension of time claims for employer-caused delays that would reduce or eliminate the gross LD exposure? Is the LD reduction to transaction price being estimated as soon as it becomes probable, rather than only recorded when the employer formally deducts it from a certified payment?

Recognition

Monitor project progress against the contractual completion and milestone dates that trigger liquidated damages (LDs), and identify as early as possible when a delay resulting in an LD exposure becomes probable.
Assess entitlement to extension of time (EOT) for employer-caused or excusable delays, which would reduce or eliminate the LD exposure, do not assume the full contractual daily/weekly rate applies without netting probable EOT days.
As soon as an LD-triggering delay (net of probable EOT) is probable, recognize the expected LDs as a reduction of the transaction price (and therefore of revenue), not as a separate expense or penalty recognized only on formal deduction.
Update the transaction price each reporting period as the actual delay position, EOT claims and negotiations evolve.
Distinguish LDs (a variable consideration adjustment to price for a contractor's own delay) from claims for extension-related costs the contractor may be pursuing against the employer for employer-caused delay, which follow the separate claims/constraint consideration.

Measurement

Estimate the LD reduction using the expected value or most-likely-amount method based on the contractual daily/weekly LD rate and the best current estimate of net delay days (gross delay less probable extension of time), applying the same constraint principle used for other variable consideration: include in the transaction price reduction only the amount for which significant reversal is not highly probable to occur. Cap the cumulative LD deduction at any contractual maximum (a cap on LDs is common) and reassess as EOT claims are resolved.

Presentation & disclosure

Disclose: (1) the accounting policy for estimating and recognizing liquidated damages as a variable consideration reduction of transaction price; (2) the amount of revenue reduction recognized for LDs in the period and cumulatively; (3) significant judgments in assessing net delay days, extension of time entitlement, and the constraint; (4) any contractual cap on LDs and how it was applied; (5) status of unresolved EOT claims that could affect the LD estimate.

Common mistakes

Waiting until the employer formally deducts LDs from a certified payment before recognizing any reduction in revenue, rather than estimating and reflecting the expected LD exposure as soon as the delay becomes probable
applying the full gross delay period to the LD calculation without netting probable extension-of-time days the contractor is likely entitled to
ignoring a contractual cap on LDs and estimating an exposure beyond that ceiling
treating LDs as a separate finance or penalty expense below the gross margin line instead of a reduction of revenue/transaction price.

Simple example

A contract has an LD rate of SAR 50,000 per day of delay, capped at SAR 5,000,000. At year-end, the project is 60 days behind the contractual completion date; the contractor has submitted an EOT claim for 25 days due to employer-caused delays, and based on the strength of supporting records, management assesses 20 of those days as highly probable to be granted. Net expected delay attributable to the contractor = 60 - 20 = 40 days. Expected LD exposure = 40 x 50,000 = SAR 2,000,000, which is below the SAR 5,000,000 cap.
Journal entry to recognize the LD reduction in transaction price:
Dr Revenue from construction contracts (transaction price reduction) 2,000,000
Cr Contract liability / provision for liquidated damages 2,000,000
If the EOT claim is subsequently fully granted for all 25 days in the following period, net expected delay reduces to 35 days (60-25), and the LD exposure reduces to 35 x 50,000 = SAR 1,750,000, requiring a partial reversal:
Dr Contract liability / provision for liquidated damages 250,000
Cr Revenue from construction contracts 250,000

Professional judgment

Estimating the net delay days requires a genuine, contemporaneous critical-path delay analysis distinguishing contractor-caused, employer-caused (EOT-eligible) and neutral/excusable delay events, which is a specialized planning/scheduling exercise, not a purely accounting judgment, accounting should rely on this analysis rather than a simplistic gross-delay assumption. The probability threshold for including EOT days as a netting item mirrors the same constraint used for other variable consideration and claims, and management's natural incentive to assume generous EOT recovery should be checked against the strength of contemporaneous notices and records, since EOT entitlement claims that fail contractual notice/time-bar requirements are much weaker than the underlying delay analysis might suggest.

Source basis

IFRS 15 · Revenue from Contracts with Customers

Paragraph references

IFRS 15.51–52IFRS 15.53IFRS 15.56–57

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

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.