IFRS 15 uses a five-step model: 1) Identify contract, 2) Identify performance obligations, 3) Determine transaction price, 4) Allocate price to obligations, 5) Recognize revenue when obligations are satisfied.

What are the criteria for revenue recognition (according to IFRS 15)?

Summary: IFRS 15 uses a five-step model: 1) Identify contract, 2) Identify performance obligations, 3) Determine transaction price, 4) Allocate price to obligations, 5) Recognize revenue when obligations are satisfied.

Overview of IFRS 15:

IFRS 15 "Revenue from Contracts with Customers" is the international accounting standard that establishes principles for reporting useful information about revenue from contracts with customers. It applies to annual periods beginning on or after January 1, 2018.

Core Principle: Recognize revenue to depict the transfer of promised goods or services to customers in an amount that reflects the consideration to which the entity expects to be entitled in exchange for those goods or services.

Scope: Applies to all contracts with customers except leases, insurance contracts, financial instruments, and certain other items.

The Five-Step Model:

  1. Step 1: Identify the contract with a customer
  2. Step 2: Identify the performance obligations in the contract
  3. Step 3: Determine the transaction price
  4. Step 4: Allocate the transaction price to the performance obligations
  5. Step 5: Recognize revenue when (or as) the entity satisfies a performance obligation

Visual Representation of the Five Steps:

Step 1: Contract → Step 2: Performance Obligations → Step 3: Transaction Price
      ↓                                      ↓                     ↓
Step 4: Allocate Price → Step 5: Recognize Revenue when Obligations Satisfied

Step 1: Identify the Contract with a Customer

Definition: An agreement between two or more parties that creates enforceable rights and obligations.

Contract Criteria (all must be met):

  1. Approval and commitment: Parties have approved the contract and are committed to perform
  2. Rights identified: Each party's rights regarding goods/services are identified
  3. Payment terms identified: Payment terms for goods/services are identified
  4. Commercial substance: The contract has commercial substance
  5. Probable collection: It is probable that the entity will collect the consideration

Contract Modifications:

  • Treat as separate contract if additional goods/services are distinct and price reflects standalone selling price
  • Treat as termination of old and creation of new contract if goods/services are not distinct
  • Treat as part of existing contract (prospective or cumulative catch-up) if partially distinct

Practical Example:

Situation: Software company signs agreement with customer for software license and support.

  • Approval: Both parties sign contract
  • Rights: Customer gets software license and 1-year support
  • Payment: $10,000 payable 50% upfront, 50% on delivery
  • Commercial substance: Both parties benefit
  • Collection: Customer has good credit history
  • Result: Contract exists under IFRS 15

Step 2: Identify the Performance Obligations

Definition: A promise in a contract to transfer a good or service to a customer.

Key Concepts:

  • Performance obligation: Promise to transfer distinct good/service
  • Distinct: Customer can benefit from good/service on its own or with other readily available resources, AND promise is separately identifiable from other promises

Identifying Distinct Goods/Services:

A good or service is distinct if BOTH conditions are met:

  1. Capable of being distinct: Customer can benefit from good/service on its own or together with other resources readily available
    • Readily available = sold separately by entity or another entity, or customer could generate benefit from earlier transfer
  2. Distinct within context of contract: Promise to transfer good/service is separately identifiable from other promises
    • Consider factors: Not highly dependent/integrated, not significantly modified/customized, not part of combined output

Series of Distinct Goods/Services:

If goods/services are substantially the same and have same pattern of transfer, they can be a single performance obligation.

Practical Examples:

  1. Computer Sale with Installation:
    • Computer: Distinct (can benefit without installation)
    • Installation: Distinct (separate service)
    • Two performance obligations
  2. Software License with Updates:
    • License: Distinct
    • Updates: Not distinct if integral to license
    • May be single performance obligation
  3. Construction Contract:
    • Building construction: Single performance obligation
    • Even though multiple activities, combined to create single output

Step 3: Determine the Transaction Price

Definition: The amount of consideration to which an entity expects to be entitled in exchange for transferring promised goods or services to a customer.

