EU E-Invoicing Mandates: What Amazon and Cross-Border Sellers Need to Do
VATAi TeamEU E-Invoicing Mandates: What Amazon and Cross-Border Sellers Need to Do
Your VAT invoice looks correct. Amazon makes it available to the customer. Your accountant includes the sale in the VAT return. So what does an e-invoicing mandate actually change?
For an in-scope transaction, the invoice also needs to be created in the right structured format and delivered through the required route. A familiar PDF download does not prove that those requirements have been met.
For Amazon Pan-EU sellers and multichannel brands, the first question is not which software to buy. It is which selling entities and transactions are covered, in which countries, and from when. A German company, a French subsidiary and a non-EU business holding several European VAT numbers do not automatically have the same obligations.
At VATAi, we recommend mapping that scope before changing your invoicing setup. This guide explains the key EU e-invoicing mandates, the deadlines that matter and the checks your finance and operations teams should prioritise.
E-invoicing means exchanging structured invoice data that business systems can process automatically. An ordinary PDF is not a structured e-invoice. National mandates already apply in several EU markets; ViDA's cross-border B2B digital reporting starts on 1 July 2030. Your obligations depend on establishment, transaction type and national rules—not simply the countries where you have VAT numbers.
What is e-invoicing—and is a PDF invoice enough?
E-invoicing is the creation, delivery and receipt of an invoice as structured data, allowing the buyer's system to read fields such as supplier details, invoice number, taxable amount and VAT without manual re-entry.
A PDF shows a person what the invoice says. A structured invoice tells software what each field means. That distinction matters when your customer, a national platform or the tax authority needs to process the data automatically.
Format and delivery are separate checks. A valid file still needs to reach the correct recipient or platform. Conversely, uploading a PDF to an online portal does not turn it into structured invoice data.
EN 16931 is the European standard for the core invoice data model. It does not mean every country uses the same portal or submission workflow. The country table below identifies the main routes sellers need to recognise.
Sources: European Commission: what e-invoicing means, European standard overview
Do EU e-invoicing mandates apply to your business?
Start with the legal entity issuing the invoice, not the Amazon storefront. Selling on Amazon.de does not, by itself, establish that your business falls under Germany's domestic B2B mandate.
Work through five questions for each sales flow:
- Who is the supplier? Identify the selling company and whether a marketplace is acting as supplier for that particular transaction.
- Where is that company established? Separate its business establishment, any relevant fixed establishments and countries where it only holds a VAT registration.
- Who is buying? Distinguish business customers, consumers and public bodies. B2B, B2C and B2G rules are not interchangeable.
- What transaction is taking place? Identify domestic sales, cross-border sales, imports and own-stock movements separately.
- What must happen to the data? Check invoice issuance, invoice receipt and tax reporting independently, including the applicable start dates.
A VAT identification number alone does not establish a fixed establishment. Equally, do not decide the issue from an FBA warehouse address alone: assess the actual operating arrangements and the relevant country's rules. Record the conclusion so your finance team and software provider work from the same assumptions.
Sources: EU VAT implementing rules, Article 11 and Polish Ministry of Finance guidance on fixed establishments for KSeF.
EU e-invoicing deadlines: eight key markets for sellers
The table covers major Pan-EU inventory and European sales markets, not all 27 EU Member States. It focuses on general business invoicing. Public-sector contracts, exemptions and special transactions need separate checks. Dates and status were checked on 31 August 2026.
For Poland, also check incoming invoices: the in-scope KSeF receipt requirement began on 1 February 2026, before some businesses' issuance deadline. A later date for sending invoices does not automatically postpone the date for receiving them.
Three distinctions that prevent expensive mistakes
France: outside e-invoicing does not mean outside e-reporting
A foreign business without a French fixed establishment is outside France's domestic invoice-exchange mandate. However, French-taxable transactions for which it owes French VAT can trigger e-reporting.
For affected foreign suppliers, the start is 1 September 2026 for large/intermediate-sized businesses and 1 September 2027 for smaller businesses. For affected acquisitions where the foreign buyer accounts for VAT, the date is 1 September 2027 regardless of size. This deserves attention when reviewing inventory arrivals into France.
Relevant European VAT one-stop-shop exclusions also need checking. Do not report the same flow simply because it appears in your French sales report. Businesses required to e-report must select an approved platform for submission.
Spain: two reforms, two implementation decisions
Spain's B2B e-invoicing reform concerns invoice exchange between businesses. Its RRSIF billing-software rules, which include the VERI*FACTU option, concern how invoicing systems create and protect billing records.
The tax authority gives 1 January 2027 for in-scope corporate income taxpayers and 1 July 2027 for other in-scope taxpayers to adapt to RRSIF. These are not universal Spanish B2B e-invoice start dates. VERI*FACTU is a compliance mode, not the name of the entire B2B mandate.
For B2B e-invoicing, the reviewed ministry implementing order is still labelled a draft. This guide therefore uses the adopted decree's 12/24-month trigger, not a projected launch date. Confirm the final order and its effective date before scheduling your rollout.
Sources: AEAT's RRSIF/VERI*FACTU FAQ, AEAT's separate B2B reform notice and ministry draft implementing order.
A VAT return is not evidence that an invoice was delivered
Treat three outcomes separately: the transaction is recorded correctly, the invoice is issued and delivered correctly, and required data reaches the tax authority. Completing one does not prove the other two happened.
For your control process, retain submission identifiers, acknowledgements and error messages where the relevant system provides them. Give someone responsibility for investigating failures. An invoice marked “generated” in an order system is not the same as a successfully completed national submission.
What changes for Amazon Pan-EU and Amazon Business sellers?
Amazon Business: invoice availability and legal compliance both matter
Amazon's published Business invoicing policy requires the customer document within one business day after dispatch confirmation. Sellers not required to apply VAT provide receipts. Credit notes for returns follow a one-business-day deadline after return confirmation.
Those platform requirements sit alongside the national rules. When a structured invoice is mandatory, uploading the usual customer-facing PDF does not, on its own, satisfy the format and routing obligation.
Amazon describes its VAT Calculation Service as calculating VAT and generating invoices on the seller's behalf. Do not treat that description as confirmation of every country's e-invoicing integration. Verify the current service coverage for your entity, country, transaction type and invoice corrections.
Pan-EU: country-level stock data still needs transaction-level logic
Inventory placement tells you where goods are held. It does not tell you everything needed to decide the invoicing obligation for the next order.
Your workflow should connect the selling entity, dispatch country, customer status, destination, VAT treatment and invoice issuer. Keep inventory transfers separate from customer orders: a warehouse move is not a sale to an Amazon Business buyer.
The operational risk is a rule applied too broadly—for example, sending every order with a Polish VAT number into the same KSeF workflow—or too narrowly, such as ignoring incoming structured invoices because most sales are B2C.
Multichannel brands: one provider connection is not complete coverage
An Amazon invoicing tool does not automatically cover your Shopify store, wholesale orders or distributor invoices. Map each channel to its invoice system and reporting route.
For founders and CFOs, the commercial issue is also cash flow and workload. Missing customer references, mismatched company details or failed delivery can create invoice disputes and manual rework. These are operational risks, not a claim that every invoice error automatically blocks payment or triggers the same penalty across Europe.
Example: one brand, three different invoicing outcomes
Consider a hypothetical German-established brand selling on Amazon and its own website, with inventory in Germany and Poland and business customers in France.
- A German domestic B2B order: assess Germany's mandate and the issuer's transition eligibility. The brand already needs to receive structured invoices; its outgoing-invoice deadline is a separate check.
- An order dispatched from Polish stock: if the brand has only Polish VAT registration and no Polish fixed establishment, registration alone does not put it into mandatory KSeF issuance. Its VAT accounting still needs handling.
- An order to a French business customer: do not select France's domestic e-invoicing route solely because the buyer is French. Check the supplier's establishment and whether the transaction is domestic or cross-border; assess any reporting obligation separately.
The lesson is practical: build invoice rules around transactions, not a list of VAT numbers. This example illustrates the scope tests above; it is not a ruling on a particular seller's establishment or tax treatment.
A practical e-invoicing checklist for CFOs and compliance teams
At VATAi, we recommend turning the country analysis into an operating checklist with named owners.
- Create an obligation register. For each entity and country, record establishment status, transaction scope, receive/send/report deadlines, exclusions, evidence and the person who approved the conclusion.
- Confirm provider coverage in writing. List the required format, delivery network or national platform, incoming-invoice support and channels covered. Ask what happens to credit notes, cancellations and rejected submissions.
- Clean the source data. Check company names, VAT IDs, customer identifiers, invoice numbers, addresses, tax codes, currency and links to original invoices. Add country-specific fields only where required.
- Prevent duplicate invoicing. Decide which system issues the legal invoice and which merely displays a copy. Do not let the ERP, marketplace and external connector independently issue conflicting documents for one sale.
- Test more than a successful sale. Include refunds, partial returns, discounts, split shipments, incorrect buyer data and a platform outage. Confirm the permitted local recovery process rather than assuming a late PDF fixes it.
- Retain the right evidence. Preserve structured originals and required records, not only screenshots or rendered PDFs. Apply the relevant country's retention and integrity requirements.
- Reconcile all three views. Match orders and refunds to invoices, then reconcile the invoice/reporting data with VAT and OSS records. Assign an owner for discrepancies before period close.
For software budgeting, compare the complete process: integrations, transaction charges, receiving, archiving, exception handling and support. A low cost per invoice is not a complete estimate if your team must resolve every failed submission manually.
Useful acceptance test: pick one real sales flow and demonstrate its path from order to invoice, recipient delivery, required tax reporting, correction and retrieval from the archive. Repeat that test for each materially different country/channel flow.
What changes under ViDA from 1 July 2030?
ViDA—the EU's VAT in the Digital Age package—introduces digital reporting based on e-invoicing for covered intra-EU cross-border B2B transactions from 1 July 2030.
That is not the first deadline for all European e-invoicing. National rules in the table apply on their own schedules, several years earlier. Nor should sellers confuse this with the Single VAT Registration reforms starting on 1 July 2028: those address different VAT registration and reporting issues.
The EU timeline also includes a 1 January 2035 alignment milestone for domestic real-time reporting systems covered by the transition. It is not permission for sellers to ignore existing national mandates until 2035.
For a European brand, the sensible design goal is reusable invoice data with country-specific routing. Prepare a reliable data foundation now while keeping the implementation calendar tied to the actual obligations of each entity.
Sources: European Commission: ViDA implementation timeline and the adopted Directive (EU) 2025/516.
Frequently asked questions
Is e-invoicing mandatory across the whole EU in 2026?
No. Several countries already mandate structured invoices for defined transactions, but there is no single 2026 start date covering every EU business. Apply the national scope tests now and separately prepare for ViDA's covered cross-border B2B rules from July 2030.
Does an Amazon-generated PDF meet an e-invoicing mandate?
An ordinary PDF alone does not meet a structured-invoice requirement. Confirm whether the service also creates and transmits the required structured document for the relevant transaction. The buyer's downloadable view is not enough to verify that process.
Does a local VAT number make a non-EU seller subject to e-invoicing?
Not by itself. VAT identification and establishment are different concepts. Several domestic mandates exclude non-established foreign businesses, but national reporting rules still need checking. France's foreign-business e-reporting is an important example.
Are B2C-only sellers unaffected?
No. An in-scope business can still have incoming-invoice obligations even when its customers are consumers. Some countries also regulate B2C invoice issuance or transaction reporting. Check purchases and sales separately.
Is Peppol compulsory throughout Europe?
No. Peppol is an invoice-exchange network, not a single EU-wide tax filing portal. Belgium uses it as the default route for its B2B mandate; other countries use different arrangements. Select the connection your actual obligations require.
Can we stop filing VAT returns once e-invoicing is connected?
Do not stop filings on that assumption. Invoice exchange, transaction reporting and VAT returns serve different purposes. Keep required domestic VAT and OSS filings until a specific applicable rule changes the obligation.
VATAi supports marketplace and multichannel sellers with VAT & EPR registration, filing and ongoing compliance, alongside OSS registration and reporting. Bring your entity list, stock countries, sales channels and current invoicing tools to the discussion so your VAT setup and invoicing project can be assessed together.