What if your checkout pricing and invoices suddenly need to speak three different government languages?
Starting January 2026, EU ViDA rollouts, national e-invoicing clearance systems, expanded UK MTD reporting, and tighter US marketplace rules, plus a €3 duty on low-value EU imports, change who collects VAT, how you invoice, and what platforms must report.
If you sell cross-border, that means updating e-invoicing, matching platform data feeds, and reworking carrier and checkout flows now.
Start by auditing your top 20 SKUs, confirming marketplace and carrier support, and patching your accounting system (ERP) invoicing formats.
Key 2026 Cross-Border E-Commerce Tax Changes (Quick Summary)

Starting January 2026, cross-border sellers face overlapping EU, UK, and US tax reporting overhauls that change collection, invoicing, and platform liability rules. The EU ViDA package introduces mandatory structured e-invoicing for many intra-EU B2B transactions, several Member States activate local clearance mandates ahead of the EU-wide 2030 deadline, and import duty rules shift for low-value parcels. In the UK, HMRC expands digital reporting requirements and adjusts import VAT treatment for distance sellers. Meanwhile, multiple US states refine marketplace facilitator collection obligations and reporting thresholds, directly affecting foreign sellers using platforms like Amazon, eBay, and Walmart.
These changes mean sellers must track three separate compliance frameworks, each with distinct registration triggers, filing frequencies, and platform data sharing requirements. A merchant shipping software subscriptions from Ireland to France and physical goods from a Polish warehouse to UK customers now operates under different invoicing schemas, transmission rails, and audit trail rules for each flow. Ignoring any one framework risks penalties, lost VAT deductions, payment delays, and in some cases removal from major marketplaces.
The 2026 wave isn’t a single regulation but a patchwork of national go-live dates, each carrying its own technical format (EN 16931 UBL, national XML, or JSON APIs), government platform (Peppol, KSeF, Chorus Pro), and fallback protocol. Sellers who treat “e-invoicing” as a single checkbox will fail audit checks in Belgium while simultaneously triggering rejection loops in Poland.
Key points every cross-border seller must act on:
Belgium: structured e-invoicing mandatory for domestic B2B from 1 January 2026. PDF-only invoices no longer compliant.
Poland: KSeF clearance rollout on 1 February 2026 (large taxpayers) and 1 April 2026 (most VAT-registered businesses). Government platform validates and assigns unique invoice numbers before invoices are legally issued.
France: all businesses must accept e-invoices from 1 September 2026. Large firms and mid-caps must also issue structured invoices from that date, with SME issuance following in September 2027.
EU import duty change: from 1 July 2026, consignments under €150 shipped by non-EU sellers registered in IOSS attract a fixed €3 customs duty. This affects margin, pricing logic, and returns workflows.
ViDA timeline: while the EU-wide digital reporting requirement for cross-border B2B applies from 1 July 2030, many Member States enforce stricter local mandates in 2026, creating a two-tier compliance landscape through 2030.
EU 2026 VAT Updates and ViDA Rollout Details

