IP and Royalty Taxation for Estonian IT Companies

How to structure IP ownership in an Estonian OÜ, account for royalty income, manage withholding tax on cross-border royalty payments, apply Estonia’s patent box regime, and handle intercompany IP licensing at arm’s length.

IP Ownership Royalty Recognition Withholding Tax DTT Credits IP Box Transfer Pricing IP Transfers
0% Corp Tax on Retained
60+ Estonia DTTs
5–10% Typical WHT Rate
IP Box Tax Preference
€100K TP Doc Threshold
FMV IP Transfer Price

5 Key Takeaways From This Page

IP ownership by the Estonian OÜ is the default — document it
All intellectual property created by employees and contractors during their engagement belongs to the OÜ by default under Estonian law — but only if the employment or contractor agreement explicitly states this. Without the clause, employees may retain individual moral rights and contractors may retain ownership of their deliverables.
Royalty income in the OÜ accumulates tax-free until distribution
Estonia’s 0% retained profit structure means that royalties, SaaS subscription revenue, and software licence fees all accumulate in the OÜ without corporate income tax until distributed as dividends. This is the central tax advantage of the Estonian IP holding structure.
Withholding tax (WHT) is deducted before you receive the royalty
When a foreign company pays royalties to your Estonian OÜ, they deduct WHT before remitting. You receive the net amount. The gross royalty (before WHT) is your revenue. The WHT is a foreign tax credit — claimable when you distribute dividends and pay Estonian corporate income tax.
Intercompany IP licences must be at arm’s length
If your Estonian OÜ licences its IP to a related company (a subsidiary, sister company, or holding company), the royalty rate must be what independent parties would agree. Setting it artificially low shifts profit to a lower-tax entity — EMTA can reassess and apply the arm’s-length rate.
IP transfers require a fair market value — and EMTA scrutinises them
Transferring IP out of your Estonian OÜ to another entity (at any price below market) is treated as a deemed distribution of the difference. EMTA assesses IP transfers with increasing scrutiny, particularly when Estonian founders transfer IP to foreign holding companies without economic substance.

What IP and royalty tax issues does an Estonian IT or SaaS company face? The primary issues are: establishing clear IP ownership in the OÜ through properly drafted employment and contractor agreements, correctly accounting for royalty income (recognised over the licence term under IFRS 15), managing withholding tax on cross-border royalty payments (deducted by foreign payers under their domestic law, reduced by double tax treaty rates), understanding and applying Estonia’s IP box regime where relevant, and complying with transfer pricing rules for any intercompany IP licensing arrangements. This page covers each area in full.

Section 1 — IP Ownership: Establishing Clean Title in Your Estonian OÜ

Employment clauses, contractor agreements, and what Estonia’s Copyright Act says about software ownership.

The Default Rule — and Why It Is Insufficient

Estonian law provides that intellectual property created by an employee in the course of their employment belongs to the employer — unless the employment contract provides otherwise. For software specifically, the Copyright Act (Autoriõiguse seadus) states that the economic rights to software created in the course of employment belong to the employer by default.

Despite this default, every employment and contractor agreement should include an explicit IP assignment clause. The reasons are practical: the default applies only to works created ‘in the course of employment’ — which creates ambiguity for work done on personal time, work that pre-existed the employment, or work created by contractors (who are not employees and thus outside the default rule entirely). Without explicit clauses, disputes arise and IP chains become unclear when approaching investors or acquirers.

Scenario Default Ownership What Goes Wrong Without a Clause Required Clause
Employee creates core product features during working hours OÜ (employer default) Usually fine — but ambiguous for overtime work; personal projects may overlap IP assignment confirming all work-related IP belongs to OÜ
Employee creates feature using personal time and tools Employee personally OÜ has no claim without explicit assignment Work-for-hire clause covering all IP related to the business area
Contractor delivers software module Contractor (not an employee) Contractor retains copyright; OÜ only has usage rights Explicit IP assignment in contractor agreement — all deliverables assigned to OÜ on creation
Contractor reuses components from their own library Contractor personally OÜ gets licence to use, not ownership; IP chain unclear IP background clause: distinguish between background IP (contractor keeps) and foreground IP (assigned to OÜ)
Founder builds initial product before company incorporation Founder personally OÜ does not own the foundational IP Founders must formally assign pre-incorporation IP to OÜ after incorporation — documented assignment agreement

IP Assignment — Key Contract Clauses

Every employment contract and contractor agreement for roles that create IP should include these essential clauses. They should be reviewed by a lawyer familiar with both Estonian and any relevant foreign law if employees are based abroad.

