Ind AS · Accounting Standards · Ind AS 115

Ind AS 115: Revenue from Contracts with Customers — Complete Guide with Case Studies

Finin2min Research Desk·June 2026· 15–20 min read Ind AS 115 Revenue Recognition Effective: 1 Apr 2018

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.

📜 In This Article

  1. Scope and applicability of Ind AS 115
  2. The 5-Step Revenue Recognition Model
  3. Step 1: Identify the Contract
  4. Step 2: Identify Performance Obligations
  5. Step 3: Determine Transaction Price
  6. Step 4: Allocate Transaction Price
  7. Step 5: Recognise Revenue
  8. Case Study — IT Services Company (TCS-type scenario)
  9. Case Study — Real Estate Developer (Godrej Properties-type)
  10. Case Study — Telecom Company (Jio/Airtel-type)
  11. Variable Consideration & Constraint
  12. Contract Modifications
  13. Contract Costs (Incremental Costs & Fulfilment Costs)
  14. Disclosure Requirements
  15. Ind AS 115 vs Old AS 9/AS 7 — Key Differences
  16. Common Errors & Audit Focus Areas

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.

1. Scope and Applicability

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).

2. The 5-Step Revenue Recognition Model

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.

📌
The Core Principle: Revenue is recognised in a manner that depicts the transfer of goods or services to customers in an amount that reflects the consideration to which the entity expects to be entitled in exchange for those goods or services.
StepQuestion to AnswerOutput
Step 1Is there an enforceable contract with a customer?Contract identified (or not)
Step 2What has the entity promised to deliver?Distinct performance obligations identified
Step 3How much will the entity receive?Transaction price determined (including variable consideration)
Step 4How is that price split across obligations?Transaction price allocated to each PO
Step 5When is each obligation satisfied?Revenue recognised at point in time or over time

3. Step 1: Identify the Contract

A contract exists (and is accounted under Ind AS 115) only when ALL five criteria are met:

  1. The parties have approved the contract and are committed to perform
  2. Each party's rights can be identified
  3. Payment terms can be identified
  4. The contract has commercial substance
  5. It is probable that the entity will collect the consideration to which it is entitled

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.

Contract Combinations

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.

4. Step 2: Identify Performance Obligations

A performance obligation (PO) is a promise to transfer either:

A good or service is distinct if it meets BOTH criteria:

Common error: Failing to identify separate performance obligations in bundled contracts — e.g., a software company selling a licence + implementation + annual support should identify at least 2–3 separate POs, not treat the entire contract as one revenue stream.

5. Step 3: Determine the Transaction Price

Transaction price = amount of consideration the entity expects to be entitled to in exchange for transferring goods/services. Key considerations:

Variable Consideration

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.

Significant Financing Component

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.

Non-Cash Consideration

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.

6. Step 4: Allocate 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:

7. Step 5: Recognise Revenue — Over Time vs At a Point in Time

Revenue is recognised either over time or at a point in time depending on when control is transferred.

Over Time — if ANY one criterion is met:

At a Point in Time — for all other performance obligations

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.

🔴 Old Standard (AS 9 / AS 7)

  • Risks and rewards transfer model for goods
  • Percentage completion for construction contracts
  • No bundling guidance — each deliverable standalone
  • No variable consideration constraint
  • Upfront recognition common in real estate

🟢 Ind AS 115 (IFRS 15)

  • Control transfer model (risks & rewards is just one indicator)
  • 5-step model; over-time or point-in-time
  • Bundled contracts must be unbundled into POs
  • Variable consideration constraint applies
  • Real estate revenue only when control transfers to buyer

📊 Case Study 1: IT Services Company

TCS / Infosys / Wipro-type Fixed Price Software Development Contract

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:

  • PO 1: Custom software development (distinct — client can use the software independently)
  • PO 2: Post-implementation support (distinct — can be purchased separately)
  • PO 3: Training (distinct — standard training, readily available in market)

Step 3 — Transaction Price: ₹5 crore fixed (no variable consideration)

Step 4 — Allocation using SSPs:

POStandalone Selling PriceAllocation %Allocated Revenue
Software Dev₹4,00,00080%₹4,00,00,000
Support (1yr)₹75,00015%₹75,00,000
Training₹25,0005%₹25,00,000
Total₹5,00,000100%₹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).

