Revenue Recognition for UK SaaS Companies: FRS 102 & IFRS 15 Explained

Why UK SaaS revenue recognition is different

If you sell a physical product, revenue recognition is straightforward: you deliver the product, you recognise the revenue. UK SaaS is fundamentally different because you are selling access to a service over time, not a one-off transaction.

When a UK customer signs a 12-month contract for £12,000 and pays upfront, you have £12,000 in the bank — but you have not earned £12,000 yet. You have earned one month's worth: £1,000. The remaining £11,000 is a liability on your balance sheet called deferred revenue (also called deferred income on a UK balance sheet). You owe the customer 11 more months of service.

Getting this right is not optional for UK SaaS companies. It affects your P&L accuracy, your balance sheet integrity, your Corporation Tax position (HMRC assesses tax on accounting profit), and how UK investors evaluate your business during fundraising due diligence. Getting it wrong can lead to material misstatements at audit, HMRC enquiries into your Corporation Tax computation, and serious problems during Series A due diligence.

Which standard applies to you? Most UK SaaS companies report under FRS 102 (the UK GAAP standard) rather than IFRS 15. Private companies below the medium-sized company threshold default to FRS 102; IFRS is mandatory for UK-listed groups and optional for smaller private companies that choose it (usually because of US parent requirements). This guide covers both, with emphasis on FRS 102 as that's what most UK SaaS founders actually deal with.

The accounting standards: IFRS 15 and FRS 102

IFRS 15: Revenue from Contracts with Customers

IFRS 15 is the international standard that governs revenue recognition. If your company reports under IFRS (common for larger UK companies or those with international operations), this is your framework.

IFRS 15 uses a five-step model:

Step 1: Identify the contract

A contract exists when both parties have agreed to it, each party's rights are identifiable, payment terms are clear, the contract has commercial substance, and collection is probable.

For SaaS, this is typically the signed subscription agreement or accepted terms of service.

Step 2: Identify the performance obligations

A performance obligation is a promise to deliver a distinct good or service. In SaaS, the primary performance obligation is providing access to the software platform over the subscription period.

This is where it gets interesting. If your contract includes implementation services, training, data migration, or a dedicated customer success manager, each of these could be a separate performance obligation — meaning revenue needs to be allocated across them.

Step 3: Determine the transaction price

The total amount the customer is expected to pay. For a straightforward £12,000 annual subscription, this is simple. For contracts with variable pricing (usage-based components, performance bonuses, or tiered pricing), you need to estimate the expected consideration.

Step 4: Allocate the transaction price to performance obligations

If you have multiple performance obligations (subscription + implementation + training), you allocate the total price to each based on their standalone selling prices. If you charge £12,000 for the subscription and £3,000 for implementation, and those reflect fair standalone prices, the allocation is straightforward.

If you bundle implementation for free (but would charge £3,000 separately), you need to allocate a portion of the £12,000 subscription price to the implementation obligation.

Step 5: Recognise revenue as obligations are satisfied

For the subscription: recognise evenly over the contract term (£1,000 per month for a £12,000 annual contract). For implementation: recognise when the implementation is complete. For training: recognise when the training is delivered.

FRS 102: The UK standard

Most UK SaaS companies below a certain size report under FRS 102, which is simpler than IFRS 15 but follows similar principles. Section 23 of FRS 102 covers revenue recognition.

The core principle is the same: revenue is recognised when it is earned, not when cash is received. For service contracts (which SaaS subscriptions are), revenue is recognised by reference to the stage of completion — meaning evenly over the service period for a standard subscription.

FRS 102 is less prescriptive than IFRS 15 about the five-step model, but the outcomes are similar for most SaaS contracts.

Deferred revenue explained

Deferred revenue (also called deferred income or unearned revenue) is the balance sheet liability that represents cash received for services not yet delivered.

How it works

January: Customer signs 12-month contract for £12,000 and pays upfront.

By December, all £12,000 has been recognised as revenue and the deferred revenue balance is zero. The obligation has been fully satisfied.

Why deferred revenue matters

For investors: A growing deferred revenue balance is a positive signal. It means customers are paying upfront for future services — a sign of customer confidence and strong cash flow generation.

For cash flow: Deferred revenue represents cash you have already received. It is working capital you can use to fund operations, even though it has not been "earned" yet from an accounting perspective.

For valuation: Some investors look at the "total backlog" (contracted revenue not yet recognised) as a forward indicator. High deferred revenue relative to quarterly revenue suggests strong visibility into future performance.

For tax: In the UK, corporation tax is generally based on accounting profits, which means revenue recognition timing affects your tax liability. Recognising revenue correctly can have meaningful tax implications.

Annual vs monthly billing: the financial impact

The choice between annual and monthly billing has significant implications beyond cash flow.

Annual billing (upfront)

• Cash flow: Receive £12,000 in month 1 instead of £1,000 per month
• Revenue recognition: Same — £1,000 per month regardless of when cash arrives
• Balance sheet: Creates deferred revenue liability (£11,000 in month 1)
• Accounts receivable: Invoice of £12,000 (plus VAT) in month 1, then nothing for 11 months
• Working capital: Strongly positive — you have the customer's cash months before you have earned it

Monthly billing (no commitment)

