Revenue is frequently the most scrutinised number in a UK-listed company’s financial statements, and IFRS 15’s contract-based model is designed to make revenue recognition more consistent and more comparable across industries by anchoring recognition to the transfer of control and by requiring explicit disclosures about judgements and uncertainty.

The most common technical pressure points (and audit hot spots) in UK practice continue to be: identifying distinct performance obligations in bundled arrangements; estimating and constraining variable consideration; over-time versus point-in-time conclusions (especially around enforceable rights to payment); principal versus agent (gross vs net); and the completeness and coherence of disclosures (including contract costs).

For UK-listed entities (and certain other issuers), consolidated accounts must be prepared using UK‑adopted IFRS, with endorsement overseen by the UK Endorsement Board and UK transparency requirements referenced through the Financial Conduct Authority rulebook.

Objective and core principle. IFRS 15’s objective is to require entities to report useful information about the nature, amount, timing and uncertainty of revenue and cash flows from contracts with customers, achieved by recognising revenue to depict transfers of promised goods/services for the consideration to which the entity expects to be entitled.

Scope. IFRS 15 applies to contracts with customers, with explicit scope exclusions for, among other things, lease contracts within IFRS 16 Leases, insurance contracts within IFRS 17 Insurance Contracts, and financial instruments within IFRS 9 Financial Instruments. It also specifies how to deal with contracts that are partly within IFRS 15 and partly within other IFRS Accounting Standards, and it permits a portfolio practical expedient when the outcome is not expected to differ materially from contracting-by-contracting assessment.

UK reporting reality. The UK regulator, the Financial Reporting Council, has repeatedly highlighted that IFRS 15 disclosures often fail to reach its quality expectations - particularly where policy wording is generic, where explanations of timing and variable consideration are thin, and where movements in contract assets and contract liabilities are not clearly explained.

IFRS 15 is commonly operationalised through a five-step process for recognising revenue from contracts with customers.

The steps themselves are prescribed; the examples below are illustrative of common UK fact patterns (retail/consumer, B2B services, construction, software/tech, and platform/intermediary business models).

Identifying the contract. IFRS 15 focuses on enforceable rights and obligations. In stressed credit or high cancellation-risk environments, the existence of a “contract” for IFRS 15 recognition can become a live issue; where collectability is not probable at inception, normal IFRS 15 recognition may not apply and revenue may, in effect, be recognised only when cash is collected and there are no remaining obligations. UK firms have warned that this issue becomes more prominent in difficult trading conditions.

Identifying performance obligations and “distinct” promises. A promised good/service is distinct if (i) the customer can benefit from it on its own or with readily available resources (capable of being distinct) and (ii) the promise is separately identifiable in the context of the contract. IFRS 15 requires careful analysis of integration/customisation/interdependence, which is where many bundled UK contracts rise or fall.

Practical UK examples:

Determining the transaction price. Transaction price excludes amounts collected on behalf of third parties (which, in UK practice, is the conceptual basis for recognising revenue net of VAT and similar taxes).

Key measurement components:

Allocating the transaction price. The default allocation approach is relative standalone selling prices (SSP) determined at contract inception. Where SSP is not directly observable, IFRS 15 permits estimation using market assessment, expected cost plus margin, or a residual approach (subject to conditions), and provides specific criteria for allocating discounts and (in some cases) variable consideration to particular performance obligations.

Recognising revenue. IFRS 15 requires revenue recognition when (or as) a performance obligation is satisfied by transferring control of a promised asset to the customer. Obligations are satisfied over time if one of three criteria is met (simultaneous receipt/consumption; creation/enhancement of an asset controlled by the customer; or no alternative use plus enforceable right to payment). Otherwise, satisfaction is at a point in time, assessed using control indicators such as present right to payment, legal title, physical possession, significant risks/rewards, and customer acceptance (among others).

The entries below are illustrative; account names and VAT mechanics will vary by entity and ERP design. The underlying recognition logic is driven by IFRS 15’s presentation model (contract assets/contract liabilities/receivables) and its variable consideration/refund liability mechanics.

Goods: sale with expected returns (refund liability)

Assume: invoiced selling price (excluding VAT) £100; expected returns 5%; cost £60.

At sale (control transfers; recognise revenue net of expected returns):

Cost recognition (reflecting expected returns):

The right-to-return asset concept aligns to IFRS 15’s right-of-return guidance and refund liability mechanics.

Services: annual support contract billed in advance (contract liability pattern)

Assume: one-year support, £12,000 billed upfront; straight-line satisfaction.

On invoice/cash receipt:

Monthly revenue recognition:

(Contract liability presentation is required when payment precedes performance.)

Construction: over-time revenue using an input method (cost-to-complete)

Assume: fixed price £10.0m; total expected costs £8.0m; costs incurred to date £2.0m; billings to date £2.0m.

Recognise revenue and margin (progress = 2/8 = 25%; revenue = 25% × £10.0m = £2.5m):

Record costs:

Software bundle: term licence (point in time) + support (over time)
Assume total consideration £12,000; SSP licence £10,000; SSP support £4,000. Allocation: licence £8,571; support £3,429.

At billing:

On licence delivery/availability (right-to-use licence; point in time):

Monthly support recognition:

(Licence recognition depends on whether the customer receives a right-to-use at a point in time or a right-to-access over time; IFRS 15 includes application guidance on this distinction.)

