Combining Contracts under Ind AS 115

Why the answer affects more than one line item

A technically correct number can still be fragile when the route from contract, data and judgement to the financial statements is not visible. The practical task in Combining Contracts under Ind AS 115 is to combine contracts negotiated as a package, with interdependent pricing or as one performance obligation, and avoid analysing artificial contract fragments. A weak conclusion may survive the first calculation but fail when a reviewer asks about scope, timing or consistency. The purpose of Ind AS 115 is to depict the transfer of promised goods or services to customers in an amount reflecting consideration to which the entity expects to be entitled. That purpose should guide the judgement and prevent the exercise from becoming a search for whichever journal entry produces the preferred result.

Technical foundation

Ind AS 115 should be read as a decision architecture. It governs contracts with customers, excluding leases, insurance contracts, financial instruments and specified non-monetary exchanges, and its measurement logic can be summarised as follows: The five-step model identifies contracts and performance obligations, determines and allocates transaction price, and recognises revenue when or as control transfers, with separate requirements for contract costs and presentation. The article’s focus—to combine contracts negotiated as a package, with interdependent pricing or as one performance obligation, and avoid analysing artificial contract fragments—sits within that architecture. A conclusion is robust only when the same assumptions are used consistently in the general ledger, valuation or calculation model, primary statements, notes and management explanations.

Implementation sequence

The work is easier to audit when it follows a visible sequence rather than a collection of disconnected spreadsheets:

1. Frame the question. estimate fixed and variable consideration, financing effects and non-cash consideration. Give the conclusion on combining contracts a date and an accountable owner.
2. Build the evidence base. allocate transaction price using observable or estimated stand-alone selling prices. Retain the source supporting combining contracts.
3. Apply the accounting test. recognise revenue over time or at a point in time and reconcile contract balances, costs and disclosures. Link it explicitly to combining contracts.
4. Quantify and reconcile. identify enforceable customer contracts and combine or modify them where required. Trace it to the reported outcome for combining contracts.

Case-based explanation

Imagine that the year-end reviewer receives this fact pattern: A customer signs separate equipment, installation and support contracts on the same day with linked discounts. The matter involves a carrying amount, transaction value or exposure of approximately ₹342 crore. Rather than starting with a spreadsheet output, the reviewer asks management to identify enforceable customer contracts and combine or modify them where required and identify distinct promised goods, services and material rights. The answers should make clear how the entity intends to combine contracts negotiated as a package, with interdependent pricing or as one performance obligation, and avoid analysing artificial contract fragments and which evidence supports that intention or conclusion.

For combining contracts, the likely source of misstatement is confusing a contract asset with an unconditional receivable. The strongest response is a calculation supported by executed contracts, approved order forms and side letters, together with a ledger-to-note reconciliation. Where judgement remains significant, the note should describe the entity-specific uncertainty and not simply reproduce the wording of Ind AS 115.

Risk of misstatement

Two recurring shortcuts deserve explicit challenge:

• Including variable consideration without applying the constraint. A reviewer will normally challenge consistency with similar transactions and with evidence used elsewhere in the financial statements. For combining contracts, the working paper should show why the entity’s facts do or do not create this risk.
• Using billing milestones as measures of progress without checking faithful depiction. The control response is to state the criterion, identify the evidence and record who approved any exception. For combining contracts, the working paper should show why the entity’s facts do or do not create this risk.

A defensible evidence pack

The evidence pack should be proportionate to materiality but complete enough for another reviewer to reproduce the conclusion:

• Performance-obligation and contract-combination memoranda, specifically cross-referenced to the conclusion on combining contracts and the affected financial-statement line items.
• Variable-consideration, financing and selling-price models, specifically cross-referenced to the conclusion on combining contracts and the affected financial-statement line items.
• Delivery, acceptance, usage and progress evidence, specifically cross-referenced to the conclusion on combining contracts and the affected financial-statement line items.

Connected-standard analysis is also necessary. Relevant interfaces include Ind AS 21, Ind AS 37 and Ind AS 38. The team should document whether these standards change recognition, measurement, tax, impairment, cash-flow classification or disclosure. For combining contracts, the final tie-out should align management reporting, the primary statements and the notes.

Key learning

A well-governed answer is repeatable, reviewable and capable of being explained without reconstructing the analysis after year end. The essential point is that the entity must combine contracts negotiated as a package, with interdependent pricing or as one performance obligation, and avoid analysing artificial contract fragments. Once that distinction is documented, the calculation, journal, reconciliation and note can follow the same logic. Practitioners should revisit the conclusion when contractual terms, operating facts or material assumptions change. A deeper study of Ind AS 115 helps connect this individual issue with the standard’s wider recognition, measurement and disclosure architecture.