VAT MOSS is technically dead — replaced by OSS in July 2021 — but the obligations it created are very much alive. Here's what actually changed, what trips up sellers who didn't notice, and the two specific exemptions that make the whole system bearable.
VAT MOSS — the EU's Mini One Stop Shop — launched in January 2015 and immediately became the most-complained-about tax rule in indie dev Twitter. It required every seller of digital services to EU consumers to charge VAT at the buyer's local rate, regardless of how small the seller was. No threshold. No grace period. A UK developer selling a €10 Figma plugin to a French customer technically had to register, charge 20% French VAT, and file a quarterly return in Luxembourg. Most people ignored it. The EU eventually noticed.
In July 2021 the system was overhauled. MOSS became OSS (One Stop Shop), the threshold exemption arrived, and the scheme expanded from "just digital services" to cover goods too. The MOSS branding mostly disappeared, but the obligations for digital sellers didn't — they just got slightly more reasonable. If you're still reading blog posts that reference VAT MOSS as the current system, those posts are describing a regime that hasn't existed for four years.
1. What changed in July 2021 (and what didn't)
The thing that changed: a €10,000 annual threshold now exists for EU sellers. If your total B2C digital sales to other EU countries stay under €10,000 in a calendar year, you can charge your home country's VAT rate on everything and forget destination-country rates exist. One quarterly return, one VAT rate, one tax authority. That's the entire simplification.
The thing that didn't change: if you're outside the EU — US, UK, Canada, Australia — you never had access to MOSS anyway (the original scheme was EU-resident sellers only). The non-Union MOSS scheme existed for non-EU sellers, and it became the non-Union OSS scheme in 2021. Same mechanics: register once in a chosen EU country, charge destination-country VAT on B2C sales, file quarterly. Still applies from the first euro. No threshold for non-EU sellers.
Also unchanged: the two-evidence location rule, which is where most practical mistakes happen.
2. The two-evidence location rule
Under EU law, the seller is responsible for determining where the customer is located. Council Implementing Regulation (EU) No 282/2011 (as amended by 1042/2013) requires two non-contradictory pieces of evidence:
"A taxable person supplying electronically supplied services, telecommunications services or broadcasting services shall collect two pieces of non-contradictory evidence from items referred to in paragraph 1 of this Article in respect of a customer."
— Article 24b, Council Implementing Regulation (EU) No 282/2011 (public law, EUR-Lex)
The acceptable evidence types: billing address, IP address geolocation, bank country, mobile country code from the SIM, and location of the customer's fixed landline. Two of those, both pointing to the same country. If they contradict each other — billing address says Germany, IP says Argentina — you have a problem you need to document your resolution of.
Most payment processors collect this automatically. Stripe records the card's billing country and the IP at checkout. Paddle and Lemon Squeezy handle it as the MoR. If you're using a direct Stripe integration without a Merchant of Record, you need to confirm your checkout flow actually stores both signals and that you can produce them if audited. "We probably log IPs somewhere" isn't a compliant answer.
The records must be kept for 10 years from the end of the year the transaction occurred — that's the EU's retention requirement, and it's longer than most people assume.
3. The threshold exemption (EU sellers only)
The €10,000 figure is cumulative across all EU countries combined — not per country. Sell €3,000 to Germany, €4,000 to France, and €4,000 to Spain and you've crossed it, even though no individual country total is high. The threshold also resets each calendar year, but you can only use home-country VAT in the year following a sub-threshold year. Cross it in 2025 and you must switch to destination-country VAT in 2025, not wait until 2026.
Use the VAT calculator to model what the destination-country rates add up to across your customer base — the rate spread matters. German customers at 19%, Hungarian customers at 27%, Luxembourgish customers at 17%. If Hungary is a meaningful chunk of your revenue, that 27% rate is going to be visible in your checkout numbers.
4. B2B sales: the reverse charge mechanism
The entire OSS/MOSS framework only applies to B2C sales — sales to private consumers. The moment a business customer gives you their valid VAT number, the rules flip. You charge 0% VAT, note "reverse charge applies" on the invoice, and the buyer self-accounts for VAT in their country. This is Articles 44 and 196 of the EU VAT Directive (2006/112/EC).
The catch: you must validate the VAT number is real before applying reverse charge. The EU runs VIES for this. If a customer gives you a fake or invalid VAT number and you apply reverse charge, you're potentially liable for the uncollected VAT. Validate at checkout, save the VIES response timestamp. This is one of those "boring but will save you money if audited" steps.
B2B reverse charge means if a meaningful fraction of your buyers are European businesses — common for developer tools, SaaS, and professional software — your actual VAT burden is much lower than the headline rates suggest. Run the actual split through a percentage calculator before panicking about OSS registration.
5. UK sellers after Brexit
The UK left the EU VAT system on 31 December 2020. UK-based digital sellers are now non-EU sellers: no €10,000 threshold, no Union OSS. The UK has its own Non-Union VAT (VATMOSS) registration system that HMRC runs — but it only covers sales to EU consumers, and it still requires registering in a single EU country and filing there quarterly.
In practice, most UK sellers under £100k annual EU revenue use a Merchant of Record (Paddle, Lemon Squeezy, Gumroad) and step entirely out of this complexity. The MoR becomes the legal seller in each jurisdiction. You get a net payment. The MoR handles the 27 different rate schedules and the quarterly returns. For above £100k, the economics of in-housing it start to make sense — the MoR fees are 5-10% of gross, which compounds quickly at scale.
6. The currency conversion trap in quarterly filings
OSS quarterly returns must be filed in euros. If you price in GBP, USD, or any non-euro currency, you convert to euros using the European Central Bank exchange rate published on the last day of the reporting period. Not the rate you got at checkout. Not the average rate for the quarter. The ECB closing rate on 31 March, 30 June, 30 September, or 31 December.
This creates a small but real discrepancy between what you collected and what you report — especially if your currency moved significantly during the quarter. The currency converter handles spot conversions, but for quarterly filing you'll want to note the ECB rate on the filing date specifically and document it. Tax authorities don't love "approximately the right amount."
Invoicing requirements are the same as standard EU VAT invoices — sequential numbering, your VAT number, the customer's VAT number for B2B, the rate applied, the gross and net amounts. The invoice generator handles the formatting including the reverse-charge legal reference when applicable.
The short version
Most solo sellers are either under the €10,000 EU threshold (in which case, charge home VAT and move on) or doing enough volume to justify a Merchant of Record (in which case, pay the 5-10% and make this someone else's problem). The narrow band where you should actually DIY the OSS filings — above the threshold, under the break-even for MoR fees — is real but small. If you're in it, the two-evidence rule and the ECB conversion requirement are the two places most audits find problems.
← All articles