VAT compliance suspension in the EU: what to do, step by step

TL;DRA VAT compliance suspension on Amazon IT is a listing deactivation or account restriction imposed when Amazon determines that a seller has not met the VAT registration, reporting, or documentation obligations required under EU law or Amazon's own marketplace policies. The suspension is not a criminal finding, and it is not necessarily permanent – but the path back requires specific evidence, a sequenced filing, and an understanding of where EU regulatory levers apply.

This guide covers the exact steps a seller on Amazon IT should take after receiving a VAT compliance notice, where the process typically breaks down, and how to read the decision points that determine whether a full appeal, an internal complaint under EU rules, or a direct legal intervention is the right route. If you are staring at a notice right now, the first thing to know is that the window to respond correctly is short, and a weak first filing narrows what is possible later.

What a VAT compliance suspension on Amazon IT actually is

Amazon's suspension of a seller for VAT compliance reasons is distinct from a standard performance deactivation. It sits at the intersection of Amazon's own policy enforcement and the EU's broader fiscal-compliance obligations – which means the notice, the appeal path, and the available regulatory levers are all different from a typical account health issue.

At its core, the suspension arises because Amazon, operating as a Very Large Online Platform (VLOP) under the Digital Services Act (DSA) and as a gatekeeper subject to the Digital Markets Act (DMA), has commercial and regulatory reasons to verify that third-party sellers trading into EU consumers meet VAT obligations. In practice, this means Amazon IT may restrict or deactivate listings – or hold disbursements – when:

• A seller has not provided a valid Italian (or other relevant EU member-state) VAT number for the jurisdictions where the seller stores inventory or meets sales thresholds.
• Documentation submitted through Amazon's VAT Services portal is flagged as incomplete, expired, or inconsistent with registration records.
• A seller's account is cross-referenced against VIES (the EU's VAT Information Exchange System) and the registration cannot be verified in real time.
• Amazon receives a compliance signal from a tax authority or third-party verification service it uses.

What makes these cases commercially painful is the timing. Inventory is often in Amazon's Italian fulfilment centers. Disbursements are paused. Sales rank erodes daily. In matters we handle, the seller's actual VAT position is frequently correct – the issue is a documentation gap, a mismatch between a recently renewed registration and Amazon's records, or a failure to update the VAT Services tool after a change in business structure.

A VAT compliance suspension is not the same as a tax fraud allegation. It is a policy-level hold, which means it can be resolved through the right evidence. The question is how to present that evidence, to whom, and in what order.

Step 1: Read the notice precisely before doing anything else

The exact wording of the suspension notice determines every subsequent step, and sellers who skip careful analysis of this document consistently make the same mistake: they respond to what they assume the notice says rather than what it actually requires.

Amazon's VAT compliance notices on Amazon IT typically fall into one of several categories, and the required response differs for each:

• Registration gap notice – Amazon cannot confirm a valid VAT registration for Italy (or for another EU jurisdiction where the seller stores goods). The remedy is documentary: a current VAT registration certificate, ideally with a VIES-verifiable number.
• Documentation update required – The seller's VAT number is registered but the documentation on file is outdated, relates to a prior legal entity, or has not been updated after a business restructuring. The remedy is an updated certificate plus, often, a short cover letter explaining the chain of continuity.
• OSS / IOSS compliance query – The notice flags One Stop Shop (OSS) or Import One Stop Shop (IOSS) registration for cross-border B2C sales. This is common for sellers shipping from outside the EU into Italian consumers or using pan-EU FBA. The remedy involves confirming the OSS/IOSS registration number and, sometimes, providing evidence of return filings.
• Third-party referral notice – Amazon states that a compliance signal came from a third-party verification partner or a tax authority referral. These are the most complex to resolve because the root of the flag is outside Amazon's direct control.

Before filing any response, confirm: which category applies, which specific documents are requested, and whether there is a stated deadline. Amazon's deadlines on VAT compliance notices are real. A missed deadline can shift the suspension from a hold into a formal termination, which activates a different (and slower) path under the Business Solutions Agreement (BSA) and the Platform-to-Business (P2B) Regulation.

Step 2: Gather and verify the right documentation

This is where most appeals fail. Sellers submit what they have rather than what was specifically requested, and the gap between the two is what triggers an auto-rejection or a second hold.

The core document set for an Italian VAT compliance response depends on notice type, but typically includes:

