IFRS 15 vs IAS 18: What Changed When IAS 18 Was Replaced and Why It Mattered
Author
Sai Manikanta Pedamallu
Published
Reading Time
5 min read
Table of Contents
IFRS 15 vs IAS 18: What Changed When IAS 18 Was Replaced and Why It Mattered
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
IAS 18 was not a bad standard. It worked reasonably well for simple transactions: sell a product, recognise revenue at delivery. The problems surfaced when transactions got complex. Bundled contracts. Licenses. Variable pricing. Long-term service arrangements. For these, IAS 18 gave you a principle and left you to figure out the rest. The result was inconsistency: two companies with economically identical contracts recognising revenue at different times using different logic, both claiming compliance with IFRS.
IFRS 15 replaced IAS 18, IAS 11 (construction contracts), and five IFRIC interpretations on 1 January 2018. The replacement was not cosmetic. The underlying principle changed, the unit of account changed, and the treatment of several specific topics changed materially.
This post is a direct comparison. What IAS 18 required, what IFRS 15 changed, and why those changes produced better financial reporting. Where the changes had specific impact on Indian companies, I cover that directly.
This is a reference post. Everything it covers is built on the five-step model explained across Posts 11 to 13. If you need the IFRS 15 mechanics, go there first.
The Foundational Shift: Risks and Rewards vs Control
This is the change that everything else flows from.
IAS 18: Revenue from the sale of goods was recognised when significant risks and rewards of ownership transferred to the buyer. The seller had to retain neither continuing managerial involvement nor effective control.
IFRS 15: Revenue is recognised when control of the goods or services transfers to the customer. Control means the ability to direct the use of, and obtain substantially all of the remaining benefits from, the good or service.
On the surface, these sound similar. In practice, they produce different answers in many situations.
Why risks and rewards was problematic:
Risks and rewards is not a single point. You can transfer some risks before others. An entity could transfer the risk of price decline to a customer while retaining the risk of physical damage during transit. IAS 18 required a judgment on which risks and rewards were "significant" and whether they had transferred. Different auditors made different calls on the same contract structure.
Control is more binary. Either the customer can direct the use of the asset and obtain its benefits, or they cannot. The indicators of control transfer under IFRS 15 (legal title, physical possession, right to payment, significant risks and rewards, customer acceptance) are still judgment-based, but they point toward a cleaner conclusion because control is the single question being answered.
Where the difference produces a different outcome:
Bill-and-hold arrangements. Under IAS 18, if the risks of ownership transferred to the buyer (they bore the risk of price decline on specific identified goods), revenue could potentially be recognised even without physical transfer. Under IFRS 15, the bill-and-hold criteria are explicit: the goods must be separately identified as the customer's, must be ready for transfer, and the customer must have requested the arrangement. More demanding conditions, more consistent outcomes.
Sale with a right of return. Under IAS 18, if returns could not be reliably estimated, revenue was deferred until the return period expired. Under IFRS 15, revenue is recognised for the consideration the entity expects to be entitled to (excluding expected returns), with a refund liability recognised for expected returns. Returns do not block revenue recognition; they shape the transaction price.
Scope: Single Framework vs Fragmented Standards
IAS 18 scope:
- Sale of goods
- Rendering of services
- Use of entity assets (interest, royalties, dividends)
IAS 11 scope (separate standard):
- Construction contracts
IFRIC interpretations (multiple):
- IFRIC 13: Customer loyalty programmes
- IFRIC 15: Agreements for construction of real estate
- IFRIC 18: Transfers of assets from customers
- SIC 31: Revenue: barter transactions involving advertising services
- IFRIC 12: Service concession arrangements (partially)
IFRS 15 scope:
One standard. Contracts with customers. Covers everything IAS 18 and IAS 11 covered, plus the interpretation topics, plus areas that had no guidance at all under IAS 18.
The fragmentation under IAS 18 was a genuine problem. A software company licensing software with post-sale support: was that a goods transaction (IAS 18 goods criteria), a services transaction (IAS 18 services criteria), or something else? There was no definitive answer. Preparers chose whichever treatment they preferred and documented a justification. IFRS 15 ends that. One framework, one answer.
The Unit of Account: Transaction vs Performance Obligation
Under IAS 18: The recognition criteria were applied to each transaction. IAS 18 acknowledged that sometimes criteria needed to be applied to "separately identifiable components" of a single transaction, but gave no guidance on how to identify those components or allocate consideration between them.
In practice, many entities applied IAS 18 to the contract as a whole. A telecom bundle of handset plus 24 months of service was treated as one transaction. Revenue was recognised on a straight-line basis over the service period, or at delivery of the handset, depending on what the entity decided was the predominant element.
Under IFRS 15: The unit of account is the performance obligation. The five-step model requires identifying all performance obligations in a contract, allocating the transaction price to each based on standalone selling prices, and recognising revenue as each obligation is satisfied.
The telecom bundle is not one transaction. It contains two performance obligations (handset and service). The transaction price is allocated. Revenue timing differs for each. This is not an option under IFRS 15. It is required.
For Indian telecom companies like Airtel and Jio, this changed the timing and pattern of revenue recognition significantly on handset-bundled plans. Revenue that was previously spread over the contract period was partly accelerated to the point of handset delivery.
Variable Consideration: Constraint vs Deferral
Under IAS 18: If revenue could not be reliably measured, it was deferred until reliable measurement was possible. No guidance on how to estimate variable amounts or what "reliable" meant in the context of uncertainty.
Under IFRS 15: Variable consideration is estimated using either the expected value method (probability-weighted amounts) or the most likely amount method, whichever better predicts the consideration. A constraint is then applied: the variable amount is included in the transaction price only to the extent it is highly probable that a significant reversal will not occur when the uncertainty is resolved.
The IFRS 15 approach is more disciplined. It requires an estimate rather than a binary recognise/defer decision. It also requires the entity to update the estimate at each reporting date as new information becomes available.
Practical impact for Indian IT companies:
Under IAS 18, a performance bonus that could not be reliably estimated was excluded from revenue entirely until the measurement period ended. Under IFRS 15, the entity estimates the bonus using the expected value or most likely amount method and includes it in revenue if the constraint is satisfied. This can pull forward revenue recognition for performance bonuses that are highly likely to be achieved, and better reflects the economic reality of services delivered.
Bundled Contracts and Multiple Elements
Under IAS 18: No specific framework for multiple-element arrangements. IAS 18 permitted separating identifiable components but provided no guidance on how to identify them or how to allocate consideration. In practice, many entities either recognised everything at the predominant element's timing, or developed their own frameworks (often borrowing from US GAAP).
Under IFRS 15: The distinctness test in Step 2 is explicit. Two conditions must both be satisfied. Standalone selling prices determine allocation in Step 4. The framework is mandatory, not optional.
Indian telecom example:
Under Ind AS 18, two telecom companies offering identical handset-plus-service bundles could recognise revenue differently. Company A treats the bundle as a service transaction and spreads revenue over the service period. Company B identifies the handset as a separate component and accelerates handset revenue to delivery. Both claim IAS 18 compliance.
Under Ind AS 115, both companies apply the same framework. The handset is distinct. The service is a separate performance obligation. Transaction price is allocated on SSP. Revenue timing is determined by when each obligation is satisfied. The two companies now produce comparable numbers.
Construction Contracts: IAS 11 and IAS 18 vs IFRS 15
This comparison deserves its own section because the change here was not just technical. It fundamentally altered how Indian real estate companies reported revenue.
Under IAS 11: Construction contracts used the percentage-of-completion method. Revenue was recognised progressively as construction progressed, based on stage of completion (typically cost-to-cost).
Under IAS 18 (and IFRIC 15): Revenue from real estate sales was recognised when significant risks and rewards of ownership transferred. For properties sold before construction, this raised the question of whether the customer obtained risks and rewards progressively (as construction progressed) or at handover. IFRIC 15 clarified that for most residential pre-sale contracts, the handover test applied: risks and rewards transferred at handover, not progressively.
Under IFRS 15: Revenue from construction and real estate uses the same framework as everything else. The question is whether the performance obligation is satisfied over time (three criteria) or at a point in time. For most Indian residential pre-sale contracts, the answer is point in time at handover, because the developer controls the asset as it is created and the customer has no right to the specific asset under construction.
What changed for Indian real estate:
Under old Indian GAAP, most developers used percentage-of-completion, recognising revenue progressively from the point collections exceeded a threshold. This was widespread industry practice before Ind AS 115.
Under Ind AS 115, for typical residential pre-sale contracts, all revenue is recognised at handover. A project that took three years to build now generates zero revenue in years one and two, and all revenue in year three.
The balance sheet effect: large contract liabilities (advance receipts from buyers) accumulated during construction, with zero revenue against them. Inventory grew as construction costs were capitalised. Then at handover, the revenue spike occurred, inventory was derecognised, and the contract liability was extinguished.
This was one of the most commercially significant transitions under Ind AS 115 for Indian listed companies. Developers like DLF, Godrej Properties, and Prestige Estates saw their revenue recognition patterns change materially from FY2019 when Ind AS 115 became mandatory.
Licences: No Guidance vs Specific Framework
Under IAS 18: No specific guidance for intellectual property licences. Revenue was recognised when the entity had transferred the significant risks and rewards of the licence to the customer. For software licences with post-delivery support, the treatment was unclear. Many entities recognised licence revenue at delivery and deferred support revenue over the support period, but the identification of the support component and the allocation of consideration had no standard basis.
Under IFRS 15: Specific framework distinguishing right-to-use licences (point in time) and right-to-access licences (over time). The test depends on whether the licensor's ongoing activities significantly affect the IP to which the customer has rights. Sales-based and usage-based royalties have a specific exception (recognised at the later of sale/usage or satisfaction of the performance obligation).
Indian pharma impact:
Under IAS 18, a pharma company out-licensing a compound under active development had no clear standard. The treatment depended on judgment about risks and rewards. Some companies recognised the full upfront fee at licence grant. Others spread it over the development period.
Under IFRS 15, the analysis is disciplined. If the licensor's ongoing development activities significantly affect the licensed compound (right to access), revenue is recognised over time. If the compound is fully developed and the licensee can use it as-is (right to use), revenue is recognised at the point control transfers.
Contract Costs: No Treatment vs Specific Rules
Under IAS 18: No guidance on costs to obtain or fulfil a contract. Most entities expensed all such costs as incurred, including sales commissions on multi-year contracts.
Under IFRS 15: Incremental costs of obtaining a contract (primarily sales commissions) must be capitalised and amortised if expected to be recovered. Costs to fulfil a contract that meet three specific criteria must also be capitalised. Both categories are subject to impairment testing.
Impact on Indian IT companies:
Large Indian IT companies with significant sales forces and multi-year outsourcing contracts now carry material contract cost assets on their balance sheets. Pre-IFRS 15, all sales commissions were expensed in the period paid. Post-IFRS 15, commissions on three and five-year outsourcing contracts are capitalised and amortised over the contract term. This defers expense recognition, improving near-term profitability and adding a new asset category that analysts must track.
Customer Loyalty Programmes: IFRIC 13 vs IFRS 15
Under IFRIC 13 (applicable under IAS 18): Award credits were accounted for as a separately identifiable component of the transaction. The fair value of the award credits was deferred and recognised when the awards were redeemed or expired. Measurement was at the fair value of the awards to the customer.
Under IFRS 15: Loyalty points are accounted for as a separate performance obligation if they represent a material right. Allocation is based on standalone selling prices, not fair value of the award. The deferred amount is recognised when the obligation is satisfied (on redemption or expiry).
The change from fair value to standalone selling price for allocation purposes can produce different deferred amounts depending on how the SSP of points is estimated. For Indian companies with large loyalty programmes, this required recalibrating their deferral models on transition.
Disclosures: Minimal vs Extensive
Under IAS 18: Minimal disclosure requirements. The entity disclosed accounting policies for revenue recognition and the amount of revenue from each significant category of transaction. No requirement to disaggregate revenue, disclose contract balances, or explain significant judgments.
Under IFRS 15: Extensive. Disaggregation of revenue by type, geography, and other factors relevant to understanding uncertainty. Opening and closing contract asset and liability balances with reconciliations. Significant judgments in applying the standard. Information about remaining performance obligations and when they will be satisfied. Contract cost asset disclosures.
This shift in disclosure requirements is significant. Under IAS 18, revenue was largely a black box. Under IFRS 15, the notes explain what was recognised, what remains to be recognised, and the judgments that determined both. For analysts tracking Indian IT backlogs or real estate pre-sales pipelines, the IFRS 15 disclosures provide information that simply did not exist under IAS 18.
Summary Comparison Table
| Area | IAS 18 | IFRS 15 |
|---|---|---|
| Core principle | Transfer of significant risks and rewards | Transfer of control |
| Scope | Goods, services, asset use (IAS 11 separate) | All contracts with customers (single standard) |
| Unit of account | Transaction | Performance obligation |
| Multiple elements | Limited guidance, no allocation framework | Mandatory identification and SSP allocation |
| Variable consideration | Defer if not reliably measurable | Estimate and constrain |
| Licences | No specific guidance | Right-to-use vs right-to-access framework |
| Construction contracts | IAS 11 percentage-of-completion | IFRS 15 over-time vs point-in-time test |
| Contract costs | No guidance, expense as incurred | Capitalise incremental costs, amortise |
| Customer loyalty | IFRIC 13 fair value deferral | Performance obligation at SSP |
| Disclosures | Minimal | Extensive: disaggregation, contract balances, judgments |
| Effective date | Superseded 1 January 2018 | Effective 1 January 2018 |
What Actually Changed in India: Ind AS 18 to Ind AS 115
Indian companies moved from Ind AS 18 to Ind AS 115 for annual periods beginning on or after 1 April 2018. The transition was mandatory. Companies could use the full retrospective method (restate all prior periods) or the modified retrospective method (cumulative adjustment to opening retained earnings with no restatement of comparatives).
Most Indian companies chose the modified retrospective method. Full restatement was impracticable for entities with thousands of active contracts at the transition date.
The sectors most affected in India:
Real estate: The shift from percentage-of-completion to point-in-time at handover was the largest revenue recognition change for any Indian sector. Developers restated their transition-date retained earnings to remove revenue recognised on projects not yet handed over, creating large contract liability balances.
Telecom: Handset-bundled plan accounting required separating performance obligations and allocating transaction prices. Activation fees that were previously recognised upfront were deferred over the service period.
IT services: Contract cost capitalisation was new for most companies. Fixed-price contract accounting using cost-to-cost was largely unchanged from IAS 11 for construction-type projects, but the framework for determining whether an obligation is satisfied over time was now more explicit.
Pharma: Milestone payments and out-licensing arrangements required more disciplined analysis of variable consideration and licence type. Some upfront recognition that occurred under IAS 18 was deferred under IFRS 15's constraint on variable consideration.
Dip IFRS Exam Angle
Comparison posts attract scenario-based questions in Dip IFRS. The examiner gives a situation and asks how it would have been treated under IAS 18 versus how it should be treated under IFRS 15, or asks why the change was made.
Know the core principle shift: risks and rewards to control. Know the specific areas where outcomes differ: bill-and-hold, bundles, licences, construction contracts. Know that IFRS 15 introduced a mandatory framework for multiple-element arrangements where IAS 18 had none.
For calculation questions: the key difference to demonstrate is SSP-based allocation under IFRS 15 versus the absence of an allocation framework under IAS 18. Show both treatments side by side if the question asks for a comparison.
FAQ
Is IAS 18 still relevant?
No. It was superseded from 1 January 2018. Understanding it matters only for historical comparison, for Dip IFRS exam purposes, and for understanding why IFRS 15 was designed the way it was.
Did all companies see revenue changes on transition to IFRS 15?
No. Companies with simple transactions (sell goods, receive payment, no variable consideration, no multiple elements) saw little or no change. The impact was concentrated in sectors with complex contracts: telecom, IT, real estate, pharma, construction.
Is the risks and rewards test completely gone?
It is one of the indicators of control transfer under IFRS 15, not the primary test. Significant risks and rewards remaining with the entity suggest control has not transferred. But it is evidence of control, not the test itself.
Why did it take so long for IAS 18 to be replaced?
The IASB and FASB began the joint project in 2002. The standard was issued in 2014 and became effective in 2018. The delay reflects the complexity of converging IFRS and US GAAP revenue standards and the extensive consultation process across industries globally.
Under IAS 18, could two companies with identical contracts recognise revenue differently?
Yes. This was one of the primary reasons for replacing IAS 18. The broad principles combined with limited specific guidance allowed different interpretations to coexist. IFRS 15 does not eliminate judgment, but it channels it through a consistent framework.
Enroll with Global Fin X
Understanding where IFRS 15 came from and what it replaced deepens your ability to apply it correctly. Our programme covers the full IFRS 15 framework across four posts in this series, with in-depth lectures, worked examples, exam-style MCQs, and a dedicated LMS for working professionals.
Enroll Now: Dip IFRS Programme
Faculty profile: www.globalfinx.in/manikanta
This is Post 16 of the Global Fin X IFRS Series. Previous: IAS 20: Government Grants. Next: IFRS 9 Part 1: Classification and Measurement of Financial Assets and Liabilities.