Assignment Clause
All IP created in connection with company business is assigned to the OÜ automatically on creation. No separate assignment documents required per deliverable.
Moral Rights Waiver
Employee/contractor waives moral rights to the extent permitted by applicable law — allows OÜ to modify, adapt, and publish without individual attribution requirements.
Background IP Declaration
Pre-existing IP brought in by the employee/contractor is declared and listed. OÜ receives a licence to use it; ownership is not claimed. Prevents disputes over prior work.
Jurisdiction Coverage
Assignment covers worldwide rights — not just Estonia. Relevant for software which is protected in multiple jurisdictions simultaneously.
Survival After Termination
IP assigned during employment/engagement remains assigned after termination. Former employees/contractors cannot later claim rights to work already delivered.
Founder IP Assignment — The Critical Step Before Fundraising: One of the most common gaps discovered during Series A due diligence is that the OÜ does not formally own the IP it was built on — because the founders wrote the early code before the company existed, and no formal assignment was ever made. Investors require clean IP ownership chains as a condition of investment.

Founder IP Assignment ProcessPre-Incorporation IP: Founder A wrote the initial prototype (2,800 lines) before OÜ was formed. Founder B designed the UX and brand assets before incorporation.

Required Action After Incorporation:

Step 1: Prepare ‘IP Assignment Agreement’ between each founder (personally) and the OÜ

Step 2: List all pre-incorporation IP: software, designs, brand assets, databases

Step 3: Define consideration — typically nominal (€1) or equity confirmation

Step 4: Execute and sign — both parties (founder as individual + OÜ representative)

Step 5: Board resolution acknowledging the assignment and recording it

Step 6: Keep the executed agreement in the company’s corporate book permanently

Without this assignment, the OÜ has at best an implied licence — not ownership. Investors and acquirers will request this document during due diligence. Can be done retrospectively but some jurisdictions require fresh consideration.

Section 2 — Royalty Income: Accounting and Recognition

When royalty income is earned, how it is measured, and how to record it in the OÜ accounts.

Types of IP Income an Estonian IT Company May Receive

Income Type Description IFRS 15 Recognition Timing Account to Use
SaaS subscription (software access) Monthly/annual access to software product Over the subscription term — monthly Revenue — Monthly/Annual Subscriptions
Perpetual software licence One-time right to use software as-is, in perpetuity At delivery of licence (point in time) Revenue — Software Licences
Term software licence Right to use software for a defined period Over the licence period (over time) Revenue — Software Licences
Royalty on unit sales/downloads Fee per copy sold or download As each sale or download occurs Revenue — Royalties
OEM / white-label licence Fee for embedding your software in another product Per-unit: as each unit ships; flat fee: over term Revenue — Licensing / Royalties
Patent licence Right to use a patented method or technology As licenced activity occurs (usually over time) Revenue — Patent Licences
Source code sale Outright sale of source code ownership At delivery and legal transfer (point in time) Revenue — IP Disposal / Capital Gain

Accounting for Royalty Received with Withholding Tax

When a foreign company pays a royalty to your Estonian OÜ, they deduct withholding tax (WHT) before remitting. The gross royalty (before WHT) is your revenue — the WHT is a tax payment made on your behalf by the foreign payer, which creates a tax asset (foreign tax credit receivable) that is offset against future Estonian tax liabilities.

Royalty Received from German Company (€10,000 gross, 5% WHT)

Account Debit (DR) Credit (CR)
Cash — Bank (net royalty received) €9,500.00
Foreign Tax Credit Receivable (WHT) €500.00
Revenue — Software Licences €10,000.00

Gross royalty = €10,000. German payer withholds 5% (Estonia-Germany DTT rate) = €500. Net received = €9,500. WHT creates a deferred tax asset recoverable when Estonian dividends are distributed.

Always record gross royalty as revenue — never the net-of-WHT amount.
A common accounting error is to record only the €9,500 net received as revenue. This understates revenue by the WHT amount, loses the tax credit, and creates a P&L that does not match the contractual royalty amount. The correct treatment always records the full €10,000 as revenue, with the €500 WHT as a separate asset. When the company later distributes dividends and pays Estonian corporate income tax, the €500 can be applied against that liability — reducing the cash tax cost.

Royalty Recognition Under IFRS 15 — Usage-Based vs Time-Based