1. Current VAT registration certificate for Italy, issued by the Agenzia delle Entrate – the Italian tax authority. The certificate must match the legal entity name on the Amazon account exactly. A discrepancy of even one word (e.g., "SRL" vs. "S.r.l.") can cause a mismatch in Amazon's verification system.
2. If the seller uses OSS or IOSS: the OSS/IOSS registration confirmation, the member-state of identification, and – where Amazon specifically asks for it – evidence of at least one submitted return period.
3. If the business structure changed: a document trail connecting the old entity to the new one (merger certificate, business transfer deed, or equivalent) so that the VAT history is unbroken in Amazon's records.
4. A clear cover statement – not a lengthy narrative but a precise, factual explanation of the current registration status, the reason for any gap, and confirmation that the issue is resolved.

We regularly see sellers submit documents that are correct in substance but contain metadata or formatting that Amazon's automated systems reject: PDFs that are password-protected, scans at low resolution, or certificates in Italian without a translation note where Amazon's system expects English. Check every file before submission.

One seller, an electronics accessories brand selling on Amazon IT and Amazon DE (spring 2025), came to us after two rejections. Both times the VAT certificate was valid. The problem was that the certificate had been issued to the holding company rather than the trading subsidiary named on the Amazon account. We prepared a chain-of-entity document pack and a precise cover letter tracing the corporate relationship, and the account was restored. The fix was not legal argument – it was document precision.

Step 3: File the response through the right channel – and preserve the record

Amazon IT provides two primary channels for responding to a VAT compliance suspension: the Seller Central case log and, where it is available, a dedicated VAT compliance submission portal linked from the notice. Using the wrong channel is a common procedural error that delays resolution by weeks.

The correct channel is always the one specified in the notice. If the notice links to a specific upload tool, use only that tool. If it routes to a Seller Central case, open and respond to that case – do not open a separate parallel case, because the two threads can conflict in Amazon's ticketing system.

When filing, follow this sequence:

1. Subject line / case title: state the notice type and the VAT number at issue. Example: "VAT Compliance Documentation – IT VAT No. [number] – Response to [Notice Reference]". Amazon's teams handling these queues work at volume; clarity accelerates routing.
2. Opening paragraph: one or two sentences confirming what is being provided and why the account is compliant. Do not open with apologies or lengthy explanations. Amazon's review teams respond to factual statements, not narratives.
3. Document list: enumerate each attachment by name and its purpose. ("Attachment 1: Agenzia delle Entrate VAT registration certificate, issued [date], confirming VAT No. [X] for [entity name].")
4. Closing statement: confirm that the documentation resolves the specific gap identified in the notice and invite a specific response if further verification is required.

Save a dated copy of everything submitted. If this matter later proceeds to an internal complaint under the P2B Regulation, to a DSA-based statement of reasons request, or to formal arbitration under the BSA dispute-resolution path, the submission record is the foundation of your position.

Step 4: If the first response is rejected – what the EU regulatory path adds

EU-based sellers – including those selling on Amazon IT – have procedural rights that do not exist for sellers on Amazon US, and this is where the myth that "EU sellers have no leverage once a platform suspends them" is most clearly wrong. Those rights are grounded in the Platform-to-Business (P2B) Regulation and the Digital Services Act (DSA).

If your initial response is rejected, or if Amazon does not respond within a reasonable period, the following tools are available:

• Statement of reasons (DSA / P2B): Under the P2B Regulation, Amazon is required to provide a specific, individualized statement of reasons when it restricts or suspends a seller's account or listings. If the notice you received does not contain a meaningful explanation – a generic reference to "VAT policy" does not qualify – you are entitled to request a detailed statement. This request, properly framed, creates a written record and often triggers a more substantive internal review.
• Internal complaint mechanism (P2B Article 11): Amazon is required to operate an internal complaint-handling system for business users. A formal complaint through this mechanism, properly referencing the P2B Regulation and the specific deficiency in the original notice, is processed separately from a standard Seller Central appeal. In matters we handle, this route frequently surfaces a case reviewer with authority to override an automated rejection.
• DSA transparency obligations: As a VLOP, Amazon is subject to DSA transparency requirements that extend to its content moderation and enforcement processes. Where a seller can document that the enforcement action was inconsistent with Amazon's stated policies – for example, where the notice cited a document requirement that the seller had already met – the DSA framework provides a basis for a structured escalation.

