In plain words
Midway through a project, the client approves extra scope or a price change. How does this affect revenue? If the added work is distinct (separable from the rest) and priced at its standalone selling price, it is a separate contract. Otherwise, if the remaining work is distinct, it is treated prospectively. In construction it is usually part of one obligation, so revenue gets a cumulative catch-up.
Why it matters
The three-path modification test (separate contract, termination-and-replacement with cumulative catch-up, or prospective treatment) each produces a materially different revenue and margin pattern for the same underlying change in scope or price, and defaulting to the administratively simplest prospective treatment when the facts actually require a cumulative catch-up can hide or delay recognition of margin deterioration on the original scope.
Diagnostic questions
Does the modification add distinct goods or services priced at their standalone selling price, so it should be accounted for as a separate contract with no effect on the original one? If not distinct from the remaining goods or services, does the modification simply change the measure of progress on a single performance obligation, requiring a cumulative catch-up adjustment to revenue in the period of change? If it adds distinct goods or services not priced at standalone selling price and the remaining scope is distinct from what has already been transferred, should it instead be treated prospectively as terminating the old contract and creating a new one? Has the modification actually been approved, whether in writing, orally, or through customary business practice?
Recognition
- Confirm the modification is approved (creates new or changes existing enforceable rights and obligations), either in writing, orally, or through customary business practice.
- Test path one first: does the modification add distinct additional goods or services at a price that reflects their standalone selling price? If yes, account for it as a separate contract, with no effect on the original contract's accounting.
- If not a separate contract, test whether the remaining goods or services are distinct from those already transferred: if distinct, account for the modification as if it terminated the old contract and created a new one, allocating remaining consideration prospectively (prospective treatment).
- If the remaining goods or services are not distinct (they form part of a single performance obligation partially satisfied, the common case for construction scope changes), account for the modification as part of the original contract with a cumulative catch-up adjustment to revenue at the date of modification.
- Apply this sequential test to every approved modification individually; do not default to prospective treatment as a matter of administrative convenience when the facts point to cumulative catch-up.
Measurement
For cumulative catch-up treatment, recompute the updated transaction price and updated measure of progress (percentage complete) as of the modification date, and recognize the cumulative adjustment to revenue (and any related margin change) in the period of modification as a change in accounting estimate, not retrospectively. For prospective treatment, allocate the remaining transaction price (original consideration not yet recognized plus new consideration from the modification) to the remaining performance obligations without adjusting revenue already recognized. For a separate contract, apply normal initial recognition to the new contract with no effect on the existing one.
Presentation & disclosure
Disclose: (1) the accounting policy for classifying contract modifications and the significant judgments applied in the sequential test; (2) the amount and nature of cumulative catch-up adjustments recognized in the period, disaggregated from revenue relating to current-period performance; (3) significant modifications pending final pricing agreement and their expected classification; (4) the effect of modifications on remaining performance obligations and expected timing of recognition.
Common mistakes
- Defaulting to prospective treatment for every approved variation because it is administratively simpler, when the added scope is not distinct from work already underway and a cumulative catch-up is actually required
- treating every modification as automatically part of the original single performance obligation without testing whether the added scope is priced at standalone selling price (which would indicate a separate contract)
- failing to recompute and true up the percentage-of-completion calculation at the modification date when cumulative catch-up applies, understating or overstating the one-time adjustment
- not distinguishing an approved price-and-scope modification (this consideration) from an unapproved claim or unpriced variation (a variable consideration constraint issue), which follow different accounting paths.
Simple example
A contractor is 60% complete on a SAR 50,000,000 building contract, with cumulative revenue recognized of SAR 30,000,000 based on costs incurred of SAR 27,000,000 against an original total estimated cost of SAR 45,000,000. The employer approves additional interior fit-out scope for SAR 8,000,000, priced below its SAR 10,000,000 standalone selling price as a negotiated package extension; the added scope is not distinct from the remaining building work still to be performed (it is part of the same overall performance obligation). Updated total transaction price = 58,000,000; updated total estimated cost = 45,000,000 + 6,500,000 (cost of the added scope) = 51,500,000. Updated percentage complete = 27,000,000 / 51,500,000 = 52.43%. Updated cumulative revenue should be 52.43% x 58,000,000 = SAR 30,410,000, a cumulative catch-up increase of SAR 410,000 over the SAR 30,000,000 previously recognized. Journal entry at the modification date: Dr Contract asset 410,000 Cr Revenue from construction contracts 410,000
Professional judgment
Determining whether added scope is 'distinct' from work already performed (pointing to prospective or separate-contract treatment) versus part of the same single performance obligation (pointing to cumulative catch-up) requires the same distinct-goods-or-services analysis used in the original performance obligation identification, applied at the modification date, for integrated construction scope this is often, but not always, judged not distinct, meaning cumulative catch-up is the more common outcome in practice despite being the least administratively convenient. Assessing whether a modification's pricing reflects standalone selling price (relevant to the separate-contract path) requires a genuine, defensible standalone price benchmark, which can be difficult for bespoke additional scope with no directly comparable market transaction.
Source basis
IFRS 15 · Revenue from Contracts with Customers
Paragraph references
Verified against the official standard texts used in the IFRS Expert skill.
Related issues
- IFRS 15Over-time revenue recognition and progress measurement
- IFRS 15Variations, claims and disputes in contract price
- IFRS 15 / IFRS 9Retentions, advances and contract balances
- IFRS 15Mobilization and contract fulfilment costs
- IFRS 15Significant financing component in contract consideration
- IFRS 15Principal versus agent in subcontracted scope
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.
