How should a SaaS company recognise subscription revenue in the EU?

Under accrual accounting, which most EU jurisdictions require, annual subscription revenue must be recognised monthly over the service period. A €12,000 annual prepayment becomes €1,000 per month, with the unearned portion sitting as deferred revenue (a liability) on the balance sheet. Booking the full amount as month-one revenue overstates income and creates an inflated tax liability.

What is deferred revenue and why does it matter for EU SaaS companies?

Deferred revenue is money collected but not yet earned, recorded as a current liability because you still owe service for it. For SaaS companies with annual billing, it can be substantial. It affects corporate tax timing (you are taxed on recognised revenue, not collected cash), dividend distribution limits, and banking assessments of your company’s financial health.

Do EU SaaS companies need to use accrual accounting?

Most EU jurisdictions require accrual accounting for companies above a low threshold. Some, like Estonia, allow micro-entities to use cash basis, but with cross-border invoicing and annual subscriptions, cash basis hides reality rather than simplifying it. Under cash basis, a €12,000 annual payment shows as January revenue, potentially triggering corporate tax on money you haven’t earned yet.

EU SaaS Accounting: Revenue Recognition & ...

You've incorporated your EU company, sorted out your VAT position, and started collecting subscription revenue. Then your accountant asks whether you're recognising revenue on an accrual or cash basis, how you're handling deferred revenue from annual prepayments, and whether your multi-currency invoices are booked at the transaction date rate or the month-end rate. If those questions make your eyes glaze over — you're the target audience for this article.

SaaS accounting operates under rules that trip up founders who've been running simpler businesses. The subscription model creates specific bookkeeping requirements that differ from one-off project invoicing: customers pay upfront for something delivered over time, and how you record that revenue determines your tax bill, your balance sheet, and whether your tax authority has questions.

Accrual vs cash: why it matters more than you think

Most EU jurisdictions require companies above a certain size to use accrual accounting. Some, like Estonia, allow micro-entities to use cash-basis accounting, but the threshold is low. The moment you're invoicing across borders with annual subscriptions, cash basis starts hiding reality rather than simplifying it.

Cash-basis accounting records revenue when the money hits your bank account. You receive €12,000 for an annual subscription in January, and your books show €12,000 of revenue in January. Simple, but misleading. Your actual obligation is to deliver twelve months of service. If the customer cancels in March, you owe a refund on nine months you already "earned."

Accrual accounting records revenue when you earn it, regardless of when the cash arrives. That same €12,000 annual subscription becomes €1,000 per month, recognised over the contract period. The remaining unearned amount sits on your balance sheet as deferred revenue, classified as a liability because you still owe service for it.

The difference isn't academic. Under cash basis, you show €12,000 profit in Q1 (assuming no other revenue) and potentially owe corporate tax on it. Under accrual, you show €3,000, because that's what you actually earned. If your Estonian OÜ distributes that inflated Q1 profit as dividends, you've paid distribution tax on money you haven't truly earned yet. The numbers compound fast when you have dozens or hundreds of annual subscribers.

For most EU SaaS founders, accrual accounting isn't optional. It's both legally required and the only way to avoid overpaying tax on revenue you haven't earned.

Subscription revenue recognition: the rules that catch founders

Revenue recognition for subscriptions follows a principle that sounds obvious but has real teeth: you recognise revenue as you deliver the service, not when you collect the payment. For SaaS, "delivery" means providing access to your software for the contract period.

Annual prepayments

When a customer pays €12,000 upfront for a year of access, you book it as follows:

Day one: Record the full €12,000 as deferred revenue (a liability on your balance sheet). Cash increases by €12,000. Revenue: zero.
Each month: Move €1,000 from deferred revenue to recognised revenue. Over twelve months, the liability unwinds to zero and revenue accumulates to €12,000.

This is where founders make the first expensive mistake. Booking the full annual payment as month-one revenue overstates your income, creates a tax liability on revenue you haven't earned, and misrepresents your financial position to anyone looking at your books: investors, tax authorities, or yourself.

Monthly subscriptions

Monthly plans are simpler. The customer pays €100 per month, you deliver one month of service, you recognise €100. Payment and delivery align. No deferred revenue, no timing mismatch.

Mixed billing periods

Most SaaS companies offer both monthly and annual plans. Your bookkeeping needs to handle both simultaneously: monthly revenue flows straight through, annual revenue gets deferred and released monthly. Not complex in principle, but it requires discipline in your accounting software setup. More on tooling below.

Deferred revenue: the liability founders forget