Contract modifications. IFRS 15 defines a contract modification as a change in scope or price (or both) approved by the parties (including approvals by customary business practices). If the parties approve scope changes before the price is finalised, the entity estimates the price change using the variable consideration guidance and constraint.

The accounting outcome commonly follows one of three patterns:

A UK construction “variation order” is a classic example: a change order adding new distinct deliverables at a commensurate price often behaves like a separate contract; a change that revises the scope of a single integrated build commonly results in cumulative catch-up (and therefore volatile period-on-period revenue).

Warranties. IFRS 15 distinguishes warranties that only provide assurance that the product complies with specifications from warranties that provide an additional service. In the latter case, the service component is a performance obligation (or combined performance obligation if you cannot reasonably separate assurance and service elements).

Principal versus agent (gross vs net). Where another party is involved, IFRS 15 requires an entity to determine whether it is promising to provide goods/services itself (principal) or arrange for another party to provide them (agent). A principal recognises revenue gross; an agent recognises revenue as its fee or commission. Indicators include primary responsibility, inventory risk, and pricing discretion, but they support (not override) the core control assessment.

A UK-relevant software distribution pattern has been specifically discussed by the IFRS Interpretations Committee: the agenda decision emphasises that the conclusion is fact-specific and requires judgement, including careful identification of the specified good/service and assessment of whether the reseller controls the licence before transfer; disclosures of performance obligations and significant judgements are explicitly expected.

Practical implication for UK firms: principal/agent is not just a P&L gross/net presentation choice - it is a control conclusion tested at the level of each specified good/service. It is also an area where the UK regulator expects clear, specific policy explanations and, where material, transparent discussion of the judgement.

Variable consideration and the constraint. Variable consideration includes discounts, rebates, refunds, credits, price concessions, incentives, bonuses and penalties. Entities must estimate variable amounts using an expected value or most likely amount approach and must update estimates each reporting period. The constraint requires inclusion only to the extent that it is highly probable a significant reversal will not occur.

UK practical examples where the constraint is decisive:

The FRC has repeatedly raised concerns where variable consideration disclosures do not specify the type of variable consideration, the estimation method, or how the constraint is applied in practice - especially where management sensitivity disclosures imply “equal upside and downside”, which is conceptually inconsistent with the constraint’s asymmetry.

Significant financing components. IF you provide or receive financing that is significant, you adjust the transaction price to reflect the cash selling price and recognise financing effects separately from revenue (interest income/expense). The one-year practical expedient is widely used in UK consumer arrangements but needs careful assessment in multi-year B2B and construction settings.

Non-cash consideration and consideration payable to customers. Non-cash consideration is measured at fair value (or indirectly via SSP if fair value can’t be reasonably estimated). Consideration payable to a customer generally reduces the transaction price unless it is for a distinct good/service received from the customer (and any excess reduces the price). This area is particularly relevant for UK retail supplier funding arrangements, marketing support, and platform incentives.

Allocation mechanics. Allocation is based on relative SSPs. Where SSPs are not observable, IFRS 15 provides estimation techniques including market assessment, expected cost-plus-margin, and the residual approach (subject to constraints). Discounts can be allocated to specific performance obligations only with observable evidence meeting IFRS 15’s criteria, and variable consideration can sometimes be allocated to specific performance obligations if strict conditions are met.

IFRS 15 includes explicit guidance for (i) incremental costs of obtaining a contract and (ii) costs to fulfil a contract - when those costs are not within the scope of other standards such as IAS 2 Inventories, IAS 16 Property, Plant and Equipment, or IAS 38 Intangible Assets.

Incremental costs of obtaining a contract. These are costs that would not have been incurred if the contract had not been obtained (e.g., certain sales commissions). IFRS 15 includes a practical expedient allowing immediate expensing when the amortisation period would be one year or less, but that expedient must be disclosed if used.

Costs to fulfil a contract. These are capitalised only if they relate directly to a contract, generate or enhance resources used to satisfy future performance obligations, are expected to be recovered, and are not otherwise within the scope of another IFRS Accounting Standard.

UK regulatory focus. The FRC has specifically warned that some companies appear to overlook IFRS 15’s contract cost requirements; it expects clear policies and (where material) quantitative disclosures.

Global firm guidance also cautions that IFRS 15’s disclosure section is not intended to be used as a checklist (materiality and entity-specific tailoring remain essential).

Sample journal entry: capitalised sales commission

Assume: £60,000 commission to obtain a 3-year contract; amortised on a straight-line basis.

On contract acquisition:

Monthly amortisation:

Presentation. IFRS 15 requires a contract to be presented as a contract asset or contract liability depending on the relationship between performance and payment; unconditional rights to consideration are presented separately as receivables. This distinction is foundational for UK balance sheets where accrued income and deferred income have historically been used, and it affects working capital narratives and covenant metrics.

Disclosure requirements. IFRS 15’s disclosure objective is explicitly to enable users to understand the nature, amount, timing and uncertainty of revenue and cash flows, requiring qualitative and quantitative information about:

In practice this means:

Where the entity applies IFRS 8 Operating Segments, IFRS 15 also requires information enabling users to understand the relationship between disaggregated revenue disclosures and segment disclosures.

This checklist is designed to be used for (i) new implementations, (ii) post-implementation health checks, or (iii) a year-end disclosure refresh. It is intentionally practical and control-oriented, reflecting the regulator’s emphasis on clarity, specificity, and linkage across the report.