Year 1 Software Revenue (60% complete)
₹2,40,00,000
Support Revenue (first 6 months)
₹37,50,000
Journal Entry — Revenue Recognition (IT Company, % Completion)
Contract Asset (Unbilled Revenue) A/c
Dr ₹2,40,00,000
Revenue from Operations A/c
Cr ₹2,40,00,000
(Revenue recognised proportionate to costs incurred; billed amount goes to Trade Receivables, unbilled goes to Contract Asset)

🏠 Case Study 2: Real Estate Developer

Residential Apartment Project — Godrej Properties / DLF-type scenario

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:

  • The apartment has no alternative use (i.e., it cannot be redirected to another buyer), AND
  • The developer has an enforceable right to payment for performance completed to date (even if the buyer cancels)

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.

Revenue Recognised (Old % Completion)
₹96 Cr (60% complete)
Revenue Recognised (Ind AS 115)
₹0 (until possession)

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.

Journal Entry — Real Estate: Advance Received During Construction
Bank A/c
Dr ₹8,00,00,000
Contract Liability (Advance from Customers) A/c
Cr ₹8,00,00,000
(On receipt of 10% booking amount — classified as Contract Liability until possession)
On Possession (Revenue Recognition):
Contract Liability A/c
Dr ₹80,00,00,000
Revenue from Operations A/c
Cr ₹80,00,00,000

📞 Case Study 3: Telecom Company

Jio / Airtel-type Bundled Contract (Handset + Data Plan)

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:

POSSPAllocated AmountRecognition
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.

Revenue Day 1 (Handset)
₹20,270
Revenue Per Month (Data)
₹811

8. Variable Consideration & The Constraint

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.

Variable Consideration — EPC Contract Performance Bonus
Contract with ₹100 Cr base fee + ₹10 Cr bonus if completed before deadline
Probability of achieving bonus: 60%
Expected Value: ₹10 Cr × 60% = ₹6 Cr. But is this "highly probable no reversal"?
If constrained — include ₹0 bonus until highly probable.
If unconstrained — recognise ₹6 Cr over project duration.
Transaction Price recognised = ₹100 Cr + constrained variable consideration

9. Contract Modifications

When a contract is modified (scope change, price change), it is treated as:

10. Contract Costs

Incremental Costs of Obtaining a Contract

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.

Costs to Fulfil a Contract

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.

Contract Cost Asset — Sales Commission Capitalisation
IT company wins 3-year managed services contract; pays sales agent ₹15 lakh commission
Contract Cost Asset A/c
Dr ₹15,00,000
Sales Agent Payable A/c
Cr ₹15,00,000
Amortisation (₹15L ÷ 36 months = ₹41,667/month):
Sales/Marketing Expense A/c
Dr ₹41,667
Contract Cost Asset A/c
Cr ₹41,667

11. Key Disclosure Requirements

Ind AS 115 requires extensive disclosures in financial statements:

Disclosure CategoryKey Items Required
Revenue disaggregationRevenue by geography, product/service type, customer type, contract type (fixed/variable), timing (point/over time)
Contract balancesOpening and closing balances of Contract Assets, Contract Liabilities, Receivables; revenue recognised from opening Contract Liability
Performance obligationsDescription of each PO, significant payment terms, obligations for returns/refunds
Significant judgementsMethods used to determine transaction price and allocation; over time vs point in time determination
Contract costsClosing balances of capitalised contract costs; amortisation and impairment
Remaining performance obligationsAggregate transaction price allocated to unsatisfied/partially satisfied POs, and when recognition expected (practical expedient if ≤1 year)

12. Common Errors & Audit Focus Areas

Top 5 Implementation Errors (Based on ICAI Guidance):
  1. Treating entire bundled IT contract as one PO instead of unbundling into licence, implementation, support
  2. Not applying variable consideration constraint — recognising too much revenue from bonus/penalty-linked contracts
  3. Real estate companies recognising revenue on percentage completion basis where "enforceable right to payment" criterion is not met
  4. Not adjusting for significant financing component in long-cycle manufacturing contracts with advance payments
  5. Expensing incremental contract acquisition costs (sales commissions on multi-year contracts) instead of capitalising

