Contract modifications · IFRS 15

In plain words

Customers often change contracts midway by adding seats, getting discounts or extending terms. IFRS 15 asks how to account for the change. If the change adds distinct services at a price that reflects their standalone selling price, the addition is a separate contract and the original is untouched. Otherwise, the test is whether the remaining services are distinct from those already provided. If they are, as with the remaining months of a subscription, the old contract is treated as ended and a new one begun, so the change applies only going forward. If they are not, the change joins the existing contract through a cumulative catch-up, adjusting revenue recognised to date in one step.

Why it matters

SaaS contracts are modified constantly (seat additions, discounts, term extensions), and the three possible treatments, separate contract, termination-and-new-contract, or cumulative catch-up on the existing contract, produce materially different revenue timing and amounts; misclassifying a modification can either double-count revenue on the added scope or wrongly restate revenue that should have been prospective only.

Diagnostic questions

Does the modification add distinct goods or services, and does the price increase reflect their standalone selling price (adjusted for the circumstances of the contract)? If not, are the remaining goods or services (for example, the remaining months of the subscription) distinct from those already transferred on or before the modification date? Has the resulting classification (separate contract, termination of the old contract and creation of a new one applied prospectively, or cumulative catch-up on the existing contract) been documented?

Recognition

Determine whether the modification adds goods or services that are distinct and whether the price increase reflects their standalone selling price (SSP), adjusted for the circumstances of the contract.
If both conditions are met, account for the modification as a separate contract, with no effect on the original contract's accounting.
Otherwise (including a modification that only changes the price, or adds goods or services not priced at SSP), assess whether the remaining goods or services, those not yet transferred at the modification date, are distinct from those transferred on or before it. If they are distinct, as the remaining months of a SaaS subscription usually are, account for the modification prospectively as a termination of the old contract and creation of a new one: the consideration not yet recognized as revenue under the original contract plus any new consideration is allocated to the remaining performance obligations or distinct services.
If the remaining goods or services are not distinct and form part of a single performance obligation that is partially satisfied at the modification date (e.g., a customised implementation in progress), account for the modification as part of the existing contract, updating the transaction price and measure of progress and recognizing a cumulative catch-up adjustment to revenue at the modification date. Where remaining goods or services include both kinds, apply each approach to the relevant part.
Document the classification decision for each material modification, since the paths produce different revenue timing.

Measurement

For the separate-contract path, measure the new contract independently at its own transaction price. For termination-and-new-contract, reallocate the sum of (a) consideration not yet recognized from the original contract and (b) the new contract's consideration across all remaining performance obligations based on their relative SSPs at the modification date. For cumulative catch-up, recompute the overall measure of progress on the combined (original plus modified) obligation and recognize the resulting adjustment immediately in the period of modification, not spread prospectively.

Presentation & disclosure

Disclose: (1) the nature and financial effect of significant contract modifications during the period; (2) the classification approach applied (separate contract, termination-and-new, or cumulative catch-up) and the policy decision tree used; (3) any material cumulative catch-up adjustments recognized and their P&L impact; (4) changes to remaining performance obligation balances arising from modifications.

Common mistakes

Booking a cumulative catch-up (adjusting revenue recognized to date) for a modification whose remaining services are distinct, such as a price change on the remaining months of a subscription, which must be accounted for prospectively
booking every seat addition as a brand-new separate contract without checking whether the added seats are priced at SSP
treating a mid-term price concession on the existing scope as a separate contract, when a price-only change on remaining distinct services is accounted for prospectively as a termination of the old contract and creation of a new one
failing to update the transaction price and measure of progress when a modification affects a single, partially satisfied performance obligation whose remaining work is not distinct
not documenting which modification path was applied, making audit and consistency review difficult.

Simple example

A customer on a 12-month SAR 600,000 platform access contract (SAR 50,000/month, invoiced monthly; 6 months already recognized = SAR 300,000) requests two changes in month 7: (a) adds 50 new seats for the remaining 6 months at SAR 400/seat/month, SAR 20,000/month in total, which is the standalone selling price; the seats are distinct and priced at SSP, so they are a separate contract; and (b) negotiates a 10% price reduction on the original seats for the remaining term, negotiated independently of the seat purchase. The remaining months are distinct from the months already provided (a series of distinct monthly services), so this price-only change is accounted for prospectively as a termination of the old contract and creation of a new one.
New seats (separate contract, no effect on original): no entry at the modification date; each month as the seats are provided and invoiced:
Dr Accounts receivable 20,000
Cr Revenue - subscription (new seats) 20,000 (SAR 120,000 over the remaining 6 months)

Price reduction on the original seats: consideration not yet recognized is now 6 months x SAR 45,000 (reduced from SAR 50,000) = SAR 270,000, recognized prospectively over the remaining 6 months; the SAR 300,000 already recognized is not adjusted (no cumulative catch-up). Each month:
Dr Accounts receivable 45,000
Cr Revenue - subscription 45,000

Professional judgment

Classifying the modification type is the central judgment and requires a documented decision tree: whether the added scope is distinct and, separately, whether it is priced at SSP determine whether a separate contract exists; if not, whether the remaining goods or services are distinct from those already transferred determines whether the modification is prospective (termination of the old contract and creation of a new one) or a cumulative catch-up. A further grey area is that distinctness assessment itself: the remaining months of a standard SaaS subscription are usually a series of distinct services, so changes to them are prospective, whereas where the remaining work is part of a single partially satisfied performance obligation, such as a customised implementation in progress, the modification is accounted for through a cumulative catch-up. Bundled changes (e.g., seats added at a discount linked to a price concession) also require judgment on whether the added items are genuinely priced at SSP.

Source basis

IFRS 15 · Revenue from Contracts with Customers

Paragraph references

IFRS 15.18–19IFRS 15.20IFRS 15.21

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.