The Shift to Mandatory E-Invoicing in Europe

The European Union is in the middle of a fundamental transformation of how businesses exchange invoices. By 2030, virtually every B2B transaction in the EU will require structured electronic invoicing through government-mandated platforms. This is not a gradual suggestion -- it is a regulatory mandate with hard deadlines and real penalties for non-compliance.

The driving force is the EU's VAT gap: the difference between expected VAT revenue and actual collections. In 2022, the EU-wide VAT gap was estimated at 61 billion EUR. E-invoicing gives tax authorities real-time visibility into business transactions, making VAT fraud and errors significantly harder to sustain.

For software companies, this creates both an obligation and an opportunity. If your platform generates invoices, processes payments, or manages business transactions for European customers, e-invoicing compliance is non-negotiable. And the complexity of supporting 27 different national systems, each with their own XML format, API, authentication scheme, and business rules, makes this a serious engineering challenge.

The ViDA Directive: EU-Wide Framework

VAT in the Digital Age (ViDA) is the EU directive that establishes the framework for mandatory e-invoicing across all member states. After years of negotiation, the directive was formally adopted in 2025 and sets the following EU-wide requirements:

2025-2026: Member states are permitted (but not required) to implement B2B e-invoicing mandates without needing a derogation from the EU Council. This removes the bureaucratic barrier that previously slowed adoption.
2028: Digital Reporting Requirements (DRR) for intra-EU B2B transactions. Suppliers must report cross-border invoice data electronically in near-real-time.
2030: Full DRR implementation for domestic B2B transactions. All member states must have systems in place to receive structured invoice data.
2035: Mandatory e-invoicing for all domestic B2B transactions across the EU, with national clearance systems fully operational.

However, ViDA sets the floor, not the ceiling. Many member states are moving far ahead of the directive's timeline, implementing their own national mandates with earlier deadlines. Italy has had mandatory e-invoicing since 2019. Romania since 2024. Poland and France are rolling out in 2026. If you wait for the EU-wide deadline, you will be years behind.

Country-by-Country Status (2026)

The table below provides the current status of e-invoicing mandates in all 27 EU member states, plus key non-EU European countries. Status categories:

Live: Mandatory e-invoicing is in effect for B2B transactions.
Live (B2G): Mandatory for business-to-government invoices only.
Rolling out: Mandate enacted, implementation in progress with phased deadlines.
Enacted: Legislation passed, go-live date set.
Planned: Government has announced plans, legislation in progress.
Under ViDA: No national mandate yet; will follow EU ViDA directive timeline.

Country	Status	System	Key Date	Format
Italy	Live (B2B + B2G)	SDI (Sistema di Interscambio)	Jan 2019 (B2B)	FatturaPA
Romania	Live (B2B + B2G)	ANAF e-Factura	Jan 2024 (B2B)	UBL CIUS-RO
Poland	Rolling out	KSeF (Krajowy System e-Faktur)	Feb 2026 (large), Aug 2026 (all)	FA(2) XML
France	Rolling out	PPF (Portail Public de Facturation)	Sep 2026 (receive), Sep 2027 (send)	Factur-X / UBL / CII
Germany	Enacted	Peppol / XRechnung	Jan 2027 (receive), Jan 2028 (send)	XRechnung (UBL/CII)
Spain	Enacted	Verifactu / FACe	Jul 2026 (revenue >8M), 2027 (all)	Facturae
Belgium	Enacted	Peppol BIS 3.0	Jan 2026 (B2B)	UBL Peppol BIS
Greece	Live (B2B + B2G)	myDATA	Oct 2020 (B2G), 2024 (B2B)	Custom XML
Portugal	Live (B2G), Planned (B2B)	FE-AP / AT Portal	2027 (B2B planned)	CIUS-PT (UBL)
Hungary	Live (reporting)	NAV RTIR	Jul 2018 (reporting)	NAV 3.0 XML
Croatia	Live (B2G)	eRacun / Fina	Jul 2019 (B2G), 2027 (B2B planned)	UBL 2.1
Bulgaria	Planned	NRA system (TBD)	2027-2028 (expected)	TBD (likely UBL)
Czech Republic	Planned	MFCR system (TBD)	2027 (planned)	ISDOC / UBL
Slovakia	Planned	IS EFA (TBD)	2027 (planned)	TBD
Netherlands	Live (B2G)	Peppol	Under ViDA for B2B	SI-UBL / Peppol BIS
Austria	Live (B2G)	e-Rechnung.gv.at / Peppol	Under ViDA for B2B	ebInterface / Peppol BIS
Finland	Live (B2G)	Peppol / Finvoice	Under ViDA for B2B	Finvoice / Peppol BIS
Sweden	Live (B2G)	Peppol	Under ViDA for B2B	Peppol BIS
Denmark	Live (B2G)	NemHandel / Peppol	Under ViDA for B2B	OIOUBL / Peppol BIS
Ireland	Live (B2G)	Peppol	Under ViDA for B2B	Peppol BIS
Luxembourg	Live (B2G)	Peppol	Under ViDA for B2B	Peppol BIS
Slovenia	Live (B2G)	eRacun / UJP	Under ViDA for B2B	eSlog 2.0
Estonia	Live (B2G)	e-arve / Peppol	Under ViDA for B2B	Estonian e-Invoice / Peppol BIS
Latvia	Live (B2G)	Peppol	Under ViDA for B2B	Peppol BIS
Lithuania	Live (B2G)	Peppol / iSAF	Under ViDA for B2B	Peppol BIS
Cyprus	Planned	TBD	Under ViDA	TBD
Malta	Planned	TBD	Under ViDA	TBD

