The 2026 Guide to EU OSS: Is Your Store’s VAT Reporting Audit-Ready?

Radek runs a PrestaShop store out of Kraków selling home fitness equipment — resistance bands, adjustable dumbbells, the odd rowing machine — into Germany, France, the Netherlands, and a growing trickle of Austrian customers. For the first quarter of the year he charged Polish VAT on every order, EU-wide, the way he always had. Nobody at his three-person operation flagged it as a problem, because nothing in PrestaShop's checkout complained. Then, in September, a letter arrived from the Polish tax office referencing a "cross-administration data match" with the German Bundeszentralamt für Steuern. His cumulative distance sales into other EU member states had passed €10,000 back in April. From that point on, he should have been charging German, French, Dutch, and Austrian VAT rates on the relevant orders and reporting them quarterly through the Union One Stop Shop (OSS) — not folding everything into his Polish return.

Nothing about his checkout was broken. His tax rules calculated Polish VAT correctly, every time, exactly as configured. The problem was that "configured correctly" and "compliant" stopped being the same thing the moment he crossed a threshold his invoicing workflow never checked for. That gap — between a store that calculates tax correctly and a store that reports it correctly — is where most OSS audit trouble starts, and it's what this guide is built around: getting your reporting itself audit-ready, not just your checkout math.

What OSS actually is, in one paragraph

The One Stop Shop is the EU's simplification for VAT on cross-border B2C sales. Instead of registering for VAT separately in every member state where you have customers, the Union OSS scheme lets you charge each customer's destination-country VAT rate and declare all of it in a single quarterly return filed through your home tax authority, which then redistributes the money to the relevant countries. It's been live since 1 July 2021, replacing the old distance-selling thresholds that used to apply per country. A companion scheme, the Import One-Stop Shop (IOSS), does something similar for imported goods valued up to €150 — that's a separate mechanism with its own monthly filing cadence, and it's worth knowing the two aren't interchangeable.

OSS is optional in the narrow sense that nobody forces you to register for it — but once you're required to charge destination-country VAT, your alternative to OSS is registering for VAT in every single country where you have customers, which is far more administrative work for almost every merchant. In practice, "optional" and "the only sane choice" end up meaning the same thing for most stores doing meaningful cross-border volume.

The €10,000 threshold: where "domestic" stops applying

This is the number that tripped up Radek, and it trips up more merchants than you'd expect because it's easy to mentally round down. The EU-wide distance-selling threshold is €10,000 per calendar year, combined across all your EU cross-border B2C sales of goods (plus certain digital services) — not €10,000 per country. Sell €3,000 worth of goods into Germany and €4,000 into France and €4,000 into the Netherlands, and you've crossed it at €11,000 combined, even though no single country individually looks large.

Below that threshold, you're allowed to charge your own domestic VAT rate on cross-border EU sales, exactly as if the customer were local. At or above it, you're required to charge the VAT rate of the customer's country — destination-based VAT — from the transaction that pushes you over, and you report that cross-border VAT centrally through OSS rather than registering everywhere individually.

Worked example: crossing the threshold mid-quarter

Here's the arithmetic version of what happened to Radek, using illustrative figures:

• January–March cross-border EU sales (excluding Poland): €3,200
• April 3: a promotional push generates a burst of orders — €7,100 in cross-border sales in a single week
• Running total after that batch: €10,300 — the threshold is crossed on the order that tips the cumulative figure past €10,000

From that specific order onward, every further cross-border B2C sale needs the destination country's VAT rate applied, not Poland's. The orders placed before the threshold was crossed can generally stay under the domestic rate already charged; you don't retroactively recharge customers who already checked out. Registration for the Union OSS scheme needs to happen by the 10th day of the month following the month in which the threshold was exceeded — so for an April crossing, registration by 10 May keeps you inside the rules. Miss that window and you may need to register for VAT directly in each destination country for the gap period, which is exactly the kind of retroactive cleanup nobody wants to do.

Domestic VAT vs OSS cross-border reporting, side by side

These aren't two flavors of the same process — they're structurally different, and mixing them up is the single most common audit trigger we see.

The practical risk sits in that last row and the rate-source-of-truth row: a store still configured for a single domestic tax rules group after crossing the threshold will keep charging the wrong VAT on every affected order until someone notices — and "someone notices" is often the tax authority, not the merchant.

Registering for the Union OSS scheme

