Revenue recognition is the single most common area of weakness we see in the management accounts of UK-resident SaaS companies. The temptation to recognise an annual subscription on invoice is strong, especially when cash is tight, but it produces accounts that overstate revenue, misrepresent margin and confuse investors. FRS 102 (the main UK GAAP standard) requires a different approach, and the September 2024 amendments to FRS 102 brought UK GAAP closer to IFRS 15 in this area.
The basic principle
Subscription revenue is earned over the period during which the service is provided, not when the invoice is raised or when the cash is collected. An annual SaaS contract billed and paid up front in January generates revenue ratably across the twelve months of the licence period. The cash received in January creates a deferred income liability on the balance sheet, which unwinds to the profit and loss as the service is delivered.
The September 2024 amendments
The FRC issued amendments to FRS 102 in September 2024, effective for accounting periods beginning on or after 1 January 2026, introducing a five-step revenue model substantially aligned with IFRS 15. Early adoption is permitted. The five steps are:
- Identify the contract with the customer.
- Identify the performance obligations in the contract.
- Determine the transaction price.
- Allocate the transaction price to the performance obligations.
- Recognise revenue as the performance obligations are satisfied.
For most SaaS companies, the practical effect is similar to existing best practice under FRS 102 Section 23, but with sharper definitions and more explicit guidance on multi-element contracts, variable consideration and contract modifications.
Performance obligations in a typical SaaS contract
A SaaS contract often has multiple performance obligations:
- The hosted software subscription. Usually a single performance obligation delivered ratably over the licence period.
- Implementation and onboarding services. If these are distinct (the customer could in principle obtain implementation separately), they are a separate performance obligation, with revenue recognised as the work is performed. If they are not distinct (only valuable in the context of the subscription), they may be combined with the subscription.
- Customer support. Where contractually committed, typically bundled with the subscription as a stand-ready obligation recognised ratably.
- Add-on modules and feature unlocks. Often distinct, with their own transaction price allocation and timing.
Deferred income and contract liabilities
The deferred income balance is one of the most commercially important numbers in a SaaS balance sheet. It represents revenue billed (or received) ahead of service delivery, and it is a useful proxy for committed forward revenue from existing customers. Investors and lenders look at the deferred income balance closely; a sudden drop typically signals either downgrades, churn or a billing-cycle shift, all of which warrant explanation.
Under the amended FRS 102 model, the deferred income balance is more formally described as a "contract liability". The substance is the same: an obligation to deliver future service against amounts already invoiced.
Setup fees
One-off setup or activation fees raise a classic SaaS revenue question. The general answer under FRS 102 is to defer the setup fee and recognise it over the expected customer life (often longer than the initial contract term) unless the setup activity transfers a distinct service. The reasoning is that pure setup fees that do not deliver a separately valuable service are effectively a payment for future SaaS access, so they should follow the subscription pattern.
Multi-year contracts and discounts
Long-term contracts with embedded discounts (for example, a 36-month deal at a 20% discount to the 12-month price) need careful allocation. The transaction price across the contract is recognised ratably, which means the monthly revenue figure is lower than the headline rate card. Annual price escalators that are fixed and known should be levelled across the contract; variable escalators (such as CPI) are recognised when they apply.
Contract modifications
Upgrades, downgrades and contract extensions are common in SaaS. The FRS 102 framework treats a contract modification either as a separate contract (if it adds a distinct service at standalone selling price), as a termination of the old contract and creation of a new one (if the remaining services are distinct from those already provided), or as a continuation with revised future revenue.
Practical implications
For most early-stage SaaS companies the key disciplines are:
- A clean billing system that ties invoice dates to service periods.
- A monthly recognition schedule that unwinds deferred income consistently.
- Separate treatment of setup fees, professional services and subscription.
- Clear identification of multi-element contracts and the allocation methodology.
How we help
PushDigits prepares statutory accounts for SaaS clients under FRS 102, including the revenue recognition policies, deferred income reconciliations and disclosure notes. We help finance teams move from invoice-based recognition to a proper subscription model that holds up under due diligence. See our annual accounts and bookkeeping pages, or book a consultation.