SaaS Revenue Recognition in Plain English (IFRS 15 / ASC 606)

Why revenue recognition matters in SaaS

In SaaS, the cash often arrives a year before the revenue does. Revenue recognition is the set of rules that decides when billed money becomes revenue in the P&L. Get it wrong and revenue, margins and growth rates are all wrong too, usually in a way the auditors find first.

The good news: the rules follow one logical model. Once you can run a contract through five steps, most SaaS revenue questions answer themselves.

Which standard applies?

Under IFRS, the standard is IFRS 15 Revenue from Contracts with Customers. Under UK GAAP, FRS 102 Section 23 covers revenue. Following the FRS 102 periodic review, a revised Section 23 based on the same five-step model applies for accounting periods beginning on or after 1 January 2026 (as at October 2026), with early adoption permitted. So a company with a calendar year end is applying it now; a company with a year starting 1 April applies it from its April 2026 year onwards.

The revised FRS 102 section includes some simplifications compared with IFRS 15. The steps below describe the shared logic.

Key terms

• Contract: an agreement with a customer that creates rights and obligations both sides can enforce. An order form plus terms and conditions usually counts.
• Performance obligation: a promise to give the customer a distinct good or service. "Distinct" means the customer can benefit from it on its own (or with things they can easily get), and it's separate from the other promises in the contract.
• Transaction price: the amount you expect to be entitled to for the contract, excluding VAT.
• Standalone selling price (SSP): what you'd charge for one item if you sold it on its own.
• Over time vs point in time: revenue is recognised as the service is delivered (over time), or when control passes in one go (point in time).
• Deferred revenue (contract liability): money billed or received before the service is delivered.
• Accrued income (contract asset): revenue earned but not yet billed.

The five steps in plain English

One rule for all of it: AI drafts, matches and flags; a person reviews and signs off. Only use AI tools your company has approved for customer and financial data.

Applying the steps, one at a time

Step 1: the contract

Most SaaS contracts are easy here. The traps are side letters, emails promising extras, and contracts where the customer can cancel at any time without penalty. If either side can walk away freely, the enforceable contract may only be the current month or the notice period. That changes how much revenue and deferred revenue you can record.

Step 2: the promises

The core promise is access to the platform for a period, which is normally one performance obligation delivered over time. The harder question is whether things like implementation, data migration or training are separate. A common test: could the customer get that service from someone else, and does the software work without it? If yes to both, it's usually distinct. If the setup work heavily customises the product so it only works because of it, it may be combined with the subscription.

Two other promises that often hide in SaaS contracts: options to renew at a big discount (which may be a "material right", a separate promise in its own right) and free months.

Step 3: the price

Start with the fixed fee. Take off discounts and credits. Add variable amounts such as usage or overage charges only to the extent it's highly probable there won't be a big reversal later. Exclude VAT; it's collected for HMRC, not earned. Most SaaS contracts have no significant financing element, but very long upfront payment terms (more than a year) may need a closer look.

Step 4: the allocation

If there's more than one promise, split the price based on standalone selling prices. Most teams keep an SSP table, reviewed at least once a year, based on what they actually charge when items are sold alone. Discounts are usually spread across all promises in proportion, unless there's clear evidence a discount relates to one item.

Step 5: recognition

Subscription access is typically recognised evenly, day by day or month by month, because the customer gets the benefit continuously. Services are recognised as they're performed (for example by hours worked against total hours) or at completion if the customer only benefits at the end. Usage is usually recognised in the month the usage happens.

AI shortcut: paste an anonymised order form into an approved AI tool and ask it to list (1) every promise to the customer, (2) every price, discount and free period, (3) start and end dates, and (4) any cancellation or renewal terms. You then judge which promises are distinct. It turns a 20-minute read into a 5-minute check.

Worked example: subscription plus implementation

MonthEndClub Co Ltd, a fictional UK SaaS company, signs a contract with a customer on 1 October:

• 12 months of platform access, plus a one-off implementation service.
• Total contract price: £30,000, invoiced upfront on 1 October, plus VAT at 20% (the UK standard rate as at October 2026).
• Standalone selling prices: platform £2,400 a month (£28,800 a year); implementation £3,200.
• Implementation is distinct (another firm could do it, and the software works without it). It's completed in October.

Steps 1 to 3. There's a signed contract, two promises (platform and implementation) and a transaction price of £30,000.

Step 4: allocate the price. Total SSP is £28,800 + £3,200 = £32,000. The customer got a £2,000 discount overall, which is spread across both items.

