Accounting for SaaS Companies in Estonia

A complete bookkeeping guide for Estonian SaaS businesses — chart of accounts, MRR waterfall accounting, deferred revenue schedules, capitalised development costs, and the monthly close process.

Chart of Accounts Deferred Revenue MRR Waterfall Dev Cost Capitalisation Monthly Close Investor Reports
1/12 Monthly Rev. Portion
IAS 38 Dev Cost Standard
5th Monthly Close
IFRS 15 Revenue Standard
7 yrs Record Retention
MRR Key Metric

5 Key Takeaways From This Page

Your chart of accounts must be SaaS-specific

A generic accounting template designed for a service company lacks the accounts needed for deferred revenue, capitalised development costs, MRR movement categories, and software subscription income. Building the right structure from day one saves months of rework.

Cash received ≠ revenue earned for subscription businesses

When a customer pays €2,400 for a two-year subscription, you receive €2,400 in cash — but you earn only €100 per month as you deliver the service. The gap between cash and recognised revenue lives on your balance sheet as deferred revenue until earned.

Development costs require two separate accounting treatments

Under IAS 38, research-phase costs are expensed immediately. Development-phase costs — once you have a technically feasible plan and intent to complete — must be capitalised as an intangible asset and amortised. Expensing everything overstates costs; capitalising everything overstates assets.

The MRR waterfall is your single most important financial report

The MRR waterfall — opening MRR → new MRR → expansion → churn → contraction → closing MRR — tells the story of your business more clearly than any P&L. Investors use it to assess growth quality; it also reconciles your subscription database to your P&L.

Monthly close is 3–5 days — if your processes are right

A SaaS monthly close that takes two weeks is a sign of under-built processes. With the correct chart of accounts, automated revenue recognition schedules, and integration between your billing system and accounting software, the close should be complete by the 5th of the following month.

What does accounting for a SaaS company involve? The core difference from a standard service company is revenue recognition: prepaid subscriptions create deferred revenue liabilities that release to the P&L over the subscription term. Beyond this, SaaS accounting involves: monthly MRR waterfall reporting, capitalised development costs under IAS 38, cost of revenue separation (hosting, support, customer success), and integration between the billing platform and the accounting system. This page covers each of these workstreams with specific account structures, journal entries, and worked examples.

Section 1 — Chart of Accounts for a SaaS OÜ

The complete account structure — built for subscription revenue, deferred revenue, capitalised dev costs, and SaaS cost of revenue

1000–1999 ASSETS — Cash, Receivables, Capitalised Development, Intangibles
2000–2999 LIABILITIES — Deferred Revenue, VAT, Accruals, Social Tax
3000–3999 EQUITY — Share Capital, ESOP Reserve, Retained Earnings
4000–4999 REVENUE — Monthly Subs, Annual Subs, Professional Services
5000–5999 COST OF REVENUE — Cloud Hosting, APIs, Customer Success, Amortisation
6000–6999 OPERATING EXPENSES — R&D, Marketing, Sales, G&A, ESOP

Section 2 — Deferred Revenue: The SaaS Balance Sheet Engine

How prepaid subscriptions create, build, and release the deferred revenue liability month by month

JE-1 — Annual Subscription Received (€1,200/year, 1 January)DR Cash — Bank €1,200 / CR Deferred Revenue — Annual Subs €1,200
JE-2 — Monthly Revenue Release (€100/month through December)DR Deferred Revenue — Annual Subs €100 / CR Revenue — Annual Subscriptions €100
Customer Annual Value Start Date Monthly Release Deferred Balance
Acme Corp €2,400 01 Jan 2024 €200 €1,800
BioTech GmbH €4,800 01 Jan 2024 €400 €3,600
Nordic Solutions €1,200 01 Feb 2024 €100 €1,000
TechStack Ltd €3,600 15 Feb 2024 €300 €3,150
Startup AB €2,400 01 Mar 2024 €200 €2,200
Deferred revenue is a healthy liability — not a problem. A SaaS company with €200,000 in deferred revenue has that amount ‘locked in’ and will recognise it as revenue in coming months regardless of new sales.

Section 3 — MRR Waterfall Accounting

How to track monthly MRR movements and reconcile them to your recognised P&L revenue

New MRR — From brand new customers
Expansion MRR — Upgrades, add-ons, additional seats
Churned MRR — Cancellations
Contraction MRR — Downgrades
Reactivated MRR — Previously churned customers returning
MRR Waterfall — April 2024
Opening MRR: €28,400 | + New MRR: +€2,090 | + Expansion MRR: +€960 | − Churned MRR: −€1,140 | − Contraction MRR: −€480 | + Reactivated MRR: +€190
Closing MRR: €30,020 | Net New MRR: +€1,620 | MoM Growth Rate: 5.7% | Churn Rate: 4.0%

Section 4 — Capitalised Development Costs Under IAS 38

What qualifies for capitalisation, how to track it, and how to amortise the resulting asset