Royalty Structure Recognition Method Monthly Entry Example
Fixed annual fee for unlimited use Recognise ratably over the 12-month licence period DR Deferred Royalty Revenue / CR Revenue (1/12 per month) €12,000 annual licence → €1,000/month
Per-unit royalty (e.g. per download) Recognise as each unit of activity occurs DR Royalty Receivable / CR Revenue as each unit occurs €2 per API call billed monthly
Minimum fee + usage overages Fixed floor recognised monthly; usage above minimum in month of occurrence Base: DR Cash / CR Revenue monthly; Overage: on usage data €500/month min + €0.10 per call above 5,000
Perpetual licence (one-time payment) Recognise at delivery — point in time DR Cash / CR Revenue at contract date €50,000 perpetual source code licence
Milestone-based licence Recognise at milestone completion DR Cash or Receivable / CR Revenue at milestone €5,000 on completion of each integration phase

Section 3 — Withholding Tax on Cross-Border Royalties

What WHT is, which countries apply it, how Estonia’s DTT network reduces it, and how to claim the credit.

How Withholding Tax Works

Withholding tax (WHT) is a tax on certain cross-border payments — including royalties — where the tax is ‘withheld’ (deducted) by the payer before remitting the net amount to the recipient. The withholding is done by the payer on behalf of the tax authority in their jurisdiction. As the recipient, your Estonian OÜ receives less cash than the gross royalty — but the withheld amount represents a tax payment made on your behalf in the payer’s country.

Without a double tax treaty, WHT rates on royalties can be 20–30%. Estonia’s network of over 60 DTTs typically reduces this to 0–10%. The treaty rate applies only if the Estonian OÜ can prove it is an Estonian tax resident — done by providing a tax residency certificate from EMTA.

WHT Rates on Royalties — Estonia’s Double Tax Treaties (Selected Countries)

Country DTT Royalty WHT Rate Domestic Rate (No Treaty) Form Required Key Notes
🇩🇪 Germany 5% or 10% 15% domestic Freistellungsbescheinigung Rate depends on IP type: 5% for patents/software; 10% for other
🇫🇮 Finland 5% 20% domestic Certificate of residence Standard treaty rate; Finland applies proactively
🇸🇪 Sweden None (0%) 0% domestic already Certificate if requested Sweden imposes no WHT on royalties regardless
🇬🇧 United Kingdom 0% (post-Brexit DTT) 20% domestic W-8BEN-E or cert of residence Estonia-UK DTT effective; 0% on qualifying royalties
🇺🇸 United States 10% 30% domestic W-8BEN-E form (IRS) W-8BEN-E mandatory — reduces 30% domestic rate to 10%
🇳🇱 Netherlands 5% Not applicable Certificate of residence EU Interest & Royalties Directive may provide 0%
🇯🇵 Japan 10% 20% domestic Certificate of residence Apply before payment to avoid 20%
🇨🇦 Canada 10% 25% domestic Certificate of residence Estonia-Canada DTT provides 10%
🇦🇺 Australia 10% 30% domestic Certificate of residence Estonia-Australia DTT effective
Non-treaty country Full domestic rate Varies: 15–30% No treaty applies Budget for full WHT rate; may not be creditable

Obtaining a Tax Residency Certificate from EMTA

To claim treaty-reduced WHT rates, your Estonian OÜ must prove to the foreign payer that it is an Estonian tax resident. This is done by providing a Tax Residency Certificate (Maksuresidentsuse tõend) issued by EMTA. The certificate confirms that the OÜ is subject to taxation in Estonia and is entitled to treaty benefits.

1
Apply via e-Tax Portal
Log in to emta.ee → Applications → Tax Residency Certificate
2
EMTA Issues Certificate
Processing time: 5–10 business days. Valid for 12 months.
3
Provide to Foreign Payer
Send certificate to royalty payer before first payment
4
Annual Renewal
Certificates expire — renew annually before expiry
5
WHT Applied at Treaty Rate
Payer withholds at DTT rate instead of domestic rate
Obtaining a Tax Residency Certificate from EMTA
Apply via e-Tax Portal → EMTA issues certificate (5–10 business days) → Provide to foreign payer → WHT applied at treaty rate. Certificates valid for 12 months.

Using WHT Credits Against Estonian Tax

The WHT paid by foreign payers is a foreign tax credit — it reduces your Estonian tax liability when you distribute dividends and pay the 28% corporate income tax. Estonia’s Income Tax Act allows foreign taxes paid on income to be credited against the Estonian tax liability on dividend distribution, up to the amount of Estonian tax that would have been due on that income.

WHT Credit Application — Dividend Distribution