✅ Key Takeaways — Ind AS 115

  • 5-step model: Identify Contract → Identify POs → Determine Price → Allocate → Recognise
  • Revenue recognition driven by control transfer, not just risks and rewards
  • Real estate companies: revenue typically at possession (point in time), not % completion
  • IT companies: bundle contracts must be unbundled; licence ≠ support ≠ implementation
  • Telecom: discount on bundles must be proportionately allocated to all POs
  • Variable consideration: include only if highly probable no significant reversal
  • Contract costs (incremental acquisition costs): capitalise and amortise over benefit period
  • Extensive disclosures required including disaggregated revenue, contract asset/liability movements
📊
Analyse Revenue Recognition in Listed Company FinancialsUse Finin2min's FinMarket tool to view revenue notes, contract asset/liability disclosures, and disaggregated revenue data for NSE/BSE listed companies.
Open FinMarket →

❓ Frequently Asked Questions

What is the key difference between Ind AS 18 and Ind AS 115?

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.

How does Ind AS 115 impact real estate company revenues?

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.

What is a Contract Asset vs a Contract Liability under Ind AS 115?

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 · Accounting Standards · Ind AS 115

Ind AS 115: Revenue from Contracts with Customers — Complete Guide with Case Studies

Finin2min Research Desk·June 2026· 15–20 min read Ind AS 115 Revenue Recognition Effective: 1 Apr 2018

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.

📜 In This Article

  1. Scope and applicability of Ind AS 115
  2. The 5-Step Revenue Recognition Model
  3. Step 1: Identify the Contract
  4. Step 2: Identify Performance Obligations
  5. Step 3: Determine Transaction Price
  6. Step 4: Allocate Transaction Price
  7. Step 5: Recognise Revenue
  8. Case Study — IT Services Company (TCS-type scenario)
  9. Case Study — Real Estate Developer (Godrej Properties-type)
  10. Case Study — Telecom Company (Jio/Airtel-type)
  11. Variable Consideration & Constraint
  12. Contract Modifications
  13. Contract Costs (Incremental Costs & Fulfilment Costs)
  14. Disclosure Requirements
  15. Ind AS 115 vs Old AS 9/AS 7 — Key Differences
  16. Common Errors & Audit Focus Areas

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.

1. Scope and Applicability

Ind AS 115 applies to all contracts with customers for the transfer of goods or services — except for:

  • Lease contracts (Ind AS 116)
  • Insurance contracts (Ind AS 104 / forthcoming Ind AS 117)
  • Financial instruments (Ind AS 109, 32, 107)
  • Non-monetary exchanges between entities in the same line of business

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).

2. The 5-Step Revenue Recognition Model

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.

📌
The Core Principle: Revenue is recognised in a manner that depicts the transfer of goods or services to customers in an amount that reflects the consideration to which the entity expects to be entitled in exchange for those goods or services.
StepQuestion to AnswerOutput
Step 1Is there an enforceable contract with a customer?Contract identified (or not)
Step 2What has the entity promised to deliver?Distinct performance obligations identified
Step 3How much will the entity receive?Transaction price determined (including variable consideration)
Step 4How is that price split across obligations?Transaction price allocated to each PO
Step 5When is each obligation satisfied?Revenue recognised at point in time or over time

3. Step 1: Identify the Contract

A contract exists (and is accounted under Ind AS 115) only when ALL five criteria are met:

  1. The parties have approved the contract and are committed to perform
  2. Each party's rights can be identified
  3. Payment terms can be identified
  4. The contract has commercial substance
  5. It is probable that the entity will collect the consideration to which it is entitled

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.

Contract Combinations

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.

4. Step 2: Identify Performance Obligations

A performance obligation (PO) is a promise to transfer either:

  • A distinct good or service (or bundle of goods/services), OR
  • A series of distinct goods/services that are substantially the same and have the same pattern of transfer to the customer

A good or service is distinct if it meets BOTH criteria:

  • Capable of being distinct: The customer can benefit from the good/service on its own or together with other readily available resources
  • Distinct within the context of the contract: The entity's promise to transfer it is separately identifiable from other promises in the contract (i.e., it is not highly interrelated with other goods/services in the contract)
Common error: Failing to identify separate performance obligations in bundled contracts — e.g., a software company selling a licence + implementation + annual support should identify at least 2–3 separate POs, not treat the entire contract as one revenue stream.

