IFRS 15 The 5-Step Revenue Model: Logic, Not Just Rules

IFRS 15 Revenue Recognition: The 5-Step Model Explained (Part 1)

By Sai Manikanta Pedamallu (ACCA, CMA US, CSCA US, CGMA, ACMA, Dip IFRS, M.Com, MBA, MA)

Lead Instructor, Global Fin X | www.globalfinx.in/manikanta

---

Revenue is the single most important line in any set of financial statements. It is what analysts look at first, what auditors scrutinise most, and what management wants to optimise. It is also the area where financial reporting failures, both accidental and deliberate, are most common.

Before IFRS 15, revenue recognition under IFRS was governed by two standards: IAS 18 for goods and services, and IAS 11 for construction contracts. Those two standards used different principles, left significant gaps, and produced genuinely inconsistent outcomes across industries. A construction company and a software company with economically similar contracts could recognise revenue at entirely different points using entirely different logic.

IFRS 15 replaced both standards, along with five related interpretations, on 1 January 2018. It introduced a single, principles-based five-step model that applies to every contract with a customer, regardless of industry, geography, or contract type. The model forces a consistent discipline: before any revenue is recognised, five questions must be answered in sequence.

This post covers Steps 1 and 2 of that model in full depth, with the Indian context woven through. Steps 3, 4, and 5, covering transaction price determination, allocation, and recognition, are in Post 12. If you want to understand why IFRS 15 replaced IAS 18 and what changed substantively, Post 16 in this series covers that comparison directly.

---

Why IFRS 15 Exists: The Problem It Was Solving

I want to spend two minutes on this because understanding the problem makes the solution easier to remember.

Under IAS 18, revenue from the sale of goods was recognised when risks and rewards of ownership transferred. Revenue from services was recognised based on stage of completion. Those two frameworks produced some genuinely odd outcomes at the boundaries. A software company selling a licence with post-sale support: was this a goods transaction (recognise at delivery) or a service transaction (recognise over the support period)? Different auditors reached different conclusions for the same contract structure.

Real estate developers recognised revenue under different bases depending on their jurisdiction and interpretation of IFRIC 15. Indian real estate companies were a prominent example: many recognised revenue at various stages of construction under percentage of completion, while others recognised it only at handover. Same economic reality, different accounting outcomes.

IFRS 15 replaced all of this with one framework built on a single principle: recognise revenue to depict the transfer of control of goods or services to a customer in an amount that reflects the consideration the entity expects to be entitled to. Control, not risk and reward. Transfer, not delivery in the old sense. Expected consideration, not invoice value.

The five steps are the mechanism for applying that principle consistently. They are not a checklist to run through mechanically. They require genuine judgment, and the Dip IFRS exam tests that judgment repeatedly.

---

Scope: What IFRS 15 Applies To

IFRS 15 applies to contracts with customers. That phrase has a specific meaning. A customer is a party that has contracted with an entity to obtain goods or services that are an output of the entity's ordinary activities in exchange for consideration.

Several categories are explicitly outside IFRS 15's scope:

• Lease contracts (IFRS 16)
• Insurance contracts (IFRS 17)
• Financial instruments and other contractual rights or obligations within IFRS 9, IAS 32, and IAS 39's scope
• Non-monetary exchanges between entities in the same line of business to facilitate sales to customers

This last exclusion matters in Indian context. Two oil companies swapping crude oil to fulfil delivery obligations in different geographies: that exchange is not a revenue transaction under IFRS 15 because neither entity is acting as a customer. It is a non-monetary exchange between entities in the same line of business.

Where a contract contains elements within IFRS 15's scope alongside elements in other standards, IFRS 15 is applied only to the portion within its scope. A contract combining a lease element (IFRS 16) and a service element (IFRS 15) is split: the lease component follows IFRS 16 and the service component follows IFRS 15.

---

The Five Steps: Overview Before the Depth

Steps 1 and 2 determine the unit of account: what contract exists and what promises within it must be tracked separately. Steps 3, 4, and 5 determine the amount and timing of revenue recognition. You cannot reach the amount and timing questions without first being clear on what contract you are dealing with and what you promised.

---

Step 1: Identify the Contract with the Customer

The Five Criteria

A contract exists for IFRS 15 purposes when all five of the following criteria are met simultaneously.