Company distributes €100,000 in dividendsEstonian dividend tax (28% applied as 22/78 on net): €28,205.13

Foreign WHT credits accumulated:
WHT from German royalties (5% on €80,000): €4,000
WHT from US royalties (10% on €30,000): €3,000
WHT from Australian royalties (10% on €15,000): €1,500
Total foreign WHT credits available: €8,500

Estonian dividend tax after credits:
Estonian dividend tax: €28,205.13
Less: foreign WHT credits applied: −€8,500
Net Estonian dividend tax payable: €19,705.13

WHT credits prevent double taxation | Credits cannot exceed the Estonian tax on the same income | Maintain WHT certificate per payer per year.

Section 4 — Estonia’s IP Box Regime

The tax preference for qualifying IP income and how it interacts with the 0% retained profit structure.

What the IP Box Is

An IP box (also called patent box or innovation box) is a special tax regime that provides a reduced effective tax rate on income derived from qualifying intellectual property — typically patents, copyrights on computer programs, and certain other registered IP. Estonia has an IP box that was introduced to align with the OECD’s modified nexus approach under BEPS Action 5, which requires a qualifying link between the IP income and R&D activity that generated the IP.

Estonia’s existing 0% retained profits tax already provides significant IP-holding benefits compared to most OECD countries. The IP box provides an additional preference: income from qualifying IP assets may benefit from a reduced tax rate on distribution.

Feature Estonia’s General Tax Regime Estonia’s IP Box Enhancement Comparison to EU IP Boxes
Tax on retained IP income 0% (no tax until distribution) 0% regardless (already zero) Most EU IP boxes: 5–10% on retained income
Tax on distributed IP income 28% dividend tax on distribution Potentially reduced rate Netherlands IP box: 9% on qualifying
Qualifying IP types All income — no IP distinction Patents, copyright software, database rights Varies by country — usually requires registration
Nexus requirement Not applicable Yes — IP linked to R&D activity BEPS-compliant: in-house R&D, not purchased IP
Documentation required Standard accounting R&D activity and IP-income nexus substantiation Detailed R&D cost tracking, project records
Estonia’s IP box is most valuable at high income levels and high distribution rates
Because Estonia already provides 0% tax on retained profits, the IP box’s primary benefit materialises when profits are actually distributed. For a growth-stage SaaS company retaining all profits for reinvestment, the IP box provides no immediate cash benefit over the standard regime. For a more mature business distributing profits to founders, the IP box reduces the effective tax rate on distributions attributable to qualifying IP income.

Section 5 — Transfer Pricing for Intercompany IP Licensing

Arm’s-length pricing, documentation requirements, and the risk of IP underpricing.

When Transfer Pricing Rules Apply to IP

Transfer pricing (TP) rules apply whenever your Estonian OÜ transacts with a related party — a company under common ownership or control. The most common IP-related TP transactions are: (1) the OÜ licences its software IP to a related sales entity in another country, (2) a foreign holding company licences IP down to the Estonian OÜ for a royalty, and (3) the OÜ transfers IP ownership to a related entity at a negotiated price.

In each case, the price must be what independent third parties would agree in a comparable transaction — the arm’s-length principle. Setting prices too low in favour of a low-tax entity (profit shifting) is the primary concern. Setting prices too high (to strip profit from a high-tax entity) also creates TP risk. Both directions can be challenged by EMTA.

TP Scenario Risk Arm’s-Length Standard Documentation Required
OÜ licences IP to UK subsidiary at 5% royalty (below market) EMTA adds back the difference as a deemed distribution; 28% corporate tax assessed Market royalty rate for comparable software IP (typically 5–25% depending on IP value and profitability) Benchmarking study using ORBIS or similar database; functional analysis; comparables analysis
UK subsidiary licences IP to OÜ at 30% royalty (above market) UK tax authority may challenge; OÜ EBITDA reduced; dividend capacity reduced Same — market rate applies in both directions Benchmarking study; economic analysis of IP ownership function
IP transferred from OÜ to Cayman Islands holding at below FMV EMTA assesses the undervalue as a deemed distribution at 28% distribution tax Fair market value of IP at transfer date — requires formal IP valuation Independent IP valuation report; legal and tax advice in both jurisdictions; EMTA notification
Management fee paid by OÜ to holding company (includes IP cost) Bundled pricing makes it hard to verify arm’s length Each service component must be priced separately; IP element extracted and benchmarked Service description, time records, cost-plus analysis for each service component

Benchmarking an Intercompany Royalty Rate

