EU VAT Fraud Reform and IOSS Oversight Explained

Warehouse scene showing empty orange metal shelves in a room with stacked cardboard boxes in the background. A man in a "FLEX" vest writes notes.

EORI vs IOR Services: The Customs Representation Mechanism for Non-EU Amazon Sellers

22.06.2026

Two workers in orange safety vests use a scanner and tablet to check packages and labels in a warehouse. The scene is focused and industrious.

Importer of Record vs Customs Agent Explained

24.06.2026

A man in an orange safety vest works on a laptop in a warehouse. He stands near metal shelves filled with cardboard boxes, suggesting an organized setup.

FLEX. Logistics

We provide logistics services to online retailers in Europe: Amazon FBA prep, processing FBA removal orders, forwarding to Fulfillment Centers - both FBA and Vendor shipments.

Pan-EU marketplace sellers operating under IOSS are entering a period of sharper enforcement. Tax authorities across member states are increasingly cross-referencing IOSS return data against marketplace transaction records, carrier manifests, and customs declarations. When those data points do not align, the exposure is not theoretical — it surfaces as audit triggers, VAT reclaim delays, and in some cases, suspension of IOSS registration.

This article explains what the current enforcement direction means for sellers, who owns each obligation in the IOSS chain, and what operational controls reduce audit exposure. It is not legal advice. Sellers should verify their specific VAT obligations with a qualified tax adviser. The logistics and data-management layer is where FLEX. can support.

How IOSS Compliance Works in Practice

IOSS — the Import One-Stop Shop — allows sellers and marketplaces to collect, declare, and remit VAT on eligible low-value consignments entering the EU. The mechanism was designed to reduce VAT fraud on sub-€150 imports and to simplify the compliance burden for cross-border sellers. In practice, it creates a chain of responsibility that is easy to misread.

When a marketplace facilitates the sale, the marketplace typically becomes the deemed supplier and takes on the IOSS obligation. When a seller sells directly — through their own storefront or via a non-facilitating channel — the seller holds the IOSS obligation and must either register directly or appoint an IOSS intermediary service to act on their behalf.

The critical operational point is that IOSS registration alone does not guarantee compliance. The IOSS number must be transmitted correctly through the logistics chain: from the seller or intermediary to the carrier, and from the carrier to customs at the EU point of entry. A missing or misrouted IOSS number at the border means the consignment may be stopped, re-assessed for import VAT, or returned — regardless of whether the VAT was already remitted in the monthly IOSS return.

What Must Be Confirmed Before Goods Move

Before a cross-border consignment enters the EU under IOSS, several data points must be confirmed and correctly transmitted across every party in the chain.

IOSS number validity: Confirm the IOSS number is active and correctly assigned to the selling entity or marketplace facilitating the transaction.
Carrier data handoff: The IOSS number must appear in the electronic customs declaration, not only in the commercial invoice.
Consignment value: Each parcel must be individually valued below the €150 threshold. Bundled shipments that exceed this limit are not eligible for IOSS treatment.
Country of destination routing: IOSS VAT rates vary by EU member state. The correct rate must be applied at the point of sale, not estimated at dispatch.

Sellers using IOSS intermediary services in the EU should confirm that their intermediary has a live data feed from the order management system, not a batch upload that lags behind shipment volumes.

What Breaks When Responsibility Is Unclear

The most common failure point in IOSS compliance is not deliberate fraud — it is ambiguity about who owns which step. When a seller uses a marketplace for some channels and a direct storefront for others, the IOSS obligation splits. If the seller's own IOSS registration is not active for the direct channel, those consignments arrive at the EU border without a valid IOSS number.

Customs authorities do not automatically hold shipments for correction. In many cases, the parcel is assessed for import VAT at the point of entry, and the carrier charges the recipient or returns the parcel. The seller then faces a refund dispute, a damaged customer relationship, and a potential VAT audit support request from the tax authority covering the period in question.

A second failure mode occurs when the IOSS number is transmitted but the monthly VAT return does not match the declared transaction volume. Tax authorities are increasingly using automated reconciliation tools to flag these gaps, and the audit exposure from a persistent mismatch can extend across multiple reporting periods.

The Intermediary Model and Who Owns the Obligation

Non-EU sellers who are required to register for IOSS cannot do so directly in most member states — they must appoint an EU-established IOSS intermediary. The intermediary acts as the fiscal representative, submitting monthly IOSS returns and remitting the collected VAT on the seller's behalf. This is not a passive administrative role. The intermediary is jointly liable for the accuracy of the return in many jurisdictions, which means the quality of data flowing from the seller to the intermediary directly affects the intermediary's own compliance exposure.

For sellers, this creates a practical obligation: the data sent to the intermediary must be complete, timely, and correctly attributed by destination country. If a seller's order management system exports transaction data in a format that does not separate EU member state destinations, the intermediary cannot file an accurate return. The gap between what the seller thinks was reported and what was actually declared is where VAT audit support requests originate.

Marketplace sellers who rely on the marketplace's IOSS number for facilitated sales must also confirm that their non-facilitated channels — including B2B orders, gift shipments, or orders routed through third-party logistics providers — are covered by a separate IOSS registration or are correctly excluded from IOSS treatment. Mixing facilitated and non-facilitated transactions under a single IOSS number is a known audit trigger across several EU member states.

