Revenue Recognition

Revenue recognition was arguably the most consequential area of accounting judgement, because reported revenue was the top line of the income statement and the foundation on which all profitability ratios and growth analyses rested. Manipulating revenue recognition — accelerating it to meet quarterly targets or deferring it to manage earnings expectations — was one of the most common forms of financial statement manipulation globally. Ind AS 115 (converged with IFRS 15) established a comprehensive five-step model to guide recognition: (1) identify the contract with the customer, (2) identify the performance obligations in the contract, (3) determine the transaction price, (4) allocate the transaction price to the performance obligations, and (5) recognise revenue when each performance obligation is satisfied.

The transition to Ind AS 115 required significant accounting changes for several Indian industries. For IT services companies, contracts often bundled multiple deliverables (software implementation, maintenance, training). Under the new standard, the total contract value had to be allocated between these distinct performance obligations based on standalone selling prices rather than recognising revenue based on contract milestones alone. This changed the timing of revenue recognition for multi-year, multi-element IT contracts.

For real estate companies — one of the most scrutinised sectors in India for revenue recognition practices — Ind AS 115 mandated a shift from the percentage-of-completion method (previously common for under-construction projects) to a model focused on when control of the unit transferred to the buyer. For many developers, this meant recognising revenue only on handover of possession rather than progressively during construction, significantly backloading revenue and profit recognition. The listed real estate sector saw material restatements when this transition occurred.

Subscription-based and contractual businesses faced their own recognition challenges. A software company receiving an annual subscription upfront recognised the cash immediately but spread revenue over the service period. Deferred revenue — the balance sheet liability representing cash received but revenue not yet recognised — was therefore a key metric for subscription businesses. Growing deferred revenue indicated future revenue backlog, a positive signal, while declining deferred revenue could foreshadow lower near-term revenue.

For investors, examining accounting policy notes for revenue recognition was essential. Policies that differed from industry norms — earlier recognition of performance bonuses, inclusion of gross versus net revenue, or deferral of certain costs against revenue — warranted scrutiny. Auditor qualifications or emphasis-of-matter paragraphs relating to revenue recognition were significant red flags, as seen in historical cases involving IT services or real estate companies where aggressive recognition practices eventually required corrections.