IFRS 15 — Revenue from Contracts with Customers
Revenue recognition: the five steps
When revenue is recognised, and why the invoice date is not the answer.
9 min read
The idea
The most repeated mistake in practice is treating the invoice date as the recognition date. An invoice is a billing document; recognition is an accounting decision grounded in the contract and what actually happened under it. The standard separates the two explicitly.
The model runs through five sequential steps: identify the contract, identify the performance obligations in it, determine the transaction price, allocate that price to the obligations, and recognise revenue as each obligation is satisfied. The steps are not theory for its own sake; each one prevents a specific error that shows up in real files.
The treatment
1 — Identify the contract
There must be an agreement with commercial substance, identifiable rights and obligations, and consideration that is probable of collection. The agreement may be written, oral, or implied by customary practice. If collection is not probable to begin with, the issue is not recognition timing but whether a contract exists at all.
2 — Identify the performance obligations
A distinct obligation is a promise of a good or service the customer can benefit from on its own or with readily available resources, and which is separately identifiable from the other promises in the contract. Supply-and-install is the classic case: they may be two obligations, or one, if the installation significantly modifies the good.
3 — Determine the transaction price
The price is the consideration the entity expects to be entitled to, after accounting for variable consideration: discounts, performance bonuses, and expected returns. Variable consideration is estimated and constrained so that a significant reversal of revenue does not occur later.
4 — Allocate the price
The price is allocated to the obligations in proportion to their standalone selling prices. When a standalone price is not observable it is estimated, for example through an adjusted market assessment or cost plus a margin. Many errors start here: allocating by what is convenient for billing rather than by standalone value.
5 — Recognise as obligations are satisfied
Revenue is recognised when control of the good or service transfers to the customer: over time when the customer consumes the benefit as it is provided or an asset is created under its control, or at a point in time when control passes at once. Indicators of transfer include a present right to payment, legal title, physical possession, the risks and rewards of ownership, and acceptance.
Contract asset versus receivable
When you recognise revenue before your right to consideration becomes unconditional, a contract asset arises, not a receivable. Contract assets convert to receivables when the right becomes unconditional, that is, conditioned only on the passage of time. Confusing the two distorts receivables ageing and the measurement of expected credit losses.
Worked example
A supply-and-install contract: the entity sells equipment and undertakes to install it at the customer's site. Installation is available from other vendors and does not significantly modify the equipment, so the two are distinct obligations. The equipment was delivered and accepted in March, installation was performed in April, and payment falls due after installation completes.
- Allocate the transaction price to the two obligations by their standalone selling prices: equipment SAR 90,000 and installation SAR 10,000, for a total of SAR 100,000.
- In March control of the equipment transferred on delivery and acceptance, so SAR 90,000 of revenue is recognised. The right to consideration is conditional on installation completing, so the debit is a contract asset, not a receivable.
- In April installation completes, so SAR 10,000 of revenue is recognised, the right to the full amount becomes unconditional, and the contract asset transfers to receivables at SAR 100,000.
Synthetic teaching amounts; the example does not address any tax treatment.
March — recognise the equipment revenue
On delivery and acceptance of the equipment, while the right to consideration stays conditional on installation.
| Account | Debit (SAR) | Credit (SAR) |
|---|---|---|
| Contract asset | 90,000.00 | — |
| Sales revenue | — | 90,000.00 |
| Total | 90,000.00 | 90,000.00 |
April — recognise the installation revenue
On completion and customer acceptance of the installation service.
| Account | Debit (SAR) | Credit (SAR) |
|---|---|---|
| Contract asset | 10,000.00 | — |
| Service revenue | — | 10,000.00 |
| Total | 10,000.00 | 10,000.00 |
April — reclassify the contract asset
When the right to consideration becomes unconditional and depends only on the passage of time.
| Account | Debit (SAR) | Credit (SAR) |
|---|---|---|
| Accounts receivable | 100,000.00 | — |
| Contract asset | — | 100,000.00 |
| Total | 100,000.00 | 100,000.00 |
Common errors
- Recognising revenue on the invoice date instead of the date control transfers.
- Treating a supply-and-install contract as one obligation without testing distinctness.
- Recording a receivable while the right to consideration is still conditional on further performance.
- Ignoring variable consideration, so revenue is recognised and then significantly reversed in a later period.
Interview question
Goods were delivered on the last day of the period and the invoice was issued only after close. When is revenue recognised?
In the period control transferred, that is on delivery and acceptance, not in the period the invoice was issued. If the right to consideration is not yet unconditional, the debit is a contract asset that converts to a receivable on billing. Late invoicing is an operational matter and does not defer recognition.