The VAT in the Digital Age (ViDA) package was adopted on 11 March 2025 and published on 25 March 2025, setting a pan-EU digital reporting requirement for cross-border B2B transactions from 1 July 2030. However, individual Member States are permitted (and several have elected) to implement mandatory structured e-invoicing and real-time VAT reporting far earlier. This creates a split compliance burden: sellers must meet local 2026 mandates in Belgium, Poland, and France while preparing systems for the broader 2030 EU framework.
ViDA is structured around three pillars. Pillar One covers digital reporting requirements and mandates EN 16931 compliant structured invoicing for intra-EU B2B supplies. Pillar Two extends the deemed supplier rule to additional platform scenarios, making marketplaces liable for VAT on a broader range of transactions (optional from 1 July 2028, mandatory from 1 January 2030). Pillar Three introduces Single VAT Registration (SVR), allowing businesses to fulfill VAT obligations across the EU through one Member State registration, phased in from 1 January 2027 with full rollout by 1 July 2028.
ViDA E‑Invoicing Requirements
Under ViDA Pillar One, every cross-border B2B invoice within the EU must be issued in a structured, machine-readable format aligned with EN 16931 by 1 July 2030. Member States can choose whether to implement a clearance model (invoices validated in real time by a government platform before issuance) or a post-audit model (invoices transmitted via certified channels but not pre-approved). Belgium, Poland, and France have already chosen clearance style or mandatory transmission models for domestic and certain cross-border flows. Sellers operating in those markets must support both local schema requirements and the future EN 16931 standard.
| Regulation Area | 2026 Change | Seller Impact |
|---|---|---|
| Structured e-invoicing (Belgium) | Mandatory for domestic B2B from 1 Jan 2026 | Must generate UBL or CII invoices; PDF no longer compliant for VAT purposes |
| Clearance platform (Poland KSeF) | Phased: 1 Feb (large) / 1 Apr 2026 (most VAT entities) | Invoice not legally issued until government platform assigns unique number; strict fallback SLAs |
| E-invoice receipt (France) | All businesses from 1 Sep 2026 | ERP and accounting must accept Chorus Pro or certified platform formats |
| E-invoice issuance (France) | Large/mid-cap from 1 Sep 2026; SME from Sep 2027 | Two-phase compliance rollout based on firm size; requires certified platform or PDP integration |
| IOSS low-value duty | Fixed €3 duty on consignments < €150 from 1 Jul 2026 | Changes landed cost, checkout pricing, carrier handoff, and returns margin calculations |
Changes to OSS and IOSS Schemes in 2026

The One-Stop Shop (OSS) and Import One-Stop Shop (IOSS) remain the primary mechanisms for simplifying EU VAT reporting, but 2026 brings subtle scope and threshold adjustments that sellers must monitor. The uniform €10,000 annual distance sales threshold for cross-border digital and goods transactions continues to apply. Exceed it in the current or prior calendar year and you must charge destination country VAT from the next sale, either via local registration or through OSS. The new EU SME cross-border exemption threshold of €100,000 EU-wide turnover, introduced in 2025, creates a narrow band where some smaller sellers remain below OSS obligations but above the €10,000 trigger for individual countries.
IOSS, which covers imports of goods valued at or below €150 shipped from third countries, faces two key changes. First, from 1 July 2026, goods sold by non-EU sellers registered in IOSS will attract a fixed €3 customs duty per consignment, even though VAT is collected at checkout and remitted via IOSS. This means pricing, carrier integrations, and returns workflows must account for the new duty. Previously, consignments under €22 were fully duty free. Second, ViDA contemplates eventual abolition of the €150 IOSS threshold altogether, though no firm repeal date has been published. Sellers should plan for IOSS to become a transitional arrangement rather than a permanent compliance shortcut.
From a practical standpoint, sellers using both EU warehousing (Union OSS, quarterly filing) and direct imports (IOSS, monthly filing) must run both schemes in parallel, maintain separate transaction logs for each flow, and reconcile country level VAT rates across both channels. A merchant fulfilling French customers from a German FBA warehouse via Union OSS and shipping direct from Shenzhen via IOSS will file two separate returns each quarter, apply different VAT treatment rules, and face distinct audit trails for the same end customer.
Seller preparation steps for OSS and IOSS in 2026:
Calculate cumulative EU sales per channel: run a 12-month rolling total for cross-border B2C sales (goods plus digital services) to confirm whether the €10,000 threshold is exceeded. If yes, register for OSS or voluntarily opt in to centralize filings.
Verify IOSS intermediary and carrier support for €3 duty: confirm your logistics provider, freight forwarder, or IOSS intermediary has updated systems to handle the 1 July 2026 duty charge and can pass costs transparently to your checkout or invoice customers correctly.
Audit country VAT rate tables: rates change mid-year (example: Estonia moved from 22% to 24% in 2025). Maintain a central rate feed and update ERP/checkout logic when rates shift to avoid back payments and corrections.
Prepare for IOSS threshold abolition: build flexibility into your import flow so that if the €150 ceiling is repealed, you can pivot to standard customs declarations or alternative schemes without replatforming.
UK 2026 Cross-Border VAT and Marketplace Reporting Changes

