SaaS accounting: the key issues

Why is SaaS accounting different?

A SaaS company invoices customers in advance for access over months or years, pays sales staff commissions upfront for revenue it will earn over several years, and spends heavily on developing its platform. Revenue under IFRS 15 follows the service, not the invoice; commissions follow the revenue they help win; and development costs are mostly expensed. So the income statement can look very different from bookings and cash flow, which is why SaaS companies also report metrics such as annual recurring revenue.

Which IFRS issues matter most in SaaS accounting?

How is SaaS revenue recognised?

Access to hosted software that the customer cannot take possession of is a service, a stand-ready obligation to provide access, recognised evenly over the subscription period. Annual billing in advance creates a contract liability that unwinds month by month. See SaaS revenue recognition under IFRS 15, and SaaS under ASC 606 for US companies.

How are implementation fees treated?

Only if implementation is a distinct service, one the customer could get from others or benefit from on its own, is it recognised as performed. Set-up activities that only prepare the platform are not services to the customer, so their fees are recognised over the subscription. See implementation and onboarding fees.

Is it a software licence or SaaS?

If the customer can take possession of the software and run it itself, it has a licence, recognised when it can use the software, with support and updates over time. If it only accesses software on the supplier's servers, it is SaaS. Hybrid offerings need each element assessed. See software licence or SaaS.

How are sales commissions accounted for?

Commissions paid only because a contract is won are incremental costs of obtaining it, capitalised and amortised over the period the related services are provided, which often includes expected renewals. See sales commissions in SaaS.

When is software development capitalised?

Under IAS 38, development of new platform features is capitalised only once technical feasibility and the other criteria are met, and maintenance is expensed. Practice varies widely, especially with agile development, so policies are closely read. See capitalising software development.

What does a SaaS balance sheet look like?

Large contract liabilities, often called deferred revenue, from billing annually in advance; trade receivables for invoices not yet paid; capitalised commissions and capitalised development costs; and often little else, because most of the value lies in customer relationships and internally built software that are not recognised. Operating cash flow is usually higher than profit in a growing SaaS business, because customers pay upfront and share-based payment is a non-cash expense. IFRS 15 also requires disclosure of remaining performance obligations, the contracted revenue not yet recognised, which gives a view of future revenue that the balance sheet does not.

What other issues arise?

Multi-year deals with price escalators, usage-based fees, free trials and discounts all affect the transaction price and its allocation. Share-based payment is often a large expense for technology companies. Metrics such as ARR and net revenue retention are not defined by IFRS and should be reconciled to revenue where possible; under IFRS 18 from 2027, subtotals of income and expenses used in public communications may need reconciling as management-defined performance measures. Customers' accounting for cloud services is a separate topic; see cloud computing costs. More detail is in the guides on deferred revenue, price escalators, usage-based pricing, free trials and introductory discounts, share-based payment, ARR and other SaaS metrics and app store revenue.

This guide is general information. It is not tax or legal advice for your situation.