Introduction
Revenue is the most significant indicator of business performance and financial health. The principle of revenue recognition is one of the most scrutinized elements of accounting standards globally, as it directly impacts reported profitability and investor perception. Any premature or delayed recognition can distort earnings, mislead stakeholders, and result in regulatory action.
In India, AS 9 governs revenue recognition in the traditional Accounting Standards framework, while Ind AS 115, aligned with IFRS 15, governs entities required to follow Ind AS. While AS 9 offers clarity for simple transactions, its limitations in handling modern business complexities prompted the need for Ind AS 115.
This article offers an extended 4,000-word professional analysis of revenue recognition, emphasizing corporate case studies, industry-specific issues, and detailed illustrations to highlight practical complexities.
Fundamental Accounting Concepts Underlying Revenue Recognition
(Already discussed earlier – retained with elaboration)
Revenue Recognition under AS 9 and Ind AS 115 – A Recap
(Already explained – retained with enhancements)
Corporate Case Studies – Extended Analysis
1. Infosys (IT Services)
Infosys often enters into contracts for ERP implementation, software licenses, and multi-year maintenance. Under AS 9, recognition largely followed completion of services or proportionate completion. With Ind AS 115, revenue recognition now depends on performance obligations: license revenue recognized upfront, while support and upgrades are spread across the service period. This required a complete overhaul of contract accounting systems.
2. Tata Consultancy Services (Global Projects)
TCS delivers projects across geographies with varied milestones. A European banking client may demand custom software development, migration, and maintenance. Under Ind AS 115, each milestone—development, migration, support—is a separate obligation, complicating allocation of revenue. The challenge lies in estimating progress on projects that stretch across multiple countries with regulatory restrictions.
3. DLF & Godrej Properties (Real Estate)
Indian real estate underwent a paradigm shift. Under AS 9 (read with AS 7 practices), percentage completion was the norm. With Ind AS 115, revenue is recognized only when enforceable right to payment exists. Developers now defer recognition until substantial completion, which suppressed early profitability but enhanced transparency. For instance, DLF had to restate its revenues when Ind AS 115 was implemented.
4. Bharti Airtel & Reliance Jio (Telecom)
Telecom operators faced complexity in bundled sales. Under AS 9, revenue often got recognized as lump sum without granular allocation. Under Ind AS 115, handsets, data plans, and talk-time are separated. Airtel had to record higher upfront handset revenue and defer telecom services revenue. Reliance Jio, with its promotional plans, had to defer significant revenue into future years.
5. Flipkart & Amazon India (E-commerce)
E-commerce platforms operate with marketplace models. The core complexity is determining principal vs. agent. Under Ind AS 115, if control does not transfer to the company, only commission income can be recognized. Flipkart records commission (net revenue), while goods sold are treated as third-party transactions. This lowered gross revenue but aligned with global standards.
6. Dr. Reddy’s Laboratories (Pharma)
Pharma companies often sell under rebate-linked agreements. Under AS 9, rebates were recorded when incurred. Ind AS 115 requires estimating rebates upfront and adjusting revenue. Dr. Reddy’s reduced upfront revenue recognition by provisioning for rebates. This prevents overstated profits.
7. Maruti Suzuki (Manufacturing)
Car sales bundled with warranties created accounting complexity. Ind AS 115 requires separation of warranty as a performance obligation, deferring part of the revenue. For Maruti, service warranties and extended warranties are deferred over time, reducing initial reported revenue.
Real-Life Illustrations – Expanded
Illustration 1: Software Implementation Contract
XYZ Ltd. signs a ₹10 crore contract for ERP system delivery:
– ERP License: ₹6 crore
– Implementation: ₹2 crore
– 2-year Support: ₹2 crore
Under Ind AS 115:
– License revenue (₹6 crore) recognized when software is transferred.
– Implementation (₹2 crore) recognized on percentage completion.
– Support (₹2 crore) spread across 24 months.
Earlier under AS 9, much of this might have been recognized upfront, overstating early profits.
Illustration 2: Real Estate Project
ABC Developers sells 100 flats worth ₹50 lakh each. By 2025, 40% construction is completed. Under AS 9, revenue could be recognized based on percentage completion. Under Ind AS 115, unless there is enforceable right to payment, recognition is deferred. This impacts both reported profits and cash-flow-based assessments.
Illustration 3: Telecom Bundle
Customer pays ₹24,000 for handset + 12-month plan. Handset standalone = ₹12,000, service = ₹15,000.
– Allocate proportionately: ₹11,294 handset, ₹12,706 service.
– Handset revenue recognized immediately, service over 12 months.
This ensures fair timing of revenue.
Illustration 4: Pharma Rebate
Pharma company sells for ₹100 crore with 15% rebate if sales exceed threshold. Expected sales exceed threshold. Under Ind AS 115, revenue recognized = ₹85 crore, not ₹100 crore.
Illustration 5: Banking Fees
Bank charges ₹1 lakh loan processing fee. Under AS 9, it might be recognized upfront. Under Ind AS 115 (read with Ind AS 109), recognition is spread over loan tenure using effective interest rate.
Industry-Specific Complexities – Expanded
1. Information Technology
– Multi-element contracts (license, maintenance, upgrades).
– SaaS-based models with subscription billing.
– Cloud computing revenue (recognized over service term).
2. Telecom
– Bundled contracts with equipment and services.
– Loyalty programmes requiring deferred recognition.
– Revenue sharing with partners.
3. Real Estate & Infrastructure
– Shift from percentage completion to performance obligations.
– Compliance with RERA complicates timing of recognition.
– Delayed recognition impacts borrowings and solvency ratios.
4. Banking & Financial Services
– Processing fees, restructuring charges, foreclosure penalties.
– Ind AS 115 links with Ind AS 109, requiring effective interest rate method.
– Complexity in securitization and sale of loans.
5. Manufacturing & Auto Sector
– Bill-and-hold sales where delivery is delayed.
– Consignment arrangements.
– Warranty and service packages requiring deferred recognition.
6. E-commerce & Retail
– Agent vs. principal complexity.
– Discount-driven contracts and promotional offers.
– Cashbacks treated as variable consideration.
Audit and Regulatory Considerations – Extended
Revenue recognition is a key audit matter (KAM) for almost all listed entities. The reliance on management judgment in Ind AS 115 increases audit risk. Auditors must:
– Verify contracts carefully.
– Assess standalone selling prices.
– Test IT systems generating revenue data.
– Evaluate management’s estimates on rebates, returns, and discounts.
SEBI, NFRA, and ICAI frequently emphasize transparent disclosures. Revenue misstatement has been one of the leading causes of corporate fraud globally.
Conclusion
Revenue recognition is no longer a mechanical exercise but a complex judgment-driven process. AS 9 offered simplicity, but its inadequacies in handling complex contracts necessitated Ind AS 115. The transition has enhanced comparability and transparency but also introduced significant challenges.
For Chartered Accountants, mastery of both standards is crucial, not just for compliance but also for guiding corporates on contract structuring, system implementation, and audit readiness.
Author Bio