IAS 38 Criterion Practical SaaS Evidence
Technical feasibility Architecture document, technical specification, proof of concept
Intention to complete Sprint backlog inclusion; product roadmap sign-off
Ability to use / sell Business case; pricing model; customer commitments
Generate probable economic benefit User research; competitive analysis
Adequate resources Resource plan; allocated engineering hours
Reliable measurement Time tracking system; sprint-to-feature mapping
Monthly Capitalised Development Cost Calculation
Total team cost: €21,945/month | Development phase (capitalise): 68% → €14,922 | Research phase (expensed): 12% → €2,633 | Bug fixes (expensed): 15% → €3,292
JE-3 — Capitalising Monthly Development Costs
DR Capitalised Software Development (1200) €14,922 / CR R&D Salaries — Development Phase (6020) €14,922

Section 5 — Cost of Revenue for SaaS

What belongs in COGS vs operating expenses — and why the distinction matters for gross margin

SaaS P&L Format — April 2024 (Monthly)
Total Revenue: €30,020 | Total Cost of Revenue: −€11,700 | Gross Profit: €18,320 | Gross Margin: 61.0%Operating Expenses: −€22,923 | Operating Loss: −€4,603

Section 6 — Billing System Integration

Connecting Stripe, Paddle, or ChartMogul to your accounting software for automated revenue recognition

1
Enable in Stripe
Configure accounting periods and recognition rules
2
Configure Recognition Rules
Monthly subs recognise immediately; annual subs 1/12 per month
3
Connect to Xero
Stripe → Xero direct integration or via A2X
4
Monthly Sync
Sync posts recognised revenue and deferred revenue movements

Section 7 — The SaaS Monthly Close Process

Day-by-day timeline from month-end to filed returns and investor pack

Day 1
Billing system sync
Stripe Revenue Recognition or A2X
Day 2
Revenue recognition
P&L revenue matches deferred revenue schedule
Day 3
Accruals & payroll
All month-end liabilities recognised
Day 4
MRR waterfall
Opening + movements = Closing MRR
Day 5
KMD VAT return
Output VAT matches sales

Frequently Asked Questions

The practical solution is a deferred revenue schedule — a spreadsheet or module in your accounting system that tracks each annual subscriber separately. For each annual customer, record: name, subscription start date, annual amount, monthly release amount (annual ÷ 12), and the remaining deferred balance. At month-end, sum the monthly release amounts across all annual subscribers — that is the amount to release from deferred revenue to recognised revenue. Monthly subscribers are recognised in full each month (no deferral). The two streams appear on separate revenue accounts (4010 for monthly, 4020 for annual) and are summed to total revenue on the P&L. Most accounting software and billing platforms (Stripe Revenue Recognition, Chargebee) can automate this, eliminating the manual schedule entirely.

Capitalisation begins when you have documented evidence that all six IAS 38 criteria are met — in practice, this is typically at the start of a sprint that has a clearly defined, technically confirmed scope. The sprint backlog entry should note the date from which costs are capitalised. Capitalisation ends when the feature is substantially complete and ready for deployment to production. Bug fixes and optimisations after launch revert to expense. In a sprint framework: discovery sprints (researching whether and how to build something) are expensed; development sprints (building confirmed specifications) are capitalised; maintenance sprints (fixing bugs, patching) are expensed. The key document is the sprint backlog with date-stamped stories tagged to capitalise or expense. Teams typically use time-tracking tags in Jira, Linear, or their sprint tool to separate capitalised from expensed developer time.

If your subscription contract has a no-refund clause and the cancellation is effective immediately (access terminated), the remaining deferred revenue is recognised as revenue at the point of cancellation — the performance obligation to provide future access has ended. Journal entry: DR Deferred Revenue (remaining 8 months’ worth), CR Revenue — Annual Subscriptions. This is an acceleration of revenue recognition, not a loss. If your contract allows the customer to continue using the product until the contracted period ends but simply will not renew, the revenue continues to be recognised monthly until the contract term expires. The accounting treatment depends entirely on what the contract says about service access after cancellation.

IFRS 15 requires that incremental costs of obtaining a contract — costs that would not have been incurred if the contract had not been obtained — be capitalised and amortised over the expected benefit period, unless the amortisation period would be one year or less (the practical expedient). For sales commissions on SaaS contracts: if a commission is paid for a monthly contract and the customer has no multi-year commitment, the practical expedient allows expensing immediately (benefit period ≤ 1 year). If a commission is paid for a 2-year contract or a customer who is expected to remain for multiple years, the commission should be capitalised and amortised over the expected customer life. In practice, most early-stage SaaS companies use the practical expedient and expense all commissions — this is acceptable unless commission amounts are material relative to revenue.

The annual report of an Estonian OÜ applying IFRS must include specific notes on revenue recognition. Required disclosures include: a description of the types of contracts and performance obligations, the significant judgements made in applying IFRS 15 (how transaction price was allocated, how recognition timing was determined), disaggregated revenue (at minimum split by subscription and professional services; often by geography), a reconciliation of opening and closing deferred revenue balances, and the amount of revenue recognised in the period from performance obligations satisfied in prior periods. For an audited OÜ, the auditors will specifically review the deferred revenue schedule and the IAS 38 capitalisation documentation. Having both well-organised before year-end significantly reduces audit time and fees.

Need SaaS-specific accounting set up correctly from day one?

Book a free 30-minute consultation. We configure your chart of accounts for SaaS, build your deferred revenue schedule, connect your subscription platform, and deliver clean monthly financials investors can trust.

companyforbusiness.ee →