If you're an EU-established merchant, you register for the Union OSS scheme through your own country's tax portal (in Poland, for example, that's done through the e-Deklaracje / VAT-OSS system tied to your existing VAT number). A few things worth knowing before you start:

• You register once, in your home member state — not per destination country.
• Registration typically takes effect from the first day of the calendar quarter after you apply, unless you're registering because you've just crossed the threshold mid-quarter, in which case it can apply retroactively to the triggering transaction if you register by the 10th-of-next-month deadline.
• Non-EU sellers use the same Union OSS scheme for goods if they hold stock in an EU country, but may need the Non-Union OSS scheme instead for cross-border services with no EU establishment — the two schemes cover different situations and aren't interchangeable. The underlying rules are set out in Council Implementing Regulation (EU) 2019/2026, if you want the primary source rather than a summary.
• Deregistering is possible if your cross-border sales drop, but it locks you out of re-registering for OSS for a short cooling-off period in some cases, so don't treat it as a switch to flip casually.

What "audit-ready" actually means for a PrestaShop store

Being audit-ready isn't about having a folder of invoices somewhere — it's about being able to reconstruct, for any transaction a tax authority points to, exactly what VAT rate was charged, why, and where that figure ended up in your OSS return. Four pitfalls account for most of the trouble we see merchants run into.

Pitfall 1: Tax rules groups still pointed at the wrong country

PrestaShop's tax rules groups calculate VAT correctly for whatever rate they're configured with — but they don't know your cumulative EU-wide sales figure, and they won't warn you when you cross €10,000. If your tax rules group for German customers is still charging Polish VAT three months after you crossed the threshold, checkout looks fine and every single one of those orders is wrong. This is a manual review item, not something to assume the platform handles.

Pitfall 2: No evidence trail for customer location

Destination VAT depends on where the customer actually is, and tax authorities expect two independent, non-contradictory pieces of evidence — typically billing address plus one of IP address, bank location, or delivery address. If your checkout only captures a delivery address and nothing else, you don't have the evidence pack an auditor will ask for when a transaction's country classification gets questioned.

Pitfall 3: Sales reports that don't reconcile to the OSS return

The number in your OSS filing needs to match the number your store's own sales reports show for the same period, broken out by destination country. If your accounting export and your storefront's order data diverge — because of manual adjustments, partial refunds handled outside the system, or currency conversion timing — that gap is exactly what a reconciliation-focused audit looks for first. We cover the mechanics of building that reconciliation in breaking down the OSS declaration step by step.

Pitfall 4: Missed or late quarterly filings

Union OSS returns are due by the end of the month following the quarter close — Q1 (Jan–Mar) is due by 30 April, Q2 by 31 July, Q3 by 31 October, Q4 by 31 January. Miss one and most member states apply late-filing penalties on top of whatever VAT was owed, and a pattern of late filings tends to invite closer scrutiny on everything else in your account.

Reporting deadlines you can't miss

Note that IOSS, if you also use it for imported low-value consignments, runs on a monthly cycle instead — don't assume the two schemes share a calendar.

Building the audit trail before an auditor asks for it

The records requirement isn't vague. OSS transactions need to be kept for 10 years and available electronically on request, covering the member state of consumption, the type of goods, the date of supply, the VAT payable and the rate used, the date and amount of payment received, and enough customer-location evidence to justify the rate applied. Ten years is a long window — long enough that "we'll reconstruct it if asked" isn't a realistic plan; you need it captured at the point of sale.

Audit-readiness checklist

• [ ] Cumulative EU cross-border sales tracked against the €10,000 threshold, updated at least monthly
• [ ] Tax rules groups mapped to current destination VAT rates for every country you ship to
• [ ] Two independent pieces of customer-location evidence captured per order
• [ ] OSS return figures reconciled against store sales reports every quarter before filing
• [ ] Returns and refunds netted correctly against the relevant reporting period (see our guide on correcting VAT errors and handling returns in OSS)
• [ ] 10-year record retention plan in place, not just "whatever the accounting software happens to keep"
• [ ] Calendar reminders set for all four quarterly deadlines, with a buffer week before each

What an actual VAT audit looks like

Audits under OSS's administrative cooperation framework often start indirectly — a discrepancy flagged by one member state's authority to another, rather than a knock on your door. You'll typically get a written request for supporting documentation on specific transactions or periods, with a deadline to respond, often through your home tax authority rather than directly from the destination country. The single biggest determinant of how painful that process is turns out to be whether your evidence was captured at the time of sale or has to be reconstructed afterward. Reconstruction is slow, error-prone, and looks worse to an auditor than having the answer ready in one export.

It's also worth being honest about a related trap: correctly configured checkout tax does not equal correct OSS reporting. PrestaShop will charge the right VAT rate if you've set it up right, but it has no concept of a quarterly OSS declaration — filing that return is entirely a manual or third-party-software task sitting outside the platform. We go into that distinction in detail in why tax rules aren't the same as tax reporting.

Run the threshold check this week

Pull your cumulative EU cross-border sales figure for the current calendar year this week, compare it against €10,000, and check the date you'd have crossed it if you haven't already. Then cross-check every tax rules group against that answer. That single fifteen-minute exercise catches the exact mistake that put Radek's business under review — and it's cheaper to run voluntarily now than to run under a deadline from a tax authority letter. If ViDA's incoming digital reporting requirements are new to you, our overview of the ViDA directive and what it means for e-commerce is a useful next read, since several of the record-keeping habits above are about to become more automated, not less strict.

Frequently asked questions

Do I need to register for OSS if I'm below the €10,000 threshold?

No — below the combined EU-wide threshold you can continue charging your home country's VAT rate on cross-border B2C sales and reporting it through your normal domestic VAT return. OSS registration becomes necessary once your cumulative cross-border sales reach or exceed €10,000 in a calendar year.

Is the €10,000 threshold per country or combined across the EU?

It's combined across all your EU cross-border B2C sales, not per destination country. A merchant selling small amounts into several different countries can cross the threshold with a combined total even if no individual country looks significant on its own.

What happens if I keep charging domestic VAT after crossing the threshold?

Every affected transaction is technically undercharged or overcharged relative to the correct destination rate, and misreported since it should have gone through OSS rather than your domestic return. Tax authorities can identify this through cross-administration data matching, and correcting it retroactively across multiple countries is considerably more work than getting it right from the transaction that crossed the threshold.

How long do I need to keep OSS records?

Ten years, electronically accessible on request, covering the destination country, goods type, supply date, VAT rate and amount, payment details, and the evidence used to determine customer location. This applies regardless of what your domestic VAT record-keeping rules require.

Does PrestaShop file my OSS return automatically?

No. PrestaShop's tax rules groups calculate and display the correct VAT rate at checkout, but filing the quarterly OSS declaration itself is a separate manual or third-party-software process — the platform doesn't submit anything to a tax portal on your behalf.

What's the difference between OSS and IOSS?

OSS (Union scheme) covers intra-EU cross-border B2C sales of goods already in the EU, filed quarterly. IOSS covers goods imported from outside the EU valued up to €150, filed monthly. They're separate registrations with separate calendars, and a merchant who both holds EU stock and imports low-value parcels may need both.

Compliance glossary

One-Stop Shop (OSS): The EU scheme letting merchants report VAT on cross-border B2C sales to multiple member states through a single quarterly return filed with their home tax authority, rather than registering in each destination country.

Import One-Stop Shop (IOSS): A separate EU VAT scheme for goods imported from outside the EU valued at €150 or less, filed monthly rather than quarterly.

Union vs Non-Union scheme: The Union OSS scheme applies to EU-established sellers (and non-EU sellers with EU stock) for goods and some services; the Non-Union scheme applies to non-EU businesses supplying services to EU consumers with no EU establishment. They're registered and filed separately.

Distance Selling Threshold (€10,000): The EU-wide annual combined limit on cross-border B2C sales below which a merchant may charge home-country VAT; at or above it, destination-country VAT and OSS reporting generally apply.

Destination-based VAT: Charging VAT at the rate of the customer's country rather than the seller's, which is the default rule for cross-border EU B2C sales once the distance-selling threshold is exceeded.

Tax Point: The date on which a supply is treated as having taken place for VAT purposes, used to determine which reporting period and which VAT rate applies to a transaction.

Related reading

• Breaking Down the OSS Declaration: A Step-by-Step for E-commerce
• Intra-EU Sales: Why Tax Rules Aren't the Same as Tax Reporting
• The ViDA Directive: What Every E-commerce Store Needs to Know
• Correcting VAT Errors: Handling Returns and Refunds in OSS
• Complete EU Compliance Checklist for Online Stores

Written by

PrestaInsights Team

At PrestaInsights, we specialize in everything PrestaShop, from hosting and performance optimization to module development and in-depth tutorials. Our goal is to help merchants, developers, and agencies succeed with up-to-date guides, practical insights, and proven best practices. Whether you're just getting started or scaling a high-traffic store, we're here to guide you.

View all posts →