Deferred revenue (sometimes called unearned revenue) is money you've collected but haven't yet earned. On the balance sheet, it sits under current liabilities, because you owe your customers something for it.

For a SaaS company with annual billing, deferred revenue can be substantial. A company with 200 annual subscribers at €1,200 each, all renewing in January, carries €240,000 in deferred revenue on 1 February, recognised at €20,000 per month over the year. That's not cash you can spend freely. It's an obligation.

Why this matters for EU founders specifically:

Corporate tax timing. Under accrual accounting, you're taxed on recognised revenue, not collected cash. Deferred revenue reduces your current-period taxable income to match what you've actually delivered. Get this wrong and you overpay.
Dividend distributions. If your Estonian OÜ or Irish Ltd shows inflated profit because deferred revenue wasn't booked properly, and you distribute that "profit," you've distributed money earmarked for future service delivery. Tax authorities may also challenge the distribution.
Banking and credit. European banks assessing your company for a business account or credit facility will look at deferred revenue. A high deferred revenue balance relative to recognised revenue signals a healthy subscription business with committed customers. Absent it, and your books look like a project-based consultancy with lumpy income.

MRR and ARR: metrics vs accounting

Monthly Recurring Revenue (MRR) and Annual Recurring Revenue (ARR) are SaaS metrics, not accounting terms. Your accountant doesn't use them. Your investor deck does. The distinction matters because they measure different things.

MRR tracks the normalised monthly revenue from active subscriptions. A customer on a €1,200 annual plan contributes €100/month to MRR, regardless of when they paid or how revenue is recognised. MRR is a forward-looking operational metric.

Recognised revenue is the accounting figure, what you've actually earned according to accrual rules in a given period. They often converge for monthly subscriptions, but diverge for annual prepayments, discounts, credits, and churn.