These tools are not automatic fixes. They add procedural steps and require careful drafting. But they meaningfully expand the seller's options past the standard Seller Central appeal-and-reject loop. For more on how EU regulatory levers apply across a range of suspension types, our complete guide to EU marketplace regulation for sellers covers the full architecture of the seller's rights framework.

It is also worth noting that where a VAT compliance suspension intersects with a broader enforcement pattern – for example, where a competitor has filed a complaint, or where a tax-authority referral is part of a wider investigation – the strategy shifts considerably. For the specific question of how to structure and file an EU marketplace delisting appeal, our analysis of appealing an EU delisting covers the current procedural landscape in detail.

The steps above describe the standard path. Your situation turns on the exact wording of the notice, the documentation history, and the account structure – which is what we review first. To get a read on where your matter stands, email info@tutamenlaw.com.

Step 5: Decision points and trade-offs the seller needs to own

Every VAT compliance suspension on Amazon IT presents a set of forks in the road. Getting the sequence right is less about legal argument and more about understanding which path fits the specific account, history, and commercial timeline.

Fork 1: Self-representation versus professional assistance. A straightforward documentation gap – a single outdated certificate, a minor entity-name mismatch – can often be resolved by an organized seller acting alone, provided the underlying VAT position is clean and the notice is clearly a first-level documentation check. The risk of self-representation rises sharply when: the first response has already been rejected; the notice involves a third-party referral; the account has a prior compliance history; or the business structure is complex (multiple entities, pan-EU FBA, OSS across member states). In those cases, an imprecise second filing can close off options that a correctly framed first escalation would have kept open.

Fork 2: Speed versus completeness. Amazon's response windows can be short. The temptation is to file the most readily available documents quickly, even if the full document pack is not yet assembled. This is nearly always the wrong trade-off. A partial response that does not address the specific gap identified in the notice will be rejected, and the rejection creates a record that makes a subsequent complete response harder to have reviewed on its merits. Assemble the complete, correct pack first. If the deadline is genuinely impossible to meet with the right documents, request an extension through the case log before the deadline passes – not after.

Fork 3: Amazon's internal process versus external escalation. The P2B and DSA tools described in Step 4 are most effective when used in sequence with Amazon's internal process, not in parallel or prematurely. Filing a formal P2B complaint before exhausting the standard appeal path can antagonize the process without adding leverage. The standard path first, then the internal complaint mechanism if that path fails, then DSA escalation if the complaint mechanism does not produce a reasoned response – that is the sequence that works.

Fork 4: Restoration only versus broader compliance audit. A VAT compliance suspension is sometimes a symptom of a broader gap in the seller's EU tax architecture. If the suspension exposed a real issue – an unregistered EU establishment, an OSS registration that covers fewer member states than the actual distribution, or a filing gap in the Italian returns – treating only the Amazon-side suspension without addressing the underlying compliance position creates a repeated-suspension risk. Where relevant, we flag this to sellers as part of the initial review, because resolving the Amazon notice and ignoring the underlying position is a short-term fix that shortens the next cycle.

For sellers also monitoring how German market regulation affects their EU account health, our breakdown of Bundeskartellamt proceedings and sellers provides a useful cross-reference on how different EU regulatory bodies interact with marketplace enforcement.

Where VAT compliance suspension appeals typically go wrong

After handling a range of VAT compliance suspensions for Amazon IT sellers, we see the same failure patterns consistently. They are worth naming directly because they are avoidable.

Filing too fast with the wrong documents. The urgency is real. But a rushed first response that does not address the specific notice category sets a negative record. Amazon's review systems weight the history of a case. A clean first filing that takes an extra day to assemble is usually better than an immediate partial filing.

Misreading which entity the VAT number must match. For sellers operating through holding structures, parent companies, or nominee arrangements, the entity on the Amazon account and the entity on the VAT certificate must align exactly – or the relationship between them must be documented precisely. This sounds elementary, but it is the single most common cause of rejection in complex cases we see.

Treating Amazon's VAT compliance team as a tax authority. Amazon is not the Agenzia delle Entrate. It is a marketplace verifying documentation against its own policy requirements. Arguments about the merits of a tax position – "our accountant says we don't need an Italian VAT number because we use FBA from a German warehouse" – are not relevant to Amazon's review team. The review team needs documents that satisfy Amazon's policy. Tax arguments belong in a separate channel if the underlying position is genuinely in dispute.

