Common mistakes in Amazon sellers' VAT management

Why Amazon amplifies VAT mistakes

Selling on Amazon in Europe automatically means intersecting: multiple countries, multiple rates, multiple logistics models (FBM, FBA, Pan-EU, EFN). As complexity increases, mistakes are almost never “big conceptual errors”, but operational details that, added together, lead to significant differences between what was paid and what should have been paid.

These mistakes often surface:

• during cross-checks between Seller Central and accounting;
• when preparing the OSS return;
• when a third-party consultant does a full annual reconciliation.

Mistake 1: confusing domestic sales, OSS and “marketplace-handled” sales

A classic: treating all Amazon sales as if they should be declared via OSS. In reality, at least three scenarios coexist in Europe:

• domestic sales in the warehouse country (e.g. IT → IT customer from an IT warehouse);
• intra-EU cross-border B2C sales, which go into the OSS return (e.g. IT → DE, FR, ES);
• sales where Amazon acts as deemed reseller, especially for non-EU sellers and IOSS flows.

If you don’t distinguish these blocks, you risk:

• overstating OSS by including domestic sales;
• declaring sales that are already the marketplace’s tax responsibility;
• understating domestic VAT in the warehouse country.

Mistake 2: ignoring the effects of foreign warehouses (Pan-EU and similar)

Activating Pan-EU or letting Amazon move stock into foreign warehouses creates local VAT obligations in those countries from the very first unit. Typical mistakes:

• thinking OSS covers “all of European VAT” and not just cross-border B2C sales;
• not applying for local VAT numbers in every country where Amazon stores goods;
• not declaring intra-EU stock transfers (FC_TRANSFER in the VAT Transaction Report).

The result: local VAT returns in Germany, France, Poland, etc. are entirely missing, while OSS only shows the cross-border sales.

Mistake 3: not distinguishing B2B from B2C

Many sellers don’t filter B2B sales (with the customer’s VAT number) out of their B2C flows. In Europe:

• intra-EU B2C sales can go into OSS;
• B2B sales follow the rules for intra-community supplies (reverse charge, VIES, etc.) and don’t go into OSS.

If you treat everything as B2C:

• you declare in OSS transactions that should have been intra-community supplies;
• you overload the OSS return with “out-of-scope” transactions;
• you create mismatches with your accounts and Intrastat records.

Mistake 4: using wrong or outdated rates

Amazon can calculate VAT for you via the VAT Calculation Service, but that doesn’t replace your advisor’s verification work. Frequent mistakes:

• sales with standard rates where reduced rates would apply (or vice versa);
• failing to update the rates of countries that have changed them in recent years;
• inconsistency between the actual product category and the tax category applied.

These mistakes create a double risk:

• under-declaration (less VAT than owed) → potential penalties;
• over-declaration (more VAT than owed) → margins eroded unnecessarily.

Mistake 5: importing incomplete or fragmented reports

The foundation of everything is the VAT Transaction Report, but it needs to be used correctly:

• download complete periods (not half-months);
• include all relevant rows (SALE, REFUND);
• don’t skip files for “quiet” months (which might only have a few refunds).

Many sellers discover, during reconciliation, that some months are missing entirely or that files cover overlapping periods. Without complete coverage, every return is suspect.

Mistake 6: not reconciling Amazon with your accounts

Keeping Amazon “separate” from accounting is another common mistake. If you don’t do a periodic reconciliation:

• Amazon fees can be understated or recorded incorrectly;
• the revenue “seen” by OSS may not match the revenue that ends up in your financial statements;
• currency conversion errors (GBP/EUR, etc.) stay hidden.

An annual reconciliation (quarterly is better) between:

• the VAT Transaction Report totals;
• Amazon account statements;
• your general ledger,

is the only way to be sure the numbers really add up.

Mistake 7: thinking OSS “starts on its own”

Many sellers believe that once the €10,000 EU threshold is crossed, OSS “activates” automatically. In reality:

• a formal registration for the OSS scheme with the Agenzia delle Entrate is needed;
• until the declared effective date, sales remain fiscally under a different regime;
• delays in registering can lead to VAT owed retroactively in various countries.

Without a clear activation date, it’s hard to tell which sales should go into OSS and which shouldn’t.

How VATManager helps avoid these mistakes

VATManager is designed precisely to catch these mistakes before they reach the return:

• automatically separates domestic sales, OSS sales, B2B and “deemed reseller” marketplace flows;
• analyses Pan-EU stock movements and flags where local VAT numbers are needed;
• checks consistency between the rate applied and the country/product category;
• checks that periods are complete, highlighting time gaps;
• produces per-country reports aligned with both OSS logic and accounting.

In practice, it turns the VAT Transaction Report into a controllable dashboard, instead of a CSV file that’s hard to interpret.