The most common method for pricing an intercompany IP licence is the Comparable Uncontrolled Price (CUP) method — finding comparable arm’s-length royalty rates in the market and applying them. For software IP, databases like ORBIS (Bureau van Dijk) and Royalty Range contain thousands of publicly disclosed software licence agreements that EMTA accepts as benchmarking comparables.

Software Royalty Benchmarking — Indicative Ranges

Enterprise SaaS platform (core product IP): 8–18% of revenueConsumer software / mobile app: 3–8% of revenue

Embedded technology / components: 3–7% of revenue

Database rights (content-rich): 2–6% of revenue

Brand / trademark (technology sector): 1–3% of revenue

Patent (high-value innovation): 10–25% of revenue

Key factors that move rates within ranges:
+ Proprietary, difficult-to-replicate technology → higher end
+ Strong brand and network effects → higher end
+ Rapidly depreciating technology → lower end
+ IP easily replaceable by alternatives → lower end

EMTA accepts ORBIS, Royalty Range, ktMINE database searches. Document the search parameters and selected comparables. Review annually.

Section 6 — IP Transfers and Restructuring

What happens when IP moves between entities — valuations, deemed distributions, and EMTA’s scrutiny.

Why Founders Transfer IP — and Why EMTA Watches

Estonian founders occasionally consider transferring IP from their Estonian OÜ to a foreign holding company — typically a Cayman Islands, Netherlands, or Luxembourg entity — for structural reasons: to hold IP above the operating company, to create a group structure for fundraising, or to redomicile the IP in preparation for an exit in a different jurisdiction.

EMTA scrutinises these transfers for two reasons: (1) if IP is transferred below fair market value, the difference is treated as a deemed distribution (subject to 28% corporate income tax), and (2) the OECD BEPS framework requires that IP location follow genuine economic substance — a transfer of IP to a shell company with no staff, no decision-making, and no actual R&D activity is increasingly challenged by both EMTA and the receiving jurisdiction’s tax authority.

Substance requirement for IP-holding entities
Post-BEPS, an IP-holding entity must have genuine economic substance: employees who make key decisions about IP development and exploitation, a physical presence where those decisions are made, and actual R&D activity or oversight activity in the jurisdiction. Transferring IP to a Dutch BV or Luxembourg SARL that has no employees and no actual activity in those countries creates BEPS risk: the OECD and EU member states have committed to challenging ’empty shell’ IP structures. An IP transfer to a genuinely operational entity with real substance is defensible; a transfer to a mailbox company is not.

The IP Valuation Requirement

When IP is transferred between related parties, the transaction must be priced at fair market value (FMV). FMV is what a willing buyer and willing seller would agree in an arm’s-length transaction with full information. For significant IP transfers — particularly the core software IP of a SaaS company — this requires a formal independent valuation using accepted methods.

Valuation Method How It Works When Appropriate Strengths and Limitations
Discounted Cash Flow (DCF) Project future royalty income from the IP; discount at appropriate WACC Primary method for income-generating IP like SaaS software Most accepted method; requires reliable revenue projections; sensitive to assumptions
Relief from Royalty (RfR) Estimate what the company would pay if it had to licence the IP from a third party Widely used for software and brand IP Requires benchmarked royalty rate; gives value = NPV of royalty stream avoided
Comparable Transaction Find comparable IP sale prices in the market When comparable deals are available Clean method but comparable data for proprietary software is often limited
Cost-Based (Development Cost) Historical cost of developing the IP as a proxy for value Only for early-stage IP with limited track record Usually understates IP value for proven, revenue-generating software

Accounting for an IP Transfer in the Estonian OÜ

When the OÜ transfers IP to a related entity at fair market value, the accounting depends on whether FMV exceeds the carrying value of the IP on the balance sheet. The difference is a gain — recognised in the P&L. If the IP was internally developed and expensed under IAS 38 (never capitalised), its carrying value is zero and the entire transaction price is a gain.

IP Transfer — Software Sold to UK Subsidiary at Agreed FMV of €500,000

Account Debit (DR) Credit (CR)
Receivable from UK Subsidiary €500,000
Accumulated Amortisation €40,000
Capitalised Software Development €200,000
Gain on IP Disposal €340,000

IP was capitalised at €200,000; accumulated amortisation €40,000; carrying value €160,000. FMV = €500,000. Gain = €500,000 − €160,000 = €340,000 recognised in P&L. If the IP had been fully expensed (internally developed, not capitalised): carrying value = €0; full €500,000 is P&L gain.

