What revenue recognition means for a SaaS business
Revenue recognition is the principle that income is recorded in the period in which the service is delivered, not when cash changes hands. For a SaaS business selling subscriptions, this means spreading the fee across the subscription term and holding any not-yet-earned portion as deferred revenue on the balance sheet. Cash receipt and revenue earned are two separate events.
This distinction matters practically: a company that invoices for annual contracts and books the full cash receipt as immediate revenue overstates its income, understates its liabilities, and may mislead investors and lenders on its true trading position. It also produces a balance sheet that does not comply with UK accounting standards.
Cash received versus revenue earned: the core distinction
When a customer pays £12,000 upfront for a 12-month subscription, your bank account receives £12,000. Your income statement does not. You have taken on an obligation to deliver 12 months of service. Each month that passes, one-twelfth of that obligation is met and one-twelfth of the fee becomes revenue. The rest remains a liability.
This separation applies regardless of your billing model:
- Monthly billing: revenue and cash receipt are broadly aligned because the service period and the billing cycle match.
- Annual upfront billing: a significant timing gap opens between cash receipt and revenue recognition, creating a deferred revenue balance.
- Multi-year contracts: the deferred revenue balance can span multiple accounting periods and must be split between current and non-current liabilities on the balance sheet.
The practical test is straightforward: at any balance-sheet date, ask how much of the service contracted has been delivered. Only that portion is revenue.
Deferred revenue on the balance sheet
Deferred revenue (sometimes called deferred income or contract liabilities) is a current or non-current liability representing cash received for services not yet delivered. It is not a debt to a lender. It is an obligation to your customer. As each month of the subscription passes, the balance unwinds and the recognised amount moves to the income statement as revenue.
A common early-stage misunderstanding is to treat deferred revenue as if it were free cash. It is not. If a customer cancels and your contract entitles them to a pro-rata refund, the deferred balance is the upper bound of what you owe back. Even where no refund applies, holding the deferred balance correctly is a legal and accounting requirement, not optional tidiness.
| View | At contract start (annual plan) | After month 1 | After month 12 |
|---|---|---|---|
| Cash position | +£12,000 received | No change | No change |
| Revenue recognised (P&L) | £0 | £1,000 | £12,000 |
| Deferred revenue (balance sheet liability) | £12,000 | £11,000 | £0 |
Illustrative example only, based on a £12,000 annual plan recognised equally over 12 months.
Recognising an annual subscription: worked example
Below is a month-by-month illustration for a single £12,000 annual plan paid upfront on 1 January. Revenue of £1,000 is recognised each month as the service is delivered. The deferred revenue balance reduces by the same amount. By 31 December the balance is zero and all £12,000 has been recognised as revenue.
| Month | Revenue recognised (£) | Cumulative revenue (£) | Deferred revenue balance (£) |
|---|---|---|---|
| 1 (January) | 1,000 | 1,000 | 11,000 |
| 2 (February) | 1,000 | 2,000 | 10,000 |
| 3 (March) | 1,000 | 3,000 | 9,000 |
| 4 (April) | 1,000 | 4,000 | 8,000 |
| 5 (May) | 1,000 | 5,000 | 7,000 |
| 6 (June) | 1,000 | 6,000 | 6,000 |
| 7 (July) | 1,000 | 7,000 | 5,000 |
| 8 (August) | 1,000 | 8,000 | 4,000 |
| 9 (September) | 1,000 | 9,000 | 3,000 |
| 10 (October) | 1,000 | 10,000 | 2,000 |
| 11 (November) | 1,000 | 11,000 | 1,000 |
| 12 (December) | 1,000 | 12,000 | 0 |
Illustrative only. A £12,000 annual subscription paid upfront on 1 January, recognised straight-line over 12 months at £1,000 per month.
The accounting entry at the point of cash receipt is: debit bank £12,000, credit deferred revenue £12,000. Each month: debit deferred revenue £1,000, credit revenue £1,000. The cumulative effect is that revenue in your profit-and-loss account matches the service you have actually delivered.
Calculator
SaaS Deferred Revenue Schedule
Put in the subscription, when it starts, how it's billed and your financial year end. The tool spreads the value evenly over the term, as UK GAAP (FRS 102 Section 23) and IFRS 15 do for a plain subscription, and shows what sits in revenue and what sits on the balance sheet at each year end. General guidance only; bundled contracts with set-up fees need a closer look.
The total the customer pays for the term. Leave VAT out: it isn't your revenue.
How many months of service the customer is buying (up to 120).
The first month the customer has access.
The month your company's accounts are made up to.
Deferred revenue is what's been billed or paid for service not yet delivered, so billing in advance is what creates it.
Your result
Your answer's ready. Press below to see it.
The UK standard: IFRS 15 and FRS 102
Two accounting standards govern revenue recognition for UK companies. Which one applies to your company depends on the reporting framework you have adopted, which in turn depends on your size and, often, investor requirements.
IFRS 15 Revenue from Contracts with Customers applies to companies that prepare accounts under International Financial Reporting Standards. This is common for UK companies that have taken VC or institutional funding and whose investors or lenders require IFRS-basis accounts. IFRS 15 sets out a five-step model:
- Identify the contract with the customer.
- Identify the performance obligations in the contract (the distinct services promised).
- Determine the transaction price.
- Allocate the transaction price to the performance obligations.
- Recognise revenue when (or as) each performance obligation is satisfied.
For a standard SaaS subscription with a single performance obligation (continuous access to the platform), revenue is recognised evenly over the subscription term as the service is delivered. Where a contract bundles distinct services (for example, onboarding and ongoing access), each obligation is identified and priced separately.
FRS 102 Section 23 applies to companies preparing accounts under UK Generally Accepted Accounting Practice (UK GAAP). Size doesn't force a company onto IFRS: the Companies Act 2006 requires it only for the group accounts of a parent whose securities trade on a UK regulated market (s403), and for everyone else it's a choice (s395). Section 23 was rewritten in the FRC's Periodic Review 2024. For accounting periods beginning on or after 1 January 2026 (earlier if you opted in), it's called Revenue from Contracts with Customers and uses the same five steps as IFRS 15, in simpler form (FRS 102, paragraphs 1.37 and 23.4). Small companies filing under Section 1A follow the same recognition rules.
For a plain subscription the answer doesn't move. Your customer gets the benefit as you provide access, so the obligation is satisfied over time (paragraph 23.81(a)) and revenue is spread across the term, which is where the old stage-of-completion rule landed too. Where it can move is a bundled contract: under the new section you identify each distinct promise, so a set-up or onboarding fee needs checking against step 2 rather than being taken to revenue on day one by habit.
US ASC 606 is the American equivalent standard and does not govern a UK company. If you are reading US SaaS accounting content and see ASC 606 cited, be aware that it describes the same underlying principle but is the wrong source for UK statutory accounts.
If you are unsure which framework applies to your company, or your investor agreements specify a reporting basis, this is a question for your accountant rather than a DIY determination. The choice between IFRS and FRS 102 has consequences beyond revenue recognition and should be set correctly from the outset.
Want this checked against your specific situation?
Leave your details and a one-line summary. One of our specialists will come back to you, with no obligation.
How revenue recognition feeds MRR, ARR and investor reporting
Monthly Recurring Revenue (MRR) and Annual Recurring Revenue (ARR) are management metrics that capture the contracted recurring value of your subscription base. They are not the same as statutory revenue, and understanding the distinction protects you in investor conversations and due diligence.
MRR is typically calculated as the sum of all active monthly subscription values at a point in time, normalised to a monthly figure. ARR is MRR multiplied by 12, or the equivalent annual contracted value. Neither is derived directly from your profit-and-loss account.
The practical gaps between MRR/ARR and statutory revenue include:
- Timing: ARR counts the full contracted annual value of every live subscription; statutory revenue counts only the portion earned in the accounting period.
- One-off revenue: professional services, setup fees or usage overages may appear in statutory revenue but are excluded from ARR if they are non-recurring.
- Churn: a cancelled subscription reduces MRR immediately but may have already been partially recognised as statutory revenue for the months already delivered.
Investors use MRR and ARR to evaluate growth trajectory. Your statutory accounts use recognised revenue to report taxable profit, meet Companies Act requirements, and form the basis of your corporation tax computation. Both sets of numbers are important and neither replaces the other.
Where revenue recognition meets tax
Revenue recognition is an accounting matter governed by the standard your company applies. Corporation tax in the UK broadly follows the accounting profit, subject to specific adjustments, so getting your revenue recognition right feeds directly into a correct corporation tax computation. A company that over-recognises revenue in one period may pay corporation tax earlier than necessary.
VAT operates under its own rules. The tax-point rules for VAT purposes are separate from your revenue-recognition accounting under IFRS 15 or FRS 102. The two systems answer different questions: revenue recognition asks when you have earned the income; VAT asks when the supply is made for tax purposes. Don't assume that because revenue is deferred for accounting purposes the VAT point is also deferred. For a continuous supply of services there's a tax point each time you issue a VAT invoice or receive a payment, whichever comes first (VAT Notice 700, paragraph 14.3). So if you're registered and invoice the £12,000 annual plan upfront, the VAT on the whole £12,000 is due then, even though only £1,000 a month becomes revenue.
Once your rolling 12-month UK taxable turnover goes over £90,000, VAT registration is mandatory. For SaaS businesses with overseas customers, sales to business customers abroad, and digital services sold to consumers abroad, are generally outside the scope of UK VAT, so they don't count toward the UK VAT threshold. Purchases can count: while you're unregistered, services bought from overseas suppliers under the reverse charge are added in, and from 1 April 2027 that reverse charge is due to apply only to VAT-registered businesses (announced at Budget 2026 on 28 October 2026, still to pass in the Finance Bill). This is a material point for SaaS companies scaling internationally, covered in detail in our post on VAT for SaaS and place of supply.
As your ARR grows toward and beyond the VAT threshold, the interaction between contracted revenue, invoicing cycles, and tax points is worth reviewing with your accountant before you hit the threshold rather than after.
Getting SaaS accounting right from the start
Deferred revenue, multi-element arrangements, and the choice of accounting standard are areas where early decisions become structural. A company that builds its chart of accounts and bookkeeping processes correctly from the first annual contract will have accurate management accounts, investor-ready financial statements, and a corporation tax computation that matches the economics of the business.
Common places where SaaS revenue accounting goes wrong include:
- Booking annual upfront payments as revenue on receipt rather than spreading over the term.
- Treating the deferred revenue balance as available cash rather than a service obligation.
- Conflating MRR/ARR with statutory revenue in board packs and due-diligence materials.
- Applying the wrong standard (or no standard) because the question was never addressed at company formation.
- Not separating distinct performance obligations in bundled contracts (for example, onboarding plus a 12-month licence).
If you are setting up your accounting function, raising a funding round, or preparing for an audit for the first time, our fractional CFO service covers finance-function design alongside ongoing commercial finance support. For month-to-month compliance, see our core compliance service. You can also read more on the commercial finance role in our post on startup CFO pay and fractional CFO cost.
Leave it to the first audit and you may be restating a year of management accounts and board packs. Set up the deferred revenue account when you sign your first annual contract and it largely runs itself. See how we support SaaS companies, or get in touch about your own contracts.