Countries with Live B2B Mandates

Italy: SDI (Since 2019)

Italy was the first EU country to mandate B2B e-invoicing and remains the most mature system. The Sistema di Interscambio (SDI) is a clearance model: all invoices must pass through SDI, which validates, registers, and delivers them to the recipient.

Key characteristics: Italy uses its own FatturaPA XML format (not UBL), requires unique progressive invoice numbering per year, and mandates digital signatures (XAdES or CAdES) on every invoice. The SDI system processes over 2 billion invoices per year and has a well-documented API, though the authentication uses certificate-based client TLS rather than OAuth2.

Mandato supports SDI with automatic FatturaPA conversion, digital signing, and status tracking. See our Italy documentation for details.

Romania: ANAF e-Factura (Since 2024)

Romania mandated B2B e-invoicing in January 2024, making it the second EU country with a full B2B mandate. The system uses UBL 2.1 with the CIUS-RO national profile and OAuth2 authentication with USB certificate-based initial authorization.

Romania's enforcement is strict: invoices not submitted through e-Factura are legally void for VAT deduction purposes. This creates strong market pressure for compliance. For a detailed technical guide, see our complete ANAF e-Factura integration guide.

Greece: myDATA (Since 2020)

Greece's myDATA platform started as a real-time tax reporting system in 2020 and has progressively expanded toward full e-invoicing. Businesses must transmit invoice data (income and expense classifications) to the AADE tax authority through myDATA. While Greece technically allows PDF invoices alongside the electronic transmission, the structured data reporting is mandatory.

Countries Going Live in 2026

Poland: KSeF (February/August 2026)

Poland's KSeF (Krajowy System e-Faktur) is one of the most anticipated e-invoicing rollouts in Europe. After a delay from the original 2024 deadline, the mandate is now phased:

February 1, 2026: Mandatory for large enterprises (annual revenue exceeding 200 million PLN).
August 1, 2026: Mandatory for all VAT-registered businesses.

KSeF uses a unique structured XML format called FA(2), distinct from both UBL and FatturaPA. The system assigns a unique KSeF reference number to every invoice, which serves as the legal identifier. Authentication uses qualified digital certificates or the trusted profile (profil zaufany) system.

France: PPF (September 2026)

France's Portail Public de Facturation (PPF) introduces a mandatory e-invoicing regime with a "Y-model" architecture. Businesses can use the government's PPF platform directly or route invoices through accredited private platforms (PDP - Plateformes de Dematerialisation Partenaires).

September 1, 2026: All businesses must be able to receive electronic invoices.
September 1, 2027: Large and medium enterprises must send electronic invoices.
September 1, 2028: All businesses, including small enterprises, must send electronic invoices.

France accepts three formats: Factur-X (hybrid PDF/XML based on CII), pure UBL 2.1, and pure CII (Cross-Industry Invoice). This flexibility is unusual among EU systems and reflects France's pragmatic approach to adoption. E-reporting of B2C transactions to the tax authority is also included in the mandate.

Belgium: Peppol BIS (January 2026)

Belgium mandated B2B e-invoicing starting January 1, 2026, using the Peppol network with the BIS Billing 3.0 standard. This makes Belgium the first major economy to adopt Peppol as its domestic B2B e-invoicing infrastructure, rather than building a national clearance system.

The Peppol approach simplifies cross-border invoicing within the Peppol network but requires businesses to register as Peppol participants and use certified Peppol Access Points. Mandato operates as a Peppol Access Point, handling the Peppol protocol and SMP registration on behalf of its customers.

Spain: Verifactu (July 2026)

Spain's approach combines e-invoicing with a Verifactu system for real-time VAT reporting. The Verifactu module requires compliant invoicing software to generate a hash chain of invoices and transmit them to the Agencia Tributaria in near-real-time.

July 1, 2026: Mandatory for businesses with annual revenue exceeding 8 million EUR.
2027: Extension to all businesses.

Spain uses the Facturae XML format, which predates the EN 16931 standard. The government is working on alignment with the European standard, but for the initial rollout, Facturae 3.2.x remains the primary format.

Countries Going Live in 2027-2028

Germany: XRechnung (January 2027)

Germany has been using XRechnung for B2G invoicing since 2020. The B2B mandate phases in starting 2027:

January 1, 2027: All businesses must be able to receive structured electronic invoices (XRechnung or Peppol BIS).
January 1, 2028: All businesses with revenue exceeding 800,000 EUR must send structured electronic invoices.

