IFRS 15 Revenue Recognition: A Practical Guide for Finance Teams and Students

IFRS 15 is not an invoice-recognition rule. Revenue is recognised when, or as, an entity satisfies a performance obligation by transferring control of a promised good or service to a customer. A contract, invoice, tax document or cash receipt may be important evidence, but none of those documents on its own determines when revenue has been earned.

This guide turns the five-step model into a practical framework for students, finance teams and reviewers. It also shows why billing, accounting revenue, EFRIS or VAT records and income-tax reporting may legitimately move at different times—and why those differences still need disciplined reconciliation.

IFRS 15 in brief

IFRS 15 Revenue from Contracts with Customers establishes the principles for reporting the nature, amount, timing and uncertainty of revenue and cash flows arising from contracts with customers. Its core principle is that revenue should depict the transfer of promised goods or services to a customer in an amount that reflects the consideration the entity expects to be entitled to in exchange.

The framework is applied through five connected steps:

1. Identify the contract with the customer.
2. Identify the performance obligations in the contract.
3. Determine the transaction price.
4. Allocate the transaction price to the performance obligations.
5. Recognise revenue when, or as, each performance obligation is satisfied.

The five steps are connected. A mistake in identifying promises can affect the transaction-price allocation, revenue timing, contract balances and disclosures that follow.

What IFRS 15 covers—and what it does not

IFRS 15 generally applies to contracts with customers: parties that obtain goods or services that are an output of the entity's ordinary activities in exchange for consideration.

Not every inflow is IFRS 15 revenue. Lease contracts, insurance contracts, financial instruments and several other contractual rights fall within other IFRS Accounting Standards. Interest, dividends, lease income and gains on disposals may therefore require a different accounting framework.

The first discipline is simple: establish the applicable standard before applying the revenue model.

Contract, invoice, cash and revenue are not the same event

Many revenue errors begin when four different events are treated as though they must happen on the same date.

Item	What it represents	Why timing may differ
Contract	Enforceable rights and obligations between parties	May be agreed before either party performs
Invoice or billing	A demand for payment under contractual terms	Billing milestones may lead or lag performance
Cash receipt	Settlement or advance funding	Cash may arrive before, at or after transfer
Revenue	Consideration allocated to a satisfied performance obligation	Recognition follows transfer of control

An advance from a customer will commonly create a contract liability until the promised goods or services are transferred. Conversely, an entity may perform before it has an unconditional right to bill; that can create a contract asset. Once only the passage of time is required before payment, the right is generally presented as a receivable.

The five-step revenue-recognition model

Step 1: Identify the contract with the customer

A contract can be written, oral or implied by customary business practices. For IFRS 15 accounting, the arrangement must meet the standard's contract criteria, including approval and commitment by the parties, identifiable rights and payment terms, commercial substance and probable collection of the consideration to which the entity expects to be entitled.

If those conditions are not met, cash received does not automatically become revenue. The arrangement is reassessed until the relevant criteria—or the standard's limited conditions for recognising non-refundable consideration—are satisfied.

Step 2: Identify the performance obligations

The entity identifies the promises to transfer distinct goods or services, distinct bundles, and qualifying series of substantially similar services with the same pattern of transfer.

A promised good or service is distinct only when the customer can benefit from it on its own or together with readily available resources and the promise is separately identifiable from the other promises in the contract. A separate line on an invoice is not automatically a separate performance obligation.

Step 3: Determine the transaction price

The transaction price is the consideration the entity expects to be entitled to for transferring the promised goods or services, excluding amounts collected for third parties. It can include fixed and variable amounts and may be affected by financing, non-cash consideration or payments to the customer.

Variable consideration—such as rebates, refunds, credits, incentives, penalties or bonuses—is estimated using the method that best predicts the amount. The estimate is constrained so that revenue includes variable consideration only to the extent that it is highly probable that a significant reversal will not occur when the uncertainty is resolved.

If payment timing provides a significant financing benefit to either party, the consideration may need to be adjusted for the time value of money. IFRS 15 includes a practical expedient where the expected period between transfer and payment is one year or less.

Step 4: Allocate the transaction price

The transaction price is normally allocated to performance obligations in proportion to their stand-alone selling prices at contract inception. Observable prices are preferred. Where they are not available, the entity estimates them using a method that maximises observable inputs.

