Destination-country VAT and the OSS scheme: where the rule breaks
A EUR 10 000 annual threshold counted across all member states together, a rate that changes mid-order, and a quarterly OSS return. What happens to the transaction that crosses the threshold, and what a system has to know so it does not issue an invoice at the wrong rate.
Why a single EU-wide VAT rate does not exist
When you sell to consumers in another member state, the rate that applies is the rate of the country where the buyer is, not your own. The rule comes from Article 59c of Directive 2006/112/EC and is known as the destination principle.
Below a certain volume of sales there is an exception: a small seller may charge their own domestic rate and pay the VAT to their own tax authority. The exception is not permanent, and it does not depend on which country you sell into. It depends on the total volume of your cross-border sales.
The consequence for a store is awkward. The rate is not a property of the product and not a property of the shop. It is the result of a calculation over the buyer's country, the tax category of the goods or service, and where the business currently stands against the threshold. A store that stores a rate on the product will issue a wrong invoice sooner or later.
The EUR 10 000 threshold: what counts and what does not
The threshold is EUR 10 000 per calendar year, counted cumulatively across all member states together, not per country. That is the most common misunderstanding we run into.
What counts: cross-border distance sales of goods to consumers in other member states, and telecommunications, broadcasting and electronically supplied services to consumers in other member states. Domestic sales do not count. Sales to businesses with a valid VAT identification number do not count, because the reverse charge applies there. Exports outside the EU do not count.
So a store with EUR 9 000 of sales to Austria and EUR 4 000 to Germany has crossed the threshold, even though it is nowhere near EUR 10 000 in either country on its own. The sum is EUR 13 000.
That calculation is arithmetic, not a measured case from our data: 9 000 plus 4 000 is 13 000, which is more than 10 000.
The transaction that crosses the threshold is the dividing line
Once sales in the year exceed EUR 10 000, the destination rule applies from the transaction that crosses the threshold onward. Not from the start of the year, and not from the next year.
In practice that means a single order can be the turning point. An order that takes a store from EUR 9 800 to EUR 10 300 is already taxed at the buyer's country rate. So a system does not need an annual switch; it needs a calculation on every order.
This is exactly where manual tracking fails. Nobody keeps a running total of cross-border sales in their head, and nobody checks it on every order at four in the afternoon. It is work for a system that already holds every invoice and therefore already knows the total.
One more thing matters: once the threshold is crossed, the destination rule also applies for the following calendar year, not only the current one. Falling back to your domestic rate is not automatic.
What OSS is, and why it solves a real problem
Without OSS, a store selling into six countries would have to register for VAT in six countries and file six returns. That was the actual situation before 1 July 2021.
The Union OSS scheme replaces that with one place. The business registers with its own tax authority, files one quarterly return splitting sales by country and rate, and makes one payment. The tax authority distributes the amounts onward.
For accounting the consequence is that the OSS return is not the same as the domestic VAT return and is not filed with it. It is its own return, with its own deadline and its own breakdown. So the data behind it must not come from free text on invoices; it has to come from fields: buyer country, rate, taxable amount.
OSS is a voluntary simplification, not an obligation. The alternative is registering in each country, which is lawful but more expensive.
Registering voluntarily before the threshold: when it pays
You can join OSS before crossing the threshold. It makes sense when you sell mostly into countries whose standard rate is lower than yours.
An arithmetic example, not a measurement: a store with a 22 percent standard rate selling mostly into Luxembourg at 17 percent charges the buyer EUR 122 or EUR 117 on EUR 100 net. At the same price to the buyer, the difference lands in the margin.
The second benefit is a stable display. A store that switches its rate mid-year ends up with two sets of prices in one year, two sets of invoices and two code paths in its data exports. Registering voluntarily from the start of the year removes that.
The decision to register voluntarily is a business and tax decision, so do not flip it casually in settings. In a system it should be an action with a date and an audit trail, not a checkbox anyone can toggle.
Where stores actually break
The first mistake is a rate stored on the product. A product carries a tax category, not a percentage. The percentage is the result of the category plus the country.
The second is a hard-coded list of rates inside one screen. A point-of-sale screen with its own list of rates in its own file will show Slovenian rates to a Croatian company. The same list then exists in five places and differs in each.
The third is taking the buyer's country from the shipping address where it should come from the billing address, or the other way round. Those two are not always the same.
The fourth is a silent default. A dropdown that offers the domestic rate when the country is unknown does not display an error; it writes one onto the invoice. The correct behaviour is to stop issuance and demand the data.
The fifth is checking the threshold at month end. By then the wrong invoice is already with the buyer.
Standard rates in selected countries
The table below lists standard rates in six countries as they stand at the time of writing, in October 2026. Rates change through national legislation, so the only reliable source is the European Commission's current overview, linked below the article. Do not copy the table into code.
Besides the standard rate, almost every country has one or two reduced rates and special cases where a reduced rate applies to specific goods. That is exactly why a product's tax category cannot simply be a flag saying taxable or not taxable.
If you sell into a country that is not in the table, do not estimate its rate from a neighbour. A wrong rate on an invoice is an error in a tax return, not an approximation.
What a system must know so the invoice comes out right
Five requirements you can verify.
One: the rate is computed at issuance from the buyer's country, the product's tax category, and the business's status against the threshold and OSS. It is stored nowhere as a number on the product.
Two: a business with a valid VAT identification number in another member state gets the reverse charge and zero percent, which is not the same as an exemption and is reported differently.
Three: the running total of cross-border sales is maintained automatically and checked on every order, not at period close.
Four: an unknown or invalid country stops issuance. There is no default here.
Five: the OSS export is built from fields, not by parsing invoice text, and it splits sales by country and rate.
In Entexia the rate is computed at issuance, and joining OSS is an action in company settings with an effective date rather than a flag in code. The running total and the rate on the invoice therefore derive from the same source.
What to check in your own store today
The check takes about fifteen minutes and does not need an accountant.
Open a product's settings and look at whether it holds a percentage or a tax category. A percentage is a warning sign.
Place a test order with an address in another country and look at the rate on the invoice preview. If it equals your domestic rate, either the system ignores the buyer's country or the threshold has not been crossed yet; which of the two it is has to be visible on screen, not guessed.
Look for a report of cross-border sales in the current year. If there is none, the threshold is not being monitored.
Enter an invalid VAT identification number for a foreign company and see what happens. The correct response is rejection, not zero percent.
Take an old order where the shipping and billing countries differ and check which one the system used.
Questions with short answers
Is the threshold counted per country? No. Cumulatively across all member states together.
Do sales to businesses count towards it? No, where the business has a valid VAT identification number, because the reverse charge applies there.
Do domestic sales count? No.
Can I stay on my domestic rate if I crossed the threshold at the very end of the year? No. The destination rule applies from the crossing transaction onward and also through the following calendar year.
Does OSS replace the domestic VAT return? No. It is an additional return with its own deadline.
Must I use OSS once I cross the threshold? Not necessarily; the alternative is registering for VAT in every country you sell into.
For your own company's situation, ask your accountant. This article describes the rule, not your data.
Comparison
| Country | Standard rate (October 2026) | Note |
|---|---|---|
| Hungary | 27% | highest standard rate in the EU |
| Croatia | 25% | two reduced rates alongside the standard one |
| Slovenia | 22% | reduced rates of 9.5% and 5% |
| Austria | 20% | two reduced rates alongside the standard one |
| Germany | 19% | one reduced rate alongside the standard one |
| Luxembourg | 17% | lowest standard rate in the EU |
See how Entexia computes the rate at issuance and keeps the running total of cross-border sales for the OSS threshold on its own.
Start free →