Step 1: Identify the contract(s) with a customer
Contracts may be written, verbal or implied by customary business practices, but must
be enforceable and have commercial substance. The model applies to each contract
with a customer once it is probable1 the entity will collect the consideration to which it
will be entitled. In evaluating whether collection is probable, the entity would consider
only the customer’s ability and intention to pay the consideration when due.
An entity may combine two or more contracts that are entered into at or near the
same time with the same customer, and account for them as a single contract,
provided they meet specified criteria.
The standard provides detailed requirements for contract modifications. Depending on
the specific facts and circumstances, a modification may be accounted for as a
separate contract or a modification of the original contract.
Step 2: Identify the separate performance obligations in the contract
Once the contract has been identified, an entity will need to evaluate the terms and
customary business practices to identify which promised goods or services, or a bundle
of promised goods or services, should be accounted for as separate performance
obligations.
The key determinant for identifying a separate performance obligation is whether a
good or service, or a bundle, is distinct. A good or service is distinct if the customer
can benefit from the good or service on its own or together with other readily available
resources and the good or service is separately identifiable from other promises in the
contract. Each distinct good or service will be a separate performance obligation.
An entity may provide a series of distinct goods or services that are substantially the
same and have the same pattern of transfer to the customer. Examples could include
services provided on an hourly or daily basis. Provided specified criteria are met, such
a series is a single performance obligation.
1 While the same threshold of ‘probable’ applies in both IFRS and US GAAP, the threshold differs
because definitions of ‘probable’ in IFRS and US GAAP differ.
Adopting the new
requirements will be a
significant undertaking
for most entities.
IASB and FASB issue new revenue recognition standard — IFRS 15 3
Step 3: Determine the transaction price
The transaction price is the amount of consideration to which an entity expects to be
entitled and includes:
An estimate of any variable consideration (e.g., it may vary due to rebates or
bonuses), using either a probability-weighted expected value or the most likely
amount, whichever better predicts the amount of consideration to which the entity
will be entitled
The effect of the time value of money, if there is a financing component that is
significant to the contract
The fair value of any non-cash consideration
The effect of any consideration payable to the customer, such as vouchers and
coupons
The transaction price is generally not adjusted for credit risk. However, it may be
constrained because of variable consideration. That is, an entity can include variable
consideration in the transaction price only to the extent it is highly probable2 that a
subsequent change in estimated variable consideration will not result in a significant
revenue reversal. A significant reversal occurs when a change in the estimate results
in a significant downward adjustment in the amount of cumulative revenue recognised
from the contract with the customer.
For sales and usage-based royalties from the licence of intellectual property, the
standard specifies that an entity does not include such consideration in the transaction
price before the subsequent sale or usage occurs.
Step 4: Allocate the transaction price to the separate performance obligations
An entity must allocate the transaction price to each separate performance obligation
on a relative stand-alone selling price basis, with limited exceptions. One exception in
the standard permits an entity to allocate a variable amount of consideration, together
with any subsequent changes in that variable consideration, to one or more (but not
all) performance obligations, if specified criteria are met.
When determining stand-alone selling prices, an entity must use observable
information, if it is available. If stand-alone selling prices are not directly observable,
an entity will need to use estimates based on reasonably available information.
Examples of reasonably available information include an adjusted market assessment
approach or an expected cost plus a margin approach. Only when the stand-alone
selling price of a good or service is highly variable or uncertain (as explained in the
standard), can a residual approach be used.
How we see it
In most instances, an entity will be able to make estimates of stand-alone selling
prices that represent management’s best estimate considering observable inputs.
However, it could be more difficult if goods or services are not sold independently by
the entity or others.
Current IFRS does not explicitly address the accounting for multiple-element
arrangements, which has resulted in diversity in practice. IFRS 15 provides detailed
requirements for transactions with multiple elements, but does not eliminate the
need to exercise judgement to determine the appropriate performance obligations
and allocate the consideration to those performance obligations.
2 The FASB standard uses ‘probable’, which has the same meaning as ‘highly probable’ in IFRS.
Revenue will be
recognised when, or
as, control of a good or
service transfers to a
customer.
Step 5: Recognise revenue when (or as) the entity satisfies a performance obligation
An entity satisfies a performance obligation by transferring control of a promised good or
service to the customer, which could occur over time or at a point in time. A performance
obligation is satisfied at a point in time unless it meets one of the following criteria, in which
case, it is satisfied over time:
The customer simultaneously receives and consumes the benefits provided by the
entity’s performance as the entity performs
The entity’s performance creates or enhances an asset that the customer controls as
the asset is created or enhanced
The entity’s performance does not create an asset with an alternative use to the
entity and the entity has an enforceable right to payment for performance completed
to date
Revenue is recognised in line with the pattern of transfer. Revenue that is allocated to
performance obligations satisfied at a point in time will be recognised when control of
the good or service underlying the performance obligation has transferred. If the
performance obligation is satisfied over time, the revenue allocated to that
performance obligation will be recognised over the period the performance obligation
is satisfied, using a single method that best depicts the pattern of the transfer of
control over time. Additional application guidance is provided to assist entities when
determining whether a licence of intellectual property transfers to a customer over time
or at a point in time.
Contract costs and other application guidance