Understanding Ind AS 115: The Framework for Revenue Recognition
Revenue recognition under Ind AS 115 has transformed how Indian companies report their income. As a CA student, you'll find this standard forms the backbone of financial reporting in almost every industry—from construction and IT services to telecommunications and e-commerce. Rather than relying on old, industry-specific rules, Ind AS 115 gives you a single, logical framework.
The heart of the standard is simple: recognize revenue when (or as) you transfer promised goods or services to a customer in exchange for consideration. But applying this principle requires discipline and careful thought.
The 5-Step Revenue Recognition Model
Ind AS 115 codifies a five-step process. Following these steps in order prevents confusion and ensures consistency:
Step 1: Identify the Contract with a Customer
A contract exists when:
- Both parties have approved the contract
- Each party's rights are identifiable
- Payment terms are clear
- The contract has commercial substance
- Collection is probable
If a contract doesn't meet these criteria, you don't apply the full standard yet. Payments received before a valid contract exist go to a liability account (contract liability), not revenue.
Step 2: Identify the Performance Obligations
A performance obligation is a promise to transfer a distinct good or service (or group of goods/services) to the customer. This is where many students stumble—you must train your eye to spot each distinct obligation.
A good or service is distinct if:
- The customer can benefit from it alone or with other resources the customer has
- The company's promise to transfer it is separately identifiable from other promises in the contract
Example: A software company sells a three-year subscription including (a) cloud hosting, (b) monthly updates, and (c) 24/7 support. Are these one performance obligation or three?
Analysis: The customer could use the hosting alone and benefit from it. The updates and support enhance the core service but are separately identifiable. However, these three items are so intertwined that they function as one integrated service. After examining the contract, you may conclude this is one performance obligation: 'continuous access to a software platform over three years.' The answer depends on contractual facts, not a rigid rule.
Step 3: Determine the Transaction Price
The transaction price is the amount of consideration you expect to receive for satisfying performance obligations. It sounds straightforward, but it has tricky corners:
Fixed consideration: The contracted price—usually clear.
Variable consideration: Discounts, rebates, refunds, penalties, or bonuses that depend on future events. You include variable consideration only if it is probable that a significant reversal will not occur when the uncertainty resolves. Conservatism applies here.
Time value of money: If a contract spans a long period and payment is substantially deferred, adjust the transaction price for the time value of money (discount it back to present value). Verify current thresholds in the latest ICAI guidance.
Non-cash consideration: If a customer pays with goods or equity, measure at fair value.
Consideration payable to the customer: Refunds, free products, or rebates reduce the transaction price.
---
Worked Example – Transaction Price with Variable Consideration:
A logistics company signs a two-year supply contract with a retailer.
- Base fee: ₹12,00,000 per year (fixed)
- Performance bonus: If on-time delivery exceeds 98%, an additional ₹50,000 per year
- Early payment discount: If paid within 10 days, 2% discount
The company estimates a 75% probability of exceeding 98% on-time delivery. The retailer typically pays within 15 days, so the 2% discount is unlikely (only 10% probability).
Transaction price calculation:
- Fixed portion: 2 × 12,00,000 = ₹24,00,000
- Bonus (variable): 75% probability × ₹50,000 × 2 years = ₹75,000 included (> 50% threshold = probable)
- Early discount: 10% probability → exclude (not probable), unless a change in assessment occurs later
- Total transaction price: ₹24,75,000
---
Step 4: Allocate the Transaction Price
If a contract contains multiple performance obligations, split the transaction price among them based on their standalone selling prices. The standalone selling price is what you would charge a customer for a good or service on its own.
Methods to estimate standalone selling price:
- Adjusted market assessment: Survey competitors' prices
- Expected cost plus margin: Cost + reasonable markup
- Residual method: Allocate the transaction price to one or more obligations at their standalone prices; allocate the remainder to other obligations (use only when you cannot reliably estimate the standalone price of some obligations)
---
Worked Example – Allocating Price to Multiple Obligations:
A telecom company sells a bundled offer:
- Mobile plan (24-month contract) with a smartphone
- Standalone mobile plan price (without phone): ₹500/month = ₹12,000 for 24 months
- Standalone phone price: ₹8,000
- Bundle price: ₹15,000 (all-in, upfront)
Total standalone prices: 12,000 + 8,000 = ₹20,000
Allocation:
- Mobile plan: (12,000 / 20,000) × 15,000 = ₹9,000 (recognized over 24 months)
- Phone: (8,000 / 20,000) × 15,000 = ₹6,000 (recognized at delivery)
---
Step 5: Recognize Revenue When (or As) Each Obligation Is Satisfied
Revenue is recognized over time or at a point in time, depending on when the customer obtains control of the promised good or service.
Over time: Revenue is recognized as work progresses if one or more of the following is true:
- The customer simultaneously receives and consumes the benefit
- The company's performance creates or enhances an asset the customer controls
- The company's performance does not create an asset with alternative use, and the company has a right to payment for work completed
Measure progress using input methods (% of costs incurred, % of time elapsed) or output methods (units delivered, milestones achieved).
Point in time: Revenue is recognized when the customer obtains control. In many retail and e-commerce scenarios, this is at delivery or customer acceptance.
Contract Assets and Contract Liabilities
These are the balances that bridge the gap between when you recognize revenue and when you receive cash.
Contract Asset: Arises when you have recognized revenue but have not yet received payment or have not yet earned the right to payment. In essence, you've delivered; the customer owes you.
Example: You complete 40% of a construction project and recognize ₹40 lakhs in revenue. The customer pays only ₹30 lakhs. Your contract asset = ₹10 lakhs (an unbilled receivable).
Contract Liability: Arises when the customer has paid but you have not yet satisfied the performance obligation. The liability is discharged by delivering the good or service.
Example: A SaaS company receives ₹60 lakhs upfront for a 12-month annual subscription. At year-end, they've delivered only 9 months' service. Contract liability = (3 months / 12 months) × ₹60 lakhs = ₹15 lakhs.
Practical Tips for CA Exams
- Identify performance obligations first — this drives everything else.
- Distinguish between contract assets and trade receivables — examiners love this distinction.
- Always ask: "Has the customer obtained control?" — this single question resolves half the confusion.
- Document your estimates — especially for variable consideration and standalone prices. Show your logic.
- Watch for long-term contracts — time value adjustments and contract modifications are common complications.
FAQs
Q: When do I record a contract asset versus a trade receivable? A: A contract asset arises when you have satisfied a performance obligation but have not yet earned an unconditional right to payment (e.g., work is complete but the customer has not approved it, or payment is contingent on a milestone). A trade receivable is recorded only when you have an unconditional right to payment.
Q: How do I handle a contract modification under Ind AS 115? A: A modification that increases the scope and price is treated as a new contract (or combined with the original, depending on facts). A modification that changes existing obligations may require reallocation of the transaction price. Verify the specific rules in your study material.
Q: If a customer returns goods within a warranty period, how do I account for returns? A: Estimate the expected returns as a variable consideration and reduce the transaction price at the outset. As returns actually occur, reverse the corresponding revenue. Maintain a provision for expected returns as a contract liability.
---
Revenue recognition is not a formula you memorize—it's a mindset. Train yourself to think in terms of promises made, obligations satisfied, and control transferred. Master Ind AS 115, and you've mastered one of the most critical standards in financial reporting.
Want structured daily guidance? Use the free day-by-day study planner to build a habit of consistent learning. For worked scenarios and practice problems, explore the free resources at caparveensharma.com.