Criterion 1: The parties have approved the contract and are committed to perform their obligations.

Approval can be written, oral, or implied by customary business practices. A purchase order accepted by a supplier is a contract. A verbal agreement to provide consulting services, confirmed by commencement of work, is a contract. An email exchange where a client asks for a specific deliverable and the supplier confirms is a contract.

For Indian IT companies like Infosys and TCS, the master service agreement with a client, followed by specific statements of work (SOWs), represents the contractual structure. The SOW, not the master agreement alone, typically contains the approved, committed obligations for a specific engagement. The SOW is where Step 1 analysis begins for each individual project.

Criterion 2: Each party's rights regarding the goods or services to be transferred can be identified.

The entity must know what it is obligated to deliver. The customer must know what they are entitled to receive. If a contract is so vague that neither party can determine their rights, it does not pass Step 1.

This criterion matters for framework agreements or blanket purchase orders, common in Indian manufacturing and government procurement. A blanket order for "up to Rs. 50 crore of engineering services over 12 months" without specific project details does not pass Step 1 on its own. The specific work orders or call-offs placed under that blanket, which identify the specific deliverables, are the contracts for IFRS 15 purposes.

Criterion 3: The payment terms for the goods or services to be transferred can be identified.

Payment terms must be determinable, not necessarily fixed. A contract with a fixed price passes this criterion. A contract with a variable element (performance bonuses, volume discounts) also passes it, as long as the basis for determining consideration is specified. An arrangement with no agreed payment basis at all does not.

Criterion 4: The contract has commercial substance.

Commercial substance means the risk, timing, or amount of the entity's future cash flows is expected to change as a result of the contract. Circular transactions designed to create the appearance of revenue without any real economic exchange fail this criterion. Related party transactions where consideration is not at arm's length may raise commercial substance questions.

IFRS 15's commercial substance requirement is directly analogous to the substance over form principle in the Conceptual Framework. The economic reality, not the legal form, determines whether a contract qualifies.

Criterion 5: It is probable that the entity will collect the consideration to which it will be entitled.

Probable means more likely than not. The entity assesses the customer's ability and intention to pay. This is a credit assessment at contract inception, not a measurement of expected credit losses on the receivable (which is an IFRS 9 question that arises after revenue is recognised).

This criterion prevents revenue recognition for contracts where collection is in doubt from the start. If an Indian IT company takes on a client that is clearly in financial distress, with known liquidity problems at the time the contract is signed, the collection criterion may not be met. Until it is probable that the entity will collect, no revenue is recognised even if services are delivered.

The assessment is based on the consideration the entity expects to be entitled to, which may be less than the stated contract price. If a client routinely pays 80% of invoices due to disputed line items and the entity accepts this without legal challenge, the assessment of probable collection should reflect the 80%, not the 100%.

What Happens When Criteria Are Not Met

If the Step 1 criteria are not met at contract inception, the entity does not apply Steps 2 through 5. Any consideration received is recognised as a liability (not revenue) until either:

• The criteria are subsequently met, or
• The contract has been terminated and the consideration received is non-refundable, and the entity has no remaining obligation

This creates a holding pattern. Consider a small Indian software developer that receives an advance of Rs. 20 lakh from a startup client. The startup is pre-revenue, has no funding commitment, and the contract has no specified payment terms beyond the advance. Step 1 criteria 3 and 5 may not be met. The Rs. 20 lakh sits as a liability. Revenue recognition waits until the contract is formalised or the advance becomes non-refundable with no remaining performance obligation.

Combining Contracts

IFRS 15 requires contracts entered into at or near the same time with the same customer (or related parties) to be combined and treated as a single contract if any of the following conditions apply:

• The contracts are negotiated as a package with a single commercial objective
• The consideration in one contract depends on the price or performance of the other contract
• The goods or services promised in the contracts are a single performance obligation

This prevents artificial splitting of a single commercial arrangement into multiple contracts to manipulate revenue timing. If an Indian construction company signs three separate contracts with a property developer on the same day for civil work, mechanical, and electrical installation, and all three are priced as a package with cross-references to each other, they must be combined for IFRS 15 purposes.

Contract Modifications