Germany's approach is notable for not requiring a central clearance platform. Instead, businesses can exchange e-invoices directly using XRechnung (based on UBL or CII) through any channel, including email, Peppol, or EDI platforms. A government reporting requirement will be added later under ViDA.

Portugal (2027, Planned)

Portugal has mandatory B2G e-invoicing and SAF-T reporting for tax purposes. A B2B e-invoicing mandate using CIUS-PT (Portugal's national UBL profile) is planned for 2027 but has not been formally enacted.

Czech Republic, Slovakia, Bulgaria (2027-2028)

These countries have announced plans for e-invoicing mandates in the 2027-2028 timeframe but details remain preliminary. All are expected to align with the EN 16931 standard and likely adopt UBL-based national profiles, similar to Romania's CIUS-RO approach.

Peppol-Based Countries

A significant group of EU countries -- primarily in Northern and Western Europe -- use the Peppol network for B2G e-invoicing and are expected to extend it to B2B under the ViDA directive. These include:

Netherlands, Austria, Finland, Sweden, Denmark, Ireland, Luxembourg, Estonia, Latvia, Lithuania

For these countries, Peppol BIS Billing 3.0 (based on UBL 2.1) is the dominant format. While B2B mandates are not yet in effect, the infrastructure is mature and adoption is growing through market forces. Belgium's January 2026 Peppol B2B mandate is likely to accelerate adoption in neighboring countries.

Mandato supports Peppol natively and can route invoices through the Peppol network for any of these countries today, even before their B2B mandates take effect.

The Format Landscape: UBL, CII, FatturaPA, and More

One of the biggest challenges for businesses operating across multiple EU countries is the diversity of invoice formats. While the EN 16931 standard defines a common semantic model, the actual XML implementations vary significantly:

Format	Base Standard	Used By	Key Difference
UBL 2.1 (Peppol BIS)	EN 16931	Belgium, Nordics, Baltics, NL, IE	Pan-European Peppol network standard
UBL CIUS-RO	EN 16931	Romania	UBL with Romania-specific mandatory fields
XRechnung	EN 16931 (UBL/CII)	Germany	Accepts both UBL and CII syntax bindings
Factur-X	EN 16931 (CII)	France	Hybrid PDF/XML; CII data embedded in PDF
FatturaPA	Custom (pre-EN 16931)	Italy	Unique XML schema, digital signature required
FA(2)	Custom	Poland	KSeF-specific structured XML
Facturae	Custom (pre-EN 16931)	Spain	Legacy format, EN 16931 alignment planned

This fragmentation is exactly why API abstraction matters. Building and maintaining converters for even three or four of these formats is a significant engineering investment, especially given the strict validation rules each country enforces.

What Should Your Business Do Now?

If your software generates invoices for European businesses, here is a prioritized action plan:

Audit your customer base. Identify which EU countries your customers operate in. Cross-reference against the timeline above. If you have customers in Italy, Romania, Poland, France, Belgium, Spain, or Germany, e-invoicing compliance is immediate or imminent.
Decide build vs. buy. Supporting one country's e-invoicing system is a 2-4 month engineering project. Supporting five or more countries is a dedicated team. An API like Mandato reduces this to a single integration that scales across countries.
Start with your largest market. Implement e-invoicing for the country where you have the most customers or revenue exposure first. Romania and Italy are live now. Poland and Belgium are mandatory in 2026.
Plan for multi-country. Even if you only need one country today, architect your invoice pipeline to support adding countries later. The ViDA directive guarantees that more countries will follow.
Test in sandbox environments. Most countries offer test environments. Start integration testing early -- government APIs have quirks that documentation does not cover.

How Mandato Handles Multi-Country Compliance

Mandato provides a single REST API that abstracts all EU e-invoicing systems. Your integration looks the same regardless of the destination country:

// Romania
const roInvoice = await mandato.invoices.create({
  country: "RO",
  supplier: { vatNumber: "RO12345678", name: "Acme SRL" },
  // ... lines, customer, etc.
});

// Italy — same API, different country code
const itInvoice = await mandato.invoices.create({
  country: "IT",
  supplier: { vatNumber: "IT01234567890", name: "Acme Italia SRL" },
  // ... lines, customer, etc.
});

// Belgium (Peppol) — same API
const beInvoice = await mandato.invoices.create({
  country: "BE",
  supplier: { vatNumber: "BE0123456789", name: "Acme BVBA" },
  // ... lines, customer, etc.
});

Behind the scenes, Mandato handles format conversion (UBL, FatturaPA, XRechnung, FA(2), Factur-X), government authentication (OAuth2, certificates, Peppol SMP), Schematron validation, submission, status polling, and error translation -- for every supported country.

When a new country goes live, you do not change your integration. You add a company connection for the new country in the Mandato dashboard, and your existing API calls work with the new country code.

Start with a free sandbox account at app.getmandato.dev. Full API documentation at docs.getmandato.dev.

EU E-Invoicing Mandate Timeline: Every Country, Every Deadline (2026)