IFRS 15 Revenue Recognition Deep Dive: Complex Scenarios

IFRS 15 Five-Step Model Recap

1. Identify the contract
2. Identify performance obligations
3. Determine transaction price
4. Allocate price to obligations
5. Recognise revenue when obligations are satisfied

Key principle: Revenue is recognised when (or as) control of promised goods/services transfers to the customer. "Control" = ability to direct use and obtain benefits.

Reference: IFRS 15 paragraphs 1— 20, examples in Appendix B.

Identifying Performance Obligations

Definition: A promise to transfer a good or service (or group of goods/services) that is distinct.

Distinct test: A good/service is distinct if:

1. Customer can benefit from it on its own (or with resources readily available), AND
2. It is separately identifiable from other promises in the contract

Example divergence (auditors' nightmare):

Contract: Software license + implementation + annual support

• One obligation: If implementation is critical to the license (customer can't use it without setup), then software + implementation = one obligation, recognised over the support term
• Three obligations: If implementation is separable (customer could use software without vendor's setup), then license, implementation, and support = three obligations, recognised at different times

Audit procedure: Obtain contracts and test management's identification of obligations. Did they consider whether components are functionally interdependent? Document the conclusion.

Variable Consideration & Price Adjustments

Variable consideration = payments that depend on future events (rebates, performance bonuses, discounts).

Measurement rule: Include variable consideration in transaction price if it's probable that it will not be reversed (i.e., highly probable that revenue will not be offset by a subsequent adjustment).

Example 1 (include): Contract offers 10% volume discount if customer purchases >100 units. After 3 months, customer has already purchased 150 units. Highly probable they'll reach 100 → include full discount in transaction price now.

Example 2 (exclude): Contract offers £10k bonus if customer achieves 95% uptime SLA. Uptime is at 80% after 6 months with 6 months remaining. Not highly probable to achieve 95% → exclude bonus from transaction price; recognise only if/when achieved.

Licensing Contracts: Right-to-Use vs Right-to-Access

Right-to-use (point in time recognition): Customer obtains control of the IP. Revenue recognised at a point in time (e.g., upfront when license is granted).

Right-to-access (over time recognition): Customer has access to the licensor's IP as it evolves (e.g., software as a service, where vendor patches and updates during the term). Revenue recognised over time.

How to distinguish:

• Does the contract specify a fixed version (right-to-use) or does the customer benefit from updates/improvements (right-to-access)?
• Can the customer use the license independently, or does it depend on vendor's ongoing support (right-to-access)?

Example: Annual SaaS license (email analytics software). Contract specifies "latest version of software as maintained by vendor." Upgrades, bug fixes, and new features are delivered continuously. → Right-to-access → Recognise over 12 months.

Contract Modifications & Amendments

Three ways to treat a modification:

1. New contract: If the modification adds new, distinct services AND the price reflects the standalone price → treat as separate contract, recognise new revenue
2. Cumulative catch-up: If the modification changes obligations but is part of the same contract → adjust transaction price, recognise cumulative catch-up adjustment in current period
3. Prospective: If the modification is a minor change → adjust transaction price prospectively

Worked example: Year 1 SaaS contract £100k/year. In month 7, customer adds a new module (value £30k for the remaining 6 months). Is this a new contract or an amendment?

If the module is distinct and the price (£30k) equals the standalone price for 6 months → new contract, recognise £30k over remaining 6 months.

If the module is not distinct (integrated into existing service) → amendment, increase transaction price from £100k to £130k, recognise the £30k over remaining 6 months (cumulative catch-up in month 7).

SaaS Multi-Year Contract: Worked Example

Audit Procedures & High-Risk Areas

• Performance obligation testing: For contracts with multiple components, obtain the contract, document management's PO identification logic, challenge "bundled" claims
• Standalone selling price: When allocating transaction price, verify that allocation percentages match standalone prices (not arbitrary allocation)
• Variable consideration: For bonuses, rebates, or volume discounts, verify the likelihood assessment and the supporting data (sales history, current volumes)
• Licensing classification: For software/IP contracts, determine right-to-use vs right-to-access by reviewing contract terms (fixed version? ongoing updates?) and substance over form
• Subsequent amendments: Post-year-end, check for amendments to contracts signed in the audit period. These may trigger cumulative catch-up adjustments
• Month-end channel stuffing: Unusual contracts at year-end (especially with right-of-return) are fraud risk. Confirm with customer and review payment terms

FAQs

This guide is simplified. IFRS 15 revenue accounting depends on specific contract facts and management judgment. Always consult the full IFRS 15 text, examples, and your own advisors before finalising treatment.

Real-Life Case Study: A Telecom Handset-Plus-Airtime Bundle