Accounting & Tax for IT and SaaS Companies in Estonia
Everything an Estonian IT or SaaS business needs to stay compliant and financially optimised — from subscription revenue recognition and MRR accounting to remote team payroll, IP taxation, and global client VAT.
5 Key Takeaways From This Page
Revenue recognition for SaaS is fundamentally different from cash
A €12,000 annual subscription paid upfront is not €12,000 of revenue in the month it is received — it is €1,000 per month over the subscription term. IFRS 15 governs how and when SaaS revenue is recognised, and getting this right is foundational to everything else.
MRR and ARR are management metrics — not accounting figures
Monthly and Annual Recurring Revenue are the primary health metrics for SaaS businesses and are reported to investors. They are calculated from contract data, not from accounting entries. Understanding the relationship between your MRR dashboard and your P&L is essential for clean reporting.
Remote team payroll requires local compliance in each country
Paying a developer in Germany, a designer in Spain, and a sales lead in the UK through Estonian payroll alone is non-compliant. Each country where someone habitually works has its own employer obligations, social security rules, and payroll registration requirements.
IP held in Estonia attracts the 0% retained profit structure
Intellectual property developed and owned by an Estonian OÜ benefits from Estonia’s 0% corporate tax on retained profits. Royalties received by the OÜ, or software licences sold to global clients, accumulate tax-free until distributed — a significant structural advantage over most EU jurisdictions.
Global B2B clients use reverse charge — VAT is simpler than you think
Most IT and SaaS services sold to VAT-registered businesses in other EU countries are zero-rated under the reverse charge mechanism. Services to non-EU clients are generally outside EU VAT scope. The complexity is in the B2C digital services layer and in countries where digital services have specific rules.
What accounting and tax services does an Estonian IT or SaaS company need? An Estonian IT/SaaS OÜ needs: monthly double-entry bookkeeping with correct IFRS 15 revenue recognition for subscriptions and project income, MRR/ARR reporting to support investor and management reporting, deferred revenue tracking for prepaid subscriptions, remote team payroll compliance in each country where staff are based, IP ownership structuring and royalty accounting, and global VAT management for B2B and B2C software services. This page covers the full picture — and links to each dedicated topic.
Section 1 — Why IT and SaaS Accounting Is Different
The structural features of software and subscription businesses that make standard accounting templates insufficient.
Four Structural Differences from a Standard Service OÜ
An IT consulting OÜ billing clients by the hour has relatively simple accounting: time and materials invoices, recognised when services are delivered. A SaaS OÜ selling monthly and annual subscriptions to hundreds of global customers has structurally different accounting challenges that require specific systems and processes from day one.
| Dimension | Standard Service OÜ | IT / SaaS Company |
|---|---|---|
| Revenue timing | Invoice when work delivered | Recognised over subscription term; prepaid amounts deferred |
| Revenue complexity | Simple — invoice = revenue | Multiple performance obligations (setup + subscription + support) may require allocation |
| Customer data | Client list with invoice amounts | Subscription database with MRR, churn, expansions, contractions, cohort data |
| Balance sheet items | Minimal — receivables and cash | Deferred revenue liability can be significant; capitalised development costs; IP assets |
| KPIs reported | Revenue, gross margin, cash | MRR, ARR, churn rate, NRR, CAC, LTV, gross margin (different definition) |
| Investor reporting | Annual financial statements | Monthly investor updates with MRR metrics; board packs; scenario models |
| Tax complexity | Estonian income tax on retained profit | IP ownership structure; royalty taxation; R&D credits; transfer pricing if multi-entity |
| Team structure | Typically all Estonian-based | Remote-first; often team across 5–10 countries with different employment regimes |
The Three Most Common IT/SaaS Accounting Mistakes
⚠ Recognising prepaid revenue immediately — Recording a €12,000 annual subscription as €12,000 revenue in the month it is received inflates current revenue, creates a balance sheet error (missing deferred revenue liability), and produces P&L volatility that misleads investors.
⚠ Single performance obligation assumption — Many SaaS products include setup, onboarding, subscription access, and support as part of one contract. IFRS 15 requires each distinct performance obligation to be identified and allocated a portion of the transaction price before recognition timing is determined.
⚠ R&D costs expensed vs capitalised incorrectly — Development costs for internally developed software must be assessed against IAS 38 criteria — the research phase is expensed; the development phase (once technical feasibility is established) must be capitalised. Expensing all development overstates costs and understates assets.
Section 2 — SaaS Metrics and Their Accounting Counterparts
MRR, ARR, churn, and NRR — where each comes from and how it relates to your GAAP financials.
The SaaS Metrics Dashboard
SaaS metrics are derived from your subscription database — the record of every active, churned, new, and expanded contract. They are not directly extracted from your accounting system, but they must reconcile to your accounting figures. Investors, accelerators, and acquirers will compare your MRR dashboard to your revenue recognition schedule — any discrepancy requires explanation.
Sum of all active subscription monthly values. New MRR + Expansion MRR − Churn MRR − Contraction MRR = Net New MRR.
MRR × 12. Represents the annualised value of all current subscriptions. Used for valuations and investor reporting.
Monthly: churned MRR ÷ beginning of month MRR × 100%. Target < 2% monthly for healthy SaaS.
(Starting MRR + Expansion − Churn − Contraction) ÷ Starting MRR × 100%. Above 100% = growth from existing customers.
Average revenue per account ÷ monthly churn rate. Measures how much revenue a customer generates on average before churning.
Total sales and marketing spend ÷ number of new customers acquired. LTV ÷ CAC should be > 3 for healthy unit economics.
How MRR Relates to Your Monthly P&L
MRR is a forward-looking operational metric calculated from contracted recurring revenue. Your monthly P&L revenue is the accounting recognition of revenue earned in the period — under IFRS 15, this equals the portion of subscription value attributable to the current month’s service delivery. For a flat monthly subscription with no other performance obligations, MRR and monthly recognised revenue should be equal. For annual subscriptions, prepaid amounts create a deferred revenue balance that gradually converts to recognised revenue each month.
MRR vs Accounting Revenue — Monthly Reconciliation Example.
Active subscribers: 142
Average monthly plan value: €199
MRR (operational metric): €28,258
Accounting revenue (IFRS 15 recognition):
Monthly subscriptions (recognised in full): €18,640
Annual subscriptions — current month’s portion: €8,900 (Annual prepayments of €106,800 ÷ 12 months)
Project / setup fees — recognised this month: +€718
Monthly recognised revenue (P&L): €28,258
MRR matches recognised revenue
Deferred revenue on balance sheet = remaining annual sub value: €106,800 annual subs × (11/12) months remaining = €97,900 deferred
Section 3 — Revenue Recognition Under IFRS 15
The five-step model, performance obligations in SaaS contracts, and how to apply it in practice
The IFRS 15 Five-Step Model
IFRS 15 (Revenue from Contracts with Customers) is the accounting standard that governs when and how revenue is recognised for IT and SaaS businesses. It replaced previous standards in 2018 and applies to all Estonian companies reporting under IFRS — which includes all OÜ companies that are either listed, have investor requirements, or are part of a group that requires consolidated IFRS accounts.
A binding agreement with a customer — signed SaaS agreement, purchase order, or accepted online terms
Each distinct service promise: subscription access, initial setup, implementation, support tiers, training
Total consideration the seller expects to receive — fixed fee, variable, discounts, free trial periods
Split the transaction price across each performance obligation based on standalone selling prices
Revenue for each obligation recognised when (or as) that obligation is satisfied — subscription: over time; setup: at point of completion
Identifying Performance Obligations in a SaaS Contract
| Contract Element | Distinct Performance Obligation? | Recognition Timing | Typical Accounting Treatment |
|---|---|---|---|
| Monthly/annual SaaS subscription | Yes — core ongoing service | Over time (monthly, as access is provided) | Recognise 1/12 per month; deferred for prepaid amounts |
| One-time setup or onboarding fee | Depends — if not distinct from subscription: combined | Over subscription term if not distinct; at completion if distinct | Usually recognised over expected subscription life, not upfront |
| Implementation / customisation | Yes if customer can benefit separately | At completion (point in time) or over project duration | Project percentage-of-completion or milestone method |
| Annual support / maintenance | Yes — distinct from core subscription | Over the support period (ratably) | Deferred and released monthly over support term |
| Professional services (consulting hours) | Yes — distinct | As hours are delivered (over time) | Recognise at billing if billed on time and materials basis |
| Training modules (self-service) | Depends — if included in subscription: not distinct | With subscription if not distinct | No separate recognition if included in subscription price |
| Free trial period | Not a performance obligation — no consideration | N/A | No revenue; subscription term begins at paid period |
Deferred Revenue — The Balance Sheet Impact
When a customer pays for a subscription in advance — a common model for annual plans — the cash received creates a deferred revenue liability. This liability is released to revenue ratably over the subscription term. A SaaS business with 50% of customers on annual plans and €500,000 ARR will have approximately €250,000 in deferred revenue on its balance sheet at any point — real cash held but not yet recognised as earned.
Monthly subscription (€200/month)
• Customer pays €200 on the 1st of each month
• Revenue recognised in full: €200 in that month
• No deferred revenue — cash and recognition are simultaneous
• Balance sheet: no deferred revenue liability
• Cash flow: predictable but requires monthly collection
Annual subscription (€2,000/year upfront)
• Customer pays €2,000 on 1 January for the full year
• Revenue in January: €2,000 ÷ 12 = €166.67
• Deferred revenue on 1 January: €2,000
• Deferred revenue releases: €166.67 per month for 12 months
• Cash flow: better — full payment received upfront
Section 4 — Why Estonia for IT and SaaS — The Tax Advantages
How Estonia’s corporate tax structure creates a specific competitive advantage for software companies
The 0% Corporate Tax on Retained Profits — SaaS Implications
Estonia’s corporate income tax applies only when profits are distributed — not when they are earned. For a SaaS business that retains most of its profits to fund growth (marketing, product development, hiring), this creates an immediate compounding advantage: every euro of retained profit reinvested in the business has not been reduced by a 20–25% corporate tax charge that would apply in most EU jurisdictions.
A UK or German SaaS company retaining €500,000 of annual profit would pay approximately €100,000–125,000 in corporate income tax before reinvestment. An Estonian SaaS company retaining the same profit pays €0 — and can reinvest the full €500,000. Over five years, this difference compounds significantly.
The Compounding Advantage — Estonia vs Germany (5-Year Model)
Annual net profit retained: €500,000 | Reinvestment rate: 100% (growth-stage company)
Germany (25% corporate tax on profit):
Year 1 after-tax retained: €375,000
Year 2 after-tax retained: €375,000
Year 3 after-tax retained: €375,000
5-year total retained: €1,875,000
Tax paid over 5 years: €625,000
Estonia (0% on retained profits):
Year 1 after-tax retained: €500,000
Year 2 after-tax retained: €500,000
Year 3 after-tax retained: €500,000
5-year total retained: €2,500,000
Tax paid over 5 years: €0 (tax deferred until distribution)
Additional capital available for reinvestment: €625,000
Effective 5-year advantage: 33% more capital retained
* 22% dividend tax applies when profits are eventually distributed | But distributed after growth — on a larger base
R&D Cost Treatment — Expense vs Capitalise
Software development costs require careful analysis under IAS 38 (Intangible Assets). The standard distinguishes between research activities (always expensed) and development activities (capitalised once specific criteria are met). For a SaaS company, this means distinguishing between costs incurred exploring whether a feature is feasible (research — expense) and costs incurred building a confirmed feature with a defined specification and reliable completion timeline (development — capitalise).
| Cost Category | Research or Development? | Treatment | Documentation Needed |
|---|---|---|---|
| Feasibility studies — can we build X? | Research | Expense immediately | N/A — no capitalisation documentation needed |
| Architecture and design after decision to build | Development (IAS 38 criteria met) | Capitalise as intangible asset | Technical specification; project plan; ability and intent to complete |
| Coding of confirmed features | Development | Capitalise | Time logs allocated to specific features; specification documents |
| Testing and quality assurance | Development (if specific to new feature) | Capitalise (up to completion) | Test plans linked to specific development projects |
| Bug fixes in existing software | Maintenance | Expense immediately | N/A — maintenance of existing asset, not new development |
| Significant enhancement that substantially changes capability | Development | Capitalise | Clear articulation of how the enhancement extends the asset’s capabilities |
| Developer salaries (mixed research/development) | Allocate by activity | Expense: research portion; Capitalise: development portion | Time sheets or sprints tagged to research vs development activities |
Section 5 — IP Ownership and Royalty Taxation
Holding IP in Estonia, royalty streams, and how to structure software licensing
Holding IP in an Estonian OÜ — The Structural Advantage
Intellectual property developed by an Estonian OÜ — software code, algorithms, brand, proprietary processes — is owned by the OÜ. When the OÜ licences this IP to customers or to related entities, royalty income flows to the OÜ as revenue. Under Estonia’s 0% retained profits structure, these royalties accumulate tax-free until distributed.
This creates an efficient structure for software companies with global customers: the Estonian OÜ owns the IP, licences it globally, collects royalties worldwide, and retains them for reinvestment — without triggering corporate income tax at the IP-holding entity level until distribution occurs.
IP Ownership. The OÜ legally owns all IP developed by its employees and contractors — document this in employment and contractor agreements.
Licence Agreements. Customers receive a licence to use the software, not ownership of it. Licence terms define permitted use, territory, and duration.
Royalty Income. Fees paid by licensees are royalty income for the OÜ. Recognised when the licence obligation is met — over the licence term for ongoing licences.
Inter-Company Licensing. If the OÜ licences IP to a subsidiary or related company, the royalty must be set at arm’s length — transfer pricing rules apply.
Royalties Received from Outside Estonia — Withholding Tax
When a foreign company pays royalties to your Estonian OÜ, the payer’s country may deduct a withholding tax before remitting the payment. Estonia has double tax treaties with over 60 countries that typically reduce withholding tax on royalties to 5–10% (sometimes 0%). The withheld amount is generally creditable against your Estonian tax liability when profits are distributed.
| Country of Royalty Payer | WHT Rate (standard treaty) | Treaty Benefit Available? | Action Required |
|---|---|---|---|
| Germany | 5–10% (Estonia-Germany DTT) | Yes — reduce to treaty rate | Provide Estonian tax residency certificate to German payer |
| Finland | 5% (Estonia-Finland DTT) | Yes | Residency certificate to Finnish payer |
| United States | 10% (Estonia-US DTT) | Yes | W-8BEN-E form filed with US payer; treaty reduces standard 30% WHT |
| United Kingdom | 0% (Estonia-UK DTT) | Yes — 0% if conditions met | Residency certificate; confirm royalty qualifies under treaty |
| Non-treaty country | Varies (15–30% typical) | No treaty — full rate applies | Budget for WHT cost; may be creditable on dividend distribution |
Section 6 — Remote Team Payroll
Paying employees and contractors across multiple countries — compliance requirements and practical options.
The Core Problem: One Company, Many Jurisdictions
IT and SaaS companies are typically remote-first. A 10-person team might include developers in Georgia, Poland, and Portugal, a designer in Spain, and a sales lead in Germany. Each of these individuals — if they are employees rather than independent contractors — creates an employment law, social security, and payroll tax obligation in their country of residence, regardless of where the company is registered.
Estonian payroll (TSD declaration, social tax, income tax) satisfies your obligations for Estonian-resident employees. It does not satisfy German, Spanish, Polish, Portuguese, or Georgian employment law. Each country has its own system. The consequences of non-compliance include back-assessed social contributions, fines, employee benefit disputes, and in some cases personal liability for management.
| Option | How It Works | Cost | Best For | Key Limitation |
|---|---|---|---|---|
| Estonian payroll only | All staff paid via TSD; social tax paid to EMTA | Low | Team genuinely based in Estonia | Non-compliant for non-Estonian residents |
| Employer of Record (EOR) | Third party (Deel, Remote, Multiplier) acts as legal employer in each country | €400–900/person/month | 1–4 employees per country; early stage | Higher cost; less contractual control |
| Local entity / subsidiary | Register a company in each employee’s country | High — ongoing compliance per country | 5+ employees in the same country | Administrative burden; permanent establishment implications |
| Genuine independent contractor | Individual operates as freelancer; invoices Estonian OÜ | Low | Truly self-employed individuals | Misclassification risk if worker looks like employee |
| Posted worker (EU) | Estonian employee temporarily works in another EU country with A1 certificate | Low-Medium | Short-term assignments < 24 months | Time-limited; specific social security treaty required |
Employee vs Independent Contractor — The Misclassification Risk.
The single most common payroll compliance error in remote IT and SaaS companies is treating employees as contractors. If an individual works exclusively (or primarily) for your company, follows your direction on how work is performed, uses your tools, and has no independent business risk, most countries will classify them as an employee — regardless of what the contract says. Misclassification discovered during a tax audit results in the company being assessed for all unpaid employer social security contributions, income tax withholding, and penalties going back to when the relationship started.
Genuine Contractor Indicators
- Works for multiple unrelated clients simultaneously
- Controls their own schedule and methods
- Uses their own tools and equipment
- Bears own business and financial risk
- Has their own registered business entity
- Can subcontract or delegate the work
- Not economically dependent on your company alone
Employee Misclassification Indicators
- Works exclusively or primarily for your company
- Follows your management direction on how work is done
- Uses company-provided tools and systems
- No personal financial risk — same outcome whether work goes well or poorly
- Long-term continuous engagement with no termination risk
- Cannot substitute another person without your approval
- Economically dependent — your company is their only income source
Section 7 — Global VAT for IT and SaaS Services
B2B reverse charge, B2C digital services, and how to structure invoicing for global customers
The VAT Framework for IT and SaaS Services
For most IT and SaaS companies, the VAT picture is simpler than it appears — because most customers are businesses, and B2B services use the reverse charge mechanism that eliminates the need to register for VAT in every customer’s country. The complexity arises in the B2C layer and in specific product types that have country-specific rules.
| Customer Type | Customer Location | VAT Treatment | Your Invoice Note | Filing |
|---|---|---|---|---|
| B2B — VAT-registered business | Estonia | 24% Estonian VAT | Standard invoice | Estonian KMD |
| B2B — VAT-registered business | EU (e.g. Germany, France) | 0% — Reverse Charge | ‘Reverse charge — Art. 196 VAT Directive’ | Estonian KMD (zero-rated line); verify VIES |
| B2B — VAT-registered business | UK (post-Brexit) | Outside EU scope — 0% | ‘Outside scope of EU VAT’ | Estonian KMD (outside scope) |
| B2B — VAT-registered business | US, UAE, other non-EU | Outside EU scope — 0% | ‘Outside scope of EU VAT’ | Estonian KMD (outside scope) |
| B2C — individual consumer | EU (any country) | Destination-country VAT rate | Apply local rate; register for OSS if > €10K EU B2C | OSS quarterly return |
| B2C — individual consumer | Non-EU | Generally outside EU VAT scope | No EU VAT | No EU filing for non-EU B2C |
Digital Services — B2C Complexity
If your SaaS product is sold directly to consumers (individuals, not businesses) in EU countries — for example, a consumer productivity app, a direct-to-consumer AI tool, or a B2C subscription service — the destination-country VAT rule applies. Every EU consumer pays VAT at their country’s rate. Once your EU B2C revenue exceeds €10,000, you must register for OSS and file quarterly returns covering all EU B2C sales.
For most B2B SaaS companies, this is not a significant issue — business customers use reverse charge and the €10,000 B2C threshold is rarely reached from the few individual accounts in the customer base. For consumer-facing SaaS products, however, EU B2C VAT compliance is a major ongoing obligation that needs dedicated tooling from day one.
A SaaS product sold exclusively to VAT-registered businesses collects 24% VAT from Estonian business customers (on KMD) and charges 0% to all other EU business clients (reverse charge, verified via VIES). For non-EU customers, the supply is outside scope — no EU VAT at all. Your entire EU VAT obligation is a monthly KMD return covering Estonian sales and your zero-rated EU B2B supplies. No OSS registration needed. No per-country registrations. This is why Estonia is particularly attractive for B2B SaaS — the VAT compliance is minimal.
What This Service Section Covers — All 6 Topics
The IT and SaaS service section covers six dedicated areas, each with its own in-depth guide. Use the topic map below to navigate to the area most relevant to your current situation.
Section 9 — How Company for Business Works With IT and SaaS Clients
Our setup for software companies — metrics integration, investor reporting, and the monthly compliance cycle
The IT/SaaS Accounting Stack
| Layer | Tools We Support | What It Does |
|---|---|---|
| Core Accounting | Merit Aktiva, Xero, QuickBooks | Double-entry bookkeeping, IFRS 15 revenue schedules, deferred revenue tracking |
| Subscription Data | ChartMogul, Baremetrics, Stripe Billing, Paddle | MRR/ARR dashboard; cohort analysis; churn tracking — feeds into financial reporting |
| Payroll (Estonian) | EMTA TSD portal, Merit payroll module | Estonian employee payroll, TSD declarations, social tax, income tax withholding |
| Payroll (International) | Deel, Remote, Multiplier — EOR for non-Estonian staff | Legal employment in 100+ countries; handles all local compliance |
| Banking | LHV, Wise Business, Revolut Business | Multi-currency accounts; bank feed to accounting software |
| VAT Filing | EMTA e-Tax (KMD + OSS), manual for UK/non-EU | Monthly KMD, quarterly OSS (if B2C consumer sales), other filings as needed |
Monthly Compliance Timeline
Monthly close: revenue recognition schedule updated, deferred revenue released, subscription movements posted
Management accounts and MRR report sent to founders/board — P&L, balance sheet, MRR waterfall
Estonian payroll TSD filed; social tax and income tax paid; international EOR invoices reviewed
Monthly KMD filed and VAT paid; input VAT reclaimed; reverse-charge entries declared
OSS return prepared if applicable; investor update pack prepared; R&D capitalisation review
Annual report filed with Business Register; auditor liaison if audit required
Pricing for IT/SaaS Clients
| Package | Suitable For | Included | Monthly Fee |
|---|---|---|---|
| IT/SaaS Starter | Bootstrapped product; < €10K MRR; Estonian team only | Monthly bookkeeping, KMD, deferred revenue tracking, annual report | From €200/month |
| IT/SaaS Growth | Funded or growing; €10K–100K MRR; remote team | All Starter + EOR invoice processing, MRR reporting, OSS if applicable | From €350/month |
| IT/SaaS Scale | Series A+; >€100K MRR; multi-country team; investor board packs | All Growth + investor reporting, R&D capitalisation, IP licensing support | From €600/month |
| Custom | Complex multi-entity; international IP structure; US/UK operations | Tailored scope; transfer pricing documentation; group consolidation | On request |