How does revenue recognition work under IFRS 15?

IFRS 15 Revenue from Contracts with Customers establishes a single, comprehensive framework for revenue recognition. The core principle is straightforward: recognise revenue when (or as) an entity satisfies a performance obligation by transferring a promised good or service to a customer, in an amount reflecting the consideration to which the entity expects to be entitled (IFRS 15.31). Control of the asset — not risks and rewards — is the determining concept (IFRS 15.33). The standard operates through a five-step model applied consistently to all contracts with customers (IFRS 15.3): - Step 1 – Identify the contract: A contract must meet specific criteria to be accounted for under IFRS 15, including approval by both parties and commercial substance. If those criteria are not met, consideration received is recognised as revenue only when the entity has no remaining obligations or has refunded any amounts received (IFRS 15.15). - Step 2 – Identify performance obligations: At contract inception, an entity identifies each promise to transfer a distinct good or service. A good or service is distinct if the customer can benefit from it on its own or with other readily available resources, and if the promise to transfer it is separately identifiable from other promises in the contract (IFRS 15.27).

How do you measure transaction price when a contract includes a significant financing component (payment terms >12 months)?

- Step 3 – Determine the transaction price: The transaction price is the amount of consideration an entity expects to be entitled to in exchange for transferring promised goods or services, excluding amounts collected on behalf of third parties (IFRS 15.35). Where non-cash consideration is received — such as materials, equipment or labour contributed by a customer — the entity assesses whether it obtains control and measures it accordingly (IFRS 15.69). Disclosure of methods and assumptions used to determine the transaction price, including variable consideration estimates, is required (IFRS 15.126). - Step 4 – Allocate the transaction price: The transaction price is allocated to each performance obligation in proportion to its standalone selling price. Where a contract is modified, the entity reassesses the allocation based on whether the modification constitutes a separate contract (IFRS 15.20). - Step 5 – Recognise revenue: Revenue is recognised when (or as) each performance obligation is satisfied. An obligation is satisfied over time if one of three criteria is met — the customer simultaneously receives and consumes the benefits, the entity creates or enhances an asset the customer controls, or the asset has no alternative use and the entity has an enforceable right to payment (IFRS 15.35). Otherwise, revenue is recognised at a point in time (IFRS 15.38). For over-time recognition, progress is measured using a single, consistently applied method per obligation (IFRS 15.39). - Bundled contracts: Failing to separate distinct performance obligations within a single contract leads to premature or delayed revenue recognition. Where goods or services are not distinct, they must be combined until a distinct bundle is identified (IFRS 15.30).

What is the treatment of a contract modification that adds distinct goods at the contract price if the customer has already paid in full?

- Variable consideration: Entities sometimes overlook the constraint on variable consideration — only include amounts that are highly probable not to result in a significant revenue reversal. - Over-time vs point-in-time: Misclassifying whether control transfers gradually or at a single moment is a frequent error, particularly in construction, licensing and long-term service contracts. Repurchase agreements also affect this analysis (IFRS 15.34). - Early-stage contracts: When an entity cannot reasonably measure the outcome of a performance obligation but expects to recover costs, revenue is recognised only to the extent of costs incurred until reliable measurement is possible (IFRS 15.45). - Disaggregation disclosure: Entities must disclose revenue disaggregated into categories that depict how revenue and cash flows are affected by economic factors, and reconcile this to segment information where applicable (IFRS 15.115).

When should a contract asset be evaluated for impairment under IAS 36, and does IFRS 9 or IFRS 15 guidance apply?

- IFRS 15.3 — Requires consistent application to contracts with similar characteristics and circumstances, including use of practical expedients. - IFRS 15.27 — Defines when a promised good or service is distinct, the foundation for identifying separate performance obligations. - IFRS 15.31 — States the core recognition principle: recognise revenue when (or as) a performance obligation is satisfied by transferring control to the customer. - IFRS 15.35 — Sets out the three criteria for determining whether a performance obligation is satisfied over time. - IFRS 15.45 — Addresses revenue recognition limited to costs incurred when contract outcome cannot be reliably measured. - IFRS 15.126 — Requires disclosure of methods, inputs and assumptions used to determine the transaction price, including variable consideration and financing effects.

