
IFRS 15 revenue recognition: the guide for subscription and usage businesses
Billing is not recognizing revenue. IFRS 15 requires both, and requires them to reconcile.
IFRS 15, "Revenue from Contracts with Customers", sets how companies applying IFRS Standards recognize revenue. Issued by the IASB in 2014, it has applied since January 1, 2018, according to the IFRS Foundation, and replaces in particular IAS 18 and IAS 11. Its US equivalent is ASC 606.
Its principle is simple: revenue is recognized when the customer obtains control of the promised good or service, for the amount the company expects to be entitled to. Not when the invoice is issued, nor when payment arrives.
For a company selling subscriptions, consumption, bundles or multi-year contracts, this difference is far from theoretical. An annual plan billed in January, a device offered with a subscription, setup fees, a first-year discount, a usage overage, an upgrade mid-contract: each situation raises the question of how much revenue to recognize, and when.
This guide explains the five-step model, applies it to the typical cases of subscription and usage-based businesses, and shows why the billing system is the main source of revenue recognition data. It does not replace the advice of your auditors or advisers, who remain the only judges of how the standard applies to your contracts.
For the overall framework, see our guide to quote-to-cash.
Contents
IFRS 15 in brief
IFRS 15 applies to companies reporting under IFRS, including listed groups in the EU for their consolidated accounts. Its core principle: recognize revenue to depict the transfer of promised goods or services to the customer, for the consideration the company expects to be entitled to.
In the European Union, IFRS Standards are mandatory for the consolidated accounts of listed companies. Other groups apply them voluntarily, often because they have international investors or a foreign parent company. The individual accounts of French companies, by contrast, are still prepared under French accounting rules, which do not adopt the full logic of IFRS 15. In the United States, companies following US GAAP apply ASC 606.
The core principle of the standard fits in one sentence: the company recognizes revenue to depict the transfer of promised goods or services to the customer, in an amount that reflects the consideration to which it expects to be entitled in exchange.
Two ideas follow:
- timing: revenue follows the delivery of what was promised, over time for a continuous service, or at a point in time for a delivered good;
- amount: it takes into account everything that changes the real price of the contract, such as discounts, variable amounts and the allocation between the different items sold together.
| Before IFRS 15 (IAS 18, IAS 11) | IFRS 15 | |
|---|---|---|
| Logic | Transfer of risks and rewards | Transfer of control to the customer |
| Approach | Several standards and interpretations depending on the type of sale | A single five-step model for all customer contracts |
| Bundles | Less detailed rules | Identification of each obligation and allocation of the price |
| Disclosures | More limited | Detailed: disaggregation of revenue, contract balances, remaining performance obligations |
The five-step model
IFRS 15 applies the same five steps to every customer contract: identify the contract, identify the performance obligations, determine the transaction price, allocate it to the obligations, and recognize revenue as each obligation is satisfied.
Step 1: identify the contract
A contract exists when the parties have approved it, each party's rights and the payment terms can be identified, it has commercial substance and collection of the consideration is probable. A contract can be written, oral or implied by customary practice. Several contracts concluded at the same time with the same customer may have to be combined.
Step 2: identify the performance obligations
A performance obligation is a promise to transfer a distinct good or service to the customer. A mobile subscription with a handset usually includes two obligations: the handset and the service. Setup fees, on the other hand, often do not correspond to any distinct service: they pay for a preparatory activity and are then attached to the main service.
Step 3: determine the transaction price
This is the amount the company expects to be entitled to. It includes variable consideration (conditional discounts, penalties, bonuses, usage), estimated and constrained to the amount for which a significant reversal is unlikely. Where relevant, it takes into account a significant financing component when payment is far out of step with delivery.
Step 4: allocate the price
When a contract has several obligations, the total price is allocated among them in proportion to their standalone selling prices, that is, the price at which each item would be sold on its own. This is the step that means a handset sold for one euro with a plan can carry a much larger share of the contract's revenue.
Step 5: recognize revenue
Revenue for each obligation is recognized when it is satisfied: over time for a service delivered continuously (a subscription, maintenance), or at a point in time for a delivered good or a one-off service.
| Step | Question | Example in a subscription contract |
|---|---|---|
| 1. Contract | Is there a contract under the standard? | A two-year contract signed by a business customer |
| 2. Obligations | What distinct things did we promise? | The monthly service, a device, training |
| 3. Price | How much do we expect in total? | Subscription fees, setup fees, first-year discount, estimated usage |
| 4. Allocation | How do we split this price? | Based on each item's standalone selling price |
| 5. Recognition | When do we recognize each part? | The service month by month, the device on delivery |
Billing vs revenue recognition
Billing answers "what does the customer owe, and when?". Revenue recognition answers "what have we earned, and when?". An annual subscription billed upfront is recognized month by month, creating deferred revenue; usage billed in arrears is recognized before the invoice.
The confusion is common: revenue is assumed to equal what was invoiced in the month. Under IFRS 15, that is only true in the simplest cases.
Take an annual subscription billed once, at the start of the year:
- the invoice is issued in January, for the whole year;
- revenue is recognized one twelfth each month, as the service is delivered;
- the difference, billed but not yet earned, is recorded on the balance sheet as a contract liability, often called deferred revenue.
Conversely, a service delivered but not yet invoiced (usage for the month billed the following month, for example) leads to revenue recognized before the invoice, with a receivable or contract asset as the counterpart.
| Situation | Invoice | Revenue recognized | On the balance sheet |
|---|---|---|---|
| Billed in advance | Before the service | As the service is delivered | Contract liability (deferred revenue) |
| Billed in arrears | After the service | As the service is delivered | Receivable or contract asset |
| Bundle | According to the commercial contract | According to the allocation of the price among obligations | Gaps tracked per obligation |
Billing and revenue recognition start from the same contracts, and must be reconcilable at all times.
IFRS 15 for subscriptions
A continuous subscription service is usually recognized on a straight-line basis over the service period. Setup fees, discounts, free months, discounted renewal options and sales commissions each require specific analysis.
Subscriptions are the most common case, and the simplest in appearance. Several situations still require analysis.
The recurring service
A subscription to a continuously delivered service is generally an obligation satisfied over time: revenue is recognized on a straight-line basis over the service period, whatever the billing frequency (monthly, quarterly, annual).
Setup or activation fees
If they do not correspond to any distinct service transferred to the customer, they are not recognized when billed but spread over the period during which the customer benefits from the service, which can extend beyond the initial contract term if the customer is likely to renew.
Discounts and free months
A discount on the first months, or free months, reduce the total contract price. For a twelve-month commitment with two free months, revenue for the whole is generally spread over the full term, rather than zero for two months and full afterwards.
Discounted renewal options
If the customer obtains an option it would not have had without signing the contract (a renewal at a significantly lower price, for example), that option may be a material right: a performance obligation in its own right, to which part of the price is allocated.
Sales commissions
The incremental costs of obtaining a contract, such as commissions paid to sales reps, are in principle capitalized and amortized over the life of the relationship, if they are recoverable. It is a topic that links sales compensation and accounting.
For how subscription billing works, see our guide to recurring billing.
IFRS 15 for usage
Usage is variable consideration. In many cases it is recognized in the period consumed, when it reflects the value transferred. Plans with included volumes, minimum commitments, prepaid credits and retroactive volume discounts each need specific treatment.
Usage-based billing adds a difficulty: the amount is not known in advance.
| Case | Usual treatment (to be analyzed contract by contract) |
|---|---|
| Pure usage, price per unit | Revenue generally follows the period's consumption, when it corresponds to the value transferred to the customer |
| Plan with included volume, then overage | The plan is recognized over the period; the overage, a variable amount, is generally attached to the period in which it is consumed |
| Annual minimum commitment | The minimum is part of the price; any true-up at the end of the period must be estimated and tracked |
| Prepaid credits | The cash received is a liability; revenue is recognized as credits are consumed, with specific treatment for credits that will never be used |
| Tiers and retroactive volume discounts | The expected average price may need to be estimated to avoid recognizing too much revenue early in the period |
In all these cases, revenue recognition depends on usage data that is reliable, complete and attached to the right contract: that is the role of billing mediation and rating. For AI offers billed per token or credit, see also our guide to AI billing.
Bundles and price allocation
In a bundle, the contract price is allocated among items in proportion to their standalone selling prices, not their commercial prices. A subsidized device can therefore carry a large share of revenue, recognized on delivery, while the service carries the rest over time.
Bundles are the classic example of IFRS 15's impact: a subsidized device sold with a subscription, a license and a maintenance service, an installation and a subscription. The commercial price of each item does not always reflect its value.
Take an illustrative example: a device sold alone for €300 is offered for €0 with a 24-month subscription at €30 a month, which is itself sold for €25 a month without the device.
- the total contract price is €720 (24 × 30);
- the standalone selling prices are €300 for the device and €600 for the service (24 × 25), or €900;
- the device receives 300/900 of the price, or €240, recognized on delivery;
- the service receives 600/900 of the price, or €480, recognized over 24 months, or €20 a month.
The customer pays €30 a month, but the company recognizes €240 on delivery then €20 a month. The gap between what is billed and what is recognized creates a contract asset that unwinds as invoices are issued.
This calculation, simple on one contract, becomes heavy across hundreds of thousands of contracts with varied combinations. It requires knowing, for each contract, the items sold, their standalone selling prices and their delivery dates.
Contract modifications
IFRS 15 treats a modification as a separate contract, as the termination of the old contract and creation of a new one, or as a cumulative catch-up adjustment, depending on whether the added goods or services are distinct and priced at their standalone selling price.
Subscription contracts change constantly: upgrades, added licenses, extensions, discounts granted along the way, partial cancellations. IFRS 15 distinguishes several treatments.
| Situation | Treatment |
|---|---|
| Addition of distinct goods or services at their standalone selling price | As a separate contract |
| Addition or change of distinct services at a different price | As the termination of the old contract and creation of a new one, for the remaining part |
| Change to items that are not distinct from those already delivered | Cumulative catch-up adjustment to revenue at the modification date |
In practice, this means every change recorded in the subscription management system can change the revenue to be recognized over the remaining term of the contract. A system that overwrites history instead of dating every change makes the analysis impossible. See our guide to subscription management software.
The data billing must provide
Revenue recognition relies on contracts and their items, list and standalone selling prices, discounts, activation and delivery dates, rated usage, dated modifications, invoices, credit notes and payments, broken down by product, country and segment.
Revenue recognition is calculated in accounting or in a dedicated tool, but it feeds almost entirely on quote-to-cash data. If that data is incomplete, the calculation is wrong, or done by hand at month end.
| Data | Why |
|---|---|
| The contract and its items (offers, options, devices) | Identify the performance obligations |
| List prices and standalone selling prices | Allocate the price of bundles |
| Discounts, their duration and conditions | Determine the transaction price |
| Activation, delivery and end-of-service dates | Know when each obligation is satisfied |
| Rated usage, by period and by contract | Recognize variable amounts |
| Dated modifications (upgrades, amendments, cancellations) | Apply the right treatment to modifications |
| Invoices, credit notes and payments | Calculate deferred revenue and receivables |
| Breakdown by product, country, segment | Produce the required disclosures |
The companies that do this best are those whose offer catalog, contracts, rating and billing share the same data, and that send accounting entries already broken down, rather than a simple billed total.
Common mistakes
The most common mistakes are confusing billed with earned, ignoring bundles, recognizing setup fees immediately, forgetting discounts and free months, overwriting contract history, handling usage outside the system and not reconciling billing with accounting.
- Confusing billed and earned: recognizing an annual invoice all at once.
- Ignoring bundles: letting the commercial price of each item serve as the allocation.
- Recognizing setup fees immediately when they do not correspond to any distinct service.
- Forgetting discounts and free months in the total contract price.
- Overwriting contract history: modifications cannot be treated correctly.
- Handling usage outside the system: estimates made in spreadsheets, hard to justify.
- Not reconciling billing and accounting: unexplained gaps between revenue, invoices and deferred revenue, which auditors flag.
Where Opencell fits
Opencell is an open source monetization platform that manages, on a single platform, the offer catalog, contracts and their modifications, usage rating, billing and payments. It automates revenue recognition and the accounting export, with a chart of accounts and period closes integrated with the ERP, giving finance reliable, dated and broken-down data to apply IFRS 15. Each company's own recognition rules remain defined with its finance teams and auditors. See the platform.
Born in telecoms in 2007, Opencell now manages €14 billion in revenue for around fifty customers, including Orange Business Services, Engie, TotalEnergies, OVHcloud and La Poste.
Frequently asked questions about IFRS 15
What is IFRS 15?
It is the international standard that defines how to recognize revenue from contracts with customers. Applicable since January 1, 2018, it replaces in particular IAS 18 and IAS 11 and is based on a single five-step model.
What are the five steps of IFRS 15?
Identify the contract, identify the performance obligations, determine the transaction price, allocate that price to the obligations, then recognize revenue when each obligation is satisfied, over time or at a point in time.
What is a performance obligation?
It is a promise to transfer a distinct good or service to the customer. A subscription with a device often has two obligations. Each receives a share of the price and its revenue is recognized at its own pace.
How do you recognize revenue on an annual subscription billed upfront?
Generally, revenue is recognized on a straight-line basis over the twelve months of service. The part billed but not yet earned is recorded on the balance sheet as a contract liability, or deferred revenue.
How is usage treated under IFRS 15?
Usage is variable consideration. In many cases, it is recognized in the period in which it is consumed, when it reflects the value transferred to the customer. Minimum commitments, tiers and retroactive discounts require an estimate of the expected price.
What is the difference between IFRS 15 and ASC 606?
They are two standards resulting from a joint IASB and FASB project, with the same five-step model. ASC 606 applies to companies following US GAAP; a few detailed differences exist between the two.
Does IFRS 15 apply to every company?
No. IFRS 15 applies to accounts prepared under IFRS, mandatory for the consolidated accounts of listed companies in the European Union and applied voluntarily by other groups. Individual company accounts often follow local accounting rules, such as French GAAP, and US companies apply ASC 606.
What role does the billing system play in IFRS 15?
It provides most of the data needed: contracts and items sold, prices and discounts, service dates, rated usage, dated modifications, invoices and payments. Without reliable data, revenue recognition is done by hand and exposed to errors.
Revenue is prepared in billing
IFRS 15 made revenue a calculation that depends on each contract: on what was promised, on how the price is allocated, and on when each item is delivered. For subscription and usage-based businesses, that calculation happens upstream of accounting, in contracts, rating and billing.
Key takeaways:
- IFRS 15 recognizes revenue on transfer of control, not on the invoice,
- the five-step model applies to all customer contracts,
- a subscription billed in advance creates deferred revenue,
- bundles require allocating the price according to the value of each item,
- every contract modification can change the revenue left to recognize,
- the quality of revenue recognition depends on the quality of quote-to-cash data.
What you bill shows up immediately. What you earn has to be calculated.
Go further with Opencell
Opencell is an agile, open source monetization platform that automates quote-to-cash, from quote to cash collection, for subscription and usage-based services. It keeps contracts, prices, discounts, dates, usage and changes in one place, giving finance the data revenue recognition depends on. Born in telecoms in 2007, it manages €14 billion in revenue for around fifty customers.
Want billing data your revenue recognition can rely on?



