E-invoicing across Europe: four models, and how to run one invoicing process

Why the models differ

Every mandate aims to reduce VAT fraud and administrative cost, but countries start from different systems, tax administrations and business habits. The result is a patchwork. For a business in one country, the local rules are enough to understand. For a group invoicing in several countries, the differences shape system architecture, data quality requirements and exception handling.

The EU’s VAT in the Digital Age package adds a longer-term direction, including electronic invoicing and digital reporting for many intra-EU transactions from 2030. Until then, national models will continue to coexist, and businesses must handle each one correctly.

Clearance: Italy and Poland

In a clearance model, invoices pass through a state platform, and the platform’s acceptance is what makes the invoice valid. Italy has used this approach for domestic B2B invoices through its exchange system since 2019. Poland’s national e-invoicing system, KSeF, has become mandatory in phases in 2026.

Clearance changes the invoice from an internal document into a state-acknowledged one. If an invoice is rejected, it does not exist for tax purposes. Integration, validation before submission and handling of rejections and outages are therefore critical.

Approved platforms: France

France routes domestic B2B invoices through approved platforms, which exchange invoices between businesses and transmit data to the tax administration. From September 2026 all businesses in scope must receive electronic invoices, with issuing obligations phased by company size through 2027. E-reporting covers transactions outside e-invoicing, such as many consumer and international sales, and certain payment data.

The French model also introduces invoice lifecycle statuses, so approval, dispute and payment information becomes part of the shared process between supplier and customer.

Network delivery: Belgium

Belgium requires structured electronic invoicing between businesses from 2026, generally using the Peppol network. Peppol is a delivery network with standard formats and access points, rather than a clearance system. The invoice is exchanged between businesses through their access points without the state approving each document first.

The main work lies in connecting systems to an access point, maintaining correct identifiers and handling delivery failures and invoice disputes.

Receiving first: Germany

Germany has required businesses to be able to receive structured electronic invoices since January 2025, with issuing obligations phased in until 2028. Germany does not currently use a central clearance platform for B2B invoices. Structured formats that follow the European standard, such as XRechnung and suitable ZUGFeRD profiles, are common.

Because receiving came first, many German businesses meet the obligation formally but still process structured invoices manually. The value comes from routing them into accounting and approval workflows.

Clearance

Italy and Poland: the state platform validates invoices, and rejected invoices are not valid.

Approved platforms

France: invoices move through approved platforms with status and reporting obligations.

Network delivery

Belgium: structured invoices are exchanged mainly through Peppol.

Receiving first

Germany: receiving required since 2025, issuing phased in by 2028.

Designing one process for several models

Groups should avoid building a separate invoicing process for every country from scratch. A better design separates the business process from the country connection. Orders, deliveries, pricing, tax determination and customer data live in the core systems. Country-specific connectors handle formats, submission, delivery, statuses and rejections.

Master data is the common foundation. Every model depends on correct customer identifiers, VAT numbers, addresses, product descriptions and tax treatments. Cleaning and governing that data once benefits every country.

Exception handling should be centralised but country-aware. A rejected Polish invoice, a failed Peppol delivery in Belgium and a disputed invoice status in France are different events, but they should appear in one monitored queue with clear ownership and response times.

Questions to ask before choosing providers

Can the provider support every country where the group invoices now and expects to invoice in the next few years? How does it handle validation before submission, rejections, outages and status updates? Where are original structured invoices archived, and can they be exported? How are master data errors surfaced? What happens when a country changes its rules?

A provider that covers formats but leaves exception handling and archiving unclear will create manual work. A provider that supports the whole invoice lifecycle and connects cleanly to core systems reduces it.

This article summarises the models to help scope system work. Businesses should confirm current requirements with tax advisers in each country.

Where this sits in what we do

This article covers one decision inside a wider engagement. The solution page sets out how that engagement runs, what it includes and what it costs to find out.

• Complete Digital Transformation — The whole stack, sequenced — brand, web, marketing, CRM, automation, reporting and infrastructure — with benefits measured afterwards rather than projected and forgotten.
• The EU AI Act: what actually applies from 2 August 2026
• Belgium's B2B e-invoicing mandate: the January 2026 big bang
• Electronic signatures under eIDAS: simple, advanced and qualified, and when national form rules still apply
• Offboarding access to SaaS tools: closing the accounts, tokens and ownership gaps when people leave
• All insight articles