IOSS Registration Checks

Confirm IOSS registration is active and covers all selling channels in use
Verify the intermediary appointment is documented and current
Check that the IOSS number is correctly formatted for carrier electronic data interchange
Confirm registration covers the correct legal entity — not a related company or holding structure
Validate that the IOSS number is not shared across unrelated sellers
Review whether any new sales channels launched since registration require an updated intermediary mandate

Transaction Data Integrity Checks

Confirm each transaction record includes the destination EU member state, not only a regional grouping
Verify that consignment values are recorded per parcel, not per order where multiple parcels are used
Check that VAT rates applied at checkout match the destination country rate at the time of sale
Confirm returns and refunds are correctly deducted in the same reporting period where possible
Validate that marketplace-facilitated transactions are excluded from the seller's own IOSS return
Review whether split shipments from the same order are each individually below the €150 threshold

Carrier and Customs Handoff Checks

Confirm the IOSS number is included in the electronic customs declaration, not only on the label
Verify the carrier accepts IOSS data via API or EDI — not only manual entry
Check that the carrier's system does not strip or truncate the IOSS number during label generation
Confirm the customs entry point country is correctly identified in the carrier routing instruction
Validate that the carrier's customs broker has the correct IOSS number on file for the account
Review carrier SLA for IOSS data transmission relative to shipment departure time

Audit Readiness and Monitoring Checks

Confirm monthly IOSS return totals reconcile against order management system export for the same period
Verify that VAT audit support documentation — transaction logs, carrier manifests, return records — is retained and accessible
Check that the intermediary provides a filed-return confirmation with a reference number each month
Confirm a process exists to flag and investigate any customs query or import VAT charge on IOSS-declared consignments
Review whether the seller has a named contact at the intermediary for escalation during an audit
Validate that global VAT compliance obligations outside the EU — UK, US, AU — are tracked separately and do not contaminate the IOSS return

Putting IOSS Operational Control Into Practice

The sellers who face the least audit exposure are not necessarily those with the most complex compliance structures. They are the ones who have mapped the data flow from order placement to customs declaration and identified every handoff point where the IOSS number could be lost, misrouted, or misattributed.

A practical starting point is to run a reconciliation between the last three months of IOSS returns and the corresponding carrier export data. If the transaction counts do not match within a reasonable margin, the gap needs an explanation before the next return is filed. Common causes include returns processed after the reporting cut-off, marketplace-facilitated orders incorrectly included in the seller's own return, and consignments that were cancelled after dispatch but before customs clearance.

For sellers managing cross-border EU VAT for ecommerce across multiple channels, the intermediary relationship is the operational control point. The intermediary should be receiving data in a format that allows automated reconciliation, not a spreadsheet that requires manual review before filing. If the current data handoff relies on a monthly email attachment, that is a process risk that will compound as transaction volumes grow.

Sellers expanding into new EU markets should also confirm whether their existing IOSS registration covers the new destination countries and whether the VAT rates applied at checkout are current. Rate changes in individual member states do not automatically update in order management systems, and a systematic rate error across a high-volume period can produce a material VAT liability that the intermediary cannot absorb without a corrected return.

Who Owns the IOSS Obligation

For marketplace-facilitated sales, the marketplace is the deemed supplier and holds the IOSS obligation. For direct sales, the seller holds it — and must appoint an IOSS intermediary service if they are not EU-established. Clarity on this split is the first control point.

Data Checkpoint Before Filing

Before each monthly IOSS return is submitted, the transaction data must be reconciled against carrier dispatch records and any returns or cancellations processed in the period. A return filed on incomplete data creates a correction obligation that attracts additional scrutiny from tax authorities.

When to Escalate an Exception

If a consignment is stopped at the EU border and assessed for import VAT despite a valid IOSS number being transmitted, escalate immediately to the carrier and the intermediary. Document the customs reference, the declared IOSS number, and the carrier's transmission log. This evidence is required for any VAT reclaim or audit defence.

What Sellers Should Decide and Control Now

IOSS compliance is not a one-time registration task. It is an ongoing data management and reporting obligation that requires a functioning handoff between the seller's order management system, the IOSS intermediary, and the carrier's customs declaration process. When any one of those handoffs is manual, delayed, or poorly formatted, the risk accumulates quietly until an audit or a customs stop makes it visible.

The practical decision for pan-EU marketplace sellers is whether the current intermediary relationship and data flow can support the transaction volume and channel mix in operation today — not the volume at the time of registration. If the seller has added new channels, new destination markets, or new logistics partners since the IOSS registration was set up, each of those changes should trigger a review of the data handoff and the return reconciliation process.

Sellers who are uncertain about their current IOSS reporting accuracy should obtain a reconciliation report from their intermediary before the next filing period. If the intermediary cannot produce one, that is itself a signal that the operational layer needs attention. VAT audit support is significantly easier to manage when the documentation is already in order than when it must be reconstructed under time pressure during an active inquiry.

FLEX. supports the operational logistics layer for cross-border EU shipments — including carrier data handoffs, customs declaration coordination, and pre-shipment compliance checks. If your IOSS data flow or intermediary reporting process needs a structural review, contact FLEX. to discuss the logistics side of your compliance setup. Verify your specific VAT and tax obligations separately with a qualified adviser.