A contract modification is a change in the scope or price, or both, of an existing contract. IFRS 15 sets out specific rules for how modifications are accounted for, and this is one of the most tested areas in Dip IFRS exams.

The first question: has the modification been approved? If not, the entity continues to apply the original contract terms. Only an approved modification, whether written, oral, or implied, triggers the accounting analysis.

Three ways to account for an approved modification:

Treatment A: Separate new contract. The modification is accounted for as a new, separate contract when two conditions are both met. First, the modification adds distinct goods or services (Step 2's distinctness test applies). Second, the price of the additional goods or services reflects their standalone selling price. If both conditions are met, the original contract continues under its original terms and the modification is a new contract.

Indian example: TCS has an application development contract with a bank for Rs. 5 crore. Six months in, the bank asks TCS to also provide cybersecurity consulting, a service TCS provides independently to other clients, for an additional Rs. 80 lakh at its standard rate. The cybersecurity consulting is distinct (it can benefit the bank independently of the application development). The price reflects standalone selling price. This is Treatment A: a new separate contract. Revenue from the original contract continues as planned. The Rs. 80 lakh is recognised separately as TCS delivers the consulting.

Treatment B: Terminate old contract, create new contract. The modification is treated as the termination of the original contract and the creation of a new one when the modification adds goods or services that are not distinct (they are integrated with the original promises), or when it adds distinct goods or services but at a price that does not reflect standalone selling price. The remaining consideration under the original contract (the amount not yet recognised) plus the modification consideration becomes the transaction price for the new contract, allocated to the remaining performance obligations.

Indian example: Infosys has a fixed-price application maintenance contract for Rs. 12 crore per year. The client requests a significant scope increase: new modules must be integrated into the existing system, and this integration is so closely tied to the original maintenance work that the two cannot be separated. The modification adds non-distinct goods. Treatment B applies. The remaining unrecognised revenue from the original contract plus the new consideration forms the revised transaction price for the remaining period.

Treatment C: Cumulative catch-up (prospective with adjustment). When the modification adds distinct goods or services but at a price that does not reflect standalone selling price, some standards require a prospective approach. In practice, Treatment B covers this, and the distinction between B and C turns on whether the remaining performance obligations are distinct. Where they are all distinct, the remaining contract consideration plus modification consideration is reallocated to the remaining obligations, and any difference from what has already been recognised is adjusted as a cumulative catch-up in the current period.

The three treatments matter because they determine whether previously recognised revenue is revisited and whether a catch-up adjustment runs through the current period's income statement.

---

Step 2: Identify the Performance Obligations in the Contract

Performance obligations are the unit of account for revenue recognition under IFRS 15. Get Step 2 wrong and every subsequent step is wrong. This is where most complexity, most litigation, and most Dip IFRS exam marks live.

What Is a Performance Obligation?

A performance obligation is a promise to transfer 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, to the customer.

The promise can be explicit (stated in the contract) or implicit (arising from the entity's customary business practices, published policies, or specific statements that create a valid customer expectation).

Implicit promises: Wipro sells enterprise software. Its standard practice, followed consistently for years, is to provide free telephone support for 90 days after delivery. No customer contract explicitly mentions this support, but every customer expects it because Wipro's marketing materials describe it. That 90-day support is an implicit performance obligation. It must be identified in Step 2 and receive an allocation of transaction price in Step 4.

This is a major shift from IAS 18. Under the old standard, post-sale support provided out of goodwill or commercial necessity was not always bifurcated from the main sale. Under IFRS 15, if the customer has a valid expectation of receiving it, it is a performance obligation.

The Distinctness Test: Two Conditions, Both Required

A good or service is distinct only when both of the following conditions are met. Meeting one is not enough.

Condition 1: Capable of being distinct.

The customer can benefit from the good or service either on its own or together with other resources that are readily available to them. Readily available means sold separately by the entity or by other vendors, or already in the customer's possession.

Condition 2: Distinct within the context of the contract.

The promise to transfer the good or service is separately identifiable from other promises in the contract. IFRS 15 provides indicators that a promise is not separately identifiable:

• The entity provides a significant service of integrating the good or service with other contract goods or services into a combined output
• The good or service significantly modifies or customises another good or service promised in the contract
• The good or service is highly dependent on, or highly interrelated with, other goods or services promised in the contract

Both conditions must be satisfied for a good or service to be a separate performance obligation. If either fails, the good or service is bundled with others until the bundle as a whole is distinct.

Applying the Distinctness Test: Three Indian Examples

Example 1: Airtel Postpaid Plan (Telecom)

Airtel sells a postpaid plan combining a handset and 24 months of network services for a single monthly payment.

• The handset: can the customer benefit from it alone? Yes. Handsets are sold separately by Airtel and by other retailers. Capable of being distinct. Is it separately identifiable from the network services? The handset does not significantly modify or customise the network service. The network service does not significantly modify or customise the handset. They are not highly interdependent in the sense that one changes the nature of the other. Separately identifiable.
• The handset is distinct: two separate performance obligations from one contract.

Network services for 24 months: each month of service is substantially the same (connectivity, same features) and has the same pattern of transfer (over time, month by month). This is a series of distinct goods that are substantially the same with the same transfer pattern, which IFRS 15 treats as a single performance obligation.

Result: two performance obligations. Handset (satisfied at point in time: delivery) and network services (satisfied over time: 24 months). Airtel cannot recognise the full contract value when the handset is delivered. The transaction price must be allocated between the two obligations based on standalone selling prices. More on allocation in Post 12.

Example 2: Infosys Fixed-Price Software Development (IT Services)

Infosys contracts to design, develop, and implement a custom enterprise resource planning system for a manufacturing company. The contract includes design, development, testing, implementation, and three months of post-go-live support.

• Design: can the client benefit from the design alone? In principle yes, but not in this case. The design is for a highly customised system specific to this client's processes. It significantly modifies and customises the development work. It is not separately identifiable.
• Development: similarly integrated with design and testing.
• Testing: integral to the development; cannot be separated without affecting the overall output.
• Implementation: the implementation of this specific custom system requires deep knowledge of all preceding phases. It is not a generic implementation that another vendor could pick up independently.
• Post-go-live support: this is the key question. If the support involves bug fixes for the custom system just built, it may be highly interrelated with the implementation. If it is generic help desk and maintenance that Infosys provides independently to other clients, it may be distinct.

Result: if the support is generic and separately priced in Infosys's standard catalogue, it is likely a separate performance obligation. The design, development, testing, and implementation together form a single performance obligation (highly integrated, custom output). Two performance obligations total if support is distinct, one if it is not.

This is exactly the judgment call that appears in Dip IFRS exam questions. The examiner gives you a contract with multiple promised elements and asks how many performance obligations exist and why.

Example 3: DLF Residential Real Estate (Pre-Sale Contract)

DLF enters a pre-sale agreement with a buyer for an apartment not yet constructed. The agreement includes the apartment unit, car parking, and a five-year maintenance contract for common areas.

• Apartment unit: clearly capable of being distinct. The customer can benefit from the apartment on its own. Is it separately identifiable? In a pre-sale construction contract where DLF is building a specific unit to the buyer's specifications (limited customisation within a standard floor plan), the construction is the core promise. Distinct.
• Car parking: capable of being distinct (parking spaces are sold separately by some developers). In this contract, the parking is bundled at a fixed price. Whether it is separately identifiable depends on whether DLF allocates a separate price to it and whether it represents a genuinely separate promise or is part of the standard apartment sale package. If parking is included in the base price with no separate economic substance, it may not be a separate performance obligation. If it has a separately identifiable value and DLF sells parking independently, it is distinct.
• Five-year maintenance contract: general maintenance services, similar to what a facilities management company provides. Capable of being distinct: maintenance can be purchased from third parties. Separately identifiable: it does not modify or integrate with the construction. This is a separate performance obligation.

Result: likely two or three performance obligations depending on the car parking treatment. The revenue recognition implications are significant: DLF recognises revenue on the apartment either at a point in time (on handover) or over time (if the control transfer criteria for over-time recognition are met, which for Indian real estate is a live debate). The maintenance revenue is recognised over five years. Without separating the obligations, DLF might recognise all revenue at handover, which overstates early revenue and understates the maintenance service revenue.

Series of Distinct Goods or Services

IFRS 15 creates a special category for situations where a contract involves multiple distinct goods or services that are substantially the same and have the same pattern of transfer to the customer. These are treated as a single performance obligation.

A cleaning services company contracted to clean a corporate office every day for 12 months provides a series of distinct daily cleaning services. Each day's cleaning is distinct (the client could benefit from a single day's cleaning). Each is substantially the same (cleaning an office). Each has the same pattern of transfer (over time, each day). The entire 12-month contract is one performance obligation satisfied over time.

This matters because it simplifies contracts that would otherwise involve accounting for hundreds of separate performance obligations. For a company like Quess Corp or TeamLease Services providing outsourced staffing and facility management across hundreds of Indian corporate campuses, treating each daily service as a series is the only workable approach.

---

How Steps 1 and 2 Interact: The Full Picture

Steps 1 and 2 together establish the accounting unit. What contract am I working with? What promises within that contract must I track separately?

The output of Steps 1 and 2 feeds directly into Steps 3, 4, and 5. If you identify two performance obligations in Step 2, the transaction price in Step 3 must be allocated to both in Step 4, and revenue is recognised for each as it is satisfied in Step 5. Misidentifying performance obligations at Step 2 does not just make Step 2 wrong. It makes every subsequent step wrong too.

A common error I see: treating the entire contract as one performance obligation when it contains multiple distinct promises, recognising all revenue at the earliest satisfaction point and understating deferred revenue. Conversely, splitting what is genuinely one integrated performance obligation into multiple pieces and recognising partial revenue prematurely.

Both errors have real financial statement consequences. An Indian IT company that recognises software licence revenue at delivery without deferring the support element front-loads revenue. The same company that defers everything until the project is complete back-loads it. Neither reflects the economics of what was delivered and when.

---

Ind AS 115 vs IFRS 15: What Is Different

Ind AS 115 is India's version of IFRS 15. It is effective for annual periods beginning on or after 1 April 2018. The standard is substantially converged with IFRS 15. Differences are narrow.

The real estate application is worth highlighting. The ITFG issued multiple clarifications on how Ind AS 115 applies to real estate pre-sale contracts. The core question, whether a pre-sale construction contract satisfies revenue over time or at a point in time, depends on whether the customer controls the asset as it is created. In most Indian residential pre-sale contracts, the developer retains control until handover. Revenue is recognised at a point in time. This was a significant change from the percentage of completion approach many developers used under old Indian GAAP.

---

Disclosures Under IFRS 15

IFRS 15 has extensive disclosure requirements. The objective is to enable users to understand the nature, amount, timing, and uncertainty of revenue and cash flows from contracts with customers.

Quantitative disclosures:

• Disaggregation of revenue into categories that depict how the nature, amount, timing, and uncertainty of revenues and cash flows are affected by economic factors (geography, product type, customer type, contract duration)
• Opening and closing balances of contract assets, contract liabilities, and receivables from contracts with customers
• Revenue recognised from opening contract liability balances
• Revenue recognised from performance obligations satisfied in prior periods

Qualitative disclosures:

• Description of performance obligations and when they are typically satisfied
• Payment terms
• Significant judgments in applying IFRS 15, particularly around timing of satisfaction and methods used to recognise revenue over time
• Assets recognised from costs to obtain or fulfil contracts

For Indian IT companies, the disaggregation of revenue by geography, service line, and contract type is particularly detailed because the diversity of their revenue streams is material to users. Infosys's IFRS 15 revenue disaggregation in its annual report breaks revenue by business segment, geography, contract type (time and material, fixed price, unit price), and deployment model (onsite vs offshore). That level of disaggregation reflects the judgment that all those dimensions are relevant to understanding revenue uncertainty.

---

Dip IFRS Exam: What You Need to Know for IFRS 15

IFRS 15 is one of the most examined standards in Dip IFRS. It appears in scenario-based questions requiring both technical knowledge and applied judgment. Here is what the exam consistently tests.

Most Tested Areas

Identifying the number of performance obligations: the examiner gives you a contract with multiple promised elements and asks you to identify how many performance obligations exist, applying the distinctness test to each element. The answer is never obvious. The question always has at least one element that could go either way, and the marks go to candidates who correctly apply both conditions of the distinctness test with clear reasoning.

Contract modifications: identifying which treatment applies (separate new contract, terminate and create new, or cumulative catch-up) and calculating the revenue recognised in the current period after the modification. These questions involve calculations as well as principle application.

Revenue over time vs at a point in time: the examiner describes a contract and asks whether revenue is recognised over time or at a point in time, and when. The over-time criteria (Step 5, covered in Post 12) are tested here, but the setup requires correct identification of performance obligations in Step 2.

Principal vs agent: whether an entity recognises revenue gross (as principal) or net (as agent) depends on which party controls the good or service before it is transferred to the customer. This is a Step 2-adjacent issue and is consistently tested.

Common Examiner Traps

Implicit performance obligations: the exam gives a scenario where the entity has a published policy of providing free service after sale. Students who only look at the explicit contract terms miss the implicit obligation and get the performance obligation count wrong.

Combination of contracts: two contracts with the same customer signed on the same day. Students analyse them separately. The examiner expects analysis of whether they should be combined.

Distinctness test: applying only one condition: students who answer "the software is distinct because the customer can use it on its own" get partial credit. Full credit requires also addressing whether it is separately identifiable from the other promises in the contract.

Collection criterion: students recognise revenue based on contract price without assessing whether collection is probable. If the scenario includes a financially distressed customer, the collection criterion is in play.

Exam Technique

When an IFRS 15 question appears in Dip IFRS, work through the five steps systematically even if the question does not explicitly ask you to. Show your reasoning at each step. Examiners award marks for the analysis, not just the conclusion. A wrong conclusion reached by correct reasoning earns more marks than a correct conclusion with no reasoning.

State your assumptions. If a fact in the scenario is ambiguous, say so. "If the post-sale support is sold separately by the entity, it is capable of being distinct and is therefore a separate performance obligation" demonstrates application better than "there are two performance obligations."

---

FAQ

Does IFRS 15 apply to all industries?

Yes, with the specific exclusions listed in the scope section above. Every industry that has contracts with customers applies IFRS 15, including IT services, telecom, real estate, manufacturing, pharma, retail, and construction.

What is the difference between a contract asset and a receivable under IFRS 15?

A contract asset arises when an entity has recognised revenue but the right to consideration is conditional on something other than the passage of time, for example, satisfying another performance obligation. A receivable arises when the right to consideration is unconditional, only the passage of time is required before payment is due.

Can revenue be recognised before cash is received?

Yes. Revenue is recognised when performance obligations are satisfied, which may be before or after cash receipt. If cash is received before performance, a contract liability (deferred revenue) is recognised. If performance occurs before cash receipt, a contract asset or receivable is recognised.

What is the practical expedient for short-duration contracts?

IFRS 15 allows entities to recognise the incremental costs of obtaining a contract as an expense when incurred if the amortisation period would be one year or less. This avoids the complexity of capitalising and amortising small contract acquisition costs for short contracts.

How does IFRS 15 treat advances received from customers before work begins?

An advance received before the entity has performed is a contract liability. It is recognised as revenue as the entity satisfies its performance obligations. If the advance carries a significant financing component (the contract has been prepaid well in advance of performance), the entity must adjust the transaction price for the time value of money, unless the practical expedient for contracts of one year or less applies.

Is IFRS 15 relevant for intragroup transactions?

No. Intragroup transactions are eliminated on consolidation. IFRS 15 applies to transactions with external customers. However, individual entity IFRS financial statements (separate financial statements) do apply IFRS 15 to transactions with other group entities if those entities are customers for the goods or services provided.

What happens if a customer has a right to return goods?

The entity recognises revenue only for the consideration it expects to be entitled to, excluding expected returns. A refund liability is recognised for the expected returns. A right-to-recover asset (at the carrying amount of the returned inventory, less any expected recovery costs) is also recognised. This is variable consideration, covered in depth in Post 12.

---

Enroll with Global Fin X

IFRS 15 is one of the most tested standards in Dip IFRS and one of the most complex in Big 4 practice. Our structured programme covers every aspect of the five-step model across four dedicated posts in this series, with in-depth lectures, worked examples, exam-style MCQs, and a dedicated LMS built for working professionals.

Enroll Now: Dip IFRS Programme

Faculty profile: www.globalfinx.in/manikanta

---

This is Post 11 of the Global Fin X IFRS Series. Previous: IFRS 1: First-Time Adoption. Next: IFRS 15 Part 2: Performance Obligations, Transaction Price and Allocation.