Revenue recognition

IFRS 15 for SaaS, in plain English.

Cash in the bank and revenue in your accounts are different things. Here's how the revenue standard applies to subscription software — and where SaaS companies usually get it wrong.

Revenue follows delivery, not invoices.

IFRS 15 sets one principle: recognise revenue as you transfer what you promised to the customer, in the amount you expect to be entitled to. For a subscription, that means spreading the price over the period of service rather than booking it when the invoice goes out or the cash arrives.

It's no longer just a question for large companies. From accounting periods beginning on or after 1 January 2026, FRS 102 Section 23 — the framework most Irish and UK private companies use — was rewritten around the same five-step model.

The five steps, applied to SaaS.

  • 1. Identify the contract — your order form, online terms or master agreement with the customer
  • 2. Identify the performance obligations — usually access to the platform, plus anything distinct such as implementation, training or premium support
  • 3. Determine the transaction price — including discounts, credits, and an estimate of variable usage fees where appropriate
  • 4. Allocate the price to each obligation based on its standalone selling price
  • 5. Recognise revenue as each obligation is satisfied — for platform access, evenly over the subscription term

How the tricky bits work.

Annual prepayment: a customer pays €12,000 up front for a year. You recognise €1,000 a month; the unearned balance sits on the balance sheet as deferred revenue and unwinds each month.

Setup and onboarding fees: if the setup work doesn't give the customer anything useful on its own, it usually isn't a separate obligation. The fee is spread over the expected customer relationship rather than recognised on day one — a frequent source of overstated revenue in early-stage companies.

Usage-based pricing: revenue is recognised as the usage occurs. Where usage fees are variable within a contract, include only the amount that is highly probable not to reverse.

Multi-year deals with discounts: the discount is generally spread across the whole contract, not taken entirely in year one or year three.

Contract costs matter too. Sales commissions paid to win a contract can often be capitalised and expensed over the life of the customer relationship, rather than hitting the P&L in the month they're paid.

What we see go wrong.

  • Treating invoices raised as revenue, so annual billing creates huge spikes in the P&L
  • Recognising setup fees immediately
  • Presenting ARR or bookings as revenue in investor reports and statutory accounts
  • No deferred revenue schedule at all — which surfaces painfully in investor due diligence
  • Ignoring the FRS 102 Section 23 transition adjustment for the first affected year

Common questions.

Does IFRS 15 apply to my small SaaS company?

If you report under full IFRS, yes. Most Irish and UK private companies report under FRS 102, whose revenue section was replaced with an IFRS 15-style five-step model for periods beginning on or after 1 January 2026. In practice, the same principles now apply.

Is deferred revenue a bad thing?

No. It's a liability on paper, but it represents cash already collected for service you will deliver. Investors generally like seeing a healthy deferred revenue balance because it means customers are paying up front.

Will this change our tax bill?

It can change which year profit falls into, and the one-off transition adjustment can have tax consequences. The total profit over the life of a contract doesn't change.

Keep reading.

Talk to a chartered accountant.

A free 30-minute call, no commitment. We'll tell you plainly what you need and what it costs.

Figures on this page were checked against Revenue, CRO and HMRC guidance in November 2026. Tax rules change; this page is general information, not advice for your specific circumstances.