5. Step 3: Determine the Transaction Price

Transaction price = amount of consideration the entity expects to be entitled to in exchange for transferring goods/services. Key considerations:

Variable Consideration

If consideration includes variable amounts (bonuses, penalties, price concessions, volume rebates, returns), the entity must estimate the amount using:

  • Expected Value method: Probability-weighted sum of possible amounts (best for large number of contracts)
  • Most Likely Amount method: Single most likely outcome (best for binary outcomes — either achieve the bonus or not)

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.

Significant Financing Component

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.

Non-Cash Consideration

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.

6. Step 4: Allocate 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:

  • Adjusted market assessment approach
  • Expected cost plus margin approach
  • Residual approach (only for SSPs that are highly variable or uncertain, after allocating to other POs)

7. Step 5: Recognise Revenue — Over Time vs At a Point in Time

Revenue is recognised either over time or at a point in time depending on when control is transferred.

Over Time — if ANY one criterion is met:

  • The customer simultaneously receives and consumes the benefits as the entity performs (e.g., cleaning services, routine IT maintenance)
  • The entity's performance creates or enhances an asset that the customer controls (e.g., constructing on customer's land)
  • The entity's performance creates an asset with no alternative use and the entity has an enforceable right to payment for performance completed to date

At a Point in Time — for all other performance obligations

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.

🔴 Old Standard (AS 9 / AS 7)

  • Risks and rewards transfer model for goods
  • Percentage completion for construction contracts
  • No bundling guidance — each deliverable standalone
  • No variable consideration constraint
  • Upfront recognition common in real estate

🟢 Ind AS 115 (IFRS 15)

  • Control transfer model (risks & rewards is just one indicator)
  • 5-step model; over-time or point-in-time
  • Bundled contracts must be unbundled into POs
  • Variable consideration constraint applies
  • Real estate revenue only when control transfers to buyer

📊 Case Study 1: IT Services Company

TCS / Infosys / Wipro-type Fixed Price Software Development Contract

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:

  • PO 1: Custom software development (distinct — client can use the software independently)
  • PO 2: Post-implementation support (distinct — can be purchased separately)
  • PO 3: Training (distinct — standard training, readily available in market)

Step 3 — Transaction Price: ₹5 crore fixed (no variable consideration)

Step 4 — Allocation using SSPs:

POStandalone Selling PriceAllocation %Allocated Revenue
Software Dev₹4,00,00080%₹4,00,00,000
Support (1yr)₹75,00015%₹75,00,000
Training₹25,0005%₹25,00,000
Total₹5,00,000100%₹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).

Year 1 Software Revenue (60% complete)
₹2,40,00,000
Support Revenue (first 6 months)
₹37,50,000
Journal Entry — Revenue Recognition (IT Company, % Completion)
Contract Asset (Unbilled Revenue) A/c
Dr ₹2,40,00,000
Revenue from Operations A/c
Cr ₹2,40,00,000
(Revenue recognised proportionate to costs incurred; billed amount goes to Trade Receivables, unbilled goes to Contract Asset)

🏠 Case Study 2: Real Estate Developer

Residential Apartment Project — Godrej Properties / DLF-type scenario

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:

  • The apartment has no alternative use (i.e., it cannot be redirected to another buyer), AND
  • The developer has an enforceable right to payment for performance completed to date (even if the buyer cancels)

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.

Revenue Recognised (Old % Completion)
₹96 Cr (60% complete)
Revenue Recognised (Ind AS 115)
₹0 (until possession)

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.

Journal Entry — Real Estate: Advance Received During Construction
Bank A/c
Dr ₹8,00,00,000
Contract Liability (Advance from Customers) A/c
Cr ₹8,00,00,000
(On receipt of 10% booking amount — classified as Contract Liability until possession)
On Possession (Revenue Recognition):
Contract Liability A/c
Dr ₹80,00,00,000
Revenue from Operations A/c
Cr ₹80,00,00,000

📞 Case Study 3: Telecom Company

Jio / Airtel-type Bundled Contract (Handset + Data Plan)

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:

POSSPAllocated AmountRecognition
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.

Revenue Day 1 (Handset)
₹20,270
Revenue Per Month (Data)
₹811

