Guide

EU top markets playbook (DE, FR, IT, ES, PL, NL)

If you sell across Europe, you do not need 27 completely different implementations. You need a strong core (EN 16931 mapping + validation) and a small set of country adapters (routing IDs, channels, and constraints). This playbook starts with the largest and most mature markets.

A repeatable approach (core + country adapters)

Build one canonical invoice data model, then export into the required syntaxes (UBL/CII/FatturaPA/KSeF). Keep validation close to generation and treat errors as product feedback.

Country adapters should be small: recipient identifiers, transport channels, and a handful of rule deltas (CIUS).

This article treats EU top markets playbook (DE, FR, IT, ES, PL, NL) as a practical reference, not just a navigation page. It explains the term or workflow in context, shows why it matters for European e-invoicing, and connects the topic to invoice creation, validation, routing, archiving, and ERP implementation decisions.

Germany (DE): XRechnung + Leitweg-ID, plus ZUGFeRD in business workflows

Germany is strongly associated with XRechnung for public sector invoicing. XRechnung is essentially EN 16931 expressed in UBL or CII with German-specific rules.

In many B2B workflows, ZUGFeRD/Factur‑X (PDF + embedded XML) is used because it preserves a human-readable PDF while enabling structured processing.

France (FR): platform workflows + Factur‑X as a practical bridge

France is a major market where platform-based exchange is common, especially for public sector invoicing. Expect requirements around French business identifiers (SIREN/SIRET) and strict party data quality.

Factur‑X (based on EN 16931) is often used as a bridge format because it combines PDF readability with structured XML.

Italy (IT): clearance-style delivery via SdI (FatturaPA)

Italy is the reference case for platform-driven e‑invoicing. Invoices are exchanged via the “Sistema di Interscambio” (SdI) using the FatturaPA XML format.

Technically, this often means: format compliance + strict identifiers + handling platform responses as part of your issuance workflow.

Spain (ES): public sector portals and evolving B2B requirements

Spain has well-established public sector e‑invoicing via FACe and uses formats like Facturae. Depending on your segment, you may also see UBL-based exchanges.

For cross‑border and multi‑country implementations, focus on clean party identifiers and consistent VAT logic—then adapt the delivery channel.

Poland (PL): KSeF as a structured platform with strict technical expectations

Poland is one of the most important “structured platform” markets. In practice, the key is: reliable integration, precise data, and handling platform responses and status.

Plan for operational excellence: retries, monitoring, and long-term storage of what you sent and what was accepted.

Netherlands (NL): PEPPOL-first exchange patterns

The Netherlands is strongly aligned with PEPPOL BIS and network exchange. This makes it a good anchor country for a “network first” strategy.

In PEPPOL contexts, participant IDs and endpoint discovery are as important as the invoice XML itself.

Testing strategy for multi-country rollouts

Use a small but representative invoice set and keep it stable: one simple invoice, one with multiple VAT rates, one with allowances/charges, one with prepayments, and one credit note.

For each country/channel, validate locally and then with the target validator or sandbox. Keep the exact XML that passed as a fixture.

A repeatable approach (core + country adapters)

A repeatable approach (core + country adapters) is where the general explanation of EU top markets playbook (DE, FR, IT, ES, PL, NL) becomes operational. The section focuses on Core: EN 16931 mapping + code lists + VAT logic, Adapter: routing ID/portal + profile validation and Ops: retry + audit trail + storage, so it can be used to check the required fields, process decisions, and validation controls before the invoice workflow is used in production.

Core: EN 16931 mapping + code lists + VAT logic
Adapter: routing ID/portal + profile validation
Ops: retry + audit trail + storage

Germany (DE): XRechnung + Leitweg-ID, plus ZUGFeRD in business workflows

Germany (DE): XRechnung + Leitweg-ID, plus ZUGFeRD in business workflows is where the general explanation of EU top markets playbook (DE, FR, IT, ES, PL, NL) becomes operational. The section focuses on Routing/IDs: Leitweg-ID in B2G scenarios, Syntax: UBL or CII (XRechnung profiles) and Pitfalls: buyer reference fields, addresses, VAT breakdown, so it can be used to check the required fields, process decisions, and validation controls before the invoice workflow is used in production.

Routing/IDs: Leitweg-ID in B2G scenarios
Syntax: UBL or CII (XRechnung profiles)
Pitfalls: buyer reference fields, addresses, VAT breakdown

France (FR): platform workflows + Factur‑X as a practical bridge

France (FR): platform workflows + Factur‑X as a practical bridge is where the general explanation of EU top markets playbook (DE, FR, IT, ES, PL, NL) becomes operational. The section focuses on Identifiers: SIREN/SIRET + VAT ID, Format: Factur‑X (EN 16931 profile) commonly used and Pitfalls: party identifiers and address strictness, so it can be used to check the required fields, process decisions, and validation controls before the invoice workflow is used in production.

Identifiers: SIREN/SIRET + VAT ID
Format: Factur‑X (EN 16931 profile) commonly used
Pitfalls: party identifiers and address strictness

Italy (IT): clearance-style delivery via SdI (FatturaPA)

Italy (IT): clearance-style delivery via SdI (FatturaPA) is where the general explanation of EU top markets playbook (DE, FR, IT, ES, PL, NL) becomes operational. The section focuses on Channel: SdI, Format: FatturaPA XML and Pitfalls: recipient codes (Codice Destinatario/PEC), platform acknowledgements, so it can be used to check the required fields, process decisions, and validation controls before the invoice workflow is used in production.

Channel: SdI
Format: FatturaPA XML
Pitfalls: recipient codes (Codice Destinatario/PEC), platform acknowledgements

Spain (ES): public sector portals and evolving B2B requirements

Spain (ES): public sector portals and evolving B2B requirements is where the general explanation of EU top markets playbook (DE, FR, IT, ES, PL, NL) becomes operational. The section focuses on Channel: FACe for B2G, Formats: Facturae and sometimes UBL and Pitfalls: identifier formats (NIF/CIF) and address completeness, so it can be used to check the required fields, process decisions, and validation controls before the invoice workflow is used in production.

Channel: FACe for B2G
Formats: Facturae and sometimes UBL
Pitfalls: identifier formats (NIF/CIF) and address completeness

Poland (PL): KSeF as a structured platform with strict technical expectations

Poland (PL): KSeF as a structured platform with strict technical expectations is where the general explanation of EU top markets playbook (DE, FR, IT, ES, PL, NL) becomes operational. The section focuses on Channel: KSeF, Format: structured XML (platform-defined) and Pitfalls: error/status handling and operational resilience, so it can be used to check the required fields, process decisions, and validation controls before the invoice workflow is used in production.

Channel: KSeF
Format: structured XML (platform-defined)
Pitfalls: error/status handling and operational resilience

Netherlands (NL): PEPPOL-first exchange patterns

Netherlands (NL): PEPPOL-first exchange patterns is where the general explanation of EU top markets playbook (DE, FR, IT, ES, PL, NL) becomes operational. The section focuses on Channel: PEPPOL, Format: PEPPOL BIS Billing 3.0 (UBL) and Pitfalls: wrong participant IDs and profile rule mismatches, so it can be used to check the required fields, process decisions, and validation controls before the invoice workflow is used in production.

Channel: PEPPOL
Format: PEPPOL BIS Billing 3.0 (UBL)
Pitfalls: wrong participant IDs and profile rule mismatches