Components to Consider:

  1. Fixed consideration: Stated amount in contract
  2. Variable consideration: Amount that varies based on future events
    • Discounts, rebates, refunds, credits, incentives, performance bonuses, penalties
  3. Significant financing component: Time value of money if payment timing differs significantly from transfer timing
  4. Non-cash consideration: Measured at fair value
  5. Consideration payable to customer: Treated as reduction of transaction price

Estimating Variable Consideration:

Use either method (choose consistently):

  1. Expected value: Probability-weighted amount
    • Best when multiple possible outcomes
    • Example: 60% chance of $100 bonus + 40% chance of $50 bonus = $80 expected
  2. Most likely amount: Single most likely amount
    • Best when binary outcomes
    • Example: Either receive $1,000 bonus or $0

Constraint on Variable Consideration:

Include variable consideration only to extent that it is highly probable that significant reversal will not occur.

Practical Example:

Situation: Construction contract with $1 million fixed price plus $200,000 bonus if completed early. Historical data: 70% chance of early completion.

  • Variable consideration: $200,000 bonus
  • Estimate: Expected value = $200,000 × 70% = $140,000
  • Constraint: If highly probable no significant reversal, include $140,000
  • Transaction price: $1,000,000 + $140,000 = $1,140,000

Step 4: Allocate the Transaction Price

Objective: Allocate transaction price to each performance obligation based on relative standalone selling prices.

Allocation Basis:

Allocate based on relative standalone selling price of each distinct good/service.

Standalone selling price: Price at which entity would sell good/service separately to customer.

Estimating Standalone Selling Price (SSP):

Use one of these methods (in order of preference):

  1. Observable price: When sold separately
  2. Adjusted market assessment: Consider market conditions, competitors, prices
  3. Expected cost plus margin: Forecasted costs plus appropriate margin
  4. Residual approach: Only if SSP highly variable/uncertain
    • Total price minus SSP of other goods/services

Allocation of Discounts:

Allocate overall discount proportionally to all performance obligations, unless evidence that discount relates to specific obligations.

Practical Example:

Situation: Sell package: Computer ($800 SSP) + Printer ($200 SSP) + 1-year support ($100 SSP). Bundle price: $900.

  • Total SSP: $800 + $200 + $100 = $1,100
  • Allocation:
    • Computer: $900 × (800/1,100) = $655
    • Printer: $900 × (200/1,100) = $164
    • Support: $900 × (100/1,100) = $81
  • Discount allocation: $200 discount allocated proportionally

Step 5: Recognize Revenue

Timing: Recognize revenue when (or as) the entity satisfies a performance obligation by transferring control of promised good/service to customer.

Transfer of Control Indicators:

  1. Right to payment: Entity has present right to payment
  2. Legal title transferred: Customer has legal title
  3. Physical possession transferred: Customer has physical possession
  4. Risks and rewards transferred: Customer has significant risks and rewards
  5. Customer acceptance: Customer has accepted the asset

Satisfaction of Performance Obligations:

At a Point in Time (goods and some services):

  • Recognize revenue when control transfers
  • Example: Retail sale, equipment delivery
  • Typically when product shipped/delivered

Over Time (services and some goods):

Recognize revenue over time if ANY of these criteria met:

  1. Customer simultaneously receives and consumes benefits as entity performs
    • Example: Cleaning services, security services
  2. Entity's performance creates/enhances asset that customer controls as asset is created/enhanced
    • Example: Construction on customer's land
  3. Entity's performance does not create asset with alternative use AND entity has enforceable right to payment for performance completed
    • Example: Custom manufacturing

Methods for Recognizing Revenue Over Time:

  1. Output methods: Recognize based on direct measurements of value transferred
    • Surveys of work performed, milestones completed, units delivered
  2. Input methods: Recognize based on entity's efforts/inputs
    • Costs incurred, time elapsed, labor hours

Practical Application Examples:

Example 1: Software as a Service (SaaS)

