Contract Modifications under Ind AS 115: New Contract, Termination or Catch-Up?

Customer contracts evolve through change orders, scope additions, price renegotiations and extensions, and each amendment can alter revenue accounting. Ind AS 115 distinguishes modifications that are separate contracts from those accounted for prospectively as termination and creation of a new contract or through a cumulative catch-up to an existing performance obligation. A professional application therefore needs more than the right journal entry: it needs a controlled decision path from contractual facts and management assumptions to measurement and disclosure. Treating every change order the same can create abrupt and unjustified revenue movements. A robust approach connects commercial substance, the Ind AS 115 decision criteria, measurement evidence and presentation consequences in one coherent file.

Confirm approval and enforceability of the modification

The decision point. A modification exists when parties approve a change that creates new or changes existing enforceable rights and obligations. For implementation, finance should capture signed changes and enforceable oral or customary changes in line with policy. Where errors often arise is booking proposed scope changes before they create enforceable terms. Where the conclusion is sensitive to a contractual clause or estimate, the file should show the alternative outcome and why the selected treatment is more appropriate.

Test for a separate contract

The core requirement. Added distinct goods or services priced at their standalone selling prices, adjusted appropriately for the circumstances, are generally accounted for as a separate contract. In a controlled close process, the analysis should compare incremental pricing with standalone evidence. A common weakness is treating any increase in contract value as a separate contract even when added goods are not distinct. A concise review note should state the trigger, the rule applied, the evidence considered and the financial-statement consequence.

Use prospective accounting for remaining distinct items

The principle. When remaining goods or services are distinct from those already transferred but the modification is not a separate contract, the existing contract is effectively terminated and the remaining consideration is allocated prospectively. For a review-ready file, systems should carry forward unrecognised consideration and combine it with modification consideration appropriately. The risk to avoid is rewriting revenue already recognised for satisfied distinct goods. Evidence should be retained at the same level of detail as the accounting conclusion, with assumptions version-controlled and exceptions explicitly approved.

Use cumulative catch-up for a continuing combined obligation

The technical anchor. When remaining goods or services are not distinct and form part of a single performance obligation already partially satisfied, the modification adjusts the measure of progress and revenue through a cumulative catch-up. In application, cost estimates, transaction price and progress measures should be updated together. A frequent failure mode is treating an integrated construction change as a new prospective contract despite one continuing obligation. The accounting result should reconcile to the underlying contract, valuation or subledger rather than rely on a standalone spreadsheet conclusion.

Control mixed modifications

The accounting logic. A modification can affect both distinct remaining items and a partially satisfied obligation, requiring application of the principles to the affected components. Operationally, complex amendments should be reviewed at performance-obligation level rather than through one contract-level flag. The main judgement risk is forcing a hybrid fact pattern into one simplified method. The working paper should identify the relevant facts, source data, judgement and conclusion so that an independent reviewer can reproduce the decision.

Practical illustration

Assume a customer adds 20 standard support licences to an existing software arrangement at their normal standalone price. The addition may be a separate contract. If instead the customer changes the specification of an integrated implementation project that is one over-time performance obligation, the modification may require a cumulative catch-up to revenue based on revised progress. The illustration is deliberately simplified: its purpose is to show how the accounting conclusion follows the underlying facts rather than to prescribe a single mechanical answer for every entity. Before posting an entry, the preparer should reconcile contractual terms, management's commercial intent, relevant estimates and system data to the specific accounting requirement. Where the outcome is sensitive, the file should show the key judgement and explain why the selected assumption is reasonable at the reporting date.

Documentation and control points

Professional application depends as much on process quality as technical knowledge. For this topic, a minimum control set should cover change-order completeness; standalone-price comparison; performance-obligation mapping; catch-up calculation; and modification effective-date control. Ownership should be clear between the business, finance and any legal, tax, valuation, credit-risk or other specialists whose evidence is required. Source data should be dated and version-controlled; manual adjustments should show preparer, reviewer, rationale and approval. The final accounting memorandum should connect the conclusion to the general ledger or relevant subledger, presentation and disclosures. If facts or estimates change, the entity should reassess the conclusion when required and preserve an audit trail explaining the change.

Closing perspective

Modification accounting works best when finance asks what changed in the rights and promises before asking how much revenue to adjust. The most useful way to apply Ind AS 115 is to treat the requirement as a decision framework rather than a compliance slogan. When the facts, accounting criteria, measurement evidence, controls and disclosure implications are considered together, the result is more consistent across reporting periods and easier to explain to management, auditors and users of the financial statements.