What does the EU One Stop Shop cover?

Cross-border B2C supplies of goods and services to consumers in EU member states where the supplier is not established, reported through a single quarterly return in one member state. It does not cover domestic supplies in the country of establishment, and it does not cover B2B supplies where the reverse charge applies. Those remain on the domestic return.

When do you have to use OSS instead of domestic VAT rates?

Once total cross-border B2C sales of goods and digital services across the EU exceed the single EU-wide threshold, the supply is taxed in the customer's member state rather than the supplier's. OSS is then the mechanism that avoids registering in each of them. Below the threshold a supplier can generally continue charging home-country VAT, but can also opt into the destination treatment.

How is a B2B sale treated differently from a B2C sale in the EU?

A cross-border B2B supply to a customer with a valid VAT identification number is generally reverse-charged, so the customer accounts for the VAT and the supplier charges none. A B2C supply is taxed at the customer's local rate and reported through OSS. The customer's status therefore determines the treatment, the return, and who pays, which is why validating the VAT number matters at the moment of sale.

When are Dutch BTW returns due?

Quarterly filing is the standard position for most businesses, with the return and payment due by the end of the month following the quarter. Monthly and annual filing exist for businesses whose circumstances require or allow them. The OSS return is separately quarterly, which means two deadlines on similar cycles and two datasets that must agree.

How do you correct an OSS return?

Corrections to a previously filed OSS period are generally made in a later OSS return rather than by amending the original, within the correction window allowed. Domestic return errors follow the domestic correction rules. Because a single misclassified sale can affect both streams, the quantification is done per period across both before either correction is prepared.

E-commerce · 🇳🇱 NetherlandsScenario

Why OSS does not cover domestic Dutch supplies

The One Stop Shop covers cross-border B2C supplies to consumers in other EU member states and nothing else, so domestic supplies in the country of establishment stay on the domestic VAT return and reporting them through OSS puts both returns wrong at once. This is an illustrative example of how Salt approaches EU VAT reporting, using an Amsterdam BV selling across the EU as the profile.

Ask how we'd handle this

Scenario — an illustrative example of how Salt approaches this problem. Not a description of a specific client engagement.

The business shape it describes: Amsterdam BV, EU-wide sales, quarterly BTW.

Scenario covers: Bookkeeping, BTW and OSS reconciliation, correction of filed returns
Jurisdiction: Netherlands
Sector: E-commerce

The setup

Take an Amsterdam BV selling across the EU, correctly registered for OSS to avoid registering in each member state, and filing BTW quarterly at home.
Domestic Dutch supplies continue alongside the cross-border sales, and the two have never been separated cleanly at the transaction level.

What usually turns out to be wrong

Domestic Dutch sales partly reported through OSS, where they do not belong, which understates the domestic return and overstates the OSS one.
The domestic BTW return and the OSS return prepared from different exports, so neither ties to the ledger and the two cannot be reconciled to each other.
Reverse-charge B2B sales not distinguished from B2C distance sales, even though only the second is an OSS supply at all.
No check that the EU-wide distance selling threshold position was correctly applied from the date it was crossed.

How this would be worked

Separate domestic supplies, EU B2B reverse-charge and EU B2C distance sales at the transaction level, with a distinct code for each.
Reconcile both return streams to a single ledger, so the domestic return and the OSS return are two views of one dataset.
Quantify the effect on each affected quarter separately, because netting errors across quarters hides which periods actually need correction.
Prepare corrections for both return streams and bring them into a single monthly close so the two cannot drift apart again.
Validate customer VAT identification numbers at the point of sale, since the B2B and B2C split is what determines which return a sale belongs on.

Why we'd be the right fit

OSS gets treated as a single answer to EU VAT, and its failure mode is quiet. The returns go in on time and simply contain supplies that belong on a different return.
Separating domestic, reverse-charge B2B and B2C distance sales at transaction level takes someone who knows what each return is for, not just how to submit it.

What the business would be able to do

Domestic BTW and OSS would come from one reconciled source and agree with the ledger and with each other.
Each sale would be coded to the correct return at the point it happens, rather than allocated at filing time.
Per-market profitability would become visible, because the sales are already separated by country for VAT purposes.

What we'd flag

Corrections across multiple quarters and two return streams have to be quantified period by period, and some of them will increase the liability rather than reduce it. A correction exercise that only fixes the favourable periods is not a correction.

Answers

Why OSS does not cover domestic Dutch supplies

Where this applies

Sales Tax · VAT · GSTService BookkeepingService All services in NetherlandsDutch GAAP (Title 9)More scenarios42 illustrative, labelled examples

Start with a number

Recognise this shape in your own books?

Tell us where you trade and what shape the books are in. You get scope, price and a start date in writing within one business day — no obligation.

Get a quote in 24 hoursBook a call instead