ViDA E-Invoicing Mandate: Country-by-Country Timeline 2026-2030
The VAT in the Digital Age (ViDA) package transforms EU VAT compliance. This guide maps every national e-invoicing mandate, the Peppol BIS 3.0 / UBL 2.1 standard, digital reporting requirements, and your compliance roadmap. Updated September 2026.
What Is ViDA? The Two Pillars
The VAT in the Digital Age (ViDA) package — adopted 2024, applying 2026-2030 — has two core pillars:
📄 Pillar 1: E-Invoicing Mandate
Structured electronic invoicing (EN 16931 / UBL 2.1 / Peppol BIS 3.0) becomes mandatory for B2B and B2G.Paper/PDF invoices are not accepted for VAT deduction once a mandate applies to that transaction. This is scope- and date-dependent, per country - not a single EU-wide switch-off date.
📊 Pillar 2: Digital Reporting (DRR)
Real-time or near-real-time transaction reporting to tax authorities. Invoice data (or summary) transmitted automatically at or near issuance. Replaces periodic VAT returns for mandated transactions.
Key Definitions
| Term | Meaning |
|---|---|
| EN 16931 | European standard for e-invoicing (semantic data model). Mandatory baseline. |
| UBL 2.1 | Universal Business Language — XML syntax implementing EN 16931. Most common format. |
| Peppol BIS 3.0 | Peppol Business Interoperability Specification — network + UBL 2.1 profile for cross-border. |
| Access Point | Certified service provider connecting you to Peppol network (like email provider for e-invoices). |
| SMP/SML | Service Metadata Publisher/Locator — directory to find recipient's Access Point. |
| DRR | Digital Reporting Requirements — real-time VAT data transmission to tax authority. |
EU-Level Timeline
| Date | Milestone | Impact |
|---|---|---|
| 11 Mar 2025 | ViDA Directive adopted (EU) 2025/516 | Legal framework established. Member States transpose into national law. |
| Jan 1, 2026 | Earliest national mandates apply | Italy, Poland, France (large taxpayers), Spain (large) — B2B e-invoicing mandatory |
| By Jan 1, 2027 | OSS and IOSS clarifications | Minor legislative clarifications affecting the One-Stop Shop and IOSS schemes take effect. Member States must transpose the ViDA directive by 31 December 2026. What the OSS €10,000 threshold change actually does. |
| Jul 1, 2028 | Single VAT Registration begins | Single VAT Registration reforms start, mandatory reverse charge applies to supplies by non-identified suppliers, and platforms in short-term accommodation rental and road passenger transport fall under the new deemed-supplier rules. |
| Jan 1, 2029 | DRR Phase 1 | Real-time reporting for cross-border B2B in mandated countries |
| Jul 1, 2030 | Cross-border B2B digital reporting | Digital Reporting Requirements apply to cross-border B2B transactions in all Member States. Periodic VAT returns are simplified or abolished. |
| By Jan 1, 2035 | Domestic systems align with the EU model | Member States with a domestic digital real-time reporting obligation must align their systems with the EU model and standards. This is the final phase of ViDA. |
| 2030-2032 | Full ViDA operational | Single VAT registration, real-time cross-border clearance, VAT gap < €10B target |
Note: Exact dates vary by Member State transposition. Above reflects latest national legislation as of Sept 2026. Always confirm with local tax authority.
Country-by-Country Mandate Status (Sept 2026)
| Country | B2G Mandate | B2B Mandate | DRR Start | Standard/Network | Authority/Portal |
|---|---|---|---|---|---|
| Italy | Since 2019 (SDI) | Since 2019 (all B2B) | Since 2019 | FatturaPA (UBL-based) / SDI | Agenzia Entrate / SDI |
| Poland | Since 2020 (KSeF) | July 2024 (voluntary), Feb 2026 mandatory | 2024+ | KSeF (national platform) / UBL | KAS / KSeF |
| France | Since 2020 (Chorus Pro) | Sep 2026 (large), Sep 2027 (all) | 2026+ | Chorus Pro / UBL 2.1 / Peppol | DGFiP / Chorus Pro |
| Spain | Since 2015 (FACe) | July 2025 (large), July 2027 (all) | 2026+ (Veri*factu) | FacturaE / UBL 2.1 / Peppol | AEAT / Veri*factu |
| Belgium | Since 2017 (Mercurius) | Jan 2026 (large), Jan 2027 (all) | 2026+ | Peppol BIS 3.0 / UBL 2.1 | FPS Finance / Peppol |
| Romania | Since 2022 (RO e-Factura) | Jan 2024 (high risk), July 2026 (all) | 2024+ | RO e-Factura / UBL 2.1 | ANAF / SPV |
| Latvia | Since 2021 | Jan 2025 (B2G), Jan 2027 (B2B) | 2026+ | Peppol / UBL 2.1 | VID / Peppol |
| Germany | Jan 2025 (B2G mandatory) | Jan 2028 (phased) | 2028+ | Peppol / EN 16931 / XRechnung | KoSIT / Peppol |
| Austria | Since 2014 (EBInterface) | Jan 2028 (phased) | 2028+ | EBInterface / Peppol | BMF / Peppol |
| Netherlands | Since 2017 (Simplerinvoicing) | Jan 2028 (phased) | 2028+ | Peppol / UBL 2.1 | Logius / Peppol |
| Portugal | Since 2019 (SPV) | Jan 2028 (phased) | 2028+ | CIUS-PT / UBL 2.1 | AT / SPV |
| Greece | Since 2022 (myDATA) | Jan 2028 (phased) | 2024+ (myDATA) | myDATA / UBL 2.1 | AADE / myDATA |
| Hungary | Since 2021 (Online Számla) | Jan 2028 (phased) | 2021+ (Online Számla) | Online Számla / UBL | NAV / Online Számla |
| Others (CZ, SK, SI, EE, LT, LU, MT, CY, HR, FI, SE, DK, IE) | Various | 2028-2030 (per ViDA) | 2028+ | Peppol / National | National tax authorities |
Deep Dives: Key Countries
Italy — The Pioneer (Since 2019)
Italy's Sistema di Interscambio (SDI) is the world's longest-running mandatory B2B e-invoicing system.
- Scope: All B2B, B2G, B2C (optional)
- Format: FatturaPA (Italian UBL profile)
- Transmission: Via SDI (central hub) — sender → SDI → recipient
- Identification: Codice Destinatario (7-char) or PEC email
- Penalties: 90-180% of VAT for non-compliance
- Archival: 10 years, digital, with timestamp + signature
Lesson for others: Central hub model works but creates single point of failure. Peppol's decentralized network is now preferred EU model.
Poland — KSeF (National Platform)
Poland chose a national platform (KSeF) over Peppol for domestic, Peppol for cross-border.
- Mandatory: February 2026 (postponed from July 2024)
- Format: UBL 2.1 with Polish extensions (FA(2), FA(3) schemas)
- Process: Invoice → KSeF → KSeF assigns KSeF number → recipient notified
- No KSeF number = no VAT deduction for recipient
- Integration: ERP → KSeF API (REST) or via certified integrator
- Cross-border: Peppol BIS 3.0 via certified Access Points
France — Chorus Pro → PDP (2026-2027)
France is transitioning from central platform to decentralized PDP (Plateformes de Dématérialisation Partenaires) model.
- Phase 1 (Sep 2026): Large enterprises (CA > €150M) — mandatory e-invoicing via PDP
- Phase 2 (Sep 2027): All taxpayers — mandatory e-invoicing via PDP
- DRR (e-reporting): Transaction data to DGFiP for all B2B (even if not e-invoiced)
- Format: UBL 2.1 (EN 16931) + French extensions (CIUS-FR)
- Network: Peppol for cross-border, PDP-to-PDP for domestic
- PDPs: Certified private platforms (20+ certified as of 2026)
Spain — Veri*factu + TicketBAI
Spain has dual tracks: national Veri*factu + regional TicketBAI (Basque Country, Navarre).
- Veri*factu (national): Mandatory July 2025 (large), July 2027 (all). Software must be certified by AEAT.
- TicketBAI (Basque/Navarre): Real-time ticket/invoice reporting to regional tax authority.
- Format: FacturaE 3.2.2 (UBL-based)
- Key difference: Veri*factu = software certification. TicketBAI = real-time push.
Germany — XRechnung + Peppol (2025/2028)
- B2G mandatory: Since Jan 2025 (XRechnung via Peppol or ZRE/OZG-RE)
- B2B mandate: Jan 2028 (phased by turnover)
- Standard: XRechnung (German CIUS of EN 16931) + Peppol BIS 3.0
- No central hub: Decentralized Peppol network. Choose any certified Access Point.
- DRR: Expected 2028+ aligned with EU DRR
Technical Requirements: What Your Invoice Must Contain
EN 16931 defines mandatory semantic elements. Your UBL 2.1 / Peppol BIS 3.0 invoice must include:
| Element | Required? | Example |
|---|---|---|
| Invoice number (unique, sequential) | Yes | INV-2026-001234 |
| Invoice date | Yes | 2026-09-15 |
| Invoice type code (380=invoice, 381=credit note) | Yes | 380 |
| Seller: legal name, address, VAT ID | Yes | Acme GmbH, Berlin, DE123456789 |
| Buyer: legal name, address, VAT ID | Yes | Client SA, Paris, FR12345678901 |
| Seller/Buyer: Peppol Participant ID (for Peppol) | Peppol only | 0192:DE123456789 |
| Line: description, quantity, unit price (net) | Yes | Consulting, 10 days, €1,200/day |
| Line: VAT rate + category code (S=standard, R=reduced) | Yes | 19%, S |
| Line: VAT amount + net amount | Yes | VAT €2,280, Net €12,000 |
| Total: VAT per rate, net total, gross total | Yes | Net €12,000, VAT €2,280, Gross €14,280 |
| Payment terms + means | Yes | Net 30, SEPA transfer |
| Currency (EUR or other + rate) | Yes | EUR |
| Invoice period (if different from date) | Conditional | 2026-09-01 to 2026-09-30 |
| Purchase order reference | Conditional | PO-2026-0456 |
| Delivery/acceptance details | Conditional | Delivered 2026-09-14 |
| Reverse charge / exemption reference | Conditional | Art. 196 Dir 2006/112/EC |
| Digital signature / seal (for authenticity) | Country-specific | XAdES-BES / QES |
Pro tip: Our UBL E-Invoice Kit generates compliant UBL 2.1 / Peppol BIS 3.0 XML from CSV/PDF. Test it before your mandate date.
Peppol Network: How It Works
4-Corner Model
Corner 1: Sender
Creates UBL 2.1 invoice in ERP
Corner 2: Sender's Access Point
Validates, signs, routes via Peppol
Corner 3: Recipient's Access Point
Receives, validates, delivers to ERP
Corner 4: Recipient
Receives structured invoice in ERP
Choosing an Access Point (2026 Certified Providers)
| Provider | Coverage | API/Integration | Best For |
|---|---|---|---|
| Unifiedpost / Banqup | EU-wide | REST API, ERP connectors | Mid-market, multi-country |
| Basware | Global | SAP, Oracle, Microsoft certified | Large enterprise, complex ERP |
| OpusCapita | Nordics + EU | API, EDI, Peppol | Nordic-focused, supply chain |
| Storecove | EU + 30 countries | REST API, webhooks | SaaS, developers, e-commerce |
| Visma / AutoInvoice | Nordics + DACH | ERP integrations | Visma ERP users |
| CGI / Pagero | Global | API, SAP, Oracle | Large multinational |
| Sovos / TrustWeaver | Global compliance | API, tax determination | Complex multi-jurisdiction |
Registration Process
- Choose Access Point (above)
- Register your Peppol Participant ID:
0192:[VAT_ID](e.g.,0192:DE123456789) - Publish to SMP (Service Metadata Publisher) — Access Point does this
- Test: send test invoice to Peppol test participant
- Go live: update ERP to send/receive via Access Point API
Your Compliance Roadmap (By Business Profile)
Profile A: EU SME, Domestic Only (e.g., German Freelancer)
- Now: Ensure invoices meet §14 UStG (PDF OK for now)
- 2025: Test Peppol via Access Point (free tiers available)
- 2027: Mandate check — if turnover > threshold, switch to structured
- 2028: Full B2B e-invoicing via Peppol
Profile B: EU Mid-Market, Cross-Border B2B (e.g., Polish SaaS)
- Now: Register for KSeF (Poland) / Peppol Access Point
- 2026: Mandatory KSeF for domestic. Peppol for EU clients.
- 2027: DRR reporting for cross-border (if mandated)
- 2028: Full EU DRR alignment
Profile C: Non-EU Selling Digital Services to EU (e.g., US SaaS)
- Now: Non-Union OSS for VAT. PDF invoices accepted.
- 2028+: ViDA may extend e-invoicing to non-EU digital suppliers. Monitor.
- Prep: Ensure billing system can generate UBL 2.1 / Peppol BIS 3.0
Profile D: Non-EU Selling Goods to EU (e.g., UK Fashion)
- Now: IOSS for ≤ €150. Standard import for > €150.
- 2026+: If EU warehouse → Union OSS + domestic e-invoicing mandate
- 2028+: Full ViDA DRR for intra-EU movements
Implementation Checklist
Phase 1: Assess (Now)
- [ ] Map all invoice flows: domestic B2B, cross-border B2B, B2G, B2C
- [ ] Identify mandate dates per country (table above)
- [ ] Audit current invoice format: PDF? Paper? Structured data available?
- [ ] Check ERP capability: UBL 2.1 export? Peppol integration?
- [ ] Estimate volume: invoices/month per country
Phase 2: Pilot (6-12 months before mandate)
- [ ] Select Access Point (test 2-3)
- [ ] Register Peppol Participant IDs per entity
- [ ] Build/test UBL 2.1 generation from ERP
- [ ] Send test invoices to friendly trading partners
- [ ] Validate received invoices import correctly
- [ ] Document error handling: rejected invoices, missing fields
Phase 3: Go Live (Mandate Date)
- [ ] Switch production invoicing to structured format
- [ ] Stop accepting paper/PDF for VAT deduction (mandated scope)
- [ ] Train AP/AR teams on new workflow
- [ ] Monitor rejection rates (target < 2%)
- [ ] Archive: 10 years, immutable, with timestamp
Phase 4: DRR Readiness (2026-2028)
- [ ] Map data fields: invoice → DRR report
- [ ] Implement real-time/near-real-time push to tax authority
- [ ] Reconcile: DRR data = VAT return = ledger
- [ ] Prepare for periodic VAT return simplification/abolition
Cost Estimates (2026)
| Component | SME (100 inv/mo) | Mid-Market (5,000 inv/mo) | Enterprise (50,000+ inv/mo) |
|---|---|---|---|
| Access Point subscription | €0-50/mo (free tier) | €200-500/mo | €1,000-5,000/mo |
| Per-invoice fee | €0.10-0.30 | €0.05-0.15 | €0.01-0.05 |
| ERP integration (one-time) | €0 (native) - €5,000 | €10,000-50,000 | €50,000-200,000 |
| Testing & onboarding | €500-2,000 | €5,000-15,000 | €20,000-50,000 |
| Annual total (est.) | €500-3,000 | €15,000-50,000 | €100,000-500,000 |
ROI: Studies show 60-80% cost reduction vs paper/PDF processing (printing, postage, manual entry, errors, disputes). Typical payback: 6-18 months.
Tools to Help You Prepare
🧾 UBL E-Invoice Kit
Upload CSV/PDF → generate valid UBL 2.1 / Peppol BIS 3.0 XML → download. Test your data structure before mandate.
🔍 VAT Validator
Verify your trading partners' VAT numbers on VIES before sending e-invoices. Invalid VAT = failed delivery.
📄 Invoice Generator
Create compliant PDF invoices today. Structured data export ready for UBL conversion.
Disclaimer: This guide is informational — not tax or legal advice.ViDA Directive (EU) 2025/516 and national transpositions evolve. Always confirm with your tax advisor, Access Point provider, or national tax authority. Last verified September 2026.