Missing the P2B window. The P2B Regulation and the DSA give sellers specific rights, but those rights are most effectively used within a defined escalation sequence. Sellers who exhaust time in back-and-forth with Seller Central support and then discover the P2B complaint mechanism late sometimes find that the factual record in the case log has already narrowed their position. Knowing the full toolkit before starting the process matters.

Assuming the suspension is about something it is not. Occasionally, what arrives labeled as a VAT compliance suspension is actually a linked-account flag, a payment-verification hold, or a General Product Safety Regulation (GPSR) enforcement action that has been miscategorized in Amazon's notice template. If the documents you are submitting feel like the wrong answer for the question being asked, look harder at the underlying notice. We have seen sellers spend weeks supplying VAT documentation for a hold that was, at root, a product safety issue. The resolution path for each is entirely different.

Related areas of practice

Related areas

• EU Marketplace Regulation – full practice covering DSA, P2B, DMA, and EU suspension defense for marketplace sellers
• Amazon Account Reinstatement – account deactivation strategy for US and EU Amazon surfaces, including plan-of-action work

If a first appeal or filing has already come back rejected, a second read of the full case history can identify the specific reason it failed and what, if anything, remains open. Email info@tutamenlaw.com with the notice and the rejection, and we will tell you what we see.

Frequently asked questions

How long does resolving a VAT compliance suspension on Amazon IT usually take?

Resolution time varies considerably depending on notice type, the completeness of the documentation submitted, and whether escalation to the P2B internal complaint mechanism is required. A straightforward documentation gap – a current certificate that simply needed updating – can clear within days of a correct filing. Cases involving third-party referrals, entity-structure complexity, or a prior rejection typically take several weeks. Cases that require a formal P2B complaint and a reasoned response from Amazon can take longer still. The single largest variable we observe is whether the first response fully addressed the specific notice category – a targeted, complete first filing compresses the timeline; a partial or misdirected filing extends it.

What are the main risks if I handle a VAT compliance suspension alone?

The primary risk is not losing the case – it is foreclosing better options through an imprecise filing. Amazon's case history for a seller's account is cumulative. A rejected response that frames the issue incorrectly creates a record that a subsequent filing has to work around. The second significant risk is missing the P2B and DSA escalation window: sellers who are not aware of their EU regulatory rights often exhaust time in the standard Seller Central loop and reach the external escalation tools too late or with a weakened record. The third risk is conflating the Amazon compliance issue with the underlying tax position and giving Amazon's review team arguments that belong in a tax-authority channel instead of documents that satisfy marketplace policy.

Do I need a lawyer for a VAT compliance suspension in the EU?

Not always. A seller with a clean VAT position, a single entity, a clearly identified documentation gap, and no prior rejection history can often resolve the matter with organized, precise self-representation. Legal assistance becomes substantially more valuable – and cost-effective, given the revenue at risk – when: the account has a prior compliance history; the first response has already been rejected; the business structure involves multiple entities or jurisdictions; the notice references a third-party referral or a tax-authority signal; or the seller wants to use P2B or DSA escalation tools, which require specific regulatory framing to be effective. We work with sellers at any point in the process, and a short initial review of the notice and account history is usually enough to clarify which route applies. Fee structures are fixed and quoted up front after that review.

About Tutamen

Tutamen is an independent law firm for online marketplace sellers. We represent Amazon, Walmart, Etsy and eBay sellers in account deactivations, frozen-funds recovery, intellectual-property disputes, arbitration and Notices of Dispute, and US federal Schedule A defense, plus EU marketplace regulation. Our work is attorney-led and confidential, with fees quoted up front. We act for founders, brand owners and in-house teams who need a specialist for a marketplace dispute. Our EU practice covers the full range of DSA, P2B, DMA, and GPSR compliance enforcement across EU surfaces, with cases handled in English. To discuss your situation, email info@tutamenlaw.com.

Disclaimer: This article is general information, not legal advice, and does not create an attorney-client relationship. Marketplace policies and the law change, and every account and case is different. For advice on your situation, contact Tutamen at info@tutamenlaw.com.

Written by Dmitri Aronov – Partner, EU Marketplace Regulation. Published February 19, 2027.