The implication for your day-to-day: don't hand your MRR dashboard to your bookkeeper and call it revenue. And don't use your accounting revenue figures for SaaS metrics. They lag behind operational reality because of recognition timing. Keep two systems: your SaaS metrics tool (Baremetrics, ChartMogul, Stripe's built-in dashboards) for operational decisions, and your accounting software for compliance and tax filings.

Multi-currency revenue: where the real complexity lives

If you invoice in multiple currencies (and most EU SaaS companies do, given the mix of EUR, USD, GBP, and sometimes SEK, PLN, or CHF), you need a currency handling policy before your first foreign-currency invoice.

The booking problem

When you invoice a US customer $1,200 and the EUR/USD rate is 1.10, you record €1,091 in revenue. When the customer pays thirty days later and the rate has moved to 1.12, the payment converts to €1,071. The €20 difference is a foreign exchange loss, and it needs to be booked somewhere.

Most EU jurisdictions require you to:

Book at the transaction date rate — the exchange rate on the invoice date
Revalue open receivables at period-end (monthly or quarterly) and recognise unrealised FX gains or losses
Book the realised gain or loss when payment settles at a different rate

Ignoring FX differences doesn't make them disappear. They accumulate, and your balance sheet drifts from reality. For a SaaS company doing €200,000 in annual revenue with 40% in USD, a 5% currency swing creates €4,000 in FX impact. Not catastrophic, but material enough to require proper tracking.

What to do about it

Use accounting software that handles multi-currency natively (Xero, Exact Online, or e-Aasvaldur for Estonian companies). Set your functional currency to EUR unless you have a specific reason not to. Record each invoice in the customer's currency and let the software calculate the EUR equivalent at the daily ECB reference rate. Review FX gains and losses quarterly. Budget for them in your annual planning. They're not rounding errors.

IFRS vs local GAAP: when it matters

If you're running a sub-€2M SaaS company, you're almost certainly not required to use International Financial Reporting Standards (IFRS). IFRS is mandatory for EU-listed companies and required above certain thresholds in some jurisdictions. Everyone else uses local GAAP, the national accounting standards of your incorporation country.

The distinction matters for revenue recognition because IFRS 15 (Revenue from Contracts with Customers) has specific, detailed rules for when and how to recognise subscription revenue, including multi-element arrangements, variable consideration, and contract modifications. Local GAAP in most EU countries follows similar principles but with less prescriptive guidance.

In practice, the accounting treatment for a typical SaaS subscription — recognise over the service period, defer what's unearned — is the same under IFRS 15 and most local GAAPs. Where IFRS gets more demanding is with complex arrangements: bundled hardware and software, tiered pricing with variable discounts, or enterprise contracts with implementation services. If your SaaS product is a pure software subscription at a fixed price, local GAAP handles it without the overhead of full IFRS compliance.

The honest caveat: some accountants default to IFRS terminology and treatment even for small companies, because that's what they learned. This isn't necessarily wrong (IFRS 15's framework is sensible), but it can mean your bookkeeper is applying enterprise-grade complexity to a ten-customer startup. If your accountant is quoting IFRS 15's five-step model for your €5,000/month SaaS, ask whether local GAAP would be simpler. It usually is.

Setting up your accounting stack

Your accounting stack needs to handle four things reliably: deferred revenue scheduling, multi-currency conversion, VAT for cross-border SaaS (see our VAT guide), and local filing in your jurisdiction.

If you're using Xolo or Enty

Both platforms handle basic bookkeeping for Estonian OÜs, but their treatment of SaaS-specific requirements varies. Xolo's accounting service recognises revenue monthly and handles deferred revenue scheduling if you flag annual subscriptions explicitly. Enty's bookkeeping is more template-driven; confirm with their team that annual prepayments are being deferred, not booked as lump-sum revenue. Neither platform is built for companies with complex multi-currency SaaS billing. Above roughly €200,000 in annual revenue or more than two billing currencies, you'll likely need standalone accounting software alongside the formation service.

Standalone accounting software

For EU SaaS companies outgrowing their formation provider's built-in bookkeeping, the practical choices are covered in depth in our accounting software guide. The short version: Xero handles multi-currency and deferred revenue well across most EU jurisdictions. Exact Online is the standard for Dutch BVs. Estonian companies often use Merit Aktiva or e-Aasvaldur for local compliance. Irish Ltds work well with Xero or Sage.

Stripe and accounting integration

If you're collecting payments through Stripe — and most EU SaaS companies are — make sure your accounting integration handles revenue recognition correctly. Stripe's own revenue recognition feature (Stripe Revenue Recognition) tracks deferred revenue automatically, but it's a separate product with separate pricing. Without it, the default Stripe-to-accounting sync records payments as revenue when collected, which is cash-basis treatment. That defeats the purpose of accrual accounting. Either enable Stripe's revenue recognition tooling or build the deferral schedules manually in your accounting software.

Common mistakes and how to avoid them

Booking annual subscriptions as month-one revenue. Already covered above, but it bears repeating. This is the single most frequent error. The fix is mechanical: set up a deferred revenue schedule for every annual plan. Your accounting software handles this automatically once configured.

Founders billing in USD from a EUR-denominated company often ignore the currency conversion delta between invoice date and payment date. Over a year, these small differences in FX gains and losses accumulate into a material line item. Book them. Review them quarterly. Treat them as a cost of doing international business.

Confusing MRR with recognised revenue. Your MRR dashboard says €10,000. Your accounting says €7,500 in recognised revenue for the month. Both are correct; they measure different things. Don't reconcile them, because they won't match. Use MRR for operational decisions and recognised revenue for tax and compliance.

Founders who ran freelance businesses on cash basis often bring that habit to their EU company. The rules are different once you're operating an Estonian OÜ, Irish Ltd, or Dutch BV. Statutory accounting requirements go beyond tracking income and expenses — deferred revenue, accrued expenses, and balance sheet reporting are required, not optional.

Then there's the bookkeeper problem. Generic bookkeepers handle project invoices and expense receipts. SaaS billing — with its recurring charges, trial periods, pro-rated upgrades, refunds, and annual prepayments — requires someone who understands subscription economics. When hiring or evaluating an accounting service, ask one question: "How do you handle deferred revenue from annual SaaS subscriptions?" If the answer is vague, keep looking.

The bottom line

SaaS accounting in the EU follows the same core principles as anywhere else: recognise revenue when earned, defer what's unearned, and track your currencies properly. The EU-specific wrinkle is that your jurisdiction determines which GAAP you follow, which filing deadlines you face, and how your corporate tax position interacts with your revenue recognition timing.

For most founders reading this, the practical checklist is short. Use accrual accounting. Set up deferred revenue schedules for annual subscriptions. Book FX gains and losses. Choose accounting software that handles multi-currency natively. And find a bookkeeper who understands that a €12,000 annual payment is not €12,000 of January revenue.

The companies that get this right from the start save themselves a painful retrospective cleanup — and keep their tax position clean without overpaying. For a comparison of how these requirements differ across Estonia, Ireland, and the Netherlands, that guide picks up where this one leaves off.

This article reflects EU accounting standards and SaaS revenue recognition practices as of March 2026. Accounting requirements vary by jurisdiction, company size, and business model; verify specific obligations with a qualified accountant in your incorporation country. This article is for informational purposes only and does not constitute financial, tax, or legal advice.