Performance obligation identification is Step 2 of the IFRS 15 model. Get this wrong, and your entire revenue recognition timeline is wrong. This guide walks through the "distinct" test, bundled products, and the audit challenges around separating vs combining obligations.
What Makes a Good or Service Distinct?
A good/service is distinct if:
- The customer can benefit from it: On its own OR with other resources they can readily obtain (e.g., they already own the complementary item)
- The entity's promise is separately identifiable: The good/service is not so integrated with other promises that it's a single obligation
Bundled Products: When to Separate
| Scenario | Distinct? | Reason |
|---|---|---|
| Smartphone + protective case (sold together at discount) | Separate | Customer can use phone without case |
| SaaS software + dedicated support team | Separate | Customer can use software with generic support |
| Car + 3-year manufacturer warranty | Separate | Warranty is separately transferable; customer can use car without warranty |
| Construction + installation of machinery | Single | Customer cannot benefit until both are complete |
| Custom software development (fully integrated solution) | Single | Delivery and integration are inseparable |
Worked Example: Mobile Phone Bundle
Scenario: Telecom company sells 2-year mobile plan with phone and service bundled for £600 total.
- Phone hardware: Distinct. Customer can use it with another provider.
- 2-year monthly service: Distinct. Transferable to another customer/phone.
- Number of obligations: 2 (hardware + service)
- Allocation: Hardware = £150 (point-in-time); Service = £450 (over-time, 24 months = £18.75/month)
Worked Example: Software + Customization
Scenario: Enterprise software vendor contracts to deliver software + 6-month customization for £100,000.
- Off-the-shelf software: Distinct. Other customers can use the same software.
- Customization services: Distinct. Services are separately identifiable (vendor could subcontract or customer could hire another firm).
- Number of obligations: 2
- Revenue pattern: Software recognized at delivery (point-in-time); customization over 6 months (over-time)
Audit Focus: The Integration Test
Auditors challenge whether items are truly separate. Common pushback:
- "You separated hardware and service, but the contract says customer must use both together. Are they truly separate?"
- "You have one PO for 'system delivery.' How did you justify two performance obligations?"
- "You allocated based on standalone prices. Where's the evidence those prices are accurate?"
Real-Life Case Study: Identifying Distinct Obligations in a Construction Contract
Scenario. A contractor agrees to design, build, and fit out a bespoke facility for £5m.
Judgement. Although design, build and fit-out could be separate services, here they are highly interdependent and the contractor integrates them into one combined output the customer controls as it is built. They are therefore not distinct in the context of the contract, so they form a single performance obligation satisfied over time.
Takeaway. "Could it be sold separately?" is only half the test. The second half, "is it separately identifiable in this contract, or is it an input to a combined item?", is what turns three activities into one performance obligation.
Illustrative composite scenario for educational purposes. Figures are indicative and do not represent any specific company.
• IFRS 15 Variable Consideration: Discounts, Bonuses & Constraint Application
• IFRS 15 Contract Assets & Liabilities: Timing Differences & Disclosure
• IFRS 15 Over-Time vs Point-in-Time Revenue: Decision Framework