For example, assume a bundle is sold for UGX 108 million and the stand-alone prices are UGX 90 million for equipment, UGX 20 million for installation and UGX 10 million for support. If there is no evidence that the UGX 12 million discount belongs to one particular component, the discount is generally allocated proportionately across the obligations.

Step 5: Recognise revenue when or as control transfers

Revenue is recognised when, or as, control of the promised good or service transfers to the customer.

A performance obligation is satisfied over time if one of three conditions is met: the customer simultaneously receives and consumes the benefits as the entity performs; the entity creates or enhances an asset controlled by the customer; or the performance creates no asset with an alternative use to the entity and the entity has an enforceable right to payment for work completed to date.

If none of the over-time criteria is met, revenue is recognised at a point in time. Indicators can include a present right to payment, legal title, physical possession, risks and rewards of ownership and customer acceptance. No single indicator automatically decides every case.

Worked example: a UGX 120 million equipment and support contract

Assume TechPro agrees to supply specialised equipment, standard installation and one year of post-installation support for UGX 120 million. For this teaching example, the promises are distinct and the transaction price is allocated as follows:

Performance obligation	Allocated amount	Recognition pattern
Equipment	UGX 90 million	When control of the equipment transfers
Installation	UGX 20 million	When the installation obligation is satisfied
Support	UGX 10 million	Over the support period if a time-based measure faithfully depicts performance

The customer pays UGX 60 million in advance on 1 January. That receipt is not yet revenue if no performance obligation has been satisfied; it creates a contract liability.

On 31 January the equipment is delivered and accepted, and an additional UGX 40 million becomes unconditionally billable. TechPro recognises UGX 90 million of equipment revenue. Billing and cash have now moved ahead of some remaining performance, so a contract liability remains.

Installation is completed on 15 February, when a final UGX 20 million becomes billable. TechPro recognises UGX 20 million of installation revenue. The remaining UGX 10 million relates to the one-year support obligation and is recognised as that service is provided.

The lesson: by 15 February the full UGX 120 million may have been billed or received, while only UGX 110 million has been earned. The remaining balance is not “missing revenue”; it represents an unsatisfied promise to the customer.

Contract assets, receivables and contract liabilities

Balance	Meaning	Typical trigger
Contract asset	A conditional right to consideration for goods or services already transferred	Performance occurs before the right to bill becomes unconditional
Receivable	An unconditional right to consideration	Only the passage of time is required before payment
Contract liability	An obligation to transfer goods or services for consideration received or due	Advance payment or billing precedes performance

Do not label every unbilled amount a receivable. The key question is whether the right to payment is unconditional. Contract assets and receivables also interact with IFRS 9 impairment requirements.

Contract modifications and common application areas

A contract modification changes enforceable rights or obligations by changing scope, price or both. The accounting depends on whether the added goods or services are distinct and whether they are priced at appropriate stand-alone selling prices.

A qualifying addition may be accounted for as a separate contract. Other modifications can require prospective treatment for remaining distinct goods or services, or a cumulative catch-up adjustment where the remaining work is part of a partially satisfied performance obligation.

Other areas that often require careful judgement include customer returns, warranties, principal-versus-agent arrangements, licences, and costs of obtaining or fulfilling contracts. The label used in a contract is not enough; the accounting follows the substance of the promise and the relevant IFRS requirements.

What finance teams should control

IFRS 15 depends on information that often sits outside the general ledger. Sustainable application therefore requires process and evidence controls, not merely a year-end journal.

• Contract intake: approved contract, enforceable rights, payment terms, customer assessment and scope conclusion.
• Performance obligations: documented promise inventory and distinctness analysis for significant contracts.
• Transaction price: controlled models for variable consideration, concessions, financing and non-cash consideration.
• Allocation: evidence for stand-alone selling prices and approval of estimation methods.
• Transfer and cut-off: delivery records, acceptance evidence, service logs, milestones and progress measures.
• Contract balances: monthly reconciliation of billing, cash, revenue, receivables, contract assets and contract liabilities.
• Modifications: formal change-order workflow with accounting reassessment before billing or system updates.
• Systems: controlled revenue schedules, interface checks, posting logic, audit trails and restricted manual overrides.
• Disclosure: tie-out to the ledger and documented significant judgements.