8. Variable Consideration & The Constraint

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:

  • High susceptibility to factors outside the entity's control (weather, market conditions)
  • Long time before uncertainty resolves
  • Entity has limited experience with similar contracts
  • Contract has a wide range of possible amounts

Common examples in India: volume rebates for FMCG distributors, construction milestones bonuses for EPC contractors, performance bonuses for IT services contracts.

Variable Consideration — EPC Contract Performance Bonus
Contract with ₹100 Cr base fee + ₹10 Cr bonus if completed before deadline
Probability of achieving bonus: 60%
Expected Value: ₹10 Cr × 60% = ₹6 Cr. But is this "highly probable no reversal"?
If constrained — include ₹0 bonus until highly probable.
If unconstrained — recognise ₹6 Cr over project duration.
Transaction Price recognised = ₹100 Cr + constrained variable consideration

9. Contract Modifications

When a contract is modified (scope change, price change), it is treated as:

  • A new separate contract: If the modification adds distinct goods/services at prices that reflect standalone selling prices
  • Termination of old + creation of new: If remaining goods/services are distinct but price is not commensurate with SSP
  • A modification of existing contract: If remaining goods/services are not distinct — prospective or cumulative catch-up adjustment

10. Contract Costs

Incremental Costs of Obtaining a Contract

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.

Costs to Fulfil a Contract

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.

Contract Cost Asset — Sales Commission Capitalisation
IT company wins 3-year managed services contract; pays sales agent ₹15 lakh commission
Contract Cost Asset A/c
Dr ₹15,00,000
Sales Agent Payable A/c
Cr ₹15,00,000
Amortisation (₹15L ÷ 36 months = ₹41,667/month):
Sales/Marketing Expense A/c
Dr ₹41,667
Contract Cost Asset A/c
Cr ₹41,667

11. Key Disclosure Requirements

Ind AS 115 requires extensive disclosures in financial statements:

Disclosure CategoryKey Items Required
Revenue disaggregationRevenue by geography, product/service type, customer type, contract type (fixed/variable), timing (point/over time)
Contract balancesOpening and closing balances of Contract Assets, Contract Liabilities, Receivables; revenue recognised from opening Contract Liability
Performance obligationsDescription of each PO, significant payment terms, obligations for returns/refunds
Significant judgementsMethods used to determine transaction price and allocation; over time vs point in time determination
Contract costsClosing balances of capitalised contract costs; amortisation and impairment
Remaining performance obligationsAggregate transaction price allocated to unsatisfied/partially satisfied POs, and when recognition expected (practical expedient if ≤1 year)

12. Common Errors & Audit Focus Areas

Top 5 Implementation Errors (Based on ICAI Guidance):
  1. Treating entire bundled IT contract as one PO instead of unbundling into licence, implementation, support
  2. Not applying variable consideration constraint — recognising too much revenue from bonus/penalty-linked contracts
  3. Real estate companies recognising revenue on percentage completion basis where "enforceable right to payment" criterion is not met
  4. Not adjusting for significant financing component in long-cycle manufacturing contracts with advance payments
  5. Expensing incremental contract acquisition costs (sales commissions on multi-year contracts) instead of capitalising

✅ Key Takeaways — Ind AS 115

  • 5-step model: Identify Contract → Identify POs → Determine Price → Allocate → Recognise
  • Revenue recognition driven by control transfer, not just risks and rewards
  • Real estate companies: revenue typically at possession (point in time), not % completion
  • IT companies: bundle contracts must be unbundled; licence ≠ support ≠ implementation
  • Telecom: discount on bundles must be proportionately allocated to all POs
  • Variable consideration: include only if highly probable no significant reversal
  • Contract costs (incremental acquisition costs): capitalise and amortise over benefit period
  • Extensive disclosures required including disaggregated revenue, contract asset/liability movements
📊
Analyse Revenue Recognition in Listed Company FinancialsUse Finin2min's FinMarket tool to view revenue notes, contract asset/liability disclosures, and disaggregated revenue data for NSE/BSE listed companies.
Open FinMarket →

❓ Frequently Asked Questions

What is the key difference between Ind AS 18 and Ind AS 115?

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.

How does Ind AS 115 impact real estate company revenues?

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.

What is a Contract Asset vs a Contract Liability under Ind AS 115?

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.