E-invoicing in Europe: what is changing, when, and what it means for your business.

A plain-language guide to Peppol, Factur-X, ZUGFeRD, and XRechnung — with a compliance timeline per country.

EU e-invoicing mandate timeline

Mandate dates, required standards, and scope per country.

Belgium

Live

January 2026

Standard: Peppol / Factur-X

Scope: B2B + B2G

Full Belgium guide →

France

Upcoming

Phases 2026 to 2027

Standard: Factur-X / UBL

Scope: B2B + B2G

Full France guide →

Germany

Live

Live since 2020 (B2G) / 2025 (B2B)

Standard: XRechnung / ZUGFeRD

Scope: B2G mandatory, B2B expanding

Full Germany guide →

Netherlands

Upcoming

B2G live, B2B per EU directive

Standard: Peppol / UBL

Scope: B2G active, B2B following ViDA

Full Netherlands guide →

Poland

Live

KSeF mandatory April 2026

Standard: FA(2) / KSeF XML

Scope: B2B mandatory (large taxpayers)

Full Poland guide →

Italy

Live

Live since 2019

Standard: FatturaPA

Scope: B2B + B2G

Standards explained in plain language

Peppol

Network

Peppol is the network, not the format. Think of it as the postal infrastructure for e-invoices: a standardised, secure network of access points that allows any participant to send or receive structured invoices to any other participant. Your accounting software generates the invoice; Peppol delivers it.

Factur-X / ZUGFeRD

Format

Factur-X (France) and ZUGFeRD (Germany) are the same format under two names: a PDF/A-3 document with a machine-readable XML invoice embedded inside. The PDF is human-readable; the XML is machine-readable. Both comply with EN 16931, the European e-invoicing standard.

XRechnung

Profile

XRechnung is a German government-specific profile of the EU e-invoicing standard. It is mandatory for invoices to German federal authorities. It uses the same underlying CII XML as Factur-X but adds mandatory fields (Leitweg-ID, seller contact, IBAN) and a stricter validation rule set.

UBL

XML standard

Universal Business Language (UBL) is an alternative XML format to CII. Both are valid under EN 16931. Peppol uses UBL by default. Factur-X and ZUGFeRD use CII. SealDoc supports both.

Does my accounting software already cover this?

Most accounting software generates the invoice XML. What it does not provide is the legal proof layer.

What your ERP does not provide:

  • RFC 3161 qualified timestamps
  • Chain of custody and tamper-evidence
  • Legal Hold capability
  • Court-ready Legal Evidence Pack

Named alternatives you may be evaluating: Billit, UnifiedPost, Avalara, Exact Online. These generate invoice XML. None provide an independent legal proof layer with RFC 3161, chain of custody, or a Legal Evidence Pack ready for court submission.

Frequently asked questions

What happens if I send a non-compliant invoice to a Belgian buyer after January 2026?
The buyer is entitled to reject it. From January 2026, Belgian businesses above certain thresholds must be able to receive Peppol invoices, and they may refuse non-structured invoices. Repeated non-compliance may result in administrative penalties.
Is Factur-X the same as ZUGFeRD?
Yes, technically. Both are hybrid PDF/XML invoice formats based on the EN 16931 standard using CII XML. The difference is branding: ZUGFeRD is the German name, Factur-X is the French name. Starting from version 1.0, the specifications are aligned.
Do I need a Peppol access point?
To receive invoices via the Peppol network, yes. To send them, your accounting software or ERP may already connect to a Peppol access point. SealDoc is not a Peppol access point — we generate the compliant document and add the legal proof layer. Your existing Peppol provider handles the network delivery.
Does my ERP or accounting software already handle this?
For generating the invoice XML: probably yes. For the legal proof layer (RFC 3161 timestamps, chain of custody, Legal Hold, Evidence Pack): no. See the comparison section above.
What is the difference between Peppol and Factur-X?
Peppol is the delivery network. Factur-X is the document format. You can send a Factur-X invoice via Peppol, or via email, or via API. They are complementary, not alternatives.
What is an RFC 3161 timestamp and why does it matter?
An RFC 3161 timestamp is a cryptographic proof that a specific document existed at a specific point in time and has not been altered since, issued by a trusted Time Stamping Authority. It matters because it provides legally admissible evidence of the document's existence and integrity — something a plain invoice file cannot provide.
What is a Legal Evidence Pack?
A Legal Evidence Pack is a ZIP file containing: the sealed PDF/A-3 document, the audit trail (who did what, when, with what IP), RFC 3161 timestamp certificates, and a manifest hash-chain that seals the entire set. It is ready to submit to court, a tax authority, or a regulatory inspector.
Is SealDoc a Peppol access point?
No. SealDoc generates Peppol-compliant invoice documents and adds the legal proof layer. Delivery via the Peppol network requires a certified access point, which your existing ERP or invoicing provider typically handles.
How does SealDoc help with GDPR compliance?
SealDoc implements GDPR Art. 17 (right to erasure via DELETE endpoint), Art. 20 (data portability via full ZIP export), and Art. 28 (data processing agreement available on request). All processing happens on EU infrastructure with no US hyperscaler dependency.
Which Factur-X profiles does SealDoc support?
SealDoc supports all five Factur-X 1.0 profiles: MINIMUM, BASIC WL, BASIC, EN 16931, and EXTENDED. XRechnung-DE is available on the Enterprise plan for German federal and large German buyers.

Check if your business is already Peppol-ready

Free. No account required. Result in under 3 seconds.

Check my VAT number