Post-Brexit Green and Red Lane Segregation: Windsor Framework Documentation Rules for UK-to-EU Flows
13.07.2026
E-Invoicing Goes Cross-Border: What the 81-Country Mandate Map Means for Sellers Operating Across the EU
13.07.2026
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.
A finance lead running Amazon, eBay, Cdiscount, Bol and Allegro across six VAT registrations builds one reporting calendar around Intrastat. It works for a year. Then France requires structured e-invoices through a certified platform, and the same shipment that triggered an Intrastat line now also needs a separate transaction-level filing that Intrastat never covered. Intrastat reports the physical movement of goods across an EU internal border, above a country-specific threshold, on a monthly declaration. E-invoicing mandates report the tax event itself: the invoice issued for a sale, formatted and transmitted through a national system, independent of whether goods physically crossed a border that month. These are two different triggers, two different data feeds, and increasingly, two different filing cadences. Sellers who treat them as one compliance task lose the point where they diverge by country, and that gap is where reporting fails quietly.
What Intrastat Actually Tracks, and Where It Stops
Intrastat exists to measure trade flows between EU member states for statistical purposes, not tax purposes. The trigger is a physical goods movement: your stock leaves a warehouse in one member state and arrives in another, whether by intercompany transfer, FBA cross-border fulfillment, or a direct customer shipment. Each destination country sets its own arrival and dispatch thresholds, and once your annual movement value crosses that line, monthly declarations become mandatory in that country.
The reporting boundary matters: Intrastat does not care who the invoice was issued to, what format it used, or when payment was collected. It cares about quantity, weight, commodity code, and value of goods physically moved. A stock transfer between your own FBA storage locations with no sale attached can still trigger an Intrastat declaration, while a domestic sale with no cross-border movement never appears on it at all.
What Intrastat Requires You to Control
Intrastat compliance depends on knowing your cumulative movement value per destination country, tracked separately from sales revenue. A seller using Amazon's pan-European FBA network moves stock between FCs constantly, often without a direct customer transaction attached to each movement. That means your warehouse management or ERP system needs to flag internal transfers as reportable events, separate from the invoicing workflow entirely.
Thresholds reset annually and differ by country and by direction (arrivals vs dispatches), so a setup built for one country's threshold structure will not transfer cleanly to another without a dedicated check.
What Breaks When Movement Tracking Is Ignored
The common failure is a seller who monitors VAT registration thresholds closely but treats Intrastat as an afterthought handled by whoever files the VAT return. Stock repositioning between FCs for peak season crosses a dispatch threshold in one country mid-quarter, and nobody notices until a late declaration request arrives from that country's statistical office.
Late or missing Intrastat filings do not usually stop goods movement in real time, but they create a compliance gap that surfaces during a VAT audit, when auditors cross-check declared movements against invoiced sales and find volumes that do not reconcile.
The Control Point Most Sellers Miss
Before adding a new fulfillment lane or a new marketplace warehouse location, check whether the added movement volume pushes any destination country over its Intrastat threshold for that calendar year. This is a five-minute check against your existing movement log, but it has to happen before the lane goes live, not after the first monthly filing deadline passes.
Sellers managing EU VAT for ecommerce sellers across multiple registrations often find this threshold check falls between the warehouse ops team and the finance team, with neither owning it by default.
What E-Invoicing Mandates Track, and Why the Trigger Is Different
National e-invoicing mandates report the invoice itself, structured in a specific electronic format and transmitted through a designated channel, at the moment of issuance. Italy's SdI system requires invoices in FatturaPA XML format routed through the Sistema di Interscambio before they are considered valid for tax purposes. France's rollout requires structured e-invoices for domestic B2B transactions through certified platforms, with a parallel e-reporting obligation covering B2C and cross-border sales that fall outside the invoice mandate itself.
The trigger point is invoice issuance, not goods movement and not payment. A seller can invoice a French customer for stock that never moved across a border that month, and the e-invoicing obligation still applies because a taxable transaction occurred. This is the structural gap: Intrastat activates on movement, e-invoicing activates on the invoice, and a single order can trigger one, both, or neither depending on where the goods sat and where the customer is billed.
Where the Two Systems Overlap
Overlap happens on cross-border B2B sales where goods physically move from a seller's warehouse in one member state to a business customer in another, and the invoice is issued for that same transaction. Here, both an Intrastat dispatch declaration and a compliant e-invoice may be required, referencing the same shipment from two different reporting angles.
A reconciliation check should confirm that the goods value on the Intrastat line and the taxable value on the corresponding invoice trace back to the same underlying transaction, even though they sit in separate systems with separate filing calendars.
Where the Two Systems Diverge
Divergence is more common than overlap in a multi-marketplace setup. B2C sales through Amazon or Bol rarely require a formal invoice under some national e-invoicing regimes but can still trigger Intrastat if stock moved cross-border to fulfill them. Conversely, domestic invoices with no cross-border movement fall under e-invoicing mandates in countries like Italy or France but never touch Intrastat at all.
A seller relying on one dashboard built around Intrastat logic will structurally miss the domestic e-invoicing obligation, because that dashboard was never designed to flag invoice-format compliance in the first place.
Owner Map: Who Tracks What
In most multi-marketplace setups, three roles touch this data and rarely compare notes. The warehouse or 3PL operations team owns stock movement records that feed Intrastat. The invoicing system, often the marketplace itself or a billing platform, generates the transaction record that feeds e-invoicing. The VAT compliance provider or in-house tax lead reconciles both into the periodic VAT return.
When these three do not share a common transaction reference, a movement can be declared on Intrastat without a matching invoice ever surfacing on the e-invoicing side, or vice versa, and nobody owns catching that gap until an authority does.
The Failure Points That Actually Trigger Audit Flags
Three failure patterns recur across sellers managing this manually. First, missing Intrastat declarations after crossing a country's threshold mid-year, because the movement log was checked at year-start but not re-checked after a new fulfillment lane or marketplace expansion. Second, invoices issued in a non-compliant format or through the wrong channel for a country with an active e-invoicing mandate, which can affect whether that invoice is valid for input VAT recovery on the buyer's side, not just a filing technicality.
Third, and most common in multi-marketplace operations, is a data mismatch between the two systems that an auditor catches before the seller does: declared goods movements that do not correspond to any invoiced transaction, or invoiced transactions with no corresponding movement record when cross-border movement should have occurred. This mismatch is usually not fraud, it is two systems built at different times by different teams that were never reconciled against a shared transaction key.
The operational fix is not one unified system overnight. It is a recurring cross-reference: pull the Intrastat movement log and the invoice register for the same period, side by side, by country, and confirm the transaction counts and values are explainable against each other.
Required data to hold per country:
- Current Intrastat arrival and dispatch threshold for each destination market
- VAT registration status and effective date per marketplace jurisdiction
- Invoice format required under the local e-invoicing mandate, where one applies
- Filing frequency and deadline for both Intrastat and e-invoicing obligations
- A shared transaction reference linking movement records to invoice records
Common failure points to check for:
- Movements that crossed a threshold mid-year without a corresponding late filing
- Invoices issued in a legacy format after a mandate went live in that country
- Movement records with no matching invoice, or invoices with no matching movement
- Marketplace-collected VAT transactions excluded from internal Intrastat tracking
- No single owner reviewing both feeds against the same reporting calendar
Building the Cross-Reference Matrix Into a Recurring Check
The practical fix is a matrix, not a new system. Build one row per country where you hold VAT registration or move stock, and columns for: current Intrastat threshold, e-invoicing mandate status, invoice format required, filing frequency for each obligation, and the internal owner responsible for that country's reconciliation. This turns two disconnected compliance tasks into one visible reference that finance and operations can both check against.
Run the matrix as a quarterly review, not a one-time setup. Thresholds change, mandate rollout dates shift, and marketplace expansion adds new countries to the list faster than most compliance calendars get updated. A seller managing forwarding to Amazon Europe across several FCs should treat this matrix the same way they treat a customs document checklist: reviewed before volume changes, not after a filing is missed.
Where a country's e-invoicing detail goes deeper than this matrix needs, route that research to the country-specific resource rather than duplicating it here, and keep this document focused on the cross-border mechanism.
A Field Example of the Gap
A seller expands from Germany and France into Italy through Amazon FBA, moving stock via pan-European inbound. Their existing Intrastat process picks up the German dispatch and Italian arrival correctly. What it misses is that domestic B2B invoices issued to an Italian business customer now need to route through SdI in FatturaPA format, an obligation that has nothing to do with the movement that already got declared.
The finance lead only catches this when a business customer's accounts team flags that they cannot recover input VAT on an invoice that was never transmitted through the correct channel, six weeks after the sale.
Movement Trigger
Goods cross an internal EU border. Reportable on Intrastat once the destination country's annual threshold is exceeded, regardless of invoice status.
Invoice Trigger
A taxable transaction is invoiced. Reportable under the local e-invoicing mandate based on format and transmission channel, regardless of whether goods moved that period.
VAT Return Trigger
The periodic VAT return consolidates both, reconciling declared movement values against invoiced sales for that reporting period and market.
Decide the Ownership Question Before the Next Country Launch
The reader decision here is not whether Intrastat or e-invoicing matters more. It is who in your operation owns the cross-reference between them, and whether that owner reviews the matrix before a new marketplace, FC, or fulfillment lane goes live rather than after a filing gap surfaces. Most multi-marketplace sellers already have both data sets somewhere; the missing piece is a recurring habit of checking them against each other by country.
Start with the countries where you currently hold VAT registration, confirm the threshold and mandate status for each, and assign one person to hold the matrix current. If your current setup relies on e-invoicing mandate EU multi-marketplace tracking split across disconnected spreadsheets, that split is exactly where the audit flag tends to originate. Country-specific invoicing detail for Germany and France sits with the specialist resources built for those markets; this matrix is the layer that keeps the cross-border mechanism from falling through the cracks between them.
This article maps the mechanism, not your specific obligations, which depend on your registrations, your marketplace mix, and each country's current rules. Verify your VAT and e-invoicing obligations with a qualified tax advisor before changing your filing process. Where the operational side needs attention, such as aligning warehouse movement data with your reporting calendar, structuring pre-Amazon storage across multiple FCs, or coordinating customs and inventory records that feed Intrastat, FLEX. can help you build the logistics layer that keeps that data clean and audit-ready.
Contact the FLEX. customs team to build a logistics setup that keeps your Intrastat and inventory data clean and audit-ready.