IFRS 15 Revenue Recognition — 5-Step Model

IFRS 15 Revenue from Contracts — Core Rule

IFRS 15 Revenue from Contracts with Customers establishes a single, comprehensive framework for revenue recognition. The core principle is straightforward: recognise revenue when (or as) an entity satisfies a performance obligation by transferring a promised good or service to a customer, in an amount reflecting the consideration to which the entity expects to be entitled (IFRS 15.31). Control of the asset — not risks and rewards — is the determining concept (IFRS 15.33).

How IFRS 15 Revenue from Contracts Works

The standard operates through a five-step model applied consistently to all contracts with customers (IFRS 15.3):

Step 1 – Identify the contract: A contract must meet specific criteria to be accounted for under IFRS 15, including approval by both parties and commercial substance. If those criteria are not met, consideration received is recognised as revenue only when the entity has no remaining obligations or has refunded any amounts received (IFRS 15.15).

Step 2 – Identify performance obligations: At contract inception, an entity identifies each promise to transfer a distinct good or service. A good or service is distinct if the customer can benefit from it on its own or with other readily available resources, and if the promise to transfer it is separately identifiable from other promises in the contract (IFRS 15.27).

Step 3 – Determine the transaction price: The transaction price is the amount of consideration an entity expects to be entitled to in exchange for transferring promised goods or services, excluding amounts collected on behalf of third parties (IFRS 15.35). Where non-cash consideration is received — such as materials, equipment or labour contributed by a customer — the entity assesses whether it obtains control and measures it accordingly (IFRS 15.69). Disclosure of methods and assumptions used to determine the transaction price, including variable consideration estimates, is required (IFRS 15.126).

Step 4 – Allocate the transaction price: The transaction price is allocated to each performance obligation in proportion to its standalone selling price. Where a contract is modified, the entity reassesses the allocation based on whether the modification constitutes a separate contract (IFRS 15.20).

Step 5 – Recognise revenue: Revenue is recognised when (or as) each performance obligation is satisfied. An obligation is satisfied over time if one of three criteria is met — the customer simultaneously receives and consumes the benefits, the entity creates or enhances an asset the customer controls, or the asset has no alternative use and the entity has an enforceable right to payment (IFRS 15.35). Otherwise, revenue is recognised at a point in time (IFRS 15.38). For over-time recognition, progress is measured using a single, consistently applied method per obligation (IFRS 15.39).

IFRS 15 Revenue from Contracts — Common Pitfalls

Bundled contracts: Failing to separate distinct performance obligations within a single contract leads to premature or delayed revenue recognition. Where goods or services are not distinct, they must be combined until a distinct bundle is identified (IFRS 15.30).

Variable consideration: Entities sometimes overlook the constraint on variable consideration — only include amounts that are highly probable not to result in a significant revenue reversal.

Over-time vs point-in-time: Misclassifying whether control transfers gradually or at a single moment is a frequent error, particularly in construction, licensing and long-term service contracts. Repurchase agreements also affect this analysis (IFRS 15.34).

Early-stage contracts: When an entity cannot reasonably measure the outcome of a performance obligation but expects to recover costs, revenue is recognised only to the extent of costs incurred until reliable measurement is possible (IFRS 15.45).

Disaggregation disclosure: Entities must disclose revenue disaggregated into categories that depict how revenue and cash flows are affected by economic factors, and reconcile this to segment information where applicable (IFRS 15.115).

IFRS 15 Revenue from Contracts — Key Paragraphs

IFRS 15.3 — Requires consistent application to contracts with similar characteristics and circumstances, including use of practical expedients.
IFRS 15.27 — Defines when a promised good or service is distinct, the foundation for identifying separate performance obligations.
IFRS 15.31 — States the core recognition principle: recognise revenue when (or as) a performance obligation is satisfied by transferring control to the customer.
IFRS 15.35 — Sets out the three criteria for determining whether a performance obligation is satisfied over time.
IFRS 15.45 — Addresses revenue recognition limited to costs incurred when contract outcome cannot be reliably measured.
IFRS 15.126 — Requires disclosure of methods, inputs and assumptions used to determine the transaction price, including variable consideration and financing effects.