Selling to US Customers From an Estonian OÜ: W-8BEN-E, Withholding and Sales Tax in 2026
A US client just emailed your Estonian OÜ asking for a W-8BEN-E, or maybe someone mentioned “30% withholding” and now you’re picturing a third of every invoice disappearing into the IRS. Take a breath. For most Estonian OÜs billing US customers for services or software, federal withholding usually isn’t the real risk — the form is mostly paperwork to prove that. The genuine exposure, the one founders miss, sits in US state sales tax. This guide walks through both, in the right order, with what to actually check before you reply to that email.
The short answer
A W-8BEN-E is the form a US payer asks a foreign company to sign so it can document your status and apply the right withholding — it doesn’t create tax, it documents it.
US-source FDAP payments to a foreign company face a default 30% withholding without a valid W-8 on file, but most Estonian OÜ service fees are foreign-source income under the sourcing rule and never enter that 30% bucket in the first place.
If your team works from Estonia, income is sourced where the work happens, not where the client sits — that’s the sourcing rule, and it does more work here than the US-Estonia tax treaty does.
Flying to the US to deliver work changes the math: time physically spent in the US allocates part of the fee to US-source income, on a days-worked basis, with no confirmed safe number of days that’s ignored.
SaaS and end-user software licenses are usually copyrighted articles or services, not royalties, under Treas. Reg. §1.861-18 — but contract wording matters, and mislabeling a deal as a “license” can invite the wrong tax treatment.
An OÜ with no US office, agent, or employees generally has no obligation to file Form 1120-F, but this is fact-specific, not automatic.
State sales tax is the part that actually applies to a company with zero US presence — economic nexus post-Wayfair reaches foreign sellers based on sales volume alone, and thresholds and SaaS taxability vary state by state.
Why is a US customer asking for a W-8BEN-E in the first place?
A US company that pays a foreign business is a withholding agent under US tax law, and it wants to protect itself before it wires you a cent. The W-8BEN-E — officially the “Certificate of Status of Beneficial Owner for United States Tax Withholding and Reporting (Entities)” — is how your OÜ tells that payer who you are, where you’re tax resident, and whether a treaty reduces US withholding. See the IRS instructions for Form W-8BEN-E.
The current revision is October 2021 (Rev. 10-2021), still the version in force. An authorized officer of the OÜ signs it, not an individual shareholder, because the form documents the entity. Once signed, it stays valid through the last day of the third succeeding calendar year: a form signed anytime in 2026 runs through 31 December 2029, unless a change in circumstances makes it inaccurate sooner.
Two lines cause most of the confusion. Part I, Line 4 asks for your Chapter 3 classification — a standard OÜ is normally treated as a Corporation. Line 9b asks for a foreign TIN; this field is normally completed with the Estonian registry code. If a US payer challenges that entry, confirm the exact format they expect.
What does the 30% withholding number actually mean?
30% is the default US withholding rate on US-source FDAP income paid to a foreign person when no valid treaty claim is on file — FDAP means “fixed, determinable, annual or periodical” income. This default sits at the center of IRS Publication 515, the main guide for US withholding on payments to foreign persons.
Here’s what surprises founders: the 30% rate only bites income that is US-source in the first place. Much of what an Estonian OÜ invoices a US client for never falls into that bucket, because of a rule that has nothing to do with treaties — sourcing, covered next.
Even so, many US payers withhold defensively when no W-8 is on file, because they carry the liability if they get it wrong. That’s why a client asks for the form even when no US tax is actually due: it’s how the payer justifies not withholding to its own auditors and the IRS.
Does the sourcing rule mean your OÜ owes nothing at all?
Usually, yes for the federal withholding piece — if all the work is done from Estonia. The IRS sourcing rule for personal services is blunt: compensation for services is sourced to where the services are performed, regardless of where the client is based, where the contract was signed, or where payment is sent. See the IRS page on source of personal service income.
Apply that to a typical setup: your team works from Tallinn, delivers a project or SaaS subscription to a US client, and never sets foot in the US. That fee is foreign-source income. It was never US-source FDAP income to begin with, so the 30% default withholding never had anything to attach to. This is the sourcing rule doing the work — not the US-Estonia treaty, which matters for a different set of cases, covered below.
The reason your OÜ’s US client fee usually escapes the 30% default isn’t a treaty exemption you have to claim — it’s that the income was never US-source in the first place, because the work happened in Estonia.
What changes if someone flies to the US to do the work?
The portion of the fee tied to US physical presence becomes US-source income. When services are performed partly in and partly outside the US, the IRS requires a time-basis allocation: you multiply total compensation by the fraction of working days spent physically in the US. The IRS’s own example on the sourcing page allocates 194 of 242 total working days to the US to arrive at the US-source dollar figure.
Do not assume a handful of US days gets ignored. No confirmed de minimis exception exists for this allocation — treat every US working day as potentially allocable until checked with a professional. If a consultant or founder is planning US travel tied to a paid engagement, log the days; it’s cheap to track and expensive to reconstruct later.
Payment type | Where work happens | Likely US tax treatment |
|---|---|---|
Consulting/dev fee | Entirely from Estonia | Foreign-source; 30% FDAP withholding does not apply (sourcing rule) |
Consulting/dev fee | Partly performed in the US | Portion allocated to US days is US-source; time-basis allocation applies |
SaaS subscription / hosted access | Delivered remotely, no US infrastructure | Typically a copyrighted-article/service transaction, not a royalty |
Software license granting reproduction/sublicense rights | Rights transferred regardless of delivery location | May be characterized as a royalty; treaty caps apply if claimed |
Sale of physical goods to US buyers | Shipped from Estonia or a US warehouse | Federal withholding generally not relevant; state sales tax nexus is the real question |
Is a SaaS subscription or software license a royalty?
Usually not — but this is genuinely fact-dependent, not a fixed rule. The governing framework is Treas. Reg. §1.861-18, which sorts transfers of software into four buckets: a transfer of a copyright right, a transfer of a copy (a “copyrighted article”), development/modification services, or provision of know-how.
The regulation draws a sharp line. A transfer counts as a sale, not a royalty, only if it conveys all substantial rights in the copyright — exclusive rights for the copyright’s remaining life. Anything short of that generates royalty income only if a real copyright right changed hands (the right to reproduce, distribute, sublicense, or build derivative works). Access to a hosted product or a standard end-user license is a copyrighted article or a service, not a royalty.
Typical SaaS subscription — customer logs in and uses the product. Usually a copyrighted article/service, not a royalty.
Standard shrink-wrap-style software license — customer installs and uses one copy. Usually a copyrighted article, not a royalty.
License granting reproduction, sublicensing, or derivative-work rights — a real copyright right has moved. This is the scenario that can generate royalty treatment.
Custom development or a “know-how” transfer — treated under its own bucket in §1.861-18, again separate from royalty income.
The regulation is explicit that substance beats the label in the contract — calling something a “license fee” doesn’t make it a royalty if the customer only received access. If your contracts use “license” loosely for what’s really a SaaS subscription, tighten the language; it can push a cautious client toward assuming royalty withholding applies when it shouldn’t.
Where a payment is genuinely a royalty, the US-Estonia treaty (Article 12) caps the US withholding rate: 5% on royalties for industrial, commercial, or scientific equipment, and 10% on all other royalties, covering copyright and software royalties when the deal is characterized that way.
What does the US-Estonia tax treaty actually cover for your OÜ?
The treaty’s main job here is protecting business profits, not services fees — the sourcing rule already does that. The US-Estonia income tax convention was signed 15 January 1998 and entered into force 30 December 1999. Under its business-profits article, US business profits of an Estonian enterprise are taxable in the US only to the extent attributable to a permanent establishment (PE) in the US.
If you do need to make a treaty claim — for a royalty payment, say — that certification lives in Part III (Lines 14–15) of the W-8BEN-E, including a Limitation on Benefits (LOB) checkbox where your OÜ identifies which LOB test it satisfies. The instructions direct filers to the LOB article text to see which tests apply.
One friction point: a US TIN (EIN) is generally required to claim treaty benefits, though instructions do permit a foreign TIN on line 9b in some circumstances. Many US payers ask for an EIN anyway before applying a reduced treaty rate. If a client’s finance team pushes back, getting an EIN is often the fastest way to unstick the payment.
When does your OÜ actually have to file something with the IRS?
Only if the OÜ is engaged in a US trade or business — and for most OÜs selling remotely from Estonia, that threshold isn’t crossed. A foreign corporation must file Form 1120-F, the US Income Tax Return of a Foreign Corporation, if engaged in a US trade or business, regardless of whether that activity produced income or the income is treaty-exempt. See the Form 1120-F instructions.
What tips a company into a US trade or business or a permanent establishment is fact-specific, but illustrative indicators generally discussed include:
A US office or other fixed place of business
A dependent agent in the US who habitually concludes contracts on the company’s behalf
Employees or personnel performing substantial activities while physically in the US
US inventory or warehousing used to fill US customer orders
Treat that list as illustrative, not a checklist — none of these alone is automatically decisive, and the determination depends on the full facts. An OÜ with no US office, employees, or contract-concluding agent generally has no US trade or business and no filing obligation — but that’s a facts-and-circumstances conclusion each year, not an automatic exemption from being Estonian.
What’s a protective return, and do you need one?
A protective Form 1120-F preserves your right to claim deductions and credits later, in case the IRS decides you did have a taxable US presence. If your OÜ is close to the line — say, an agent relationship that might count as habitually concluding contracts — filing protectively costs little and avoids losing deductions if challenged later. The IRS treats a protective return as timely if filed within 18 months of the original due date.
Will you get a 1099 or a 1042-S from your US client?
Neither, usually — and that’s expected, not a red flag. Form 1099 reports payments to US persons; since your OÜ is foreign, a valid W-8BEN-E means the client should not issue a 1099. Form 1042-S reports US-source income paid to foreign persons subject to withholding — and since work performed entirely outside the US is foreign-source, it typically generates no 1042-S obligation either.
If any portion of the work was performed while physically present in the US, that US-source slice should show up on a 1042-S, not a 1099. If you get a 1099 by mistake, flag it to the client’s AP team immediately — it implies they’ve classified you as a US person.
Where does the real risk sit: state sales tax
A company with zero US physical presence is not automatically exempt from state sales tax — this is the point most founders miss entirely. The US Supreme Court’s 2018 decision in South Dakota v. Wayfair let states impose sales-tax collection duties based on economic nexus — sales volume into the state — rather than requiring physical presence. That holding was designed to reach out-of-state and remote sellers, and it doesn’t carve out foreign ones.
Thresholds vary state by state — there is no single national number. As a general range: most economic-nexus states use a $100,000 annual sales threshold, some pairing it with a 200-transaction count; other states set higher thresholds, historically as high as $250,000 or $500,000. Many states have dropped the transaction-count prong entirely and rely on the dollar threshold alone, while others still retain some transaction-count test. Check each state where you have real sales volume rather than assuming one figure applies everywhere.
Is SaaS actually taxable? It depends entirely on the state
There is no general US rule on SaaS taxability — it’s decided state by state, largely on whether that state treats remotely-accessed software as tangible personal property, a taxable service, or a non-taxable service. The examples below are illustrative only; always check the specific states where your customers are billed.
State | SaaS commonly taxable? | Note (example only, verify current rule) |
|---|---|---|
Texas | Yes | Taxed as a “data processing service,” with a partial exemption reducing the taxable base |
New York | Yes | Described by practitioners as taxable regardless of business or personal use |
California | No | Cloud/remotely-accessed software generally treated as a non-taxable service |
Florida | No | Generally not taxed as tangible personal property |
Virginia | No | Generally treated as a non-taxable service |
Missouri | No | Generally treated as a non-taxable service |
Because this varies so much, the practical move is to map your actual customer base against each relevant state’s current rule rather than assume a national default in either direction. A product that’s clearly exempt in California can be clearly taxable in Texas for the same transaction type.
Do marketplaces change any of this?
Selling through a marketplace shifts the collection burden to the platform for those sales — direct sales stay your problem. A growing number of states require marketplace facilitators — the platforms that host and process third-party sales — to collect and remit tax on behalf of sellers using them, taking the individual seller off the hook for those transactions specifically.
But direct sales made outside a marketplace remain the seller’s own responsibility, and you may still need registrations where you sell directly even if marketplace sales are already covered. Don’t assume a marketplace handling some of your sales tax means it handles all of it.
What does registering and filing actually involve?
Once you trigger nexus in a state, you register with that state’s department of revenue — there’s no single national filing. The mechanics, at a high level:
Register for a sales tax permit with the department of revenue in each state where you’ve triggered nexus
Collect tax at the rate applicable to the customer’s location, not your own
File periodic returns — commonly monthly, quarterly, or annually depending on your sales volume in that state
Remit the collected tax with each filing
There is no federal sales tax and no centralized national filing — each state runs its own system, its own rates, and its own filing calendar. If you sell into several states above threshold, budget real time (or a service) for this; it doesn’t shrink because your company is Estonian.
What should you actually do this quarter?
Start with the form your client is asking for, then look at the bigger picture they didn’t ask about.
Get the W-8BEN-E signed by an OÜ officer, using the current Rev. 10-2021 form, and send it before the client withholds defensively
Confirm whether any of your delivery work happened, or will happen, on US soil — if yes, start logging days for a time-basis allocation
Review your SaaS/license contracts for language that accidentally implies a royalty grant when you’re really selling access to a hosted product
Tally your US sales by state for the trailing 12 months and flag any state near or above a $100,000 threshold
Check SaaS/digital-goods taxability specifically for the states on that list — don’t extrapolate from one state to another
If a state is clearly triggered, register with that state’s department of revenue before you owe a filing you didn’t know about
This article is general information, not tax advice — a founder with real numbers on the table should have a US tax professional look at their specific facts before filing anything or signing a treaty claim. But it should turn a vague fear of “30% withholding” into a short list of things to actually check, most of which point toward state sales tax as where careful attention pays off.
Frequently asked questions
Does an Estonian OÜ need a W-8BEN-E for every US client?
Only when a US client requests one to document your foreign status before paying you — it’s the client’s compliance requirement as a withholding agent, not a form you file with the IRS unprompted. If a client asks, provide a current, correctly completed form promptly; delaying it is often what triggers defensive 30% withholding.
How long is a W-8BEN-E valid?
A W-8BEN-E is valid from the date signed through the last day of the third succeeding calendar year, unless a change in circumstances makes it inaccurate sooner. A form signed anytime in 2026 is valid through 31 December 2029.
Does the US-Estonia tax treaty mean my OÜ pays zero US tax?
No — a treaty allocates taxing rights and relieves double taxation, it never produces zero tax by itself. In most services-fee cases the sourcing rule, not the treaty, is what keeps US withholding from applying, because the income is foreign-source to begin with.
If my developer visits the US for a week, does that trigger US tax?
It can allocate part of that engagement’s fee to US-source income on a time-worked basis, and there’s no confirmed safe number of days that gets ignored. Log the days worked in the US and check the allocation with a professional rather than assuming a short trip is immaterial.
Is my SaaS subscription a royalty for US tax purposes?
Usually not — a standard SaaS subscription is typically a transfer of a copyrighted article or a service under Treas. Reg. §1.861-18, not a royalty-generating license. It becomes royalty territory mainly when the customer actually receives rights to reproduce, distribute, sublicense, or create derivative works, not just access.
Does my OÜ have to file a US tax return?
Only if it’s engaged in a US trade or business — generally meaning a US office, a dependent agent concluding contracts, US personnel doing substantial work, or US inventory filling orders. An OÜ with none of those typically has no Form 1120-F obligation, but this is a facts-and-circumstances test, not an automatic exemption.
My company has no US office or staff — am I exempt from US state sales tax?
No. Since South Dakota v. Wayfair, states can require out-of-state and foreign sellers to collect sales tax based on economic nexus — sales volume into the state — with no physical presence required at all. Physical presence is simply not the test anymore.
How do I know if a specific US state taxes my SaaS product?
There’s no general rule; it’s decided state by state, so you check each state where you have meaningful sales. Examples commonly cited as taxable include Texas and New York, while California, Florida, Virginia, and Missouri are commonly cited as not taxing SaaS — but confirm current treatment for your specific product and use case.
