IFRS 15 revenue recognition: A complete guide with examples

For any business that sells on contracts, when to recognize revenue is one common concern. Whether it's a one-time service, a multi-year subscription, or a bundle of a product and service, the process of when the revenue actually gets counted as earned is not straightforward. Getting it wrong can be catastrophic for your financial statements which won't be accurate and might show the business in the green while it's all red in reality.

This is the exact problem that IFRS 15 tries to solve. Before it came into effect, revenue recognition rules weren't uniform. Two businesses selling identical products could report their revenue differently. IFRS 15 replaced that with an industry-agnostic framework that serves as the base for all companies.

This guide walks you through what IFRS 15 is, what it covers, explains the five-step rule with clear examples, and highlights where it can go wrong for subscription-based businesses.

What is IFRS 15?

IFRS 15 (Revenue from Contracts with Customers) is an international accounting standard that defines how and when a business should recognize revenue. Issued by the International Accounting Standards Board (IASB), it became effective for reporting periods as of January 1, 2018.

The fundamental idea behind IFRS 15 is revenue should be recognized when control of a good or service transfers to the customer, in an amount that reflects what the business expects to be entitled to in exchange.

IFRS 15 is applied consistently across the 140+ jurisdictions that follow IFRS, including the UK, EU, Australia, and most of Asia. India applies a near-identical local version, Ind AS 115, with minor differences. The major exception is the US, which doesn't use IFRS 15 at all. It follows its own equivalent, ASC 606.

The five-step model for revenue recognition

To recognize revenue under IFRS 15, a business must apply the following five steps.

Step 1: Identify the contract

As per IFRS 15, a contract is an agreement between two or more parties that creates enforceable rights and obligations. It needn't necessarily be a formal written agreement. Even a verbal agreement or one that's implied by standard business practice can qualify as long as they meet certain criteria: both parties should have approved it, it should have a commercial basis, payment terms are clear, and collection of consideration is probable.

Example: A manufacturing company sends a purchase order to a vendor for $5,000 worth of steel parts. The vendor responds back with an order confirmation. This combination of the purchase order and order confirmation forms a contract.

Step 2: Identify the performance obligations

A performance obligation is a promise to deliver a good or service to a customer. Many contracts bundle more than one. For example, a software subscription might come along with a premium support plan and dedicated onboarding. If each of the promised items or service is distinct, then they need to be accounted for separately.

Example: If the purchase order from the example above specifies $4,500 worth of steel beams and $500 for custom installation, the vendor must consider these two as separate obligations and account for the revenue from them separately instead of grouping them into one $5,000 lump sum.

Step 3: Determine the transaction price

This is the amount of consideration a business expects to receive from its customer for providing the agreed upon goods and services. It might sound simple on paper, but it gets complicated when variable components such as discounts, rebates, refunds, usage based fees, and the like enter the picture.

Example: A telecom company charges a subscription fee of $10 per month and $0.05 for each phone call made. The transaction price is not the subscription fee alone, as there is a usage-based fee involved. The company needs to estimate the variable usage component too, using either the expected value method or the most likely amount method, whichever accurately predicts the consideration it will actually be entitled to.

Step 4: Allocate the transaction price to performance obligations

The next step is to set the transaction price for each of the performance obligations identified in Step 2. This is done based on their standalone selling prices (SSP). If the SSP is not available for each of the performance obligation, it should be calculated based on the current market conditions.

Example: A SaaS company is providing a bundled annual contract of $10,000 to its customer that covers the platform fee, implementation, and support. If sold separately, these obligations could sell for $8,000, $2,000 and $1,000 respectively. The $10,000 actual contract price would be allocated proportionally across the three obligations based on that ratio, instead of assigning random amounts to each.

Step 5: Recognize revenue as or when performance obligations are satisfied

This step defines when the business can officially record revenue on their income statement. Revenue is recognized only when the business satisfies its performance obligations and transfers control of the promised goods and services to its customer. Control gets transferred either all at once or gradually over a period of time depending on the obligation.

Example: In the SaaS example quoted in the previous step, the revenue from implementation gets recognized progressively across the set-up phase, the platform fee and support revenue gets recognized evenly over the 12-month subscription period.

Why this gets complicated for subscription and recurring-revenue businesses

The five-step model of revenue recognition lists the rules clearly, but putting it in practice is difficult for subscription-based businesses.

Mid-term contract modifications: A customer upgrading, downgrading, or altering user seats during the subscription leads to reassessing the performance obligations and the transaction price. Often, this could lead to a new contract or modifications to the existing contract.

Variable and usage-based pricing: Metered billing, tiered pricing, and consumption-based models mean the transaction price isn't fixed during the contract signing. This has to be re-estimated periodically during the contract term.

Multi-element bundles: SaaS contracts bundle software fee, set-up fee, and support fees. Each of these have to be unbundled and recognized based on their timeline.

Deferred revenue tracking: Annual and multi-year contracts involve lump-sum prepayments. These advance payments need to be recorded as liabilities and gradually moved to earned revenue during the course of obligation fulfillment.

Multicurrency transactions: For businesses selling across multiple countries, currency conversion comes into play. The transaction amount has to be converted to the business's reporting currency and the altering exchange rates make it more complicated.

None of these are troublesome on a spreadsheet when a business is dealing with only a handful of customers. The real problem happens when things scale. For a business managing thousands of contracts with customers across the globe with different pricing models, manual tracking becomes time-consuming and error-prone.

How billing automation supports IFRS 15 compliance

This is precisely why a lot of finance teams look at automation as an option. A billing platform with built-in revenue recognition can:

• Automatically unbundle multiple line items in a contract to separate obligations based on a standalone selling price.

• Recalculate transaction values as the customer's requirement changes during the subscription course.

• Handle plan upgrades and downgrades, with either prospective or retrospective revenue allocation, based on the pro-rated difference in transaction value.

• Help with real-time currency conversion in foreign transactions.

• Keep track of deferred revenue and recognize them as earned as and when obligations are met.

• Maintain an audit trail of all financial transactions so every change can be accurately traced back to its source.

Zoho Billing is built to handle this kind of complexity. From proration and multi-element allocation to deferred revenue tracking, finance teams can stay compliant with IFRS 15 without manually recalculating recognition schedules for every contract change. If you want to see how it applies to your own billing setup, you can get in touch with our team for an exclusive demo of Zoho Billing.

Conclusion

IFRS 15 is no longer a compliance checkbox. It exists to make sure a business's revenue numbers reflect what it has earned and not what it has invoiced. For subscription- and contract-based businesses, this means thinking carefully about performance obligations, variable pricing, and the timing of revenue recognition on every contract.

Getting the five-step process of revenue recognition right is doable at a small scale. As a business starts managing a higher volume of contracts, complexity seeps in. This builds a strong case for automating revenue recognition, deferred revenue tracking, and adaptive revenue adjustments.