HMRC is expanding digital reporting obligations and refining import VAT treatment for distance sellers shipping goods into the UK. From April 2026, Making Tax Digital for VAT (MTD) extends to a broader set of transactions, requiring API based submission of VAT returns and supporting data for businesses above the registration threshold. While MTD has been mandatory for VAT-registered businesses since 2019, the 2026 phase tightens transaction level data granularity and shortens submission windows, affecting sellers who previously relied on quarterly bulk uploads or manual CSV reconciliation.
For goods imported into the UK and sold to UK consumers, the treatment depends on value and fulfillment method. Goods valued at or below £135 shipped directly from outside the UK to UK buyers trigger VAT collection at the point of sale (similar to EU IOSS), with the seller or marketplace responsible for remitting UK VAT. Goods above £135, or goods entering UK fulfillment centers before sale, fall under standard import VAT and customs duty rules. In 2026, HMRC is clarifying attribution rules for split shipments (part dropship, part FBA) and tightening proof of export requirements to prevent double VAT charges on returns or re-exports.
Key obligations for sellers shipping from EU or US to the UK in 2026:
MTD compatible software: accounting or ERP systems must support API submission of VAT returns. Spreadsheet only workflows no longer meet HMRC requirements for most registered businesses.
Marketplace collection coordination: if selling via Amazon UK, eBay UK, or Etsy, verify which party (seller or platform) is responsible for collecting and remitting VAT on sub-£135 imports. Misattribution creates compliance gaps and potential double collection.
Evidence of delivery and dispatch: maintain proof of dispatch from origin country and proof of delivery to UK consumer. HMRC audits increasingly request carrier tracking, customs declarations, and end customer delivery confirmations to validate zero rating or import VAT treatment.
Northern Ireland Protocol considerations: goods moving between Great Britain and Northern Ireland, or from EU to Northern Ireland, follow different VAT and customs rules. Sellers with pan-UK distribution must segment inventory and apply correct treatment per destination.
US Marketplace Facilitator and Sales Tax Changes Affecting Cross-Border Sellers

Marketplace facilitator laws now operate in over 45 US states, shifting sales tax collection responsibility from individual sellers to the platform when transactions occur via Amazon, eBay, Walmart, Etsy, or similar marketplaces. For cross-border sellers, this means the platform typically collects and remits sales tax on US sales, but the seller remains responsible for nexus determination, exemption certificate management, and reporting in states where the platform doesn’t facilitate the full transaction (for example, when a sale originates on the seller’s own website and fulfills from a US warehouse).
In 2026, several states are updating economic nexus thresholds, expanding the definition of “marketplace facilitator,” and introducing new reporting requirements for platforms and sellers. Colorado requires marketplaces to report detailed transaction data to the state and issue annual statements to sellers, even when the marketplace collects tax. Washington and California have proposed rules requiring sellers to maintain and produce exemption certificates on demand, including for transactions where the marketplace collected tax, to prove the correct tax treatment during audits. These changes create additional documentation burdens for foreign sellers who don’t have US legal entities or local tax advisers.
Because US sales tax is determined at the state, county, and city level, a single shipment from a California warehouse to a buyer in Aurora, Colorado, can trigger multiple overlapping tax rates and special district charges. Cross-border sellers using multi-channel fulfillment (FBA, third party logistics, dropship) must track physical presence (inventory locations, employees, trade show attendance) in each state to determine nexus, then apply the correct combined rate at checkout. A seller with inventory in Texas, Washington, and New Jersey has nexus in at least three states and must monitor rule changes, threshold updates, and exemption certificate requirements in all three, plus any state where economic nexus (typically $100,000 in sales or 200 transactions per year) is triggered.
Marketplace Platform Obligations for 2026

