Ind AS 115: Identifying Performance Obligations When Contracts Bundle Goods and Services
Imagine a software company sells you a licence, installs the software, and promises one year of customer support — all in one contract for a single price. How much revenue gets recognised, and when? That question sits at the heart of Ind AS 115, and it is one of the most examiner-favourite areas in CA Final Financial Reporting.
Let's break it down the way I explain it in class — step by step, no jargon overload.
---
Why 'Bundled' Contracts Create a Problem
When a seller clubs multiple goods or services into one contract and charges a single lump-sum price, accounting gets tricky. Revenue timing depends on when each obligation is satisfied, not merely when cash is received. If you treat the whole bundle as one obligation, you risk recognising revenue too early or too late.
Ind AS 115 solves this by requiring you to unbundle the contract into its performance obligations first.
---
Step 2 of the Five-Step Model: Identify Performance Obligations
The Ind AS 115 five-step model is:
- Identify the contract
- Identify the performance obligations ← today's focus
- Determine the transaction price
- Allocate the transaction price
- Recognise revenue when (or as) each obligation is satisfied
A performance obligation is a promise to transfer either:
- A distinct good or service, or
- A series of distinct goods or services that are substantially the same and have the same pattern of transfer
---
The 'Distinct' Test — Two Hurdles to Clear
This is where students lose marks. A good or service is distinct only if it satisfies both of the following conditions:
Hurdle 1 — Capable of Being Distinct (Customer's Perspective)
The customer can benefit from the good or service on its own, or together with other resources that are readily available to them. Ask yourself: could the customer use this item independently, or sell it, or consume it without the rest of the bundle?
Hurdle 2 — Distinct Within the Context of the Contract (Entity's Perspective)
The entity's promise to transfer the good or service is separately identifiable from other promises in the contract. In plain English: are the items really independent, or is the seller's job to weave them together into one integrated output?
Both hurdles must be cleared. Fail even one, and the item is bundled with related goods/services into a single performance obligation.
---
Signals That Items Are NOT Separately Identifiable
Ind AS 115 gives practical indicators that promises are not distinct within the contract context:
- The entity provides a significant integration service — it combines the items into one combined output (think a construction contract that uses materials, labour, and design together).
- One item significantly modifies or customises another item in the contract.
- The goods or services are highly interdependent — neither has standalone utility without the other.
If any of these apply, you combine those items into one performance obligation.
---
Worked Logic: Software Bundle Example
Suppose TechSol Ltd enters a contract with a client for:
- (A) A software licence
- (B) Installation services (customising the software to the client's servers)
- (C) One year of post-installation technical support
Applying the distinct test:
- (A) + (B) together: The installation significantly customises the software for the client's environment. The licence alone has no utility until installation is done. They are highly interdependent → combine A and B into one performance obligation (recognised over time, as installation progresses).
- (C) Technical support: The client can benefit from support independently — other vendors offer similar support, and support does not modify the software. It is separately identifiable → separate performance obligation (recognised over the 12-month support period).
Result: Two performance obligations, not three and not one. Revenue is recognised across two different timelines.
---
Allocating the Transaction Price Using Standalone Selling Price
Once obligations are identified, the transaction price is allocated in proportion to each obligation's standalone selling price (SSP) — the price the entity would charge for that item if sold separately.
If SSP is not directly observable, Ind AS 115 allows estimation methods such as:
- Adjusted market assessment — what would the market pay?
- Expected cost plus margin — cost to fulfil plus a reasonable margin
- Residual approach — only in limited, specific circumstances (verify eligibility in the latest ICAI study material)
For our TechSol example, if SSP of (A+B) is ₹4,00,000 and SSP of (C) is ₹1,00,000, and total contract price is ₹4,50,000, allocate:
- A+B: 4,00,000 / 5,00,000 × 4,50,000 = ₹3,60,000
- C: 1,00,000 / 5,00,000 × 4,50,000 = ₹90,000
---
Exam Strategy Tips
- Always write both hurdles of the distinct test — one-hurdle answers lose easy marks.
- State clearly whether each obligation is satisfied at a point in time or over time.
- When a question gives you a lump sum, automatically think: Do I need to split this?
- Watch for keywords like 'integrated solution', 'customised output', or 'significant modification' — these signal a combined obligation.
- Cross-check your SSP allocation — it must add up to the transaction price (before any variable consideration adjustments).
---
FAQs
Q1. What if the contract has a variable component — does that affect how I identify obligations? Identifying performance obligations is a separate exercise from determining or allocating variable consideration. Identify obligations first, then handle variable amounts in Steps 3 and 4. Keep the steps clean and sequential.
Q2. Can a warranty be a separate performance obligation under Ind AS 115? Yes — but only if it provides a service beyond assurance that the product meets agreed specifications (an assurance-type warranty is accounted for under Ind AS 37). If the customer can purchase the warranty separately or it covers additional services, it qualifies as a distinct performance obligation. Verify the latest ICAI guidance for exam-specific treatment.
Q3. My question has five items in the contract. Must I test each one individually? Yes, the distinct test applies item by item. However, items that fail the test get combined into a bundle. You may end up with fewer performance obligations than items — that is perfectly normal and expected.
---
Mastering Ind AS 115 is less about memorising rules and more about applying a logical sequence to every contract scenario. The best way to build that instinct is structured daily practice. Use the free day-by-day study planner at caparveensharma.com/free-planner?src=article to schedule your FR revision, and sharpen your application skills with free case-scenario practice available in the courses at caparveensharma.com. You've got this!