EU E-Invoicing & Peppol EN16931 2026: Country Mandates Roadmap & Implementation Guide

The 2026 EU E-Invoicing Landscape at a Glance

No two European e-invoicing systems look identical on the wire, but every single one now sits on the same semantic model — EN16931. The card grid below summarises the six national systems covered in this guide; keep it handy as you read each deep-dive section.

1. EN16931 — The European Semantic Standard

What EN16931 Actually Is

EN16931-1 is the European standard "Electronic invoicing — Part 1: Semantic data model of the core elements of an electronic invoice", published by CEN (European Committee for Standardization) in October 2017 and republished as the consolidated EN16931:2017+A1:2019 in 2019. It is the legal reference cited by Directive 2014/55/EU on electronic invoicing in public procurement and, by extension, by every subsequent national B2B e-invoicing law in the EU. EN16931 does not specify a wire format — it defines a semantic data model: fields, codes, business rules and validation constraints every compliant invoice must carry. The standard has roughly 180 information elements (e.g. BT-1 Invoice number, BT-3 Invoice type code, BT-9 Payment due date, BT-31 Seller VAT identifier, BG-25 Invoice line) and around 500 business rules grouped into BR (mandatory), BR-CO (cross-rules) and BR-S/Z/E/AE (VAT category rules).

EN16931-2 and EN16931-3 — Syntaxes and CIUS