• Cash flow: £1,000 per month as earned
• Revenue recognition: £1,000 per month — billing and recognition are synchronised
• Balance sheet: No deferred revenue (or minimal, depending on billing date vs period end)
• Accounts receivable: £1,000 (plus VAT) each month
• Working capital: Neutral — cash arrives roughly when revenue is recognised

Quarterly billing

• Cash flow: £3,000 every three months
• Revenue recognition: Still £1,000 per month
• Balance sheet: Up to £2,000 deferred revenue at any point within a quarter
• Working capital: Moderately positive

The strategic implication: annual billing is almost always preferable for SaaS companies. It improves cash flow, reduces churn (customers who have paid for a year are less likely to cancel), and creates a deferred revenue balance that investors view positively.

Common revenue recognition mistakes

Recognising annual contracts in full upfront

This is the most common mistake, especially in early-stage companies that track revenue on a cash basis. If you invoice £12,000 and book it all as January revenue, your January P&L is overstated and your February-December P&L is understated. More importantly, your balance sheet is wrong — you are missing the deferred revenue liability.

Ignoring multi-element arrangements

If your contract includes subscription + implementation + training, and you recognise all revenue ratably over the subscription period, you may be understating early-period revenue (implementation revenue should be recognised when delivered, not spread over 12 months).

Inconsistent treatment of discounts

If you give a customer a 20% discount for annual prepayment, the revenue recognised per month should be based on the discounted price, not the list price. Sounds obvious, but many companies track MRR at list price and revenue at actual price, creating reconciliation headaches.

Not tracking contract modifications

When a customer upgrades mid-contract, you need to decide whether it is a contract modification or a new contract. Under IFRS 15, this matters for how the additional revenue is recognised. Under FRS 102, the treatment is less prescriptive but still needs to be consistent.

Confusing bookings, billings, and revenue

• Bookings: The value of signed contracts (used for sales tracking, not accounting)
• Billings: Invoices raised (used for cash flow tracking)
• Revenue: Earned income recognised in the P&L (the only one that matters for your accounts)

These three numbers will be different in any given month. All three are important, but only revenue goes in the P&L. Mixing them up creates confusion with investors and auditors.

Setting up your chart of accounts

Your chart of accounts should support proper SaaS revenue recognition from the start. Key accounts to include:

Revenue accounts (P&L)

• Subscription revenue — recurring software access fees
• Implementation revenue — one-time setup and onboarding fees
• Professional services revenue — consulting, training, custom development
• Usage-based revenue — overage charges, API calls, storage

Balance sheet accounts

• Trade receivables (debtors) — invoices raised but not yet paid
• Deferred revenue (current) — revenue to be recognised within 12 months
• Deferred revenue (non-current) — revenue to be recognised after 12 months (for multi-year contracts)
• Accrued revenue — revenue earned but not yet invoiced (common for usage-based billing)

Contra and adjustment accounts

• Revenue discounts — for tracking the impact of discounting separately
• Credit notes — for refunds and adjustments

Having this structure from the start makes monthly close easier, gives auditors what they need, and enables the kind of granular analysis that investors expect.

Working with auditors

If your company is audit-required (or you choose to have an audit for credibility), revenue recognition will be the auditor's primary focus area for a SaaS business.

What auditors look for

• Revenue recognition policy — Documented, consistent, and compliant with the relevant standard
• Contract review — Sample of contracts to verify recognition matches terms
• Deferred revenue reconciliation — Opening balance + cash received - revenue recognised = closing balance
• Cut-off testing — Revenue recognised in the correct period, especially around year-end
• Multi-element arrangements — Proper allocation across performance obligations

How to prepare

1. Document your revenue recognition policy in writing. Include how you handle annual contracts, monthly contracts, implementation fees, and contract modifications.
2. Maintain a contract-level schedule showing each customer's contract value, start date, end date, billing frequency, and monthly recognised revenue.
3. Reconcile deferred revenue monthly. The roll-forward (opening + new billings - recognised revenue = closing) should tie to your balance sheet every month.
4. Keep contracts accessible. Auditors will sample contracts and match them to your revenue schedule. If you cannot produce the signed agreement, that is a finding.

The practical approach

For most UK SaaS companies at the early stage, the practical approach to revenue recognition is:

1. Use accrual accounting from day one. Do not run your books on a cash basis. The transition later is painful and requires restatement.
2. Recognise subscription revenue evenly over the contract term. This is correct for nearly all standard SaaS subscriptions under both IFRS 15 and FRS 102.
3. Recognise implementation and setup revenue when the service is delivered (typically at go-live). If the implementation is not distinct from the subscription (customer cannot benefit from implementation alone), spread it over the subscription term.
4. Track deferred revenue at the contract level. A single deferred revenue balance is not enough for audit or analysis. You need to know the components.
5. Reconcile monthly. If your deferred revenue roll-forward does not tie, you have a problem. Find it immediately, not at year-end.

Revenue recognition is one of those areas where getting it right from the start saves enormous time and cost later. If you are unsure about your current approach, have a qualified finance professional review it before your next audit or fundraise. At ScaleWithCFO, this is one of the first things we assess when working with a new SaaS client — because everything else builds on the accuracy of your revenue numbers.