Accounting for SaaS Companies in Estonia

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.

Why a SaaS-Specific CoA Is Necessary

A chart of accounts for a SaaS company needs several account categories that simply do not exist in standard templates: a deferred revenue account for prepaid subscriptions, separate cost of revenue accounts that capture hosting, third-party APIs, customer success, and support costs (not just COGS in the physical goods sense), capitalised software development as an intangible asset, and revenue accounts separated by subscription tier and type.

The structure below is designed for an Estonian SaaS OÜ with monthly and annual subscription plans, a small amount of professional services revenue, a remote team, and cloud infrastructure costs. Adapt it to your specific product and cost profile.

Section 2 — Deferred Revenue: The SaaS Balance Sheet Engine

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

The Deferred Revenue Lifecycle

Deferred revenue is one of the most important and most misunderstood items on a SaaS balance sheet. It represents cash received from customers for services not yet delivered. It is a liability — the company owes the customer future service delivery in exchange for the payment already made. As the service is delivered each month, the deferred revenue is released to recognised revenue on the P&L.

A growing SaaS company should see its deferred revenue balance increasing over time — this is a healthy sign that annual subscription sales are growing faster than the monthly release. A declining deferred revenue balance in a growing company may indicate a shift from annual to monthly plans, which reduces upfront cash and should be monitored.

Deferred Revenue Schedule — Multi-Subscriber Example

In practice, deferred revenue is tracked customer-by-customer in a schedule (often a spreadsheet or within your billing tool). The schedule shows each annual subscriber, their subscription start date, monthly release amount, and the remaining deferred balance at any point. This schedule is the source document for your balance sheet deferred revenue figure and for the revenue recognition journal entries each month.

Annual Subscription Deferred Revenue Schedule — Position at 31 March 2026

Section 3 — MRR Waterfall Accounting

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

The MRR Movement Categories

The MRR waterfall is a structured view of how your Monthly Recurring Revenue changed during a period. It breaks the movement from Opening MRR to Closing MRR into five distinct categories, each of which tells a different story about business health. Unlike the P&L, which shows revenues on an accrual basis, the MRR waterfall is a subscription-database metric — it shows contracted recurring value at each point in time.

Monthly MRR Waterfall — Worked Example

MRR Waterfall — April 2026

MRR Waterfall → P&L Revenue Reconciliation

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 — The Two-Phase Model

IAS 38 (Intangible Assets) requires that internally generated software development costs be assessed against a two-phase model. The first phase — research — encompasses all work done to explore whether and how to solve a problem. These costs are expensed as incurred. The second phase — development — begins once the company has decided to build a specific solution, has a viable technical approach, intends to complete the project, and has the resources to do so. Development-phase costs meeting all six IAS 38 criteria must be capitalised.

For a SaaS company, the practical split is approximately: sprint planning, architecture research, and proof-of-concept work are research (expensed); coding of confirmed features, testing, and deployment preparation are development (capitalise). The demarcation must be documented — it cannot be determined retrospectively.

Tracking Capitalised Development Costs

The practical challenge in capitalising development costs is tracking which hours of developer time relate to capitalised development versus expensed research or maintenance. This requires a time-tracking system where developers log hours against tagged categories: Research, Development (capitalise), Bug Fix/Maintenance, Internal Tools, and Admin.

Amortisation of Capitalised Development Costs

Once a capitalised feature or software module is complete and available for use (deployed to production), amortisation begins. The amortisation period is the estimated useful economic life of the asset — typically 3–5 years for SaaS software components, though this varies by type. Amortisation is charged to Cost of Revenue (Account 5060) because it represents the ongoing cost of delivering the product to customers.

JE-4 — Monthly Amortisation of Capitalised Software

Amortisation of €46,200 of capitalised features at an average 3-year useful life: €46,200 ÷ 36 months = €1,283/month base + additional assets per project schedule = €3,850 total. Charged to COGS — not OpEx — because it is a product delivery cost.

Section 5 — Cost of Revenue for SaaS

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

SaaS Cost of Revenue — The Definition

Cost of revenue (also called COGS) for a SaaS company comprises costs that are directly tied to delivering the product to customers — costs that scale with customer count or usage, and without which the product could not be delivered. It is important to distinguish these from operating expenses, which are period costs of running the business that do not directly drive product delivery.

The gross margin percentage (revenue minus cost of revenue, divided by revenue) is one of the most important benchmarks investors use to assess a SaaS company. A SaaS business typically targets 70–80%+ gross margin. Getting COGS classification right is essential for meaningful benchmarking — overloading COGS with operating costs artificially depresses gross margin; underloading it makes the business look more efficient than it is.

Gross Margin Analysis — What a SaaS P&L Should Show

Section 6 — Billing System Integration

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

Why Integration Is Critical for SaaS

A SaaS company with 200 subscribers, a mix of monthly and annual plans, regular new sign-ups, upgrades, downgrades, and churns generates hundreds of subscription events per month — each with revenue recognition implications. Managing this manually in a spreadsheet is error-prone, time-consuming, and becomes unscalable beyond approximately 50 subscribers. Integration between your billing platform and accounting software is not optional at scale — it is a prerequisite for accurate monthly closes.

Stripe Revenue Recognition — Setup for Estonian OÜ

Stripe Revenue Recognition is a built-in Stripe feature (available on Stripe’s Growth plan) that automatically creates deferred revenue schedules for each subscription, recognises revenue monthly, and generates accounting-ready reports. For an Estonian OÜ using Stripe, this is the most straightforward path to automated IFRS 15-compliant revenue recognition.

Section 7 — The SaaS Monthly Close Process

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

Target: Close by the 5th, Investor Pack by the 7th

A well-run SaaS company should be able to close its books within 5 days of month-end. The key constraint is not data volume — it is process design. With automated billing integration, pre-built revenue recognition schedules, and clear accountant ownership, the close is predictable and fast. When it takes longer than 10 days, the root cause is usually missing integration, unresolved prior-month items, or unclear ownership.