Step 1: Identify the Contract
Contract Combination Assessment
(Optional)Contract Modification Assessment
(Optional)Understanding the IFRS 15 Five-Step Revenue Recognition Model
IFRS 15 Revenue from Contracts with Customers replaced IAS 18 Revenue, IAS 11 Construction Contracts, and their related interpretations with a single, comprehensive revenue recognition framework. The standard applies to all contracts with customers, with limited exceptions for leases (IFRS 16), insurance contracts (IFRS 17), and financial instruments (IFRS 9). At its core, IFRS 15 establishes a five-step model that entities apply to determine when and how much revenue to recognise. With 129 paragraphs in the main body and extensive application guidance in Appendix B, manually navigating the standard for each contract is impractical — which is precisely why an interactive decision tree approach is essential.
Step 1: Identify the Contract (IFRS 15.9–21)
A contract is an agreement between two or more parties that creates enforceable rights and obligations. IFRS 15.9 requires five criteria to all be met before a contract exists: the parties have approved the contract and are committed to perform, each party's rights can be identified, payment terms can be identified, the contract has commercial substance, and it is probable the entity will collect the consideration. If any criterion is not met, IFRS 15.15 requires the entity to recognise consideration received only as a liability until the criteria are met or the contract is terminated. This step also addresses contract combinations (IFRS 15.17) — where multiple contracts entered into near the same time should be treated as one — and contract modifications (IFRS 15.18–21), which are accounted for as a separate contract, prospectively, or as a cumulative catch-up depending on whether the modification adds distinct goods or services at commensurate pricing.
Step 2: Identify the Performance Obligations (IFRS 15.22–30)
At contract inception, the entity assesses each promised good or service and identifies those that are distinct — forming separate performance obligations. A good or service is distinct under IFRS 15.27 when it meets two criteria: the customer can benefit from it on its own or together with readily available resources (capable of being distinct), and the promise to transfer it is separately identifiable from other promises in the contract (distinct within the contract context). IFRS 15.29 provides guidance on when promises are not separately identifiable, including significant integration, significant modification or customisation of other promises, and high interdependence. Where goods or services are not distinct, they must be combined with other promises until the resulting bundle is distinct (IFRS 15.30). The series provision in IFRS 15.22(b) treats a series of substantially similar distinct goods or services with the same transfer pattern as a single performance obligation.
Step 3: Determine the Transaction Price (IFRS 15.47–72)
The transaction price is the amount of consideration the entity expects to be entitled to in exchange for transferring goods or services. Five components may affect the price: variable consideration (IFRS 15.50–55), estimated using the expected value or most likely amount method, subject to a constraint that limits inclusion to amounts highly probable not to result in a significant reversal (IFRS 15.56); significant financing components (IFRS 15.60–65), with a practical expedient for contracts where payment occurs within one year of transfer (IFRS 15.63); non-cash consideration measured at fair value (IFRS 15.66); and consideration payable to a customer, which reduces the transaction price unless the payment is for a distinct good or service (IFRS 15.70).
Step 4: Allocate the Transaction Price (IFRS 15.73–90)
When a contract has multiple performance obligations, the transaction price must be allocated to each based on their relative standalone selling prices (SSP). IFRS 15.76–80 provides four methods for estimating SSP: observable price when sold separately (preferred), adjusted market assessment approach, expected cost plus margin approach, and residual approach (permitted only when the SSP is highly variable or uncertain, per IFRS 15.79). IFRS 15.82 permits allocation of a discount entirely to specific performance obligations when certain criteria are met, and IFRS 15.84–86 permits variable consideration to be allocated entirely to a specific performance obligation if the variable payment relates specifically to satisfying that obligation.
Step 5: Recognise Revenue (IFRS 15.31–45)
Revenue is recognised when the entity satisfies a performance obligation by transferring a promised good or service to the customer — that is, when the customer obtains control. IFRS 15.35 provides three over-time criteria: if any one is met, revenue is recognised over time using an appropriate progress measurement method (output or input methods, per IFRS 15.B15–B19). If none of the over-time criteria are met, revenue is recognised at the point in time when control transfers, using the indicators in IFRS 15.38 — including present right to payment, transfer of legal title, physical possession, risks and rewards, and customer acceptance.
Why an Interactive IFRS 15 Decision Tree?
IFRS 15 is one of the most complex standards ever issued by the IASB, spanning 129 paragraphs in the main body plus extensive application guidance. For a single complex contract — such as a multi-element software arrangement or a construction contract with variation orders — manually working through the standard can take 30 to 90 minutes. This tool reduces that time by guiding you through only the relevant decision nodes for your specific contract, while automatically generating the documented audit trail that ISA 230 requires.
Non-Big 4 firms face a particular challenge: the major firms maintain proprietary guidance platforms (PwC Viewpoint, KPMG IFRS Handbook, EY Atlas, Deloitte iGAAP) that their staff use for IFRS 15 analysis. Public resources are limited to static PDF flowcharts, behind-paywall publications, or educational articles that provide general overviews without interactive decision support. This tool fills that gap — providing a professional, interactive IFRS 15 analysis tool accessible to every practitioner.
Unlike static flowcharts, this tool records every answer and rationale you provide at each decision point. The result is a complete decision trail with IFRS 15 paragraph references that can be included directly in your audit working papers — documenting not just the conclusion but the reasoning and judgment applied at each step.
Worked Example: Multi-Element Software Contract
Scenario: TechCorp Ltd enters into a contract with ClientCo to provide: (1) a perpetual software license for €250,000, (2) implementation and customisation services for €150,000, and (3) annual post-implementation support for three years at €50,000 per year. Total contract price: €550,000. Payment terms: 30% on signing, 40% at go-live, 30% in equal annual instalments over the support period.
Step 1 — Identify the Contract
All five IFRS 15.9 criteria are assessed: the contract is a signed master services agreement (criterion a — approved); rights to software, services, and support are clearly specified (criterion b); payment milestones and annual fees are defined (criterion c); TechCorp has not previously provided software to ClientCo and the arrangement changes its cash flow profile (criterion d — commercial substance); ClientCo has strong creditworthiness (criterion e — probable collection). Result: contract exists.
Step 2 — Identify Performance Obligations
Three promised deliverables are assessed for distinctness under IFRS 15.27. The software license is capable of being distinct (the customer can use the software without the other services) and is separately identifiable (it does not significantly modify or customise other promises). The implementation services involve significant customisation of the software — the implementation is not available from other vendors and creates interfaces that modify the software's core functionality. Under IFRS 15.29, the implementation is not separately identifiable and must be combined with the license into a single PO. The annual support is a stand-ready obligation that the customer could obtain from third parties; it is both capable of being distinct and separately identifiable. Result: two POs — (1) License + Implementation (combined), (2) Annual Support.
Step 3 — Determine the Transaction Price
Fixed consideration: €550,000. No variable consideration, no non-cash consideration. Significant financing component assessment: the payment profile (30/40/30 over approximately 3.5 years) creates a gap between payment and transfer. However, the entity applies the practical expedient under IFRS 15.63 for each individual PO — the license+implementation payment timing is within one year of delivery, and the annual support payments are made concurrently with the service period. No financing adjustment required. Transaction price: €550,000.
Step 4 — Allocate the Transaction Price
SSP determination: TechCorp regularly sells the software license at €300,000 (observable price). Implementation services have no observable SSP — using the expected cost plus margin approach, estimated SSP is €180,000. Annual support is sold separately at €55,000/year, or €165,000 total. SSP total: €645,000. Relative allocation: License+Implementation = (€480,000 / €645,000) × €550,000 = €409,302. Support = (€165,000 / €645,000) × €550,000 = €140,698.
Step 5 — Recognise Revenue
PO 1 (License + Implementation): Does the entity's performance create an asset with no alternative use and does it have an enforceable right to payment for performance to date? The customised software has limited alternative use (specific to ClientCo's systems), and the contract includes milestone-based payment clauses providing enforceable right to payment. IFRS 15.35(c) is met — recognise over time using cost-to-cost input method (€409,302 over the implementation period). PO 2 (Annual Support): The customer simultaneously receives and consumes the benefit of the stand-ready support obligation as TechCorp performs. IFRS 15.35(a) is met — recognise over time, ratably over each annual support period (€46,899 per year).
IFRS 15 Revenue Recognition Audit Toolkit — free PDF
Complete audit toolkit: IFRS 15 five-step decision flowchart poster (A3 printable), contract assessment working paper template, performance obligation identification checklist, SSP allocation worksheet, over-time vs. point-in-time determination guide, industry-specific application notes for 12 sectors, and ISA 240/315 fraud risk assessment for revenue.
No spam. Unsubscribe anytime.
Frequently Asked Questions
What is the IFRS 15 five-step model for revenue recognition?
How does this IFRS 15 flowchart differ from static PDF decision trees?
When should I use the IFRS 15 revenue recognition flowchart?
How do I determine if revenue should be recognised over time or at a point in time?
What is a performance obligation under IFRS 15?
How does the constraint on variable consideration work under IFRS 15?
What standalone selling price methods are available under IFRS 15?
Can I export the IFRS 15 assessment as an audit working paper?
How does IFRS 15 apply to SaaS and software arrangements?
What is the difference between a contract modification treated as a separate contract versus prospective or cumulative catch-up?
Industry-Specific IFRS 15 Flowcharts
Each industry variant provides tailored guidance notes alongside every decision node, industry-specific worked examples, and common performance obligation patterns.
Country-Specific IFRS 15 Guidance
Related Audit Tools
IFRS 15.9 — An entity shall account for a contract with a customer that is within the scope of this Standard only when all five criteria are met.
IFRS 15.22 — At contract inception, an entity shall assess the goods or services promised in a contract and shall identify as a performance obligation each promise to transfer to the customer either a distinct good or service or a series of distinct goods or services that are substantially the same.
IFRS 15.47 — An entity shall consider the terms of the contract and its customary business practices to determine the transaction price.
IFRS 15.73 — The objective of allocating the transaction price is to allocate an amount that depicts the consideration to which the entity expects to be entitled in exchange for transferring the promised goods or services to the customer.
IFRS 15.31 — An entity shall recognise revenue when (or as) the entity satisfies a performance obligation by transferring a promised good or service to a customer.