IFRS 15 Revenue Recognition: Complete Guide with 5-Step Model & Worked Examples

IFRS 15: Overview and Scope

IFRS 15 applies to all contracts with customers except:

• Insurance contracts (IFRS 17)
• Lease contracts (IFRS 16)
• Financial instruments (IFRS 9)

The core principle: recognize revenue when (or as) control of goods/services transfers to the customer.

Step 1: Identify the Contract

A contract must have:

• Approval by both parties (written, oral, or implied)
• Identified rights and obligations
• Payment terms
• Commercial substance (likely to result in goods/services transfer)

Audit focus: Is there truly a contract? Or just an email exchange? Is payment probable? If payment is unlikely, don't recognize revenue.

Step 2: Identify Performance Obligations

A performance obligation is a promise to transfer a distinct good or service to the customer.

What is "Distinct"?

A good/service is distinct if the customer can benefit from it on its own (or with other resources they can obtain) and the entity's promise is separately identifiable from other promises.

Examples: Distinct vs Non-Distinct

Step 3: Determine Transaction Price

Transaction price = amount of consideration expected in exchange for goods/services.

Fixed Consideration

Price is fixed at contract date. Example: £10,000 for software license.

Variable Consideration

Price depends on future events (discounts, rebates, bonuses, penalties). Use the expected value or most likely amount method (whichever better predicts performance).

Variable Consideration Example
Contract: Deliver 1,000 units at £100/unit. Discount available if customer orders 2,000+ units by year-end.
— Most likely scenario (70% probability): 1,000 units sold at £100 = £100k
— Upside scenario (30% probability): 2,000 units sold; discount applied; incremental 1,000 at £90 = £190k total
— Expected value: (70% × £100k) + (30% × £190k) = £127k
— Recognize £127k in revenue (unless constraint applies — see below)

Constraint on Variable Consideration

Only include variable consideration if it's highly probable it won't be reversed. If there's significant uncertainty, apply a constraint and recognize a lower amount.

Step 4: Allocate the Price

If the contract has multiple performance obligations, allocate the transaction price based on standalone selling prices.

Allocation Example
Contract: Software + 1-year support for £12,000
— Standalone selling price of software: £10,000
— Standalone selling price of support: £2,500
— Total: £12,500
— Allocation to software: (£10,000 / £12,500) × £12,000 = £9,600
— Allocation to support: (£2,500 / £12,500) × £12,000 = £2,400

Step 5: Recognize Revenue

Recognize revenue when (or as) control of the good/service transfers to the customer.

Point-in-Time vs Over-Time Recognition

• Point-in-time: Single moment when control transfers. Example: Retail sale at checkout
• Over-time: Revenue recognized throughout the performance period. Examples: SaaS subscriptions, professional services

Over-Time Recognition Methods

Contract Assets & Liabilities

Contract Asset

Recognized when revenue is recognized but payment hasn't been received. It's a conditional right to payment.

Contract Asset Example
SaaS company recognizes £10,000 in revenue (customers using service). Invoice hasn't been sent yet.
Journal Entry:
Dr Contract Asset £10,000 | Cr Revenue £10,000

(When invoiced: Dr Accounts Receivable £10,000 | Cr Contract Asset £10,000)

Contract Liability

Recognized when the customer pays before goods/services are delivered. Also called "deferred revenue."

Contract Liability Example
Customer prepays £24,000 for 1-year SaaS subscription.
Journal Entry at receipt:
Dr Cash £24,000 | Cr Contract Liability (Deferred Revenue) £24,000

Monthly, as service is delivered:
Dr Contract Liability £2,000 | Cr Revenue £2,000

Worked Examples

Example 1: SaaS (Over-Time, Output Method)

Scenario: Software company sells 1-year SaaS license for £12,000 (monthly billing).

• Performance obligation: One: deliver software access for 12 months
• Revenue recognition: Over-time, as customer benefits monthly
• Method: Output (time-based)
• Monthly revenue: £12,000 / 12 = £1,000/month

Example 2: Manufacturing (Over-Time, Input Method)

Scenario: Construction company enters a £1,000,000 contract to build a custom facility. Total estimated costs: £800,000.

• Performance obligation: One: construct the facility
• Revenue recognition: Over-time as control transfers (customer benefits as construction progresses)
• Method: Input (cost-to-cost)
• Year 1: Costs incurred £240,000 (30% of total £800k)
• Year 1 revenue: 30% × £1,000,000 = £300,000

Example 3: Retail + Extended Warranty (Point-in-Time + Over-Time)

Scenario: Electronics retailer sells a laptop for £800 + 2-year extended warranty for £150 (total £950).

• Performance obligations: Two separate obligations
• Laptop: Point-in-time (control transfers at sale); £800 revenue immediately
• Warranty: Over-time (obligation to provide protection over 24 months); £150 recognized over 24 months (£6.25/month)

Warranties & Right of Return

Warranties

• Assurance warranty: Confirms product meets agreed standard. Not a separate obligation; don't allocate price.
• Performance warranty: Obligation beyond standard. IS a separate obligation; allocate price to it.

Right of Return

If the customer can return goods, recognize revenue only to the extent payment is not expected to be refunded. Set up a refund liability for expected returns.

Right of Return Example
Retailer sells 100 units at £100/unit (£10,000). Historical return rate: 5%.
— Revenue: £10,000 × 95% = £9,500
— Refund liability: £10,000 × 5% = £500
Journal Entry:
Dr Cash £10,000 | Cr Revenue £9,500 | Cr Refund Liability £500

Audit Red Flags in IFRS 15

Red Flag 1: Channel Stuffing

Finding: Company recognizes revenue on shipment to distributor, but distributor has no customer orders yet (goods may be returned).

Auditor action: Does the distributor have control? Or can the company force returns? If control hasn't transferred, defer revenue.

Red Flag 2: Round-Trip Transactions

Finding: Company A sells goods to Company B (related party); B immediately sells back to A. Revenue recognized both directions.

Auditor action: Eliminate the round-trip; they net to zero economic activity.

Red Flag 3: Variable Consideration Overestimation

Finding: Company includes full bonus/incentive in revenue without properly constraining.

Auditor action: Challenge: Is it "highly probable" the bonus won't be reversed? If not, apply a constraint.

Red Flag 4: Extended Payment Terms

Finding: Company sells to a customer with 3-year payment terms. Recognizes full revenue immediately.

Auditor action: Is payment probable? If not, defer revenue. If yes, consider financing component (revenue adjustment).

IFRS 15 vs ASC 606 (US GAAP)

IFRS 15 and ASC 606 are largely aligned (they were converged in 2014/2018). Minor differences exist on lease scope, insurance, and transition guidance, but both use the same 5-step model. Most multinationals apply them identically.

Real-Life Case Study: A Software Company Applying the 5 Steps