Ind AS 115 Contract Modifications: Separate Contract, Prospective Accounting or Cumulative Catch-Up?

Contract amendments are common in software, construction, consulting, outsourcing and long-term service arrangements. A customer may add units, extend the term, change specifications, revise the price or approve a change order after work has started. Under Ind AS 115, the accounting is not determined by the legal label “amendment” or “variation”. The finance team must decide whether the change creates a separate contract, is accounted for prospectively as a termination of the old contract and creation of a new one, or requires a cumulative catch-up adjustment to revenue already recognised.

The current first-party starting point is ICAI’s Compendium of Indian Accounting Standards for 2025-2026. Its Volume I index lists Ind AS 115, Revenue from Contracts with Customers. ICAI also maintains an Educational Material on Ind AS 115 page and a publication landing page for practical implementation guidance.

Start with one question: has an enforceable modification been approved?

Ind AS 115 treats a contract modification as a change in scope, price, or both that is approved by the parties and creates or changes enforceable rights and obligations. Approval does not always need a freshly signed document; depending on the facts and law governing the arrangement, it may be written, oral or implied by customary business practice. If the parties have not approved the modification, the entity continues accounting for the existing contract until the modification becomes enforceable.

A price can still be unresolved when scope has been approved. In that situation, the entity does not wait automatically for a final invoice amount. It estimates the resulting change in transaction price using the variable-consideration requirements, including the constraint on amounts whose later reversal could be significant.

The three accounting outcomes

1. Separate contract: distinct additions priced at stand-alone selling price

A modification is accounted for as a separate contract only when both conditions are met: the scope increases because additional promised goods or services are distinct, and the price increases by consideration that reflects their stand-alone selling prices, adjusted where appropriate for the circumstances of the contract.

Example: a customer has a one-year cloud-support contract and later purchases an additional, separately usable training package at the normal stand-alone price. If the training is distinct and the added price reflects its stand-alone selling price, the original support contract continues unchanged and the training is accounted for as a separate contract.

2. Prospective accounting: remaining goods or services are distinct, but the modification is not a separate contract

If the separate-contract test fails, the next question is whether the goods or services remaining after the modification are distinct from those already transferred. When they are distinct, Ind AS 115 accounts for the change prospectively as if the existing contract were terminated and a new contract created on the modification date.

The consideration allocated to the remaining performance obligations generally comprises the portion of the original transaction price that had not yet been recognised as revenue plus the consideration promised as part of the modification. Revenue already recognised for goods or services transferred before the modification is not reopened merely because the remaining arrangement has changed.

Example: a supplier agrees to deliver 100 identical units at ₹1,000 each. After 40 units are delivered, the customer adds 30 more units at a price that does not meet the stand-alone-selling-price condition for separate-contract treatment. If each unit is distinct, the entity combines the unrecognised consideration for the remaining 60 original units with the modification consideration and allocates that total prospectively to the 90 units remaining after the change.

3. Cumulative catch-up: remaining goods or services are not distinct from what has already been transferred

If the remaining goods or services are not distinct and form part of a single performance obligation that is already partially satisfied, the modification is treated as part of the existing contract. The entity updates the transaction price and, where relevant, the measure of progress, then recognises the resulting adjustment to revenue immediately on a cumulative catch-up basis.

This outcome is common in integrated construction or implementation projects where the customer changes the design or scope but the added work is not a separate output from the performance obligation already being delivered.

Example: a contractor is building one highly integrated facility and recognises revenue over time using an appropriate measure of progress. Mid-project, the customer approves a design change that adds ₹20 lakh of consideration and ₹15 lakh of expected cost. If the modified work is not distinct from the partially completed facility, the contractor updates the transaction price, expected costs and progress calculation. The difference between revenue that should have been recognised to date under the revised economics and revenue already recognised is recorded immediately as a cumulative catch-up.

What if a modification is mixed?

A modification can affect an existing non-distinct performance obligation and also add distinct goods or services. Apply the relevant treatment to each affected portion rather than forcing the entire amendment into one accounting outcome.

A practical decision framework

1. Document approval. Identify what changed, when the change became enforceable and what evidence supports approval.
2. Map the new promises. Determine whether added or changed goods and services are distinct under the same Ind AS 115 distinctness analysis used for performance obligations.
3. Test pricing. Compare modification consideration with stand-alone selling prices and document any contract-specific adjustment that explains a discount or premium.
4. Apply the separate-contract test first. If both distinctness and stand-alone-selling-price conditions are met, keep the modification separate.
5. If not separate, examine what remains. If remaining goods or services are distinct from those already transferred, account prospectively as termination plus a new contract.
6. If they are not distinct, update the existing performance obligation. Recalculate transaction price and progress and record the cumulative catch-up at the modification date.
7. Split mixed modifications. Do not force a single treatment where different promises require different outcomes.

Common mistakes

• Treating every signed change order as a separate contract. Separate-contract accounting requires both distinct added goods or services and appropriate stand-alone-selling-price economics.
• Reversing old revenue in a prospective modification. When remaining goods or services are distinct, prior revenue is generally left intact and the revised consideration is allocated to what remains.
• Using cumulative catch-up merely because a contract is long term. The key issue is whether the modified goods or services are distinct from those already transferred, not the contract duration.
• Waiting for final pricing after scope is enforceable. An approved scope change with unresolved price may require an estimate under the variable-consideration rules.
• Ignoring updated cost estimates. In an over-time performance obligation, a scope modification can change both transaction price and the measure of progress.
• Failing to preserve stand-alone selling price evidence. Pricing analysis is often the difference between separate-contract and prospective treatment.

Documentation checklist

• Original contract, amendment evidence and enforceable modification date.
• Distinctness assessment for added or changed promises.
• Stand-alone selling price support and explanation of discounts or premiums.
• Unrecognised original consideration and revised transaction price.
• Updated cost-to-complete and progress calculation where revenue is recognised over time.
• Journal entry and disclosure impact showing why the treatment is separate, prospective or cumulative catch-up.

Practical takeaway

For every Ind AS 115 contract amendment, do not start with the journal entry. Start with the promises that changed. If distinct additions are priced at stand-alone selling price, account for a separate contract. If the separate-contract test fails but the remaining goods or services are distinct, account prospectively. If the remaining work is not distinct from a partially satisfied performance obligation, update the existing contract and recognise a cumulative catch-up. A short decision memo covering approval, distinctness, pricing and remaining performance obligations usually makes the accounting conclusion much easier to audit.