EN16931-2 specifies two permitted XML syntaxes: UBL 2.1 (OASIS, used by Peppol BIS Billing 3.0, KSeF, Belgium, the Netherlands and most Nordics) and UN/CEFACT CII (used by XRechnung Germany and by France's Factur-X / ZUGFeRD hybrid PDF). EN16931-3 defines how member states publish a CIUS (Core Invoice Usage Specification) — a constrained subset of EN16931 with extra national fields. Production examples: XRechnung CIUS adds Leitweg-ID routing, mandatory bank account and German tax codes; Peppol BIS Billing 3.0 CIUS removes optional fields ambiguous across countries; Italian FatturaPA is a semantic mapping rather than a strict CIUS but conformance to EN16931 was added in 2020.

Why EN16931 Matters Strategically

EN16931 is the reason 2026 is a tractable problem rather than 27 separate problems. Every national mandate is ultimately a CIUS or mapping on the same field set. A single canonical invoice object — en16931:Invoice — can be serialised to FatturaPA XML for Italy, KSeF FA(2) for Poland, XRechnung for Germany, Peppol BIS 3.0 for Belgium / Netherlands / France's PDP route, and Verifactu JSON for Spain. This is exactly how Zunapro is built.

EN16931 Legal Status in 2026

EN16931 is referenced as the legal basis in Directive 2014/55/EU (mandatory B2G EU since April 2020), Italian D.Lgs. 127/2015 (FatturaPA semantic conformance from 2020), the Polish KSeF Act of 16 June 2023 (FA(2) baseline), French Ordonnance 2021-1190, German Wachstumschancengesetz § 14 UStG, Belgian Royal Decree of 19 December 2023, and the EU ViDA package (Council adoption March 2025) which confirms EN16931 as the EU-wide reference for July 2030 onwards.

2. Peppol BIS Billing 3.0 — The Dominant Implementation

The Origins of Peppol

Peppol (originally "Pan-European Public Procurement Online") began in 2008 as an EU-funded project to enable cross-border public procurement. In 2012 the network was transferred to OpenPeppol AISBL, a Belgian non-profit international association headquartered in Brussels with 700+ member organisations across 40+ countries (including non-EU jurisdictions: Norway, the UK, Singapore, Australia, New Zealand, Japan, USA GSA pilot). Peppol is therefore not an EU institution — it is a global open-network standard governed by OpenPeppol. The European Commission strongly recommends it for the 2014/55/EU directive, but member states are free to use any EN16931-compliant transport.

Peppol BIS Billing 3.0 — The Concrete Profile

Peppol BIS Billing 3.0 is the OpenPeppol Business Interoperability Specification for invoice exchange. Released in 2018 and updated quarterly, it is an EN16931 CIUS (strict subset, no optional ambiguous fields), serialised in UBL 2.1 XML, exchanged over the Peppol four-corner network using AS4 (Applicability Statement 4) transport with mTLS, identified by urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0.

The Four-Corner Model

Peppol exchange follows a strict four-party topology: C1 sender's ERP, C2 sender's Access Point, C3 receiver's Access Point, C4 receiver's ERP. Routing between C2 and C3 uses the Peppol SML (Service Metadata Locator) — a DNS-based lookup that resolves a receiver's Peppol identifier (e.g. 0208:0479394530 for a Belgian VAT number) to the receiver's SMP (Service Metadata Publisher), which lists supported document types and Access Point endpoint. No central tax authority sits in the path — the structural opposite of the Italian SdI or Polish KSeF clearance model.

Peppol BIS 3.0 in Production — Country Coverage

By mid-2026 Peppol BIS 3.0 is the primary or required transport in Belgium (mandatory B2B from January 2026), the Netherlands (Peppol via Simplerinvoicing since 2017, mandatory B2G), Luxembourg (mandatory B2G since 2023), Denmark, Sweden, Finland, Norway (Peppol-default for B2G since 2019–2022), France (one of two interop methods via PDPs from September 2026), Germany (one acceptable EN16931 carrier for E-Rechnung), and Ireland, Estonia, Latvia and Lithuania (Peppol B2G live).

3. Country Mandates Timeline 2017–2028

The single most useful artefact for a European seller is a chronological view of who has to do what by when. The timeline below summarises the six headline mandates, in order of go-live.

Italy — FatturaPA via SdI (Mandatory since 1 January 2019)

Italy was the first major EU member state to make B2B e-invoicing universally mandatory. The platform — Sistema di Interscambio (SdI) — has been operated by Agenzia delle Entrate (via SOGEI) since 2014, originally B2G only (mandatory June 2014). On 1 January 2019, D.Lgs. 127/2015 extended the mandate to all domestic B2B and B2C. By 2026 SdI processes roughly 2.5 billion FatturaPA documents per year.

FatturaPA technical highlights: pre-clearance CTC — invoice not legally valid until SdI returns a positive ricevuta di consegna; proprietary FatturaPA XML (not Peppol UBL but semantically EN16931-aligned since 2020); Codice Destinatario — 7-character routing code identifying the receiver's intermediary; PEC (Posta Elettronica Certificata) as alternative routing when no Codice Destinatario is set; Esterometro — separate report for cross-border invoices, now folded into SdI cross-border flows since 2022. Italy added FatturaPA mandates for forfettario small taxpayers (turnover under EUR 25,000) in stages 2022–2024, completing the universalisation.

France — Chorus Pro + PDPs (B2G 2017, B2B 2026–2027)

France's e-invoicing journey began with Chorus Pro, the central B2G platform operated by AIFE (Agence pour l'Informatique Financière de l'État) since January 2017. Chorus Pro onboarded suppliers in waves from large enterprise (2017) down to micro-entreprises (2020). The B2B mandate, originally planned for July 2024 and delayed twice, now sits at: 1 September 2026 — all French VAT-registered businesses must be able to receive structured e-invoices, and large and intermediate companies must issue; 1 September 2027 — SMEs and micro-entreprises must issue. The architecture is a Y-model: businesses connect either directly to the Portail Public de Facturation (PPF) — Chorus Pro extended for B2B — or via a Plateforme de Dématérialisation Partenaire (PDP), a private certified provider. PDPs route via Peppol or direct PPF integration. As of 2026 roughly 70 PDPs are accredited.

Germany — E-Rechnung (Receiving January 2025, Issuing 2027–2028)

Germany's e-invoicing mandate is anchored in the Wachstumschancengesetz (Growth Opportunities Act, March 2024) and § 14 UStG. Rollout: 1 January 2025 — all German VAT-registered businesses must be able to receive structured e-invoices (no transition period); 1 January 2027 — companies with turnover above EUR 800,000 must issue structured e-invoices; 1 January 2028 — all remaining businesses must issue. Accepted EN16931-compliant formats: XRechnung (KoSIT CIUS) and ZUGFeRD 2.x / Factur-X (hybrid PDF/A-3 with embedded CII XML, jointly maintained with France). B2G entities use the Leitweg-ID as routing identifier.

Spain — Verifactu (2026) + Crea y Crece B2B

Spain runs two parallel reforms. Verifactu / SIF (Sistema Informático de Facturación) — Royal Decree 1007/2023, mandatory from 1 July 2025 for large taxpayers and 1 July 2026 for all corporate income tax payers. Verifactu introduces a real-time hash-chain "fingerprint" of every invoice, optionally pushed to AEAT in near-real-time. Crea y Crece Law (Ley 18/2022) — mandates B2B e-invoicing across all Spanish businesses; technical regulation has been delayed by the Council of State and final transposition is expected late 2026 with implementation phased 2027–2028. Both regimes converge on EN16931 semantics; the public Facturae XML format remains the legacy B2G transport.

Poland — KSeF (February + April 2026)

KSeF (Krajowy System e-Faktur — National e-Invoice System) is the most aggressive 2026 rollout. Operated by the Polish Ministerstwo Finansów and tax administration KAS under the 2023 KSeF Act (amended in 2024), the timeline is: 1 February 2026 — mandatory for large taxpayers (turnover above PLN 200M in 2024); 1 April 2026 — mandatory for all VAT-registered businesses. The FA(2) structured XML schema is submitted to the KSeF API; the system returns a 10-character KSeF identifier. Pre-clearance CTC — invoice not legally valid before KSeF acceptance, with a limited 24-hour offline mode.

Belgium — B2B Peppol (1 January 2026)

Belgium becomes the first EU member state to ship a pure Peppol-only B2B mandate. The Royal Decree of 19 December 2023 mandates that, from 1 January 2026, every B2B invoice between Belgian VAT-registered entities must be exchanged as a structured Peppol BIS Billing 3.0 document. No central clearance hub — Belgium relies entirely on the four-corner Peppol architecture. The Belgian Peppol Authority is SPF BOSA (Federal Public Service Policy and Support), which also operates the B2G platforms Mercurius and Hermes. As of mid-2025 roughly 35 Peppol Access Points were accredited in Belgium.

4. ViDA — VAT in the Digital Age

The Three Pillars of ViDA

The European Commission proposed VAT in the Digital Age (ViDA) in December 2022. After two years of negotiation it was adopted by the Council of the EU on 11 March 2025 as Directive (EU) 2025/516 amending the VAT Directive 2006/112/EC. The three pillars: Pillar 1 — Digital Reporting Requirements (DRR) imposes mandatory cross-border B2B e-invoicing and near-real-time digital reporting from 1 July 2030, based on EN16931, while permitting national domestic mandates to remain; Pillar 2 — Platform Economy introduces deemed-supplier rules for short-term accommodation and passenger transport platforms from 1 January 2030, with optional earlier opt-in from January 2028; Pillar 3 — Single VAT Registration extends the One Stop Shop (OSS) regime so cross-border sellers need only one VAT registration rather than one per country, from 1 July 2028.

What ViDA Means for 2026 Mandates

ViDA does not repeal the Italian, Polish, French, German, Spanish or Belgian national mandates — those continue under existing national law. ViDA's Article 218 amendment removes the requirement that member states must obtain a derogation to mandate e-invoicing, retrospectively legalising Italy's FatturaPA, Poland's KSeF and France's reform under EU law. From 1 July 2030, ViDA additionally mandates EN16931-based structured invoicing for all intra-EU B2B transactions (no more paper or PDF for cross-border), near-real-time digital reporting of supply data within 10 days of invoice issue (replacing the EC Sales List for cross-border), and EN16931 as the EU reference — forcing national CIUS convergence to ensure semantic compatibility.

ViDA Practical Impact

For Zunapro-class platforms the strategic implication is simple: an architecture built on a canonical EN16931 invoice now is automatically ViDA-ready for 2030. The same invoice object that serialises to FatturaPA, KSeF, XRechnung, Peppol BIS 3.0 and Verifactu will serialise to whatever ViDA defines — because ViDA is EN16931.

5. Common Standard Adoption Across the EU

Why a Single Standard Won

Until 2017 the European invoice space was a fragmented mess of national XML schemas — ebInterface in Austria, OIOUBL in Denmark, Facturae in Spain, FatturaPA in Italy, FIDAVISTA in Latvia, ISDOC in Czechia — and cross-border invoicing required N-to-M format conversion. Directive 2014/55/EU and the publication of EN16931 in 2017 changed the trajectory: every B2G receiver in the EU had to accept EN16931, and every national CIUS now starts from the EN16931 baseline rather than from scratch.

Adoption by Topology

EU national systems converge on EN16931 via three topologies: Centralised pre-clearance (CTC) — Italy SdI, Poland KSeF, Spain SIF (mandatory variant); invoice routed through tax authority, EN16931 used as semantic baseline but proprietary syntax on the wire. Decentralised Peppol four-corner — Belgium, Netherlands, Luxembourg, Nordics; Peppol BIS Billing 3.0 (an EN16931 CIUS in UBL 2.1) used directly. Hybrid Y-model — France (PPF + PDPs), Germany (XRechnung via Peppol or direct upload); multiple acceptable transports, EN16931 semantics enforced.

The Common-Standard Pay-off

Because all three topologies share EN16931 semantics, a sender that emits one EN16931-compliant invoice can be onboarded to any topology with a different serialiser plus a country-specific transport adapter. This is the structural reason platforms like Zunapro, Tradeshift, Pagero, Sovos and Comarch can offer multi-country compliance from a single codebase.

6. Continuous Transaction Controls (CTC)

What CTC Actually Is

Continuous Transaction Controls (CTC) is the umbrella term for tax-authority systems where invoice or transaction data is reported to the state in near-real-time — replacing or augmenting traditional periodic VAT returns. CTC is the structural megatrend of European VAT in the 2020s and the framework against which all six 2026 mandates are designed.

Three CTC Flavours

Pre-clearance CTC — invoice must be submitted to and accepted by the tax authority before it is legally valid (Italy SdI, Poland KSeF). Strongest VAT-gap reduction; tightest operational latency. Real-time reporting CTC — invoice issued first, transaction data pushed to the tax authority within minutes (Spain Verifactu optional hourly push, Hungary RTIR since 2018). Periodic e-reporting — structured data files (SAF-T variants like Polish JPK_VAT, Romanian SAF-T) submitted monthly or quarterly. Lower latency, not strictly "continuous".

Hungary RTIR — The Sleeper Hit

Although not in our six-country deep-dive, Hungary's Real-Time Invoice Reporting (RTIR) is the longest-running CTC in the EU. Since 1 July 2018 every Hungarian B2B invoice has had to be pushed to the NAV (Nemzeti Adó- és Vámhivatal) Online Számla API within milliseconds. RTIR is widely credited with cutting Hungary's VAT gap from above 20% to under 5% between 2017 and 2024 — the proof case European policymakers cite when arguing for CTC.

CTC Latency Requirements 2026

Country	Model	Latency	Penalty for Late
Italy (SdI)	Pre-clearance	12 days from supply	up to 100% of VAT
Poland (KSeF)	Pre-clearance	Real-time (24h offline mode)	up to 100% of VAT
Hungary (RTIR)	Real-time reporting	< 1 second post-issue	up to HUF 500K per invoice
Spain (Verifactu)	Real-time reporting (optional push)	Hourly batch	EUR 150–50,000 per breach
France (PPF/PDP)	Y-model + reporting	Within issuance window	EUR 15 per invoice (capped EUR 15K/yr)
Belgium (Peppol)	Decentralised, no clearance	n/a (post-2028 reporting)	VAT denial + admin fines

7. Cross-Border E-Invoice Flow

The Real-World Scenario

Consider a typical 2026 cross-border B2B transaction: a German wholesaler ships goods to an Italian retailer. Pre-2017 this generated one paper invoice, one EC Sales List entry and one Intrastat declaration. From 2026 the digital flow is materially different.

Step-by-Step Cross-Border Flow

1. German wholesaler issues an EN16931-compliant invoice; Zunapro renders it as XRechnung CII XML for the domestic E-Rechnung obligation. 2. The same canonical invoice is rendered separately as a Peppol BIS Billing 3.0 UBL XML for cross-border transport. 3. Zunapro's Peppol AP looks up the Italian retailer's identifier via the Peppol SML / SMP and posts the UBL over AS4 to the Italian receiver's AP. 4. The Italian receiver's AP ingests the Peppol UBL and, where required, converts it to FatturaPA XML for submission to SdI. 5. From July 2030 (ViDA), both sides must additionally report the cross-border transaction to their respective tax authorities within 10 days using the EN16931 data set.

Why Peppol Wins Cross-Border

Peppol's four-corner model with SML/SMP discovery is the only existing infrastructure that can route an invoice from a sender in country A to a receiver in country B without prior bilateral integration — exactly the property ViDA needs. No central EU clearance hub is being built; Peppol fills the void.

The Italian Cross-Border Wrinkle

Italy uniquely requires all cross-border invoices issued by or to Italian VAT taxpayers to be reported to SdI, even when the counterparty is in another EU country. Since 1 July 2022 this has been folded into the FatturaPA flow (replacing the Esterometro). Practical implication for a German seller invoicing an Italian buyer: even if your domestic German obligation is XRechnung, your Italian counterparty's obligation forces a FatturaPA representation. Zunapro generates both from one canonical invoice.

8. Peppol Authority Providers

The Peppol Authority Structure

Each Peppol jurisdiction designates one Peppol Authority — typically a public agency or designated body — responsible for accrediting Access Points and Service Metadata Publishers, enforcing the Peppol Specifications and signing the AS4 transport certificates. OpenPeppol itself acts as the "Peppol Coordinating Authority" for jurisdictions without their own designated authority.

EU Peppol Authorities 2026

Country	Peppol Authority	Accredited APs (mid-2026)
Belgium	SPF BOSA (Federal Public Service Policy and Support)	~35
France	AIFE (Agence pour l'Informatique Financière de l'État) + DGFiP	~70 PDPs (Peppol-via-PDP)
Germany	KoSIT (Koordinierungsstelle für IT-Standards)	~60
Italy	AgID (Agenzia per l'Italia Digitale)	~45 (Peppol track, in addition to SdI intermediaries)
Netherlands	NPa (Netherlands Peppol Authority, Simplerinvoicing Foundation)	~50
Denmark	Danish Business Authority (Erhvervsstyrelsen)	~30
Sweden	DIGG (Agency for Digital Government)	~30
Finland	State Treasury (Valtiokonttori)	~25
Norway (EEA)	DFØ (Direktoratet for forvaltning og økonomistyring)	~35
Luxembourg	CTIE (Centre des technologies de l'information de l'État)	~10
Poland	OpenPeppol coordinating (KSeF parallel for domestic)	limited (Peppol used for cross-border)
Spain	Ministerio de Asuntos Económicos y Transformación Digital	~20

Choosing an Access Point

From a seller's perspective, AP choice matters for cost, throughput SLA, supported document types (orders, dispatch advice, credit notes) and country coverage. Zunapro integrates with a portfolio of pre-vetted Access Points — including OpenPeppol-certified bilateral partners — so tenants do not select or negotiate individually.

9. Penalties per Country

The Real Stakes of 2026

Penalty regimes vary widely. The cards below summarise headline risks. Beyond direct fines, the most painful consequence is input-VAT recovery denial — in several jurisdictions an invoice that does not meet the structured-format obligation cannot be used to deduct input VAT.

Italy — FatturaPA Penalties

Missing FatturaPA: EUR 250 to EUR 2,000 per invoice (Art. 6 D.Lgs. 471/1997). Late FatturaPA: 90% to 180% of the underlying VAT. Severe or structural non-compliance: up to 100% of unpaid VAT plus criminal exposure above EUR 30K fraud thresholds.

Poland — KSeF Penalties (from April 2026)

Not issuing via KSeF: up to 100% of VAT. Issuing in KSeF with incorrect data: up to 100% of underpaid VAT. Counterparty input-VAT denial if the seller's invoice is not in KSeF. Penalties are suspended for the first three months (Feb–April 2026 grace).

France — Chorus Pro / PPF Penalties

Missing structured invoice: EUR 15 per invoice (capped EUR 15,000/yr). Missing transaction-data reporting: EUR 250 per breach (capped EUR 45,000/yr). Cumulative cap EUR 60,000/yr per type. Input-VAT denial risk for counterparties accepting non-conforming invoices.

Germany — E-Rechnung Penalties

General administrative fines under § 379 AO: up to EUR 5,000. Potential denial of input VAT for invoices that fail § 14 UStG structured-format requirement. Receiving obligation enforced from January 2025; issuing phased 2027 (large) / 2028 (SME).

Spain — Verifactu Penalties

Failure to use a SIF / Verifactu-compliant invoicing system: EUR 150 per invoice. Manipulation of an SIF system: EUR 50,000 per case. Producer of non-compliant software: up to EUR 150,000.

Belgium — B2B Peppol Penalties

Initial breach: EUR 1,500 per occurrence, rising to EUR 3,000 and EUR 5,000 on repeat. Input-VAT denial risk for buyers accepting non-Peppol invoices. Six-month soft-enforcement window through June 2026 confirmed by FOD Financiën.

10. Practical Multi-Country E-Invoice Strategy

The Canonical-Invoice Architecture

The lesson from the previous nine sections is concrete: do not build six country integrations — build one canonical EN16931 invoice object and six render-and-route adapters. Every Zunapro tenant has exactly one internal invoice schema; serialisers convert it to FatturaPA, KSeF FA(2), XRechnung CII, Peppol BIS 3.0 UBL, Verifactu JSON and any future format as needed.

Decision Tree by Use Case

Pure domestic seller in one country → implement that country's CIUS only (XRechnung Germany, FatturaPA Italy, KSeF Poland). Peppol optional but recommended. Multi-country EU seller → canonical EN16931 + per-country renderers + Peppol AP partnership for cross-border (Zunapro default). Marketplace seller (Amazon, Allegro, Otto, ManoMano) → marketplace handles the consumer invoice but you still owe B2B invoices to marketplace operators and wholesale buyers — full canonical EN16931 still required. Non-EU seller invoicing into EU → canonical EN16931 + selective country renderers + Peppol AP. ViDA Single VAT Registration (2028) simplifies cross-border VAT but does not exempt structured-invoice duty.

The Zunapro Six-Country Stack 2026

Zunapro ships per-jurisdiction renderers and connectors: Italy — FatturaPA XML + SdI intermediary submission + Codice Destinatario routing; France — PPF connection + Peppol-via-PDP fallback + receiver-status registration; Germany — XRechnung CII + Leitweg-ID routing for B2G + Peppol BIS UBL cross-border; Spain — SIF / Verifactu hash-chain compliance + AEAT push connector + Facturae for B2G; Poland — KSeF FA(2) XML + KSeF API + 10-character KSeF ID tracking + 24h offline mode; Belgium — Peppol BIS Billing 3.0 UBL + SPF BOSA-accredited Access Point + Hermes/Mercurius bridge for B2G.

Migration Plan for an SME 2026 — 90-Day Outline

Days 1–10: map current invoice flow against EN16931, identify field gaps. Days 11–30: pick a canonical platform (Zunapro), migrate the first country in scope — usually the one with the closest deadline. Days 31–60: parallel-run old and new for ~30 days, validate every outbound invoice against the official EN16931 / national validator. Days 61–90: switch to canonical-only issuance, add remaining countries incrementally with one renderer and one submission endpoint at a time.

Why This Is Cheaper Than Per-Country Stacks

A multi-country tenant on Zunapro pays once for the canonical EN16931 engine, then per-country activation fees for renderers and AP throughput. Compared with running six separate national invoicing tools, total cost of ownership drops by 60–75% over a 3-year horizon, and engineering risk drops further because a single team owns one schema rather than six.

EU E-Invoice Country Comparison Table 2026

The single most useful artefact for choosing scope is a side-by-side country view. The table below summarises 2026 status, format and topology.

Country	Mandate Status 2026	Format / CIUS	Topology	Authority
Italy	Mature, mandatory since 2019	FatturaPA XML (EN16931-aligned)	Pre-clearance via SdI	Agenzia delle Entrate
France	B2B receiving Sept 2026; issuing Sept 2026/2027	UBL / CII / Factur-X	Y-model (PPF + PDPs)	AIFE / DGFiP
Germany	Receiving mandatory Jan 2025; issuing 2027–2028	XRechnung / ZUGFeRD 2.x	Decentralised + Peppol	KoSIT
Spain	Verifactu mandatory 2026; Crea y Crece phased 2027+	Facturae / Verifactu JSON	Post-issuance CTC	Agencia Tributaria (AEAT)
Poland	KSeF Feb 2026 large; April 2026 universal	FA(2) XML (EN16931-aligned)	Pre-clearance via KSeF	Ministerstwo Finansów / KAS
Belgium	B2B mandatory Jan 2026	Peppol BIS Billing 3.0 UBL	Decentralised Peppol	SPF BOSA

Reading the table: Italy and Poland are the pre-clearance heavyweights; Belgium and the Netherlands are pure Peppol; France runs the Y-model; Germany sits in between with a flexible format menu; Spain is rolling out the post-issuance CTC pattern via Verifactu. Across all six the semantic baseline is identical — EN16931.

EU Legal Framework 2026 — What Changes

Directive 2014/55/EU — The B2G Foundation

Directive 2014/55/EU on electronic invoicing in public procurement remains the legal anchor: since April 2020 every public contracting authority in the EU must accept EN16931-compliant invoices. National transpositions vary in syntax (XRechnung in Germany, FatturaPA in Italy, UBL on Peppol in BE/NL/DK) but converge on the EN16931 semantics.

The ViDA Directive (EU) 2025/516

Adopted 11 March 2025 by the Council, ViDA amends Directive 2006/112/EC. Key articles: Article 218 amendment removes the historic requirement that member states obtain a derogation to mandate e-invoicing, legalising existing national mandates EU-wide. Articles 217–242 (new) set mandatory cross-border B2B structured invoicing and digital reporting from 1 July 2030. Article 369 OSS extensions extend One Stop Shop to a Single VAT Registration regime from 1 July 2028. Article 28a deemed-supplier rules apply to platforms in short-term accommodation and passenger transport from 1 January 2030.

National CIUS Publications

Germany ships XRechnung 3.x via KoSIT (current 3.0.1 mid-2025); Italy ships FatturaPA 1.7.1 with EN16931 semantic mapping maintained by Agenzia delle Entrate; Poland ships FA(2) (FA(3) in beta mid-2026) via Ministerstwo Finansów; France/Germany jointly maintain Factur-X 1.07; Spain ships the Verifactu RD 1007/2023 technical schema via AEAT; Belgium applies Peppol BIS Billing 3.0 directly with no national CIUS. The cross-border Peppol BIS 3.0 CIUS is maintained by the OpenPeppol Change Management Board.

Data Protection and Audit Trail

Invoice data falls under GDPR (Regulation (EU) 2016/679) — storage, encryption and access-control obligations apply. Retention is 10 years in most member states (Italy and Poland strictly 10, Germany 10, France 6–10, Spain 4 plus optional 10). Pre-clearance mandates carry the audit trail in the tax authority's system; decentralised Peppol mandates require seller-side immutability and cryptographic signing.

How to Start EU E-Invoicing — 2026 Step-by-Step

1. Define Your Country Scope (Decision Tree)

Maximum coverage → enable all six (IT, FR, DE, ES, PL, BE) from day one. Earliest deadline first → Poland KSeF (Feb 2026), Belgium Peppol (Jan 2026). Largest revenue concentration → start with the country where you invoice the most. Cross-border priority → enable Peppol BIS 3.0 first, national formats second.

2. Legal-Entity and VAT Setup

EU-established sellers extend their existing VAT registration, use OSS for cross-border B2C and prepare for ViDA Single VAT Registration from July 2028. Non-EU sellers (Turkish, UK, US, CH) appoint a fiscal representative in each country with a national mandate, or use ViDA Single VAT Registration once available. Country-specific identifiers to register: Codice Destinatario / PEC in Italy, Leitweg-ID in Germany, KSeF authorisation token in Poland, Peppol Participant ID in Belgium / Netherlands.

3. EN16931 Validator Pre-Flight

Before you ship a single invoice through any national system, validate against the official EN16931 ruleset. The European Commission's eInvoicing Building Block hosts the canonical validator. Zunapro runs every outbound invoice through the validator on the way out, surfacing violations in the panel before the invoice reaches SdI, KSeF, Chorus Pro or any Peppol AP.

4. Peppol Access Point Onboarding

For Belgium, Netherlands, Luxembourg, Nordics and cross-border France/Germany, you need a Peppol Access Point. Onboarding: choose an OpenPeppol-accredited AP partner (Zunapro provides pre-vetted options); register your Peppol Participant Identifier (typically your VAT number prefixed with the country scheme — 0208 for BE, 9914 for AT, 0184 for DK, 0204 for DE); publish your SMP entry listing supported document types (Invoice, Credit Note, optional Order, Despatch Advice); test AS4 send/receive against the test environment, then promote to production.

5. Connect via Zunapro (15-Minute Integration)

1. Sign in to Zunapro and open the Europe / Accounting module. 2. Activate each country — paste API keys / OAuth credentials for SdI, KSeF, PPF, AEAT, KoSIT validator. 3. Map your master catalog — Zunapro auto-suggests EN16931 field mappings from your existing ERP / catalog schema. 4. Enable Peppol BIS + national CIUS renderers — single toggle per country. 5. Go live — first compliant invoice typically sent in under 15 minutes for a single-country tenant.

EU E-Invoicing FAQ 2026