Combine only after applying paragraph 17
For entities applying Ind AS, first confirm that the customer arrangements fall within Ind AS 115 and satisfy the applicable contract-recognition requirements. Separate contracts within that framework must be accounted for as one contract when paragraph 17’s conditions are met. The entry point is contracts made at or near the same time with the same customer or related parties of that customer. At least one of the paragraph’s three linkage criteria must also be met. Shared customer identity or adjacent contract numbers alone is insufficient. Combination determines the accounting contract; it does not automatically produce one performance obligation or immediate revenue.
Read the applicable text: MCA: Ind AS 115, paragraphs 5–9, 17–30, 35–46, 73–86 and 105–108.
Document the three linkage routes
The paragraph addresses a negotiated package with a single commercial objective, consideration in one contract dependent on another contract’s price or performance, or promised goods or services that constitute a single performance obligation under paragraphs 22–30. Test the commercial evidence: approval papers, negotiations, cross-referenced pricing, conditional discounts and integration promises. A sales-system label is useful for locating documents but is not the accounting conclusion.
Use near-time evidence without inventing a day threshold
Paragraph 17 does not state a universal number of days for at or near the same time. Explain the negotiation and contracting sequence in context. Two signatures on one day do not prove a package; different signature dates do not resolve the question either. A review rule flagging nearby contracts can identify candidates, but must leave room for a documented assessment of customer relationships and substantive linkage.
Continue the revenue model after combining
Identify performance obligations in the combined contract, establish the transaction price and allocate it under the applicable requirements. Paragraphs 73–86 address allocation, including relative stand-alone selling prices and specific discount or variable-consideration rules. Contract line prices are not automatically stand-alone selling prices. Recognise revenue only as the relevant performance obligations are satisfied. A combined contract can still contain obligations with different recognition patterns.
Separate combination from modification
Paragraphs 18–21 address changes in scope or price and their accounting. A later change order is not automatically another contract to be swept into paragraph 17, nor does a separate purchase-order number necessarily prevent modification accounting. First determine the event being assessed and its enforceable terms. Record whether the working concerns contracts at inception, an approved modification or a different transaction, then apply the relevant requirements.
Preserve the source-to-accounting bridge
Retain original legal contract identifiers and link them to a combined accounting reference. Maintain one transaction-price population, a performance-obligation allocation and separate billing, cash and revenue roll-forwards. Exclude duplicate source totals when the combined header is used for reporting. Review modifications and new commercial evidence through a controlled process. The purpose is a reproducible accounting judgment, not rewriting the customer’s contracts or forcing the invoicing system to issue a single invoice.
Six worked illustrations
All facts and amounts are fictional. Calculations illustrate the stated assumptions, not a predetermined legal outcome.
Illustrative example 1: A negotiated package
Two near-time contracts with the same customer are documented as a package with one commercial objective. Fixed consideration is ₹12,00,000 and ₹3,00,000, giving a combined transaction-price input of ₹15,00,000, assuming no further adjustments. Combination does not itself establish when any of that amount becomes revenue.
Illustrative example 2: Two distinct obligations after combination
Assume the combined contract has two distinct obligations, stand-alone selling prices ₹12,00,000 and ₹8,00,000, and transaction price ₹18,00,000. With no specific allocation exception, relative allocation is ₹10,80,000 and ₹7,20,000: 60% and 40% of the price. Separate invoice line amounts cannot override that supported allocation.
Illustrative example 3: Interdependent consideration
Assume two near-time contracts with the same customer have interdependent consideration. Their stated prices are ₹10,00,000 and ₹4,00,000, with a ₹1,00,000 discount conditional on the combined arrangement. On the assumption that this adjustment belongs in the transaction price under the applicable requirements, the total is ₹13,00,000. On these stated facts paragraph 17(b) requires combination. Estimating the transaction price, applying any variable-consideration constraint and allocating the discount remain additional tasks.
Illustrative example 4: Integrated obligation with a supported progress measure
Two contracts combined under paragraph 17 have ₹7,00,000 and ₹5,00,000 consideration. Assume the promises form one performance obligation, over-time recognition is independently justified and the appropriate progress measure is 40%. Cumulative revenue is ₹4,80,000 on the ₹12,00,000 transaction price. The remaining ₹7,20,000 is not automatically a receivable or contract liability; those classifications need billing and other facts.
Illustrative example 5: Same customer without the linkage criteria
Two unrelated near-time contracts have fixed prices of ₹2,00,000 and ₹3,00,000. Assume none of paragraph 17’s linkage criteria is met. Their ₹5,00,000 commercial aggregate is a management control total, not a sufficient basis to account for them as one contract under paragraph 17. Each contract still needs its own revenue assessment.
Illustrative example 6: Eliminate a reporting duplicate
A combined accounting header carries ₹15,00,000 while its two source contracts together also total ₹15,00,000. A report summing the header and sources would show ₹30,00,000, overstating the population by ₹15,00,000. Use linked detail or the header once; do not count both levels as independent consideration.
Ten-step verification table
| Step | Action | Evidence |
|---|---|---|
| 1 | Confirm the reporting framework | Ind AS applicability, reporting period, standard scope and contract-recognition criteria. |
| 2 | Collect the complete contract set | Legal identifiers, dates, amendments and customer parties. |
| 3 | Check the entry conditions | Near-time evidence and same-customer or related-party analysis. |
| 4 | Test the package criterion | Negotiation history and single commercial objective. |
| 5 | Test consideration dependence | Cross-pricing, conditional discounts and performance links. |
| 6 | Test the obligation linkage | Promises assessed under paragraphs 22–30. |
| 7 | Record the combination conclusion | Reasoned paragraph 17 assessment and source references. |
| 8 | Complete the revenue analysis | Performance obligations, price, allocation and recognition support. |
| 9 | Separate modifications | Approved changes and paragraphs 18–21 assessment. |
| 10 | Reconcile once through reporting | Source contracts, combined reference, billings and recognised revenue. |
Sixteen practitioner FAQs
1. Is combination optional when paragraph 17 applies?
The standard requires combination when its entry conditions and at least one linkage criterion are met.
2. Does the same customer alone require combination?
No. The near-time condition and one or more stated linkage criteria must also be established.
3. Can related parties of the customer be relevant?
Yes. They appear in paragraph 17’s customer condition; document the relationship rather than assuming it from similar names.
4. Is there a fixed thirty-day test?
Paragraph 17 does not prescribe that universal numerical threshold.
5. Do identical signature dates prove a single commercial objective?
No. Examine the negotiations and commercial substance.
6. Must all three linkage criteria be satisfied?
No. One or more is sufficient once the entry conditions are met.
7. Can interdependent pricing be a combination indicator?
Yes. Consideration depending on another contract’s price or performance is one express criterion.
8. Does a combined contract always have one performance obligation?
No. Identify obligations under the applicable requirements after determining the accounting contract.
9. Can some promises across contracts form one obligation?
Paragraph 17(c) expressly contemplates the relevant goods or services, including some promised in each contract, forming one performance obligation.
10. Does combination create revenue on signature?
No. Recognition follows satisfaction of performance obligations, not the combination decision alone.
11. Are invoice prices always stand-alone selling prices?
No. Support stand-alone selling prices and apply the allocation requirements and any applicable exceptions.
12. Must all discounts be allocated proportionately without further analysis?
No. The standard contains requirements for allocating particular discounts or variable consideration to specified obligations.
13. Is every later purchase order assessed only under paragraph 17?
No. Determine whether it is a modification, a new contract or another event under the relevant requirements.
14. Should original legal contract numbers be discarded?
No. Preserve them and link them to the combined accounting reference.
15. Can a remaining transaction price be labelled a contract liability automatically?
No. Classification depends on performance, billing, payment and enforceable rights, not simply unrecognised consideration.
16. What is the main reporting control?
One traceable consideration population, with no double counting of combined headers and their source contracts.
Official sources
MCA: Ind AS 115, paragraphs 5–9, 17–30, 35–46, 73–86 and 105–108
ICAI: Ind AS 115, 2025–26 compendium incorporating notified amendments through 2025