Key Points
- Each performance obligation identified in a contract gets its own revenue allocation and its own recognition pattern.
- A good or service is distinct if the customer can benefit from it on its own and the promise is separately identifiable within the contract.
- Misidentifying performance obligations is the single fastest way to misstate the timing of revenue recognition.
- IFRS 15.27 lists specific indicators for determining whether promises are separately identifiable, including significant integration and customisation.
What is Performance Obligation?
IFRS 15.22 requires the entity to identify, at contract inception, every performance obligation in the arrangement. The identification hinges on a two-part test at IFRS 15.27: the customer can benefit from the good or service either on its own or together with other readily available resources (the "capable of being distinct" leg), and the entity's promise to transfer that good or service is separately identifiable from other promises in the contract (the "distinct within the context of the contract" leg).
The second leg is where judgment concentrates. A software licence and a two-year implementation service might each be capable of being distinct, but if the implementation significantly modifies the software, IFRS 15.29(a) treats them as a single obligation. The auditor's job under ISA 540.13(a) is to evaluate whether the entity applied the right framework to the right unit of account. Get the performance obligation identification wrong and every downstream step (allocation of the transaction price, timing of recognition) inherits the error.
For contracts with variable consideration, the allocation happens at the performance obligation level, which makes correct identification doubly important.
Worked example: Dupont Ingénierie S.A.S.
Client: French engineering services firm, FY2025, revenue €92M, IFRS reporter. Dupont enters a €2.4M contract with a Belgian manufacturer to deliver a customised water treatment system. The contract includes design, equipment supply, installation, and a 12-month maintenance package.
Step 1 — Identify promised goods and services
The contract contains four explicit promises: (a) engineering design for the system, (b) manufacture and delivery of the physical equipment, (c) on-site installation and commissioning, and (d) a post-installation maintenance package.
Step 2 — Assess "capable of being distinct"
The customer could source maintenance from a third party, so promise (d) passes the first leg. The design, equipment, and installation, however, require evaluation. The design is bespoke to the customer's facility, and the equipment is configured to that design.
Step 3 — Assess "distinct within the context of the contract"
Dupont's design work significantly modifies and customises the equipment (IFRS 15.29(a)). The installation involves integrating the custom equipment into the customer's existing plant infrastructure. These three promises (design, equipment, installation) are highly interdependent. They fail the IFRS 15.29(c) test because each significantly affects the other. The maintenance package, by contrast, does not modify or customise anything.
Step 4 — Allocate the transaction price
Dupont allocates the €2.4M transaction price to the two performance obligations based on relative stand-alone selling prices. The combined design-equipment-installation obligation receives €2.16M (based on comparable project pricing). The maintenance obligation receives €240,000 (based on Dupont's standard annual maintenance rate for systems of this size).
Conclusion: two performance obligations produce two distinct recognition patterns (the combined obligation recognised over time as the system is built; maintenance recognised monthly), and the allocation is defensible because both stand-alone selling prices are traceable to market evidence.
Why it matters in practice
The FRC's 2021/22 thematic review of IFRS 15 disclosures found that entities frequently failed to disclose the judgments involved in identifying performance obligations, particularly for bundled arrangements. IFRS 15.123 requires disclosure of significant judgments that affect the amount and timing of revenue, and performance obligation identification is explicitly listed.
Teams often default to treating each deliverable in a contract as a separate performance obligation without performing the IFRS 15.29 analysis. When goods or services are highly interdependent or significantly modify each other, the correct answer is fewer obligations, not more. ISA 540.13(a) requires the auditor to challenge whether the entity's method reflects the economics of the arrangement.
Performance obligation vs. deliverable (legacy IAS 18)
| Dimension | Performance obligation (IFRS 15) | Deliverable (IAS 18) |
|---|---|---|
| Identification test | Two-part: capable of being distinct and separately identifiable within the contract (IFRS 15.27) | No formal identification framework; relied on "components" of a transaction with limited guidance |
| Bundled arrangements | Explicit indicators for combining promises (IFRS 15.29): significant integration, customisation, high interdependence | Separation was judgment-heavy with minimal structural guidance, often resulting in inconsistent practice |
| Revenue allocation | Relative stand-alone selling prices required (IFRS 15.73) | Residual method was common; no single mandated allocation approach |
| Disclosure | Disaggregation by performance obligation type required (IFRS 15.114) | No equivalent disaggregation requirement |
The shift matters because IFRS 15's structured identification test produces more consistent results across entities in the same industry. Under IAS 18, two firms with identical contracts could legitimately identify different units of account.
Related terms
Frequently asked questions
How do I document performance obligations in the audit file?
Include a schedule listing every promise in the contract, the IFRS 15.27 assessment for each promise, and the conclusion on which promises combine into a single obligation. IFRS 15.123 requires disclosure of significant judgments, so the audit file should mirror that disclosure with the supporting analysis that underpins it.
Does the number of performance obligations affect the audit risk assessment?
Yes. Contracts with multiple performance obligations require separate allocation of the transaction price and separate recognition timing. ISA 315.12(f) directs the auditor to understand the entity's revenue recognition policies. More obligations increase the number of estimates and the risk that the allocation contains misstatement.
Can a performance obligation span multiple contracts?
IFRS 15.17 requires the entity to combine contracts entered into at or near the same time with the same customer if certain criteria are met (for example, the contracts are negotiated as a package with a single commercial objective). When contracts are combined, the performance obligation identification applies to the combined arrangement, not to each contract individually.