CFA Program Level I
IFRS 15 five-step revenue recognition model: CFA Level I
IFRS 15 recognises revenue in five steps: identify the contract, identify the performance obligations, determine the transaction price, allocate that price to the obligations by relative stand-alone selling prices, and recognise revenue as each obligation is satisfied. Variable amounts such as bonuses are estimated and included in the transaction price.
The five steps
1. Identify the contract or contracts with a customer.
2. Identify the performance obligations. A performance obligation is a promise in the contract to transfer a distinct good or service to the customer.
3. Determine the transaction price: the consideration the entity expects to be entitled to for transferring the promised goods or services. If part of it is variable, such as a bonus, the entity estimates that amount.
4. Allocate the transaction price to each performance obligation on the basis of relative stand-alone selling prices.
5. Recognise revenue when, or as, each performance obligation is satisfied, which is when the customer obtains control of the good or service. The IASB issued IFRS 15 in May 2014, together with the FASB's introduction of Topic 606 into US GAAP.
Allocation, worked
Example: a contract sells a machine and two years of support for EUR1,200 in total. Sold separately, the machine is EUR1,000 and the support EUR500, so stand-alone prices total EUR1,500.
Machine: 1,200 x 1,000 / 1,500 = EUR800. Support: 1,200 x 500 / 1,500 = EUR400. The EUR300 discount falls on both obligations in proportion to their stand-alone prices.
The machine is a good, typically satisfied at a point in time, so EUR800 is recognised on delivery. The support is a service, typically satisfied over time, so EUR400 is recognised across the two years using a measure of progress, here EUR200 a year if the work is even.
Point in time or over time
A promise to transfer goods is typically satisfied at a point in time. A promise to provide services is typically satisfied over time.
For an obligation satisfied over time, the entity chooses a measure of progress and recognises revenue as the work is done, not when the contract ends and not when the customer pays.
Where the exam catches people
- Believing a performance bonus is left out until it is received: variable consideration is estimated and included in the transaction price.
- Believing a bonus or discount is a separate performance obligation: it changes the transaction price, not the list of promises.
- Believing a bundle discount goes entirely to one item: it is spread across the obligations by relative stand-alone selling prices.
- Believing service revenue is recognised when the customer pays: it is recognised as the obligation is satisfied, usually over time.
- Believing allocation comes before determining the transaction price: the price is set in step 3 and allocated in step 4.