IFRS 15: The Long Road to Revenue Recognition
Two rounds of public exposure, three industry battles, and a scoping strategy designed to leave room for standards still to come.
Before 2014, an entity's revenue recognition policy depended less on the economics of its contracts than on which side of the Atlantic it reported from.
Under IFRS, the relevant guidance was IAS 18 Revenue and IAS 11 Construction Contracts — short, principle-based standards written for a simpler world, never substantially expanded to address the bundled, multi-element contracts that had become routine by the 2000s. Under US GAAP, the opposite problem existed: more than a hundred pieces of industry- and transaction-specific guidance, accumulated over decades, frequently producing different accounting for economically similar transactions depending on which industry happened to get its own rule first.
The complaint from both sides centred on the same figure: revenue — the single line every analyst looks at first — was not comparable.
Two airlines could sell an identical ticket-plus-loyalty-point bundle under different policies.
A software company and a construction company, applying the same broad principle, could reach opposite conclusions about when a contract was "done enough" to record.
This is the problem IFRS 15 solves. Solving it took twelve years, two formal rounds of public exposure — one of them unplanned — and a set of industry-specific compromises that are still visible, and in places still being tested, inside the standard today.
Act I: Two Philosophies, One Transaction
In 2002, the IASB and the FASB opened a joint project to build a single revenue recognition model usable under both IFRS and US GAAP. The goal was explicit: a common standard that entities could apply consistently across industries, jurisdictions, and capital markets — removing the inconsistencies on both sides and providing a sturdier framework for resolving revenue questions as they arose, rather than continuing to patch old standards one industry at a time.
The two starting points could not have been further apart. IFRS's guidance was thin enough that entities routinely borrowed from US GAAP's far more detailed — but also far more fragmented — body of rules just to get an answer. Neither side could adopt the other's framework wholesale. The project had to build something genuinely new.
Act II: A Concept Arrives, With Two Loose Threads
In December 2008, the boards published their first Discussion Paper. Two ideas arrived together, not in sequence: a contract creates performance obligations to transfer goods or services, and revenue is recognised when the customer obtains control of those goods or services.
Performance obligation and control were never competing concepts — they were a pair from day one, built around the idea that revenue should track what an entity actually has left to deliver.
Respondents broadly supported that core idea. But two specific concerns surfaced immediately, and both would resurface, largely unresolved, through every later round of the project.
The first was about timing.
The Discussion Paper proposed identifying performance obligations by looking at when each promised good or service would be transferred — a test respondents flagged as impractical wherever transfer happens continuously rather than in a single moment, most obviously in long-term construction.
The second was about control itself.
Respondents asked the boards to clarify how "control" would apply to service contracts and to assets built up over time, warning specifically that an unclear standard risked implying completed-contract accounting — record nothing until the asset is finished and handed over — for construction generally.
For an industry that had used some form of percentage-of-completion accounting for decades, this was not a footnote. It was the central question.
Act III: The Year the Boards Broke Their Own Rules
The June 2010 Exposure Draft drew nearly 1,000 comment letters, from construction, manufacturing, telecommunications, technology, pharmaceuticals, financial services, media, energy, and franchising.
The two concerns from 2008 had not gone away. Respondents kept pushing back on how control would apply to service and work-in-progress contracts, and raised a related worry: that the new "distinct goods or services" test for identifying performance obligations would force entities to slice contracts into more pieces than was useful to anyone.
What happened next was unusual. Nothing in the boards' own due process required a second exposure draft — the redeliberations could, in principle, have gone straight to a final standard.
The boards decided otherwise, unanimously, citing the importance of revenue to every reporting entity and the risk of unintended consequences for specific industries.
A revised Exposure Draft followed in November 2011, drawing roughly 350 further comment letters. Two formal rounds of public exposure, nine years into a project that had started with two ideas almost everyone agreed on in principle.
Act IV: Three Industries, Settled
Three debates, in particular, dominated both rounds of consultation and ultimately reshaped the final standard.
Construction kept most of its existing practice, through a dedicated three-condition test for recognising revenue over time rather than at a single point.
Telecommunications was permitted a portfolio-level approach to pricing, sparing entities from assessing every near-identical contract on its own terms.
Licensing of intellectual property was split into a right to use and a right to access, with royalties carved out and tied directly to the customer's own sales or usage.
Each of these compromises reshaped real accounting outcomes in its industry, not merely its terminology — a story detailed in full in a later article in this series.
Act V: What Stayed Outside
Two further industries never had to fight at all, because the boards kept them out of the room from the start — for opposite reasons.
Insurance contracts were excluded cleanly, with little need for extended negotiation, because IFRS already had a standard covering them, however imperfect: IFRS 4, issued a decade earlier in 2004.
There was no gap to fill, so there was little to argue about.
The boundary only grew delicate years later, when IFRS 17 replaced IFRS 4 in 2017 and the boards had to add a specific accommodation letting entities choose between IFRS 17 and IFRS 15 for fixed-fee service contracts that technically meet the definition of insurance — extended warranties and roadside assistance being the obvious examples — so that genuinely non-insurance businesses would not be forced into an insurer's measurement model.
Rate-regulated activities were excluded for the opposite reason: IFRS had no guidance for them at all.
Rather than asking the revenue project to absorb that unresolved question, the boards pursued it on a separate track. That work eventually produced IFRS 14 in January 2014, four months before IFRS 15 itself.
IFRS 14 was explicit about its own limits from the outset: a narrow, interim holding position, not a considered answer. That question would take another twelve years to resolve-a story told in full in our IFRS 20 article.
One footnote is worth keeping in mind before moving on. Conceptually, the model the boards built is not really a revenue model at all — it is an asset-and-liability model, in which a contract creates a net contract asset or liability that moves as the entity performs, and revenue is simply the label attached to an increase in that position.
The boards chose that label deliberately, for ease of application, which puts IFRS 15 in slightly unusual company among IFRS standards, most of which are named after balance sheet items rather than income-statement ones.
Conclusion
IFRS 15 is usually described as a single achievement: one revenue model, replacing more than a hundred pieces of fragmented guidance, applicable across industries and jurisdictions alike. That description is accurate, but incomplete.
The harder achievement was knowing what to leave out.
A project with an unlimited mandate could have tried to resolve insurance, rate-regulated pricing, and every open licensing question within the same standard, in the same twelve years. The boards chose not to. Each of those questions was allowed to remain unresolved, on its own track, for as long as it needed — four years for licensing, three for insurance, twelve for rate regulation — while the core model shipped on time in 2014.
That discipline is easy to overlook, because it produces no clause in the standard itself. It shows up only in what IFRS 15 does not try to do. But it is the reason the standard has aged well: a narrower, better-defended core, instead of a broader one weakened by unfinished edges.
This idea—protecting the core by clearly defining its boundaries—isn't unique to accounting standards. It's also a design principle that I've come to appreciate repeatedly through my experience as a product manager. Whether you're developing accounting standards or software products, long-term success often depends not on how many problems you try to solve, but on having the discipline to define what belongs inside the product—and what does not.
The five-step model that resulted from that discipline — and the mechanics of how it actually applies, contract by contract — is the subject of the next article in this series.
Slide Deck Available
This article's key concepts — scope, the three measurement models, and the core structural shifts — are available as an editable white-label slide deck, ready to present to your team or clients.
Bonus infographics from this article are included for free use.
👉 [Get the slide deck ：IFRS15-History_WhiteLabel_Training_Deck.pptx]
For educational purposes only. You may use and adapt this deck for internal training, client advisory, and CPD sessions. Redistribution or resale as a standalone product is prohibited.
Practice Questions
Practice questions based on this article are available on IFRS-OneQ. Reinforce what you've read — one question at a time.
Test your understanding on IFRS-OneQ！
Disclaimer: This article is for educational purposes only and reflects the author's interpretation of the relevant IFRS Standards as at the date of publication. It is not intended to provide accounting, legal, or tax advice. Readers should refer to the authoritative IFRS literature and consult qualified advisers before applying the guidance to specific circumstances.