The gain on IP transfer is not immediately subject to corporate income tax in Estonia
Estonia’s 0% retained profit structure means the €340,000 gain on IP disposal, while recognised in the P&L, does not immediately create a corporate income tax liability. It increases the retained earnings available for distribution — and the 28% distribution tax applies when and if those retained earnings are distributed as dividends. This is another structural advantage of holding IP in an Estonian OÜ: even on an IP exit, no immediate tax crystallises until the profit is distributed.

Frequently Asked Questions

For each country’s developers, you need employment or contractor agreements that contain an IP assignment clause valid under that country’s law. Estonian law’s default IP assignment for employees applies only to Estonian-resident employees. For developers in Germany, UK, Poland, or elsewhere, the assignment must comply with local employment and copyright law. German law requires specific consideration for the IP assignment in some cases. UK law has strong employed inventor rights for patents. The practical approach: use local legal counsel in each country to draft country-specific IP assignment clauses that ensure the OÜ gets clean title to all IP created, regardless of where the developer is located. Your EOR platform (Deel, Remote) typically includes jurisdiction-specific employment templates with IP assignment provisions.

Possibly — but it needs verification. US WHT on royalties paid to non-US persons is generally 30% unless reduced by a treaty. Under the Estonia-US DTT, the rate is reduced to 10% for royalties. However, the 10% rate applies only if the Estonian OÜ has filed a W-8BEN-E form with the US payer certifying its Estonian tax residency and treaty eligibility. If no W-8BEN-E was filed, the US payer may be incorrectly not withholding — which could expose them to US IRS penalties and potentially expose you to a demand for back-WHT from the IRS. Alternatively, if the payment is for services (not royalties), WHT may genuinely not apply. Review the nature of the payment: if it is for providing access to software (subscription/SaaS), it may be treated as a services payment rather than a royalty in the US, which changes the WHT analysis. Provide a W-8BEN-E if not already done.

No — it requires careful preparation. The steps are: (1) commission an independent IP valuation using DCF or Relief from Royalty methods; (2) structure the transfer at fair market value — the Netherlands entity must pay the Estonian OÜ the FMV, which is either cash or a receivable; (3) ensure the Netherlands entity has genuine economic substance — employees, directors, and active management in the Netherlands; (4) review the Dutch royalty box regime for IP income tax treatment in the Netherlands (the ‘Innovation Box’ provides a 9% rate on qualifying IP income); (5) structure the intercompany licence from the Netherlands entity back to the Estonian OÜ at arm’s length; (6) notify EMTA of the cross-border transaction if required under Estonian TP reporting rules. The total cost of doing this properly — legal, tax advisory, valuation — is typically €15,000–50,000 depending on IP complexity. It only makes financial sense if the tax saving over 5–10 years exceeds this cost. Do not proceed without comprehensive advice in both jurisdictions.

In economic terms, SaaS subscription fees are functionally similar to royalties — you are paid for the right to use software you developed. In accounting terms, they are recognised as service revenue under IFRS 15 (over the subscription period) rather than as royalty income in the traditional sense. For tax purposes, the classification matters in cross-border contexts: if a US customer pays you a subscription fee for cloud-hosted software where they never download or possess the software, the US IRS typically treats this as a services payment (not a royalty), which means US WHT on royalties does not apply. If the customer downloads software and uses it locally, it is more likely treated as a royalty for WHT purposes. This distinction is country-specific — Germany, Japan, and some other countries treat SaaS payments differently from the US. For the WHT analysis, the contractual nature of the right granted (software-as-a-service vs licence to use software) determines the classification.

WHT credits in Estonia can only be applied against the Estonian distribution tax (corporate income tax on dividends) when dividends are actually distributed. They cannot be refunded in cash, applied against other taxes, or carried forward indefinitely without limit — though in practice there is no time limit on credits accumulated, and they remain available to offset future distribution tax. The credit is calculated per country and per type of income under each DTT. Before declaring a dividend, your accountant should prepare a credit calculation matching each credit to the income it was withheld on and confirming eligibility under the relevant DTT. A €63,000 credit pool is material — it represents €63,000 of distribution tax that will not need to be paid in cash, which at a 28% rate corresponds to €225,000 of dividend distributions that are effectively tax-free from the Estonian perspective.

Need help structuring IP ownership and royalty taxation?

Book a free 30-minute consultation. We review your IP ownership structure, set up royalty accounting, apply the correct WHT credits, and ensure your intercompany licences are at arm’s length.

companyforbusiness.ee →