A contract register should connect each customer arrangement to its performance obligations, allocated price, transfer evidence, billing events, revenue schedule and closing balances. In an ERP environment, the billing engine should not automatically be assumed to be the revenue engine unless it has been deliberately configured and tested for the entity's IFRS 15 policy.

That control logic connects directly to FGL's practical guide to reconciling ERP sales, EFRIS, VAT and income-tax reporting and the wider Systems & Automation desk.

ICPAU examination technique

For a Financial Reporting question, a strong answer follows the standard rather than the order in which the facts appear in the scenario.

1. Confirm the arrangement is within IFRS 15 and that a qualifying contract exists.
2. List the promises and apply both parts of the distinctness test.
3. Determine fixed and variable consideration, apply the constraint and assess financing where relevant.
4. Allocate the transaction price using relative stand-alone selling prices.
5. Assess each obligation against the over-time criteria; otherwise determine the point of control transfer.
6. Calculate revenue for the reporting period and determine closing contract balances.
7. Prepare the accounting entries and explain the financial-statement effect.
8. Identify the fact that actually changes the conclusion—such as customer acceptance, alternative use, an enforceable right to payment, integration of promises or an uncertain bonus.

The ICPAU CPA syllabus includes IFRS 15 within Financial Reporting, so the five-step model should be understood as an applied reasoning framework rather than a memorised list.

Accounting revenue is not automatically VAT or tax turnover

One of the most useful professional lessons is that an accounting conclusion does not automatically determine the tax conclusion. IFRS 15 asks when control of promised goods or services has transferred and how much revenue should be recognised. VAT, EFRIS and income-tax records follow their own legal rules and evidence requirements.

The Ericsson AB v URA analysis illustrates why differences between VAT and income-tax sales figures must be investigated and reconciled rather than treated as automatic proof that one ledger is wrong. The Tax Appeals Tribunal decision is a tax-law authority; it does not replace IFRS 15 for financial reporting.

Finance teams should therefore reconcile the contract register, ERP billing, EFRIS documents, VAT return, revenue ledger and income-tax turnover schedule while keeping each conclusion grounded in the rules that govern that record.

Common IFRS 15 mistakes

• Recognising revenue on the invoice date without assessing transfer of control.
• Treating an advance receipt as revenue while promised goods or services remain outstanding.
• Assuming every contract line, fee or milestone is a separate performance obligation.
• Using billing milestones as a measure of progress without proving they faithfully depict performance.
• Ignoring the variable-consideration constraint or failing to update estimates at period end.
• Confusing a conditional contract asset with an unconditional receivable.
• Allocating consideration using stated contract prices without testing stand-alone selling prices.
• Failing to reassess modifications, options, renewals or changes in scope and price.
• Posting automated revenue schedules without preserving evidence of delivery, acceptance or service.

Practical contract-review checklist

• Confirm that the counterparty is a customer and document the contract criteria.
• Identify explicit and implied promises, including options, warranties and stand-ready services.
• Apply the distinctness test and document integration or interdependence judgements.
• Determine fixed and variable consideration and assess financing.
• Support stand-alone selling prices and allocation with observable evidence where available.
• Determine point-in-time or over-time recognition for each performance obligation.
• Select and control a measure of progress that faithfully depicts performance.
• Map billing, cash, revenue, receivables, contract assets and contract liabilities.
• Reconcile schedules to the general ledger each reporting period.
• Reassess modifications, estimates and significant judgements before close.

For related FGL resources, continue through the Accounting & IFRS knowledge desk or the Medisell v URA evidence analysis, which shows how unexplained accounting variances can become tax-audit issues even when the underlying accounting explanation may be legitimate.

Primary sources and further reading

• IFRS Foundation — IFRS 15 Revenue from Contracts with Customers
• IFRS Foundation — Revenue from Contracts with Customers project history
• ICPAU — CPA Examination Syllabus 2023
• Ericsson AB v Uganda Revenue Authority, Application No. 60 of 2020, [2026] UGTAT 24

FGL review: September 2026. This guide is educational and should be applied to the facts and enforceable terms of each contract. Financial-reporting conclusions should be checked against the applicable IFRS Accounting Standards and current professional guidance; tax and legal consequences require separate analysis under the relevant law.