Top 7 Risks of Rising Freight Costs for German Importers
14.05.2026
Top 5 Compliance Weaknesses in EU Inventory Transfers
16.05.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.
German tax authorities have access to more cross-border transaction data than most e-commerce operators realise. Marketplace platform operators are required to report seller turnover to the Bundeszentralamt für Steuern, customs declarations feed into import VAT records, and intra-EU stock movements leave traces in acquisition VAT filings — or they should. When those data points do not align with what a seller has declared, the gap becomes a signal. Not every gap triggers a formal audit, but certain patterns draw attention reliably and repeatedly. This article identifies seven of those patterns, explains the specific data mismatch that creates exposure, and describes the documentation and filing discipline that reduces the risk. It is written as operational guidance for finance teams and e-commerce operators, not as legal advice. For any specific VAT position, a qualified tax adviser should be consulted. The goal here is to help operators understand where their fulfilment and compliance workflows may be creating audit-visible inconsistencies before those inconsistencies become a formal inquiry.
1. Turnover Declared Does Not Match Marketplace Data Submitted to German Tax Authorities
Since the EU's DAC7 directive came into force, marketplace platforms operating in Germany are required to report seller transaction data to national tax authorities. This means the Bundeszentralamt für Steuern receives structured data on gross sales, return credits, and fee deductions for sellers active on major platforms. When a seller's VAT return shows declared turnover that does not reconcile with the platform-reported figures, the discrepancy is visible at the authority level without any manual audit trigger being needed.
The most common cause of this mismatch is not deliberate under-declaration. It is a timing and categorisation problem. Sellers often declare net revenue after platform fees, while the platform reports gross transaction value. Others exclude promotional credits or voucher redemptions from their declared figures without applying a consistent methodology. Some sellers operating across multiple storefronts on the same marketplace consolidate figures incorrectly, particularly when one storefront is registered for German VAT and another is not.
The practical control here is reconciliation before filing, not after. Finance teams should obtain the platform's transaction report for each VAT period and map it line by line against the figures being submitted. Where the methodology for excluding fees, credits, or returns differs from what the platform reports, that difference should be documented and defensible. Sellers using FBA inventory management across multiple European fulfilment centres should also confirm that their German VAT registration captures all taxable supplies originating from German stock, not only orders placed on the German storefront.
2. Intra-EU Stock Transfers Without Corresponding Acquisition VAT Declarations
When goods move from a warehouse in one EU member state to a fulfilment centre in Germany — whether as part of an Amazon pan-European programme, a multi-country inventory distribution, or a seller-managed replenishment — that movement is treated as a deemed intra-community supply and a corresponding deemed acquisition. The seller is required to declare the acquisition in Germany and, in most cases, hold a valid German VAT registration at the point the goods arrive.
The audit signal here is the absence of acquisition VAT entries in a German VAT return for a seller who is known to hold stock in German fulfilment centres. Customs and logistics data, combined with marketplace inventory records, can indicate that goods are present in Germany. If the VAT return shows no acquisition entries, or if the acquisition values appear inconsistent with the volume of stock held, that gap is a recognisable pattern for tax authority review.
Sellers enrolled in Amazon's pan-European FBA programme are particularly exposed to this trigger if they have not registered for VAT in every country where Amazon places their inventory. A German VAT registration alone does not resolve the obligation if stock is also being held in Poland, the Czech Republic, or other programme countries. The operational fix requires mapping every country where inventory is physically located, confirming VAT registration status in each, and ensuring that intra-EU stock transfer values are reported consistently in both the origin and destination country returns. Pre-Amazon storage arrangements that involve cross-border consolidation before FC delivery should be reviewed with the same lens.
3. High Return Credit Note Volume Relative to Gross Sales
A high ratio of credit notes to gross sales is a data pattern that can attract scrutiny in any VAT audit context, but it is particularly relevant for e-commerce operators in Germany, where consumer return rates in certain product categories are structurally high. The issue is not the returns themselves — those are a normal feature of German e-commerce. The issue is whether the credit notes issued to customers are correctly reflected in the VAT return, and whether the volume and value of credits is consistent with what the marketplace platform has reported.
Two specific failure modes appear regularly. The first is a seller who processes return credits in their accounting system but does not adjust the output VAT figure in the corresponding VAT period. The credit note reduces the revenue line but the VAT liability is not corrected, creating an overpayment that, paradoxically, can still trigger questions if the declared figures do not match platform data. The second failure mode is the reverse: a seller who reduces output VAT for returns that were not actually completed — for example, where the customer initiated a return but the goods were not received back into stock, or where a refund was issued as a goodwill gesture without a physical return.
The documentation standard that prevents both problems is a closed-loop return record: a credit note linked to a confirmed return receipt, a restocking entry or disposal record, and a VAT adjustment in the correct period. For sellers using removal handling services or third-party returns processing, the returns data from those providers needs to feed into the VAT reconciliation, not sit in a separate operational system that finance never sees. Return credit note volume should be reviewed as a ratio against gross sales each period, and any spike should be investigated before the VAT return is filed.
4. OSS Declarations Not Reconciling With German Domestic VAT Filings
The One Stop Shop scheme allows sellers to declare and pay VAT on cross-border B2C sales to EU consumers through a single registration in their home member state, rather than registering in every destination country. For sellers who are also registered for German VAT — because they hold stock in Germany, import goods into Germany, or make domestic supplies — the OSS and the German VAT return must be carefully separated. Sales that qualify for OSS reporting must not appear in the German VAT return, and sales that are taxable in Germany must not be reported through OSS.
The audit trigger arises when the combined figures from OSS declarations and German VAT returns either overlap or leave gaps. A seller who reports all B2C sales through OSS but also holds German stock may be incorrectly routing domestic German supplies — where the goods are already in Germany at the point of sale — through OSS rather than the German VAT return. Domestic supplies from German stock are not eligible for OSS and must be declared locally. Conversely, a seller who has German VAT registration but has not activated OSS may be under-declaring on cross-border B2C sales to other EU countries.
The reconciliation test is straightforward in principle but operationally demanding: for every order, the location of the goods at the point of dispatch determines whether the supply is domestic (German VAT return) or cross-border B2C (OSS eligible). Sellers using FBA inventory management across multiple European fulfilment centres need their order management system to capture the dispatch warehouse for every transaction, not just the delivery country. Without that data, the split between OSS and domestic German VAT cannot be made accurately, and the resulting declarations will not reconcile.
5. FBA Inventory Movements Creating Taxable Events Absent From VAT Returns
Amazon's fulfilment network moves inventory between warehouses without seller instruction and often without seller visibility at the transaction level. When goods move between fulfilment centres located in different EU member states, those movements are intra-community transfers that carry VAT obligations in both the origin and destination country. When goods move between fulfilment centres within Germany, the movement itself does not create a cross-border VAT event, but it does affect which FC is the dispatch point for subsequent customer orders — which matters for OSS eligibility and domestic supply classification.
The audit exposure comes from sellers who have not built a process to capture these FC-to-FC movements in their VAT compliance workflow. Amazon provides inventory event data through Seller Central reports, but that data is not automatically formatted for VAT return input. A seller who relies on sales order data alone — without reconciling it against inventory movement data — will miss the intra-community transfer entries that should appear in their German VAT return and in the recapitulative statement (Zusammenfassende Meldung). Over multiple VAT periods, the cumulative gap between inventory movements and declared acquisitions can become significant.
The operational fix requires a regular pull of Amazon's inventory ledger reports, mapped against the VAT registration countries in the seller's fulfilment footprint. For sellers using pan-European FBA or the European Fulfilment Network, this mapping should be done at least monthly, and the resulting intra-EU transfer values should be reviewed by the VAT compliance team before each return is filed. Sellers who have recently changed their fulfilment structure — for example, moving from a single German FC to a multi-country distribution model — should treat the transition period as elevated risk and consider a retrospective review of prior period returns.
6. Customs Import Value Significantly Below Selling Price
When goods are imported into Germany and the declared customs value is materially lower than the price at which those goods are subsequently sold, the gap can attract scrutiny from both customs authorities and VAT auditors. The concern is not only import duty — it is whether the import VAT base accurately reflects the transaction value, and whether the pricing relationship between related entities involved in the import chain is consistent with arm's-length principles. Sellers who import from affiliated suppliers, use intercompany pricing, or declare a manufacturing cost rather than a transfer price should ensure their customs valuation methodology is documented and defensible. EORI registration records, customs declarations, and sales data are all accessible to German tax authorities, and a persistent gap between import value and retail price is a visible signal in that data set.
7. Late or Amended Filings After a Fulfilment Structure Change
A change in fulfilment structure — moving warehouse locations, switching from self-fulfilment to FBA, adding a new European FC, or changing the legal entity responsible for imports — almost always creates a transitional VAT compliance gap. The old filing pattern no longer fits the new operational reality, and the new pattern takes time to implement correctly. Amended returns filed shortly after a structural change, or returns filed late during a transition period, are a recognised audit signal because they suggest the compliance framework did not keep pace with the operational change. The practical control is to involve the VAT compliance team in any fulfilment restructuring before it goes live, not after the first return under the new structure has already been filed incorrectly.
When to Escalate Beyond Internal Review
Escalate to a qualified VAT adviser when more than one of these seven triggers applies simultaneously to your current filing position. Revisit your compliance setup when you add a new fulfilment country, change your import entity, or enrol in a new Amazon programme that redistributes inventory across borders. Bring in operational support when your returns processing or FBA inventory data is not feeding into your VAT reconciliation — because the compliance gap is then a data infrastructure problem, not only a filing problem, and it will recur every period until the data flow is fixed.
Fixing the Handoff Between Operations and VAT Compliance
Most of the seven triggers described in this article are not caused by deliberate non-compliance. They are caused by a structural disconnect between the operational systems that generate the data — marketplace platforms, fulfilment networks, customs declarations, returns processors — and the compliance workflow that is supposed to capture and declare that data correctly. The seller's finance team is often working from accounting system exports that do not include FC-level inventory movements, return receipt confirmations, or intra-EU transfer records. The result is a VAT return that is internally consistent but externally inconsistent with the data that tax authorities already hold.
The practical priority for any operator selling into Germany through FBA or a multi-country fulfilment model is to audit the data flows first, before auditing the returns themselves. Identify every system that generates a VAT-relevant event — order management, inventory management, returns processing, customs clearance, platform reporting — and confirm that each feeds into the VAT reconciliation process in the correct period and with the correct categorisation. Where gaps exist, they should be closed before the next return is filed, not after a query arrives.
If your current fulfilment setup involves cross-border inventory movements, FBA prep services, or pre-Amazon storage in Germany, the operational layer and the compliance layer need to be aligned. FLEX. works with operators at the point where fulfilment decisions and VAT obligations intersect — if you are reviewing your German fulfilment structure and want to understand where the compliance handoffs need to be tightened, that is a conversation worth having before the next filing period.
Seven data patterns consistently draw VAT audit attention in German cross-border e-commerce: turnover mismatches against platform-reported figures, intra-EU stock transfers without acquisition VAT entries, credit note volumes inconsistent with return records, OSS and domestic German VAT returns that do not reconcile, FBA inventory movements absent from VAT declarations, customs import values significantly below selling price, and late or amended filings following a fulfilment structure change. Each trigger reflects a gap between operational data and declared figures — and each is preventable with the right reconciliation discipline and data infrastructure in place.
