An Estonian OÜ for App Developers: App Store and Google Play Payouts, VAT and Reporting [2026]
If you sell an app or in-app content through Apple’s App Store or Google Play, the platform — not you — is legally treated as the seller to the end customer, and it is the platform that accounts for VAT in the EU, UK and most other markets where it operates. That single mechanism, called the deemed supplier rule, is the most important thing an app developer running an Estonian OÜ needs to understand, because it changes who owes VAT without removing your own reporting, bookkeeping or tax obligations.
The short answer
Apple and Google are the deemed suppliers for app and in-app-purchase sales through their stores: they receive and supply the service to the consumer, and they handle end-user VAT in the EU, UK and many other territories.
This is a shift of who accounts for VAT, not a disappearance of your obligations — you still book the sale, report it correctly, and reconcile gross payout against net bank deposit.
Sell directly on the web (a subscription outside the stores) and you are back on the hook for consumer VAT yourself, subject to the EU’s €10,000 distance-selling threshold and OSS, which does not cover domestic Estonian sales or B2B.
B2B/enterprise licensing to another VAT-registered business is generally handled under reverse charge: you invoice without Estonian VAT and the business customer self-accounts.
Estonia’s own VAT registration threshold is €40,000 turnover, at a standard rate of 24% (since 1 July 2025); the KMD return is due by the 20th of the following month.
The developer account and the invoicing entity must match — an account still in a founder’s personal name while the company invoices creates a compliance and payout headache that is entirely avoidable.
Who actually accounts for VAT when your app sells through the App Store or Google Play?
Apple and Google do, for the vast majority of consumer sales. Under the deemed supplier rule, when a platform facilitates the sale of a digital service or in-app content to an end customer, the platform is treated in law as if it received the service from you and supplied it itself to that customer. You are treated as supplying the platform, not the consumer. That reclassification is why Apple and Google collect and remit VAT on end-user purchases across the EU, the UK and a long list of other jurisdictions, and why your App Store or Play Console invoices to consumers already show tax handled.
Is this a removal of your VAT exposure, or just a shift of who reports it?
It is a shift of liability, not a disappearance of it. Apple and Google take on the legal duty to charge and remit VAT to the consumer’s country, which is genuinely valuable — you are not tracking VAT rates across dozens of EU member states plus the UK for every in-app purchase. But your company still has its own accounting entries for every payout, still needs to record the transaction correctly in its books, and still needs to reflect platform sales properly on your own VAT return and annual accounts. Treating a deemed-supplier payout as “tax already dealt with, nothing to do” is the single most common bookkeeping mistake among app-developer OÜs.
How do sales channels compare for who accounts for VAT?
The channel you sell through determines who is legally on the hook for consumer VAT, and that is the single variable that should shape how you set up invoicing and bookkeeping for each revenue stream. The table below maps the channels an app business typically runs through.
Sales channel | Who accounts for end-customer VAT | What you still must report |
|---|---|---|
App Store / Google Play (app purchase, in-app purchase, subscription sold through the store) | Apple or Google, as deemed supplier, in the customer’s country | Gross sales and platform commission in your books; the net payout reconciled against your invoice/report from the store; the sale reflected in your VAT return records even though you charge no VAT yourself |
Direct web subscription or one-off sale to an EU consumer (outside the store) | You, the developer, subject to the EU €10,000 distance-selling threshold and OSS above it | OSS quarterly return once you cross €10,000 in cross-border EU B2C digital sales; Estonian VAT on domestic Estonian consumer sales, which OSS does not cover |
B2B / enterprise licensing to a VAT-registered EU business | The business customer, under reverse charge | Invoice without Estonian VAT, quote the customer’s VAT number, and report the transaction on your KMD and the EU sales list where applicable |
Sales to non-EU consumers or businesses | Generally outside EU VAT scope; local rules of the customer’s country may apply | Keep evidence of customer location; check whether the destination country has its own digital-services VAT/GST regime |
What about selling subscriptions directly on the web, outside the app stores?
Here the deemed-supplier shield disappears and you are the one accounting for VAT. If you sell a subscription or digital add-on straight from your own website to an EU consumer, you are making a B2C digital service sale, and the EU-wide distance-selling rule applies: below €10,000 in annual cross-border B2C digital sales you may charge your home-country VAT rate, and above it you must charge the customer’s country rate and report through OSS (One Stop Shop), which files quarterly. Two things trip people up here. First, OSS does not cover domestic Estonian sales to Estonian consumers — those go through your normal Estonian VAT return. Second, OSS does not cover B2B sales at all; those follow the reverse-charge rules described below.
How does B2B and enterprise licensing work?
When you license your app, API or in-app content to another VAT-registered business anywhere in the EU, the standard mechanism is reverse charge: you issue an invoice without Estonian VAT, and the business customer self-accounts for VAT in its own country. This applies whether the buyer is an enterprise licensing your SDK, a reseller, or a platform integrating your service B2B rather than distributing it to consumers. You still need the customer’s valid VAT number on the invoice and still need to report the transaction correctly on your Estonian VAT return and, where relevant, an EU sales list — reverse charge changes who pays, not whether the sale gets reported.
What about customers outside the EU?
Non-EU consumer and business sales generally fall outside EU VAT scope, but that is not the end of the analysis. If a non-EU customer buys through Apple or Google, the deemed-supplier mechanism may still apply locally, since Apple and Google run equivalent deemed-supplier or marketplace-facilitator regimes in many non-EU markets too. If you sell to non-EU customers directly, check whether their country runs its own digital-services VAT or GST regime — a growing number do — and keep basic evidence of customer location (billing country, IP, payment method country) so you can support the treatment you apply if it is ever questioned.
How do you actually read an app store payout report?
A payout report is not a single number you copy into your books — it is several line items that each mean something different, and the figure that lands in your bank account is the last of them, not the first. Both Apple’s and Google’s reporting show, in substance, the gross price the customer paid, the platform’s commission deducted before payout, an indication that VAT/tax has already been handled on the underlying sale, and, for developers outside the store’s settlement currency, an FX conversion applied before the transfer. The table below names the mechanisms without inventing specific percentages, since commission structures and rates vary by program, content type and platform tier and should be read from your own current agreement rather than assumed.
Line item on the payout report | What it represents | Why it matters for your books |
|---|---|---|
Gross sale / gross proceeds | The price the end customer paid, before any deduction | This is typically the figure you record as gross revenue, matched to the transaction date, not the payout date |
Store commission / service fee | The platform’s cut, deducted before you are paid | This is your cost of sale or a deduction against gross revenue, not something you separately invoice or pay |
Tax handled by platform | Confirmation that end-customer VAT/GST was accounted for by the platform as deemed supplier | You do not add Estonian VAT on top of this sale, but you still record it as a sale in your accounting system and VAT records |
Currency conversion / FX rate applied | The rate used to convert store-currency proceeds into your payout currency | Creates a realised FX gain or loss that belongs in your books separately from the underlying sale |
Net payout / amount transferred | What actually arrives in your bank account | This is the number your bank statement shows; it is never the same figure as gross revenue, and reconciling the two every period is the core bookkeeping task |
Why isn’t your revenue the same as what lands in the bank?
Because between the customer’s payment and your bank balance sit at least three deductions: the store’s commission, any currency conversion, and the payout schedule’s timing lag. Revenue for accounting purposes should generally be recognised at the gross sale amount for the period the customer bought, with the commission booked as a cost, not netted silently out of revenue — netting it out understates your top-line revenue and can distort metrics you might need for investors, lenders or your own annual report. If you only ever book the net bank deposit, your books will not tie out against the store’s own sales reports, and reconciling the two after the fact becomes far harder than doing it correctly each period.
The payout that hits your bank account is the end of a chain of deductions, not the start of your accounting — book the gross sale, the commission, and the FX movement as three separate entries, and the reconciliation takes care of itself.
Do you need to register for Estonian VAT, and at what rate?
You must register once your Estonian VAT-taxable turnover reaches €40,000 in a calendar year, though voluntary registration below that threshold is allowed and is common for app businesses that want to reclaim input VAT on development tools, ad spend or contractor invoices early. The standard Estonian VAT rate is 24%, in force since 1 July 2025. Whether app-store sales count toward that €40,000 threshold depends on how the deemed-supplier transaction is treated in your specific structure, so this is a case to confirm with an accountant rather than assume; direct web sales to Estonian consumers and B2B invoices you issue clearly do count.
What’s the compliance calendar for an app-developer OÜ?
The recurring filings are the same ones every Estonian OÜ carries, and missing them is expensive and personal to board members, not just the company. Keep this list on a calendar rather than remembering it.
KMD (VAT return): monthly, due by the 20th of the following month, once VAT-registered.
TSD (payroll declaration): monthly, due by the 10th, whenever you pay salary, board-member fees or certain other payments.
Annual report (majandusaasta aruanne): due within 6 months of financial year end — 30 June for a calendar-year company — covering revenue, expenses, and the tax treatment of any profit distribution.
Source-document retention: payout reports, invoices, contractor agreements and bank statements kept for 7 years.
Late filing: fines of up to €3,200 per violation, repeatable, and can attach to board members personally, not only the company.
Does Estonia’s 0% tax on retained profit actually fit an app business?
For a bootstrapped app studio reinvesting payouts into development, servers, ads and hiring rather than paying out to founders, it is a genuinely good fit, not a marketing line. Estonia taxes distributed profit at 22%, calculated as 22/78 of the net distribution, and taxes retained/reinvested profit at 0%. An app business plowing this quarter’s App Store and Google Play net revenue straight back into the next feature release, more UA spend, or a new hire pays no corporate income tax on that reinvested amount — the tax point only arrives when profit is actually distributed to shareholders. That reward for reinvestment lines up naturally with how early-stage app studios actually spend their cash, which is why it is worth structuring your distributions deliberately rather than as an afterthought.
How do you pay yourself from an app-developer OÜ?
Two mechanisms, and most founders use a mix: a board-member fee or salary (subject to Estonian payroll taxes, reported via TSD), or a dividend distribution taxed at 22%, calculated as 22/78 of the net amount distributed at the company level. Salary gives you predictable personal income and, where relevant, social-tax-backed benefits; dividends are simpler to administer but only make sense once there is distributable profit and only after the 22/78 charge is accounted for. Neither choice is automatically better — it depends on your personal tax residence, your need for regular income, and whether you would rather leave payout-driven cash in the company to fund the next release under the 0% retained-profit treatment described above.
Why must the developer account be registered in the company’s name?
Because the entity that legally receives the payout has to match the entity that invoices, books the revenue and files the VAT return — and a mismatch between the two is one of the most common, most avoidable messes in this niche. If your Apple Developer Program or Google Play Console account is still registered to a founder personally while the OÜ is the entity doing the accounting, invoicing and VAT reporting, you end up with payouts landing in the wrong name, ownership disputes if a co-founder leaves, and awkward questions from a bank or payment processor about whose money it actually is. Migrating a developer account after the fact is possible with both platforms but takes real lead time and paperwork, so get the account into the company’s name at setup, not after the first six-figure payout arrives. A payment-provider freeze is exactly the kind of problem a name mismatch invites — see what to do if Stripe or PayPal blocks an Estonian company for the pattern.
Where else could this actually be taxed — place of effective management and CFC exposure?
Wherever you, the founder, actually live and run the company day to day. Registering an OÜ in Estonia does not by itself decide where the company is taxed if the real decision-making happens somewhere else: place of effective management, permanent establishment, and CFC (controlled foreign company) rules are the three doors through which your home country can reach in and tax the OÜ as if it were local, regardless of the Estonian registration. This is not a theoretical risk for a solo app developer working from home in another country — tax authorities increasingly look at where strategic decisions are actually made, not just where the certificate of incorporation was issued. Confirm your specific exposure with a local advisor before assuming Estonian registration alone settles the question; this is exactly the kind of honest caveat worth reading before you incorporate, alongside the other downsides of e-Residency worth knowing upfront.
Frequently asked questions
Do I charge VAT on App Store or Google Play sales myself?
No. Apple and Google are the deemed suppliers for consumer sales through their stores and account for end-customer VAT themselves in the EU, UK and many other territories. You still record the sale in your own books and reflect it correctly in your VAT reporting, but you do not add VAT to those transactions yourself.
Does app-store revenue count toward the Estonian €40,000 VAT registration threshold?
It depends on how the deemed-supplier transaction is classified for your specific setup, and this is genuinely a case-by-case question rather than a universal rule. Confirm the treatment with an accountant rather than assuming either way, while direct web sales to Estonian consumers and B2B invoices clearly count.
What is the EU €10,000 threshold, and does it apply to my App Store sales?
The €10,000 figure is the EU-wide distance-selling threshold for direct B2C digital sales you make yourself outside the app stores; below it you may charge your home VAT rate, above it you charge the customer’s country rate via OSS. It governs your own web-store sales, not app-store transactions where Apple or Google are the deemed supplier.
Can I use OSS to cover domestic Estonian sales?
No. OSS explicitly excludes domestic Estonian sales and B2B sales. Domestic consumer sales in Estonia go through your regular Estonian VAT return, and B2B sales anywhere follow reverse-charge rules rather than OSS.
How do I book app-store commission in my accounts?
Record the gross sale amount as revenue for the period the customer bought, and record the store’s commission as a separate cost or deduction. Netting commission silently out of revenue understates your top-line figures and makes reconciling your books against the store’s own sales reports much harder.
Do I need a separate VAT registration for selling to UK customers?
For app-store sales, no — the deemed-supplier treatment generally extends to UK sales too, with Apple or Google handling UK VAT. For direct web sales to UK consumers outside the stores, UK VAT rules apply separately from the EU’s OSS system, so check the current UK threshold and registration rule rather than assuming EU figures carry over.
What happens if my developer account and invoicing entity don’t match?
You risk payouts landing under the wrong legal name, disputes over ownership of the account and its revenue history, and friction with banks or payment processors questioning whose funds they are handling. Migrate the developer account into the company’s name as early as possible rather than after revenue has already built up.
Does running my OÜ from another country change where it’s taxed?
It can. Place of effective management, permanent establishment, and CFC rules in your home country can all pull an Estonian OÜ into local taxation regardless of its Estonian registration, if the real management decisions happen where you actually live and work. Confirm your position with a local advisor.
Is Estonia’s 0% tax on retained profit actually zero forever?
It is 0% for as long as profit stays undistributed. The moment you distribute profit as a dividend, it is taxed at 22%, calculated as 22/78 of the net distribution. The 0% is a deferral tied to reinvestment, not a permanent exemption on money you eventually take out.
