Cross-border VAT: when a marketplace starts asking questions

Most sellers meet VAT compliance the same way: a notification from the marketplace, a deadline, and a list of tax numbers they do not yet hold. By that point the underlying issue has usually existed for months.

What actually triggers a request

Marketplaces reconcile three data sets: the tax numbers you declare, the stock movements they can see, and the sales reports they generate. A request appears when those three stop agreeing. Typical causes:

• Stock transferred into a country's fulfilment network without a local VAT number.
• Distance sales exceeding the threshold for the destination country.
• A registration that lapsed because filings stopped after the first year.
• An EPR registration missing for a category the platform now enforces.

What satisfies the request

In practice, authorities and platforms want three things: a valid number, filed returns that match platform reports, and a payment record. A certificate alone rarely closes the file if the returns behind it are inconsistent.

Where the exposure is retrospective, the sequence matters. Registering first and then filing historic periods is usually cheaper than waiting for an assessment, but the exact remedy depends on the country and on how long the gap has been open.

Sequencing across several countries

If you sell into five EU markets, do not register in all five at once. Start with the countries where you hold stock or exceed thresholds, then add markets as volume justifies the recurring filing cost. Every registration creates a permanent filing obligation, whether or not you keep selling there.

What we would check first

Before filing anything, we map stock locations, current registrations, platform reports and EPR status into one table. Most of the cost of a VAT problem comes from registering in the wrong order, not from the tax itself.