Beyond the Numbers: How IND AS 115 Brought Transparency to Revenue Recognition – A Cross-Industry Roadmap for Businesses & Investors

 

IND AS 115 in Action: 5 Industry Examples That Show How Revenue Recognition Changed Forever

If you've been following our series on India's accounting revolution, you already know that IND AS 115 fundamentally reshaped how companies recognize revenue. But theory only goes so far – let's see how this plays out in the real world across five major industries.

Example 1: Construction Contracts – Building Bridges, One Performance Obligation at a Time

The Old Way (IND AS 18):

A construction company would recognize revenue progressively as work was completed – simple percentage-of-completion method.

The New Way (IND AS 115):

Revenue is now recognized based on transfer of control, not just progress.

Real-World Scenario:
Imagine a company building a bridge for a government client. Under IND AS 115, they must first identify distinct performance obligations within that single contract:

Performance Obligation	When Control Transfers	Revenue Recognized
Design completion	When designs approved & handed over	✅ At design sign-off
Construction phases	As each section is completed & accepted	✅ Milestone-based
Testing & handover	After successful testing & customer acceptance	✅ At final delivery

Example 2: Software Companies – It's Not Just About the Download Anymore

The Old Way:

Click → Download → Book revenue. Simple.

The New Way:

Every contract must be unbundled into separate performance obligations.

Real-World Scenario:
A software company sells an enterprise license package to a corporate client for ₹50 lakhs. The contract includes:

 

Component	Old Treatment	New Treatment (IND AS 115)
Software license	Full ₹50L at download	Recognized over license period
Installation support	Bundled, often ignored	Separate obligation – recognize on completion
Training services	Usually not separated	Distinct obligation – recognize when training delivered
Ongoing support	Sometimes deferred	Separate subscription revenue over support period

Key Takeaway: What looked like one sale is now potentially four separate revenue streams, each with its own recognition timeline.

---

📱 Example 3: Telecom – Unbundling the "Free Phone" Illusion

The Old Way:

Services provided = Revenue booked. Device subsidies? Often opaque.

The New Way:

Every element of that "mobile plan + free phone" deal gets its own treatment.

Real-World Scenario:
A telecom company offers a customer:

• A smartphone (₹30,000 value)
• A 24-month postpaid plan (₹999/month)
• Data pack bundled in

Under IND AS 115:

text

┌─────────────────────────────────────────────────┐

│ CONTRACT PRICE: Allocated across obligations │

├─────────────────────────────────────────────────┤

│ 📱 Mobile Device → Revenue at delivery │

│ 📡 Mobile Services → Revenue over 24 months │

│ 📊 Data Pack → Revenue as data consumed │

└─────────────────────────────────────────────────┘

Key Takeaway: That "free" phone isn't free anymore – it has a standalone selling price, and revenue recognition reflects reality, not marketing gimmicks.

---

🛍️ Example 4: Retail – Beyond the Billing Counter

The Old Way:

Customer pays → Goods handed over → Revenue recognized. Done.

The New Way:

The sale might just be the beginning of multiple performance obligations.

Real-World Scenario:
An electronics retailer sells an air conditioning unit with installation and extended warranty:

Stage	Event	Revenue Recognition Trigger
Sale	Customer purchases AC	⏳ Not yet – control hasn't fully transferred
Delivery	AC reaches customer location	✅ Partial – goods transferred
Installation	Technician installs & tests unit	✅ Remaining goods revenue + installation revenue
Warranty period	2-year coverage active	✅ Deferred revenue recognized over warranty period

Key Takeaway: For retailers offering complex products with add-on services, the point of sale is no longer the point of full revenue recognition.

---

🏥 Example 5: Healthcare – Treating Each Service as a Separate Promise

The Old Way:

Service provided = Revenue recorded. Straightforward for most healthcare providers.

The New Way:

Even healthcare contracts have layers that must be peeled back.

Real-Word Scenario:
A hospital provides a comprehensive treatment package to a patient:

Performance Obligation	Example	Recognition Point
Diagnosis	Tests, consultations, reports	Upon completion & report delivery
Treatment	Surgery, procedures, therapy	When service performed
Follow-up care	Post-op visits, rehab sessions	Over the follow-up period
Medication/Supplies	Drugs, medical devices	At dispensing/delivery