Step 5: recognise. Platform revenue is £27,000 ÷ 12 = £2,250 a month. Implementation revenue of £3,000 is recognised in October, when the work is done.

Journal 1, 1 October: raise the invoice. Nothing has been delivered yet, so the whole net amount goes to deferred revenue.

For VAT, the tax point for a continuous supply of services like this is typically the earlier of the invoice date and the payment date, so the £6,000 goes on the return covering 1 October, even though most of the revenue comes later.

Journal 2, 31 October: release October's revenue.

November to September: each month, Dr deferred revenue £2,250, Cr subscription revenue £2,250.

Notice what the allocation did. If the team had booked implementation at its full list price of £3,200 and put the balance of £26,800 against the platform, implementation revenue in October would be overstated by £200 and the whole discount would land on the subscription. When invoice lines don't match the SSP split, the allocation drives revenue, not the invoice.

Common SaaS situations, quickly

If you report under US GAAP (ASC 606)

ASC 606 uses the same five steps, and most SaaS answers are the same. A few differences come up in practice:

• Collectability: the "probable" threshold for a valid contract is set higher under US GAAP than under IFRS, so doubtful customers fail Step 1 more often.
• Licence renewals: under ASC 606, revenue for a renewed term-based licence typically can't start before the renewal period begins. This matters more for on-premise licences than pure SaaS.
• Immaterial promises: ASC 606 allows an election to ignore promises that are immaterial in the context of the contract.
• Sales taxes: US GAAP allows a policy election to exclude all sales taxes from the transaction price. Under IFRS and FRS 102, VAT is simply excluded because it's collected on HMRC's behalf.

Common mistakes and audit watch-outs

• Following the invoice, not the contract. Invoice lines and timing don't decide revenue. The promises and their delivery do.
• Recognising setup fees upfront by default. Only distinct services are recognised as delivered. Setup that just gets the customer onto the platform is often spread over the subscription.
• No SSP evidence. If you allocate a price, keep the SSP table and how it was set. Auditors will ask.
• Missing side letters. Extra promises made by email still count. Ask sales every month.
• Ignoring free months. Three months free on a 15-month deal means revenue is spread over 15 months, not 12.
• Treating AI summaries as the contract. An AI summary can miss a clause or invent one. Judgements are made against the signed document, and the reviewer records which clause supports each conclusion.

Tools that can help

Billing tools such as Chargebee and Stripe Billing produce revenue schedules from subscription data, and larger teams often use NetSuite's revenue features. Smaller teams on Xero or QuickBooks commonly run the schedule in Excel or Google Sheets and post a monthly journal. An approved AI assistant helps with contract reading and first drafts. None of these replace the five-step judgement; they make the mechanics faster.

Key takeaways

• Revenue follows delivery, not billing or cash.
• Run every non-standard contract through the five steps: contract, promises, price, allocation, timing.
• Subscriptions are usually recognised evenly; distinct services as they're delivered.
• Keep an SSP table and evidence for how it was set.
• Revised FRS 102 Section 23 brings UK GAAP onto a five-step model for periods beginning on or after 1 January 2026.
• AI is good at reading contracts and building schedules; the judgement and sign-off stay with people.

FAQs

Is deferred revenue a liability?

Yes. It's money billed or received for service not yet delivered, so the company owes the customer that service. It sits on the balance sheet until it's released to revenue.

Why doesn't revenue match what we billed this month?

Because billing follows the payment terms and revenue follows delivery. An annual invoice raised in October shows a big billing number but only one month of revenue.

Does the new FRS 102 revenue section apply to us yet?

It applies to accounting periods beginning on or after 1 January 2026 (as at October 2026), unless a company chose to adopt early. Your year-end date decides when it starts. Your auditor or adviser can confirm transition choices.

Can AI do our revenue recognition?

It can do much of the reading and arithmetic: summarising contracts, allocating prices and drafting schedules. Deciding whether a service is distinct, setting SSPs and signing off the numbers are judgements that stay with people, and every AI output is checked against the contract.

Related guides

• How to Build and Reconcile a Deferred Revenue Schedule
• Annual Upfront Billing: The Journals, Month by Month
• Setup Fees and Implementation Services: Recognise Now or Later?
• ARR vs MRR vs Revenue: Why They Don't Match and How to Reconcile Them

More in Revenue guides.

From the Club

Recognised evenly over the term of your employment. The Team Mug · The Dad Hat

Join the Club. New guides, early access and members-only batches. Join here.

This guide is general information about common practice. It isn't tailored to any business, and standards, tax rules and figures change. Check your own circumstances, the latest rules and, where needed, a qualified professional before acting.

Last reviewed: October 2026.