Ind AS 115 — Revenue from Contracts with Customers — fundamentally changed how Indian companies recognise revenue. Converged with IFRS 15, it replaced AS 7 (Construction Contracts) and AS 9 (Revenue Recognition) with a single, principles-based 5-step model. Mandatory for all Ind AS companies from 1 April 2018, it has had the most significant impact on IT services, real estate, telecom, and subscription businesses. This guide covers the complete standard with verified accounting entries, case studies from Indian listed companies, and common implementation pitfalls.
Standard Reference: Ind AS 115, issued by MCA vide Companies (Indian Accounting Standards) Rules, 2015 (as amended). Converged with IFRS 15 (issued by IASB in May 2014). Effective date: 1 April 2018 (mandatory for all Ind AS Phase I and Phase II companies). The standard supersedes Ind AS 11 (Construction Contracts) and Ind AS 18 (Revenue) for periods beginning on or after that date.
Ind AS 115 applies to all contracts with customers for the transfer of goods or services — except for:
A customer is defined as a party that has contracted with an entity to obtain goods or services in exchange for consideration. This definition excludes collaborative arrangements where both parties share risks and benefits (those may fall under other standards).
All revenue under Ind AS 115 flows through a five-step model. Revenue is recognised when (or as) the entity satisfies a performance obligation by transferring control of a promised good or service to a customer.
| Step | Question to Answer | Output |
|---|---|---|
| Step 1 | Is there an enforceable contract with a customer? | Contract identified (or not) |
| Step 2 | What has the entity promised to deliver? | Distinct performance obligations identified |
| Step 3 | How much will the entity receive? | Transaction price determined (including variable consideration) |
| Step 4 | How is that price split across obligations? | Transaction price allocated to each PO |
| Step 5 | When is each obligation satisfied? | Revenue recognised at point in time or over time |
A contract exists (and is accounted under Ind AS 115) only when ALL five criteria are met:
The collectability criterion (#5) has been a major change for real estate and infrastructure companies in India — where historically revenue was sometimes recognised before there was reasonable certainty of collection. Under Ind AS 115, if collectability is not probable at inception, revenue cannot be recognised until either the contract criteria are met or the contract is terminated with consideration retained by the entity.
Multiple contracts entered at or around the same time with the same customer must be combined if they are economically interdependent — negotiated as a package, prices are interrelated, or the goods/services are a single performance obligation.
A performance obligation (PO) is a promise to transfer either:
A good or service is distinct if it meets BOTH criteria:
Transaction price = amount of consideration the entity expects to be entitled to in exchange for transferring goods/services. Key considerations:
If consideration includes variable amounts (bonuses, penalties, price concessions, volume rebates, returns), the entity must estimate the amount using:
The estimated variable consideration is included only to the extent it is highly probable that a significant revenue reversal will NOT occur when the uncertainty resolves — the variable consideration constraint.
If the timing between payment and transfer of goods creates a significant financing benefit (more than 12 months), the transaction price must be adjusted to reflect the time value of money. Interest income/expense is recognised separately from revenue.
If a customer pays in non-cash form (shares, property, rights), the fair value of the non-cash consideration is included in the transaction price.
The transaction price is allocated to each performance obligation in proportion to its standalone selling price (SSP) — the price at which the entity would sell the good/service separately.
If SSP is not directly observable, it must be estimated using:
Revenue is recognised either over time or at a point in time depending on when control is transferred.
Indicators that control has passed at a point in time include: present right to payment, legal title transferred, physical possession transferred, significant risks and rewards of ownership transferred, customer acceptance.
Scenario: Tech Solutions Ltd wins a ₹5 crore fixed-price contract to develop a custom ERP system for a client. The contract includes: (a) Custom software development — 12 months, (b) 1-year post-implementation support, (c) Training — 3 days at go-live.
Step 2 — Performance Obligations identified:
Step 3 — Transaction Price: ₹5 crore fixed (no variable consideration)
Step 4 — Allocation using SSPs:
| PO | Standalone Selling Price | Allocation % | Allocated Revenue |
|---|---|---|---|
| Software Dev | ₹4,00,000 | 80% | ₹4,00,00,000 |
| Support (1yr) | ₹75,000 | 15% | ₹75,00,000 |
| Training | ₹25,000 | 5% | ₹25,00,000 |
| Total | ₹5,00,000 | 100% | ₹5,00,00,000 |
Step 5 — Recognition: PO 1 (Software Dev) — over time using input method (% of costs incurred / total estimated costs). PO 2 (Support) — over time, straight-line over 12 months. PO 3 (Training) — at a point in time (on completion of training days at go-live).
Scenario: Real Estate Co. launches "Green Vista" residential project — 200 apartments at ₹80 lakh each. Buyers pay 10% on booking, 80% in construction-linked installments, 10% at possession. Total project value: ₹160 crore.
Critical Question — Over Time or At a Point in Time?
Under Ind AS 115, real estate revenue is recognised at a point in time (on possession/legal transfer) UNLESS the entity can establish that control transfers over time. For this, the developer must prove:
In India, most state RERA (Real Estate Regulatory Authority) agreements allow buyers to cancel and receive refunds — making the "enforceable right to payment on cancellation" criterion very difficult to meet. Therefore, most Indian real estate developers recognise revenue at possession — a significant shift from pre-Ind AS practice of percentage completion recognition.
Advance received from buyers during construction is classified as Contract Liability (deferred revenue) on the balance sheet — not revenue. This depresses reported revenue during construction phases but produces a one-time revenue surge at possession — visible in the financials of Godrej Properties, Prestige Estates, and others post-Ind AS adoption.
Scenario: Telecom Co. offers a bundle: Smartphone (market price ₹25,000) + 12-month data plan (market price ₹12,000/year) for ₹30,000 total upfront. Customer pays ₹30,000 on Day 1.
Step 2 — Two Distinct POs: (1) Smartphone hardware, (2) Monthly data service over 12 months
Step 4 — Allocation:
| PO | SSP | Allocated Amount | Recognition |
|---|---|---|---|
| Smartphone | ₹25,000 | ₹20,270 (25/37 × 30,000) | Day 1 (point in time) |
| Data Plan | ₹12,000 | ₹9,730 (12/37 × 30,000) | Over 12 months (₹811/month) |
| Total | ₹37,000 | ₹30,000 |
Note: The discount of ₹7,000 (₹37,000 SSP vs ₹30,000 received) is allocated proportionately across both POs — not entirely to one. This prevents front-loading revenue by attributing all the discount to the ongoing service.
Variable consideration must be estimated and constrained to amounts where it is highly probable a significant revenue reversal won't occur. Factors that increase likelihood of reversal:
Common examples in India: volume rebates for FMCG distributors, construction milestones bonuses for EPC contractors, performance bonuses for IT services contracts.
When a contract is modified (scope change, price change), it is treated as:
Sales commissions paid only if a contract is won (incremental costs) are capitalised as a "Contract Cost Asset" and amortised over the expected benefit period. Practical expedient: if amortisation period would be ≤12 months, expense immediately.
Setup costs (e.g., cost to mobilise before a construction project starts) are capitalised if they: relate directly to a specific contract, generate resources that will be used to satisfy POs, and are expected to be recovered.
Ind AS 115 requires extensive disclosures in financial statements:
| Disclosure Category | Key Items Required |
|---|---|
| Revenue disaggregation | Revenue by geography, product/service type, customer type, contract type (fixed/variable), timing (point/over time) |
| Contract balances | Opening and closing balances of Contract Assets, Contract Liabilities, Receivables; revenue recognised from opening Contract Liability |
| Performance obligations | Description of each PO, significant payment terms, obligations for returns/refunds |
| Significant judgements | Methods used to determine transaction price and allocation; over time vs point in time determination |
| Contract costs | Closing balances of capitalised contract costs; amortisation and impairment |
| Remaining performance obligations | Aggregate transaction price allocated to unsatisfied/partially satisfied POs, and when recognition expected (practical expedient if ≤1 year) |
Ind AS 18 (old standard, now withdrawn) used different recognition criteria for goods (risks and rewards transfer) and services (stage of completion). Ind AS 115 replaces both with a single 5-step model based on 'control transfer'. The most significant practical difference: Ind AS 115 requires bundled contracts to be split into distinct performance obligations with separate revenue allocation; it introduces a variable consideration constraint; it mandates capitalisation of incremental contract acquisition costs; and for real estate, it generally delays revenue recognition to possession rather than allowing % completion.
Ind AS 115 significantly defers revenue recognition for most real estate developers. Under the old AS 7 (Construction Contracts), developers recognised revenue as construction progressed (percentage completion method). Under Ind AS 115, revenue is generally recognised at possession/handover — the point when control (physical possession, legal title, risks and rewards) transfers to the buyer. During construction, advances received are classified as Contract Liabilities. This depresses reported revenue during multi-year projects but creates a large one-time recognition at possession. Developers with large pending possessions show high Contract Liability balances on their balance sheets.
A Contract Asset arises when an entity has performed (transferred goods/services) but has not yet billed the customer — essentially unbilled revenue. Common in milestone-billing IT contracts where work is done but the invoice hasn't been raised yet. A Contract Liability (previously called 'Deferred Revenue') arises when the customer has paid before the entity has performed — advance from customers, subscription fees for future periods, booking advances in real estate. The balance sheet must show these separately from trade receivables and other liabilities. Contract Assets are subject to impairment testing under Ind AS 109.
Ind AS 115 — Revenue from Contracts with Customers — fundamentally changed how Indian companies recognise revenue. Converged with IFRS 15, it replaced AS 7 (Construction Contracts) and AS 9 (Revenue Recognition) with a single, principles-based 5-step model. Mandatory for all Ind AS companies from 1 April 2018, it has had the most significant impact on IT services, real estate, telecom, and subscription businesses. This guide covers the complete standard with verified accounting entries, case studies from Indian listed companies, and common implementation pitfalls.
Standard Reference: Ind AS 115, issued by MCA vide Companies (Indian Accounting Standards) Rules, 2015 (as amended). Converged with IFRS 15 (issued by IASB in May 2014). Effective date: 1 April 2018 (mandatory for all Ind AS Phase I and Phase II companies). The standard supersedes Ind AS 11 (Construction Contracts) and Ind AS 18 (Revenue) for periods beginning on or after that date.
Ind AS 115 applies to all contracts with customers for the transfer of goods or services — except for:
A customer is defined as a party that has contracted with an entity to obtain goods or services in exchange for consideration. This definition excludes collaborative arrangements where both parties share risks and benefits (those may fall under other standards).
All revenue under Ind AS 115 flows through a five-step model. Revenue is recognised when (or as) the entity satisfies a performance obligation by transferring control of a promised good or service to a customer.
| Step | Question to Answer | Output |
|---|---|---|
| Step 1 | Is there an enforceable contract with a customer? | Contract identified (or not) |
| Step 2 | What has the entity promised to deliver? | Distinct performance obligations identified |
| Step 3 | How much will the entity receive? | Transaction price determined (including variable consideration) |
| Step 4 | How is that price split across obligations? | Transaction price allocated to each PO |
| Step 5 | When is each obligation satisfied? | Revenue recognised at point in time or over time |
A contract exists (and is accounted under Ind AS 115) only when ALL five criteria are met:
The collectability criterion (#5) has been a major change for real estate and infrastructure companies in India — where historically revenue was sometimes recognised before there was reasonable certainty of collection. Under Ind AS 115, if collectability is not probable at inception, revenue cannot be recognised until either the contract criteria are met or the contract is terminated with consideration retained by the entity.
Multiple contracts entered at or around the same time with the same customer must be combined if they are economically interdependent — negotiated as a package, prices are interrelated, or the goods/services are a single performance obligation.
A performance obligation (PO) is a promise to transfer either:
A good or service is distinct if it meets BOTH criteria:
Transaction price = amount of consideration the entity expects to be entitled to in exchange for transferring goods/services. Key considerations:
If consideration includes variable amounts (bonuses, penalties, price concessions, volume rebates, returns), the entity must estimate the amount using:
The estimated variable consideration is included only to the extent it is highly probable that a significant revenue reversal will NOT occur when the uncertainty resolves — the variable consideration constraint.
If the timing between payment and transfer of goods creates a significant financing benefit (more than 12 months), the transaction price must be adjusted to reflect the time value of money. Interest income/expense is recognised separately from revenue.
If a customer pays in non-cash form (shares, property, rights), the fair value of the non-cash consideration is included in the transaction price.
The transaction price is allocated to each performance obligation in proportion to its standalone selling price (SSP) — the price at which the entity would sell the good/service separately.
If SSP is not directly observable, it must be estimated using:
Revenue is recognised either over time or at a point in time depending on when control is transferred.
Indicators that control has passed at a point in time include: present right to payment, legal title transferred, physical possession transferred, significant risks and rewards of ownership transferred, customer acceptance.
Scenario: Tech Solutions Ltd wins a ₹5 crore fixed-price contract to develop a custom ERP system for a client. The contract includes: (a) Custom software development — 12 months, (b) 1-year post-implementation support, (c) Training — 3 days at go-live.
Step 2 — Performance Obligations identified:
Step 3 — Transaction Price: ₹5 crore fixed (no variable consideration)
Step 4 — Allocation using SSPs:
| PO | Standalone Selling Price | Allocation % | Allocated Revenue |
|---|---|---|---|
| Software Dev | ₹4,00,000 | 80% | ₹4,00,00,000 |
| Support (1yr) | ₹75,000 | 15% | ₹75,00,000 |
| Training | ₹25,000 | 5% | ₹25,00,000 |
| Total | ₹5,00,000 | 100% | ₹5,00,00,000 |
Step 5 — Recognition: PO 1 (Software Dev) — over time using input method (% of costs incurred / total estimated costs). PO 2 (Support) — over time, straight-line over 12 months. PO 3 (Training) — at a point in time (on completion of training days at go-live).
Scenario: Real Estate Co. launches "Green Vista" residential project — 200 apartments at ₹80 lakh each. Buyers pay 10% on booking, 80% in construction-linked installments, 10% at possession. Total project value: ₹160 crore.
Critical Question — Over Time or At a Point in Time?
Under Ind AS 115, real estate revenue is recognised at a point in time (on possession/legal transfer) UNLESS the entity can establish that control transfers over time. For this, the developer must prove:
In India, most state RERA (Real Estate Regulatory Authority) agreements allow buyers to cancel and receive refunds — making the "enforceable right to payment on cancellation" criterion very difficult to meet. Therefore, most Indian real estate developers recognise revenue at possession — a significant shift from pre-Ind AS practice of percentage completion recognition.
Advance received from buyers during construction is classified as Contract Liability (deferred revenue) on the balance sheet — not revenue. This depresses reported revenue during construction phases but produces a one-time revenue surge at possession — visible in the financials of Godrej Properties, Prestige Estates, and others post-Ind AS adoption.
Scenario: Telecom Co. offers a bundle: Smartphone (market price ₹25,000) + 12-month data plan (market price ₹12,000/year) for ₹30,000 total upfront. Customer pays ₹30,000 on Day 1.
Step 2 — Two Distinct POs: (1) Smartphone hardware, (2) Monthly data service over 12 months
Step 4 — Allocation:
| PO | SSP | Allocated Amount | Recognition |
|---|---|---|---|
| Smartphone | ₹25,000 | ₹20,270 (25/37 × 30,000) | Day 1 (point in time) |
| Data Plan | ₹12,000 | ₹9,730 (12/37 × 30,000) | Over 12 months (₹811/month) |
| Total | ₹37,000 | ₹30,000 |
Note: The discount of ₹7,000 (₹37,000 SSP vs ₹30,000 received) is allocated proportionately across both POs — not entirely to one. This prevents front-loading revenue by attributing all the discount to the ongoing service.
Variable consideration must be estimated and constrained to amounts where it is highly probable a significant revenue reversal won't occur. Factors that increase likelihood of reversal:
Common examples in India: volume rebates for FMCG distributors, construction milestones bonuses for EPC contractors, performance bonuses for IT services contracts.
When a contract is modified (scope change, price change), it is treated as:
Sales commissions paid only if a contract is won (incremental costs) are capitalised as a "Contract Cost Asset" and amortised over the expected benefit period. Practical expedient: if amortisation period would be ≤12 months, expense immediately.
Setup costs (e.g., cost to mobilise before a construction project starts) are capitalised if they: relate directly to a specific contract, generate resources that will be used to satisfy POs, and are expected to be recovered.
Ind AS 115 requires extensive disclosures in financial statements:
| Disclosure Category | Key Items Required |
|---|---|
| Revenue disaggregation | Revenue by geography, product/service type, customer type, contract type (fixed/variable), timing (point/over time) |
| Contract balances | Opening and closing balances of Contract Assets, Contract Liabilities, Receivables; revenue recognised from opening Contract Liability |
| Performance obligations | Description of each PO, significant payment terms, obligations for returns/refunds |
| Significant judgements | Methods used to determine transaction price and allocation; over time vs point in time determination |
| Contract costs | Closing balances of capitalised contract costs; amortisation and impairment |
| Remaining performance obligations | Aggregate transaction price allocated to unsatisfied/partially satisfied POs, and when recognition expected (practical expedient if ≤1 year) |
Ind AS 18 (old standard, now withdrawn) used different recognition criteria for goods (risks and rewards transfer) and services (stage of completion). Ind AS 115 replaces both with a single 5-step model based on 'control transfer'. The most significant practical difference: Ind AS 115 requires bundled contracts to be split into distinct performance obligations with separate revenue allocation; it introduces a variable consideration constraint; it mandates capitalisation of incremental contract acquisition costs; and for real estate, it generally delays revenue recognition to possession rather than allowing % completion.
Ind AS 115 significantly defers revenue recognition for most real estate developers. Under the old AS 7 (Construction Contracts), developers recognised revenue as construction progressed (percentage completion method). Under Ind AS 115, revenue is generally recognised at possession/handover — the point when control (physical possession, legal title, risks and rewards) transfers to the buyer. During construction, advances received are classified as Contract Liabilities. This depresses reported revenue during multi-year projects but creates a large one-time recognition at possession. Developers with large pending possessions show high Contract Liability balances on their balance sheets.
A Contract Asset arises when an entity has performed (transferred goods/services) but has not yet billed the customer — essentially unbilled revenue. Common in milestone-billing IT contracts where work is done but the invoice hasn't been raised yet. A Contract Liability (previously called 'Deferred Revenue') arises when the customer has paid before the entity has performed — advance from customers, subscription fees for future periods, booking advances in real estate. The balance sheet must show these separately from trade receivables and other liabilities. Contract Assets are subject to impairment testing under Ind AS 109.