Situation: Annual subscription $1,200, access to software platform.

  1. Contract: Yes, signed agreement
  2. Performance obligation: Single - access to platform for 1 year
  3. Transaction price: $1,200 fixed
  4. Allocation: Not applicable (single obligation)
  5. Recognition: Over time (customer receives benefit), straight-line over 12 months = $100/month

Example 2: Construction Contract

Situation: Build warehouse for $5 million over 2 years, costs $4 million, progress measured by costs incurred.

  1. Contract: Yes
  2. Performance obligation: Single - constructed warehouse
  3. Transaction price: $5 million fixed
  4. Allocation: Not applicable
  5. Recognition: Over time (creates asset on customer's land), using input method (costs incurred)
    • Year 1 costs: $2 million
    • Percentage complete: 50% (2M/4M)
    • Revenue Year 1: $2.5 million (5M × 50%)

Example 3: Mobile Phone with Service Plan

Situation: Sell phone for $200 (SSP $400) with 2-year service plan $40/month (SSP $960). Bundle price: $1,160.

  1. Contract: Yes
  2. Performance obligations: Two - phone (distinct), service (distinct)
  3. Transaction price: $1,160
  4. Allocation:
    • Total SSP: $400 + $960 = $1,360
    • Phone: $1,160 × (400/1,360) = $341
    • Service: $1,160 × (960/1,360) = $819 ($34.13/month)
  5. Recognition:
    • Phone: At point in time (when delivered)
    • Service: Over time, monthly over 24 months

Special Topics in IFRS 15:

1. Principal vs. Agent Considerations:

  • Principal: Controls good/service before transfer, recognizes revenue gross
  • Agent: Arranges for principal to provide good/service, recognizes commission net
  • Indicators of control: Primary responsibility, inventory risk, pricing discretion

2. Warranties:

  • Assurance-type warranty: Part of performance obligation (no separate obligation)
  • Service-type warranty: Separate performance obligation
  • Distinction: Whether warranty provides additional service beyond assurance

3. Rights of Return:

  • Recognize revenue for expected sales (net of returns)
  • Recognize refund liability for expected returns
  • Recognize asset for returned goods (at lower of cost or NRV)

4. Licenses of Intellectual Property:

  • Right to access IP: Recognize over time (if continuously updated)
  • Right to use IP: Recognize at point in time (if static)

5. Bill-and-Hold Arrangements:

  • Recognize revenue when control transfers (not when billed)
  • Must meet specific criteria for bill-and-hold

Disclosure Requirements:

Quantitative and Qualitative Disclosures:

  1. Contracts with customers - disaggregation of revenue
  2. Contract balances - opening/closing receivables, contract assets/liabilities
  3. Performance obligations - remaining obligations and timing
  4. Significant judgments - methods, estimates, changes
  5. Assets recognized from costs to obtain/fulfill contracts

Transition and Implementation:

Transition Methods:

  1. Full retrospective: Restate all periods presented
  2. Modified retrospective: Apply at adoption date, recognize cumulative effect

Key Points to Remember:

  1. Five-step model is the core framework
  2. Control transfer determines timing of revenue recognition
  3. Distinct goods/services are key to identifying performance obligations
  4. Transaction price includes variable consideration subject to constraint
  5. Allocation based on standalone selling prices
  6. Over time recognition requires meeting specific criteria
  7. Judgment required in many areas
  8. Enhanced disclosures required for transparency
  9. Consistent application across similar contracts
  10. Documentation essential for audit trail

Comparison with Old Standards:

AspectOld Standards (IAS 18, IAS 11)IFRS 15
FrameworkRules-based, industry-specificPrinciples-based, single model
TimingRisks/rewards transferControl transfer
Multiple elementsLimited guidanceDetailed five-step model
Variable considerationRecognize when receivedEstimate with constraint
DisclosuresMinimalExtensive and detailed

Final Note: IFRS 15 represents a significant change in revenue recognition, moving from rules-based to principles-based approach. It requires careful analysis of contracts and significant judgment in many areas.

Share this page: Twitter Facebook LinkedIn