Five Step IFRS 15 Revenue Recognition Checklist for Accounting Teams
IFRS 15 requires revenue to be recognised when control of a promised good or service passes to the customer, not when an invoice goes out. Every contract runs through the same five-step model: identify the contract, identify the performance obligations, work out the transaction price, allocate that price, then recognise revenue as each obligation is satisfied. Whether that happens over time or at a single point depends entirely on who holds control, and when.
TL;DR:
Revenue recognition depends on control passing to the customer, not on invoicing or billing milestones.
Most errors come from misidentifying performance obligations or incorrectly applying the distinctness and recognition criteria.
Proper allocation of transaction price requires estimating stand-alone selling prices, not just using invoice splits.
Contract modifications are treated based on whether they are distinct obligations, blending remaining work, or applying prospectively.
Disclosures should clearly explain judgment calls on SSP, variable consideration, and contract changes to ensure audit readiness.
Table of Contents
What Are the Five Steps of IFRS 15 Revenue Recognition?
Each step answers a specific question, and skipping one is where most errors creep in.
Identify the contract. You need enforceable rights and obligations, commercial substance, and a reasonable expectation of collecting payment. A verbal agreement or a purchase order can qualify just as much as a signed document, provided both parties are committed.
Identify the performance obligations. Break the contract into distinct promises. A software licence bundled with implementation support and ongoing updates is rarely one obligation. Watch for “series” guidance too. A subscription delivered in substantially the same way each month is usually treated as a single obligation recognised over time.
Determine the transaction price. This covers fixed fees, variable amounts, non-cash consideration, and any financing baked into payment terms.
Allocate the transaction price. Split it across obligations based on relative stand-alone selling price, using estimation where a price isn’t directly observable.
Recognise revenue. Book it when, or as, each obligation is satisfied, based on control transfer.
The ACCA’s summary of the five steps is a useful practical companion here, particularly for teams applying the model for the first time to a portfolio of varied contracts.
Do You Recognise Revenue Over Time or at a Point?
This is the judgement that trips up more finance teams than any other part of the standard. Revenue is recognised over time if one of three criteria is met: the customer simultaneously receives and consumes benefits as you perform, your work creates or enhances an asset the customer controls as it’s built, or the asset has no alternative use to you and you have an enforceable right to payment for work completed to date.
If none of those apply, revenue is recognised at a single point, and you look for control indicators instead: has legal title passed, has physical possession transferred, has the customer accepted the asset, and do they now bear the risks and rewards of ownership?
A SaaS subscription typically qualifies for over-time recognition. The customer consumes access continuously across the contract term.
A construction contract building a bespoke asset on the customer’s land usually meets the “no alternative use plus enforceable payment right” test.
A one-off software licence sold outright, where control passes on delivery, is normally point-in-time.
Where recognition is over time, you also need a method to measure progress. Input methods (costs incurred, labour hours) work well for construction. Output methods (units delivered, milestones achieved) tend to suit fixed-fee service contracts better.
Pro Tip: Document why you chose an input or output method at the start of the contract, not at year-end. Auditors will ask, and “it seemed reasonable” isn’t a defensible answer six months later.
How Do You Handle Variable Consideration Under IFRS 15?
Transaction price is the amount you expect to be entitled to, excluding anything collected on behalf of third parties such as sales taxes. Where the price is variable, you estimate it using one of two methods.
Expected value: appropriate when you have a range of possible outcomes, such as a portfolio of similar contracts with rebate tiers.
Most likely amount: better suited to a binary outcome, such as a single performance bonus that either applies or doesn’t.
Then comes the constraint. You only include variable amounts to the extent it’s highly probable there won’t be a significant reversal once the uncertainty resolves. The ACCA notes that this constraint gets particular scrutiny from auditors on long-term contracts, and estimates need refreshing every reporting period rather than set once and forgotten.
You also need to check for a significant financing component. Payment terms stretching well beyond delivery, or heavily front-loaded deposits, can mean part of the consideration is really interest in disguise, requiring separate treatment.
How Do You Allocate the Transaction Price Correctly?
Allocation runs on relative stand-alone selling price (SSP), and this is where a lot of finance teams get caught out. A contractually stated price split across line items is not automatically the SSP split IFRS 15 requires. Paragraph 77 of the standard is explicit that an invoice showing separate prices for hardware and support doesn’t necessarily reflect what each would sell for on its own, so reallocation is often required even when the numbers look tidy already.
Where SSP isn’t directly observable, three estimation techniques are permitted: adjusted market assessment (what would a similar customer pay in that market), expected cost plus a margin, or the residual approach for a single item with highly variable pricing. Discounts and variable consideration should generally be allocated proportionally across all obligations, unless there’s clear evidence the discount relates to only one part of the bundle.
Pro Tip: Keep a standing SSP schedule per product or service line, updated annually. Rebuilding the allocation logic from scratch for every new contract wastes hours and invites inconsistency.
Contract Changes, Add-Ons, and Who’s Really the Seller
Modifications get one of three treatments: a separate contract (new distinct goods at their SSP), a cumulative catch-up (blending remaining obligations into the existing contract), or prospective treatment (accounting for the change going forward only). Which applies depends on whether the added goods or services are distinct and priced at their stand-alone value.
Separate contract: new obligation, priced at SSP, no impact on existing revenue already recognised.
Cumulative catch-up: remaining obligations aren’t distinct from what’s already delivered, so you reallocate and true up.
Prospective: remaining goods are distinct but not priced at SSP, so you blend the remaining consideration across what’s left.
Principal versus agent hinges on who controls the good or service before it reaches the customer. Look at who bears primary responsibility for fulfilment, who carries inventory risk, and who has pricing discretion. A SaaS platform reselling a third-party add-on module, where the platform sets the price and owns the customer relationship, usually reports as principal and recognises the gross amount. If the platform merely arranges the sale and the third party fulfils it, net presentation as agent is more likely correct.
What Must You Disclose Under IFRS 15?
Disclosure is not an afterthought bolted on at year end. It’s the mechanism through which the standard makes judgement visible to readers of the accounts.
Disaggregate revenue into categories that reflect how economic factors affect it, such as geography, contract type, or timing of transfer.
Provide roll-forwards of contract assets and contract liabilities, showing opening and closing balances.
Disclose the transaction price allocated to remaining performance obligations and when you expect to recognise it.
Explain significant judgements, including methods used to determine SSP and measure progress on over-time contracts.
Disclose any assets recognised from the costs to obtain or fulfil a contract, and how they’re amortised.
Where Do Companies Go Wrong With IFRS 15?
The most common mistake is bundling. Treating a software licence, onboarding, and a year of support as one obligation because they’re sold together, when they’re clearly separable, distorts the timing of everything downstream. A close second is leaving variable consideration unconstrained, recognising the full bonus or rebate amount before it’s highly probable it will actually be earned. A third is the old habit carried over from IAS 18: assuming the invoice date equals the recognition date. It doesn’t, and auditors know it doesn’t.
A short practical checklist helps before audit fieldwork starts:
Build a contract inventory covering every revenue stream, not just the largest customers.
Document the judgement behind every SSP estimate and every over-time versus point-in-time call.
Keep evidence supporting SSP estimates, not just the final number used.
Re-test variable consideration constraints each period, with a paper trail showing why estimates changed or didn’t.
Prepare disclosure templates in advance rather than drafting them from a blank page at year-end.
Pro Tip: For a SaaS multi-year contract with an upfront implementation fee, check whether that fee actually transfers a distinct benefit. Most of the time it doesn’t, and it should be spread over the subscription term rather than recognised on day one. KeystoneFA’s guide to SaaS revenue recognition covers this scenario in more depth, including the interaction with the incoming FRS 102 changes.
How Do You Account for Non-Cash Consideration?
IFRS 15 doesn’t restrict transaction price to cash. If a customer pays you in shares, goods, services, or advertising space, you measure that non-cash consideration at fair value, and it goes into the transaction price the same way a cash payment would.
The complication is that fair value isn’t always obvious. A start-up paying a supplier partly in equity has to estimate what that equity is worth at contract inception, which usually means using an independent valuation or a recent funding round as a reference point. If fair value genuinely cannot be estimated reliably, the fallback is to measure indirectly, using the stand-alone selling price of the goods or services promised in exchange. That’s a narrow exception, not a default option, so document why a direct fair value estimate wasn’t feasible before reaching for it.
A specific wrinkle applies where the customer contributes goods or services to help you fulfil the contract, such as materials supplied by a construction client. If you obtain control of those contributed items, you treat them as non-cash consideration and include them in the transaction price. Advertising barter arrangements sit in the same category. A media owner running a client’s advert in exchange for the client’s products needs to value the products received, not simply record zero revenue because no cash changed hands.
Volatility is the practical headache. Consideration paid in something like a quoted security or a cryptoasset can move in value between contract inception and the measurement date, and IFRS 15 requires updating the estimate only for reasons unrelated to the form of consideration itself, such as changes in the underlying performance obligation, not for market price movements. Separating those two causes in your workings is essential, because conflating them leads to restating revenue for reasons the standard never intended.
What Counts as a Valid Contract Under IFRS 15?
A contract exists, for revenue recognition purposes, only when five conditions are all met together: the parties have approved the arrangement and are committed to their obligations, each party’s rights regarding the goods or services can be identified, payment terms can be identified, the contract has commercial substance, and collection of consideration is probable.
Enforceability is the concept that trips people up, because it’s a legal question dressed as an accounting one. IFRS 15 doesn’t require a signed, formal document. A framework agreement, a series of purchase orders, or even an established pattern of trading can create enforceable rights and obligations depending on the jurisdiction and the parties’ conduct. What matters is whether either party could be compelled, through legal or equivalent means, to perform. If a customer can walk away with no penalty and no history of the arrangement being enforced, you may not have a contract yet, regardless of what a document says.
Collectability deserves more attention than it usually gets. The standard asks whether it’s probable you’ll collect the consideration you’re entitled to, which is not the same as the full contract price if you’d reasonably offer a price concession to a struggling customer. This assessment happens at inception and should be reassessed if facts change materially, such as a customer’s credit position deteriorating significantly before performance is complete. Where a contract fails the criteria entirely, for example collection is not considered probable, revenue recognition is deferred, and any consideration received is typically recorded as a liability until either the contract criteria are subsequently met or the specific circumstances allowing recognition in IFRS 15’s contract-failure guidance apply.
For businesses working across multiple contracts with the same customer, remember that combination rules apply when contracts are entered into at or near the same time with the same customer and are negotiated as a package, or where the consideration in one depends on the other, or where the goods and services across contracts form a single performance obligation.
When Does IFRS 15 Apply, and How Do You Transition?
IFRS 15 has been mandatorily effective for annual reporting periods beginning on or after 1 January 2018 for entities reporting under full IFRS. Any UK business adopting IFRS for the first time now, whether following a group restructuring, a listing, or a decision to move away from UK GAAP, applies it from the outset rather than treating it as a future change.
Two transition methods were available when the standard first took effect, and the choice still matters conceptually for anyone studying prior transition disclosures or explaining historic restatements to stakeholders.
The full retrospective method restates all prior periods presented in the financial statements as though IFRS 15 had always applied, using the practical expedients the standard permits, such as not restating contracts completed before the earliest period presented. This gives the cleanest year-on-year comparability but demands substantially more restatement work.
The cumulative effect method (sometimes called the modified retrospective approach) applies IFRS 15 only from the date of initial application, recognising the cumulative effect of adopting it as an adjustment to opening retained earnings, with no restatement of comparative periods. Entities using this route must disclose, for each affected line item, what the figures would have been under the previous standard, giving readers a like-for-like reference point without a full restatement.
For a business adopting IFRS today for the first time, first-time adoption under IFRS 1 interacts with IFRS 15 rather than the original transition provisions, but the underlying judgement work is identical: build a contract inventory, assess each performance obligation, and be ready to explain every material change in revenue timing compared with your previous framework.
Where Do Businesses Underinvest in IFRS 15 Compliance?
Judgements around SSP and variable consideration get made once at go-live and rarely revisited. That’s the gap I’d fix first. Small finance teams don’t need more process, they need a lighter recurring review built into month-end, not a one-off project.
— Shoaib
Getting IFRS 15 Right With Support From KeystoneFA
This advisory service offers technical depth applied by experienced professionals, scaled to suit growing businesses rather than multinational firms.
[
](www.keystonefa.co.uk)
Getting the five-step model right on paper is one thing. Defending your SSP estimates, your variable consideration constraint, and your control judgements to an auditor is another. The service includes contract review, revenue policy drafting, disclosure notes, and audit readiness checks to help document judgements behind financial numbers before audit queries. If your business is bundling SaaS subscriptions, multi-year service contracts, or bundled goods and installation, that documentation gap is usually where problems surface first. Pricing for KeystoneFA’s core packages runs from £99 to £199 per month, scaled to what your business actually needs. Book a review through the KeystoneFA site to get your contracts and disclosures checked before your next audit cycle.
Sources
Start with the IFRS 15 standard itself, then the ICAEW’s tracker and a practitioner deep dive for edge cases like SaaS licensing.
FAQ
What Are the Five Criteria for Revenue Recognition?
IFRS 15 doesn’t set five separate recognition criteria; it sets a five-step model: identify the contract, identify performance obligations, determine the transaction price, allocate it, and recognise revenue as obligations are satisfied. Within step one, a contract must also meet five separate conditions covering approval, identifiable rights, payment terms, commercial substance, and probable collection.
How Is Revenue Recognised Under IFRS 15?
Revenue is recognised when control of a promised good or service transfers to the customer, either over time or at a single point, based on control indicators set out in the standard. It is never recognised simply because an invoice has been issued or a milestone billed.
What Are the Five Steps of Revenue Recognition According to IFRS 15?
The steps are: identify the contract, identify the distinct performance obligations, determine the transaction price, allocate that price across the obligations, and recognise revenue when or as each obligation is satisfied. ACCA’s step-by-step guidance applies these to worked examples.
At What Point Is Revenue Recognised?
Revenue is recognised at the point (or points, if over time) at which the customer obtains control of the good or service. For a point-in-time sale, that usually means legal title, physical possession, and risk have all passed. For an over-time contract like a SaaS subscription, revenue is spread across the period the service is delivered, not booked when the invoice is raised.
Does KeystoneFA Help With IFRS 15 Implementation?
Yes. KeystoneFA supports growing UK businesses with revenue policy drafting, contract review, and disclosure preparation as part of its wider accounting and advisory services, with current pricing listed on the KeystoneFA website.
Recommended