EU Customs Overload: 30-, 60- and 90-Day Compliance Milestones
25.07.2026
Pan-EU Import VAT Refund Audit: 9 Checks to Run on Your Cross-Border Customs Filings After the Austrian Court Ruling
26.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 seller registers for VAT in Germany, gets the number issued, and starts moving stock from a Polish warehouse the same week. Then the invoice gets flagged: the German VAT number does not validate on VIES, so the zero-rated intra-Community transfer cannot be justified on paper. The stock has already moved. The paperwork has not caught up.
This is not a rare edge case. VIES VAT validation checks whether a VAT number is active in the database each member state feeds to the European Commissionās system, and new registrations often lag before they show as valid. If a number sits in unconfirmed status while goods cross a border, the seller is exposed to local VAT charges, Amazon compliance flags, or a stalled EC Sales List entry. The fix usually is not legal; it is timing and sequencing.
What VIES Validation Actually Confirms
VIES VAT validation checks one specific thing: whether a VAT identification number is currently active in a member stateās tax authority database at the moment of the query. It does not confirm that a company is compliant, that its returns are filed, or that its intra-Community activity is registered correctly ā only that the number itself resolves as valid right now.
For cross-border e-commerce, this matters because the zero-rate treatment on intra-Community supply depends on both parties holding a valid, verifiable VAT number at the time of the transaction. When a seller moves inventory between an Amazon FC in Germany and a 3PL facility in Poland, or invoices a business customer in another member state, the invoicing system often checks VIES status automatically. A failed check can mean the transaction defaults to local VAT rules instead of the zero-rated cross-border treatment the seller expected.
In practice, a VIES rejection is frequently an activation lag rather than a real problem with the registration. Newly issued VAT numbers can take time to sync into the shared database, and the exact lag depends on the member stateās own processing queue, not on anything the seller did wrong.
What to confirm before stock crosses a border
Before treating a cross-border stock movement as VAT-free, confirm the VAT number status directly through the VIES portal, not just through internal records. A number can be legitimately registered with a tax authority while still showing as unconfirmed in the shared EU database for a period after issuance.
Check the registration date against the planned transfer date. If the VAT number was issued in the last few weeks and the intra-EU cross-border activation has not yet synced, that gap is the most common source of failed validation ā not a fault in the underlying registration.
Also confirm which entity is invoicing the movement. If stock is transferring between a sellerās own warehouses in Poland and Germany under the same VAT identity, the documentation trail and the VIES check both need to reflect that single entity correctly across both country records.
What breaks when the number does not validate
When VIES VAT validation fails at the point of invoicing, the zero-rate intra-Community supply treatment cannot be applied with confidence. The transaction may need to be re-issued with local VAT charged instead, which changes pricing, reconciliation, and the sellerās own input VAT position.
On Amazon specifically, automated marketplace verification checks can flag a mismatch between the VAT number on file and its VIES status. This can trigger a hold on listings tied to that marketplace account, or a request for the seller to re-submit VAT documentation before inventory in that country is released for sale.
There is also a reconciliation cost. If a supply was invoiced as zero-rated but the VAT number was not valid at that moment, it can create a mismatch on the EC Sales List (recapitulative statement) that the seller or their accountant has to explain retroactively, which is a slower and more expensive fix than catching the gap before the shipment moves.
Where Responsibility Actually Sits
The VAT registration and its VIES status are the sellerās legal and tax responsibility, confirmed through their own tax advisor or the relevant national tax authority. This is not something a 3PL or fulfillment partner can activate or validate on the sellerās behalf. What a logistics partner can control is the operational side: making sure inventory movement between facilities happens in a way that matches what the sellerās VAT documentation actually supports.
This distinction gets blurred in practice because the two problems surface at the same moment. A rejected VIES check and a stalled cross border stock transfer look like one operational failure from the warehouse floor, but they have different owners. The tax registration status needs to be resolved through the sellerās VAT registration process; the physical movement of goods between hubs can be sequenced by the logistics partner so that a shipment does not go out ahead of confirmed VAT readiness.
In multi-country inventory positioning ā splitting stock across a Polish and a German hub, for example ā the practical safeguard is holding the transfer until the VAT number tied to the destination country shows as active on VIES, rather than assuming registration confirmation and database sync happen on the same day.
Checks before a cross-border transfer
- VAT number confirmed active on the official VIES lookup, not just on the registration certificate
- Registration date compared against the planned stock movement date to flag activation lag risk
- Correct legal entity name matching across both the sending and receiving country registrations
- Invoice template set to reflect zero-rated intra-Community supply only once VIES status is confirmed
- EC Sales List (recapitulative statement) draft checked against the same transaction before filing
Signals something is off
- Amazon Seller Central shows a VAT-related listing hold or inventory restriction in a specific marketplace
- An invoicing system rejects a transaction or defaults to local VAT unexpectedly
- A tax advisor flags a mismatch between filed EC Sales List entries and actual stock movement records
- A newly issued VAT number still fails the VIES check weeks after confirmed registration
- Stock physically arrives at a destination hub before VAT documentation for that country is confirmed ready
Operational controls for stock positioning
- Sequence cross border stock transfer VAT compliance checks before, not after, the shipment leaves the origin hub
- Keep a standing log of VAT numbers per country with their last confirmed VIES check date
- Route Amazon FC forwarding in Europe only once the destination countryās VAT status is confirmed active
- Separate pre-Amazon storage inventory by VAT jurisdiction so a hold in one country does not freeze unrelated stock
Who owns what in a VIES dispute
- Seller or their tax advisor owns registration, activation timing, and correspondence with the national tax authority
- Logistics partner owns physical sequencing of stock movement against confirmed VAT readiness
- Amazon Seller Central account owner owns responding to marketplace VAT verification requests directly
- Finance or bookkeeping owns EC Sales List reconciliation and correcting any zero-rate transactions filed in error
The Decision Rule Worth Applying
If a VAT number has not shown as active on VIES for more than a few weeks after registration, treat any planned zero-rated stock transfer to or from that country as on hold until the sellerās tax advisor confirms the status directly with the relevant tax authority. Moving goods ahead of that confirmation shifts the risk from a paperwork delay to a retroactive audit exposure, which is a much harder problem to unwind.
Where FLEX. fits into this picture is on the logistics side of that decision, not the tax side. Running dual-hub warehousing across Poland and Germany means inventory can be held or released from either facility depending on which countryās VAT documentation is actually ready, rather than forcing a single all-or-nothing shipment. That flexibility is what turns a VIES rejection from a full stop into a scheduling problem.
The practical sequence is: confirm VAT status first, release stock second, reconcile EC Sales List entries third. Skipping the order does not save time; it just moves the delay downstream to a more expensive stage, usually during a tax authority review months later.
Owner: Seller / Tax Advisor
VAT registration, VIES activation, and correspondence with the tax authority sit with the seller and their advisor. A logistics partner cannot validate or accelerate this status on the sellerās behalf.
Checkpoint: VIES Status Log
Keep a dated record of the last confirmed VIES VAT number check per country. Recheck before any cross-border stock transfer, not only at initial registration.
Escalation: Hold Before Ship
If VIES status is unconfirmed, hold the shipment at the origin hub rather than releasing it and hoping documentation catches up before an audit.
What to Lock In Before the Next Cross-Border Shipment
A VIES rejection rarely means the underlying VAT registration is wrong. More often it means the database sync has not caught up with a recent registration, or a stock movement was scheduled without checking status first. Either way, the fix is procedural: confirm status, then move stock, not the other way around.
The decision an operator actually needs to make is where the checkpoint sits in the shipping process. If VIES confirmation happens after a pallet has already left a Polish hub for a German Amazon FC, the seller is reacting to a problem instead of preventing one. Building that check into the pre-dispatch routine, alongside carton labeling and pallet structure confirmation, closes that gap.
Multi-country inventory positioning works when the logistics side and the tax side move in the same order: registration confirmed, VIES validated, then stock released between hubs. FLEX.ās dual-hub warehousing in Poland and Germany is built around that sequencing, holding inventory at either facility until the sellerās VAT documentation supports the release.
A rejected VIES check is a tax and registration question first, and FLEX. does not offer tax filing or legal advice on VAT status. What FLEX. does provide is the operational layer around it: EU VAT-aware fulfillment and dual-hub warehousing across Poland and Germany that holds or releases stock in step with confirmed VAT readiness, rather than forcing a shipment before the paperwork is settled.
If your team is expanding into multi-country stock positioning and needs the logistics side sequenced correctly around VAT compliance and cross-border activation, get in touch with FLEX. to review how inventory could move between hubs without outrunning your VAT documentation. Verify VAT registration and VIES status directly with your tax advisor or the relevant national tax authority before relying on this content for compliance decisions.