Marketplace operators face expanded liability and reporting obligations under ViDA Pillar Two and parallel national rules in the EU, UK, and select US states. The deemed supplier rule, already in force since July 2021 for many EU transactions, will extend to additional categories of cross-border and digital sales from 1 July 2028 (optional) and 1 January 2030 (mandatory). Under this rule, the marketplace is treated as both buyer and seller for VAT purposes, meaning the platform (not the individual merchant) owes VAT on facilitated sales. This simplifies compliance for small sellers but requires platforms to capture detailed transaction data, validate seller VAT registrations, and maintain audit ready records for every jurisdiction.
Platforms must also support structured invoice exchange and country specific VAT rate application. When a German buyer purchases from a French seller via a marketplace, the platform must determine whether the transaction is B2B (reverse charge) or B2C (destination VAT), apply the correct French or German VAT rate, generate a compliant invoice or receipt, and report the transaction to the appropriate tax authority. In clearance jurisdictions like Poland, the marketplace needs to submit invoices to the national platform (KSeF) in real time and receive a government assigned invoice number before the transaction is considered complete.
Required Seller Data for 2026 Marketplace Compliance
To meet these obligations, marketplaces will require sellers to provide and maintain accurate master data and transaction details:
VAT identification numbers: valid VAT IDs for every jurisdiction where the seller is registered. Platforms validate IDs against VIES (EU) or national databases and reject incomplete or invalid registrations.
Local tax identifiers: SIREN/SIRET (France), NIP (Poland), CIF (Spain), company registration numbers, and other jurisdiction specific identifiers required for invoice headers and government reporting.
Product classification and HS codes: accurate commodity codes and product categories to determine applicable VAT rates, exemptions, and customs duty treatment for cross-border shipments.
Stock location and fulfillment method: physical warehouse addresses, FBA versus dropship flags, and carrier integrations to support correct VAT treatment (distance sales, import VAT, or local supply) and proof of delivery requirements.
Transaction level metadata: order timestamps, payment methods, buyer country, shipping address, invoice amounts (net, VAT, gross), and currency to enable CESOP reporting (Central Electronic System of Payment Information) and automated VAT return generation.
Documentation, Record-Keeping, and Proof of Compliance Requirements (2026)

Structured e-invoicing and real-time VAT reporting create new documentation standards that replace static PDFs and spreadsheet reconciliations. In clearance jurisdictions, the invoice isn’t considered legally issued until the government platform validates the structured file, assigns a unique identifier, and returns a confirmation receipt. Sellers must retain not only the invoice itself but also the transmission log, validation response, and any rejection or correction records. Audit trails must be immutable, timestamped, and accessible for the retention period specified by each jurisdiction, typically five to ten years.
Cross-border transactions require additional proof of dispatch and delivery. For distance sales under OSS, sellers must maintain evidence that goods left the origin country and arrived in the destination country, such as carrier tracking numbers, customs export declarations, and signed delivery confirmations. For IOSS imports, the seller or intermediary must retain the IOSS VAT identification number, proof that VAT was collected at checkout, the carrier’s customs declaration, and confirmation that the consignment value didn’t exceed €150. Missing or incomplete evidence can result in VAT reassessment, penalties, and loss of IOSS eligibility.
E-invoicing integration extends beyond issuing invoices. Sellers must also accept and process structured invoices from suppliers and service providers. In France, all businesses must be able to receive e-invoices via Chorus Pro or a certified Partner Dematerialization Platform (PDP) from 1 September 2026, regardless of whether the business is required to issue e-invoices at that date. Accounting systems must parse UBL, CII, or national XML formats, extract VAT amounts and line item data, and post entries automatically to the general ledger.
Three categories of verification documents sellers must maintain for 2026 audits:
Transmission receipts and platform confirmations: government or certified platform acknowledgment that an invoice was received, validated, and assigned a unique number (clearance models) or accepted for transmission (post-audit models).
Cross-border shipping evidence: carrier tracking records, proof of export from origin country, proof of import and delivery in destination country, and signed delivery confirmations or digital delivery logs for services.
VAT calculation worksheets and rate tables: documented methodology for determining applicable VAT rate (standard, reduced, exempt, zero rated), including product category, buyer location, and applicable exemption or threshold. Version controlled rate tables with effective dates and change logs.
2026 Compliance Timelines and Seller Preparation Checklist

