The five steps
- Identify the contractAn agreement with enforceable rights and a commercial substance.
- Identify performance obligationsEach distinct good or service promised.
- Determine the transaction priceThe amount the company expects to be entitled to.
- Allocate the priceSpread it across obligations by stand-alone selling prices.
- Recognise revenueWhen or as each obligation is satisfied.
A worked example
A company sells a software licence and one year of support for a combined price of Rs 1,30,000. Sold separately, the licence is Rs 1,20,000 and support is Rs 24,000. Assume both are distinct and the licence is a right to use the software as it exists when delivered.
| Obligation | Stand-alone price (Rs) | Allocated price (Rs) |
|---|---|---|
| Licence | 1,20,000 | 1,08,333 |
| Support | 24,000 | 21,667 |
| Total | 1,44,000 | 1,30,000 |
Allocation is 1,30,000 × 1,20,000 / 1,44,000 for the licence and the balance for support. The licence revenue is recognised when control passes. The support revenue of Rs 21,667 is recognised over the year, roughly Rs 1,806 a month.
Point in time or over time
- Over time when the customer receives and consumes the benefit as the company performs, or when the company creates an asset the customer controls
- Otherwise at the point in time when control passes
Who follows it
Ind AS 115 applies to companies that follow Ind AS. Other entities follow the older AS 9 on revenue recognition. Check which framework applies before you apply the model.
Most revenue questions are settled by reading what exactly the contract promises and when control passes.
FAQs
What is a performance obligation?
A promise in the contract to transfer a distinct good or service to the customer.
Is revenue recognised when cash is received?
Not necessarily. Recognition follows the transfer of goods or services, so cash may be received before or after.
Does the model apply to every revenue item?
No. Some items, such as leases and financial instruments, are covered by other standards.