The 2026 compliance calendar is a cascade of overlapping deadlines, each requiring distinct technical, operational, and governance readiness. Belgium’s 1 January 2026 mandate arrives first, followed by Poland’s phased KSeF rollout in February and April, France’s September receiving and issuing requirements, the EU’s July IOSS duty change, and the Netherlands’ January 2027 audit file update. Sellers operating across multiple jurisdictions can’t sequence these projects linearly. Instead, preparation must run in parallel with shared infrastructure (master data, API integrations, validation logic) and jurisdiction specific outputs (schemas, transmission rails, government platform accounts).
A practical pilot approach starts with Belgium, treating it as a proving ground for data extraction, format generation, transmission, and reconciliation. Belgium’s UBL/CII requirement aligns closely with the future EU-wide EN 16931 standard, making it a logical first implementation. During the pilot, sellers validate that their ERP or accounting system can export the required fields (line item VAT, buyer VAT ID, invoice date, payment terms, product codes), generate syntactically correct UBL or CII XML, transmit the file via Peppol or a certified Access Point, handle acceptance or rejection responses, and post confirmed invoices to the ledger. Once that flow is stable, the same infrastructure can be extended to Poland (with KSeF specific schema adaptations), France (Chorus Pro or PDP integration), and other markets.
Six step preparation checklist for 2026 cross-border VAT and e-invoicing compliance:
Inventory cross-border flows by jurisdiction and channel (weeks 1 to 2): map every sales channel (own website, Amazon, eBay, Shopify), fulfillment method (FBA, dropship, third party logistics), and destination country. Calculate rolling 12 month sales per country to identify OSS, IOSS, and local registration triggers.
Audit master data completeness and accuracy (weeks 3 to 4): verify that every legal entity, warehouse location, and customer record contains valid VAT IDs, local tax identifiers (SIREN, NIP, etc.), and correct legal addresses. Cleanse duplicates and incomplete records. Establish a governance process for ongoing updates.
Select and integrate certified platforms and Access Points (weeks 5 to 8): choose Peppol Access Point providers for EU transactions, register for KSeF and Chorus Pro accounts, configure API credentials, and test connectivity. Ensure ERP or middleware can generate required file formats (UBL, CII, KSeF XML) and handle transmission protocols (AS4, SFTP, REST API).
Build and test invoice generation and validation logic (weeks 9 to 12): develop templates and mappings for each jurisdiction’s schema. Implement pre-validation (schema checks, VAT ID validation, mandatory field checks) before transmission. Create exception workflows for rejections, corrections, and manual overrides. Run end to end tests with sample invoices and confirm acceptance by government or certified platforms.
Establish monitoring, reconciliation, and audit trail controls (weeks 13 to 14): define SLAs for invoice acceptance, payment posting, and exception resolution. Implement automated dashboards tracking transmission success rates, rejection reasons, and outstanding corrections. Configure immutable logs and archiving for invoices, receipts, and transmission metadata.
Conduct Belgium pilot and expand to Poland, France, and IOSS flows (weeks 15 to 20): execute live transactions in Belgium, monitor acceptance and reconciliation, resolve any schema or connectivity issues. Replicate successful patterns for Poland KSeF (phased Feb/Apr 2026), France Chorus Pro (Sep 2026 receiving; issuing per firm size), and IOSS €3 duty handling (Jul 2026). Iterate on exception handling and platform support based on pilot learnings.
Final Words
Act now: 2026 brings major VAT, ViDA, OSS/IOSS, UK digital reporting, and US marketplace shifts.
This post walked through EU ViDA rollout dates, OSS and IOSS rule changes, UK reporting expansions, US marketplace facilitator updates, expanded platform obligations, documentation needs, and a step-by-step readiness checklist.
Track the 2026 cross-border VAT and marketplace tax reporting changes for sellers closely. Run small tests, update invoicing and data flows, and set clear deadlines. Do this early and you’ll avoid surprises and keep revenue steady.
FAQ
Q: How much can I sell online without paying tax in 2026?
A: The amount you can sell online without paying tax in 2026 depends on the buyer and seller jurisdiction; there’s no global exemption. Check local economic-nexus thresholds, OSS/IOSS rules, and marketplace reporting requirements, then register if needed.
Q: What tax changes take effect in 2026?
A: The tax changes taking effect in 2026 include expanded EU ViDA e-invoicing, OSS/IOSS scope shifts, UK digital reporting expansion, and new US marketplace reporting and collection rules. Audit invoices and update registrations to meet higher reporting needs.
Q: How much can I sell on eBay without paying tax in 2026?
A: The amount you can sell on eBay without paying tax in 2026 depends on buyer and seller locations; eBay may collect VAT or report sales. Check eBay’s seller tax guidance and register for VAT/OSS/IOSS where required.
