# European E-Invoicing Formats and Networks by Country: ERP Planning Table

> Source: https://netray.co/tools/european-e-invoicing-formats-by-country-reference
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

Which e-invoice format or network applies in each European country, with the syntax behind it, for ERP output planning.

## Category

regional

## Region

European Union

## Audience

- ERP consultant
- Finance controller
- IT manager

## Tool

**Kind:** worksheet

**Mode:** reference

**Columns:**

#### Country or scope

**Key:** country

**Type:** text

#### Format or channel

**Key:** format

**Type:** text

#### Syntax

**Key:** syntax

**Type:** text

#### Delivery channel

**Key:** channel

**Type:** text

#### Typical scope

**Key:** scope

**Type:** text

**Rows:**

**Country:** EU wide

**Format:** EN 16931 semantic model

**Syntax:** UBL or UN/CEFACT CII

**Channel:** Not a channel

**Scope:** Core standard under Directive 2014/55/EU for public buyers

**Country:** EU and beyond

**Format:** Peppol BIS Billing 3.0

**Syntax:** UBL 2.1

**Channel:** Peppol network (4 corner model)

**Scope:** B2G and increasingly B2B

**Country:** Germany

**Format:** XRechnung

**Syntax:** UBL or CII

**Channel:** Email, portals, Peppol

**Scope:** B2G; B2B structured invoice receipt required

**Country:** Germany

**Format:** ZUGFeRD

**Syntax:** PDF/A-3 with embedded CII XML

**Channel:** Email, EDI

**Scope:** B2B and B2G hybrid invoice

**Country:** France

**Format:** Factur-X

**Syntax:** PDF/A-3 with embedded CII XML

**Channel:** Certified platforms

**Scope:** B2B reform, phased introduction

**Country:** France

**Format:** Chorus Pro

**Syntax:** Factur-X, UBL, CII

**Channel:** Chorus Pro portal

**Scope:** B2G, mandatory

**Country:** Italy

**Format:** FatturaPA

**Syntax:** XML (national schema)

**Channel:** SdI exchange system

**Scope:** B2B, B2G and B2C, mandatory

**Country:** Spain

**Format:** Facturae

**Syntax:** XML (national schema)

**Channel:** FACe portal

**Scope:** B2G, mandatory above thresholds

**Country:** Austria

**Format:** ebInterface

**Syntax:** XML (national schema)

**Channel:** Unternehmensserviceportal, Peppol

**Scope:** B2G, optional B2B

**Country:** Netherlands

**Format:** SI-UBL / NLCIUS

**Syntax:** UBL

**Channel:** Peppol, SimplerInvoicing

**Scope:** B2G; B2B optional

**Country:** Belgium

**Format:** Peppol BIS Billing 3.0

**Syntax:** UBL 2.1

**Channel:** Peppol

**Scope:** B2G; B2B mandate from 2026

**Country:** Denmark

**Format:** OIOUBL / Peppol

**Syntax:** UBL

**Channel:** NemHandel, Peppol

**Scope:** B2G, mandatory

**Country:** Sweden

**Format:** Peppol BIS Billing 3.0

**Syntax:** UBL 2.1

**Channel:** Peppol

**Scope:** B2G, mandatory for public buyers

**Country:** Norway

**Format:** EHF (Peppol BIS)

**Syntax:** UBL

**Channel:** Peppol

**Scope:** B2G, mandatory

**Country:** Poland

**Format:** KSeF structured invoice

**Syntax:** XML (FA schema)

**Channel:** KSeF national platform

**Scope:** National system, phased mandate

**Notes:** Mandates and dates differ by country and are changing; this table describes formats and channels, not legal obligations or deadlines. Confirm current rules with your tax adviser and your ERP vendor's localization documentation before you commit to a project plan.

## Content

**Intro:** E-invoicing in Europe is not one format. It is a family of national schemas, a common semantic model (EN 16931) and the Peppol network. This table helps ERP teams for European manufacturers see which output formats and delivery channels they need per country before scoping the work.

**Sections:**

#### How to use the table

**Body:** List the countries in which your legal entities issue or receive invoices, then filter the table by each country and note the format, syntax and channel. The result is a short requirements list for your ERP project: which XML schemas the system must produce, which must it read, and which access points or portals you must connect to. Export the filtered rows to Excel and add owner, vendor module and test date columns.

#### Semantic model, syntax and channel

**Body:** Three layers get confused. EN 16931 is the semantic data model: which business terms an invoice carries. UBL and CII are two syntaxes that express that model in XML. XRechnung, Peppol BIS and Factur-X are profiles or containers that constrain the model for a community. The channel is how the file travels: email, a national portal, or the Peppol network. A good ERP localization states clearly which layer each feature covers.

#### Hybrid versus pure XML

**Body:** ZUGFeRD and Factur-X are hybrid: a readable PDF/A-3 with an embedded XML file, so a human and a machine read the same document. XRechnung, FatturaPA and Facturae are pure XML, and the visual copy is generated separately. For a manufacturer with many small European customers who still expect a PDF, hybrid formats ease the transition; for public sector customers pure XML is usually required.

**Bullets:**

- Check whether your ERP produces the XML natively or relies on an add-on.
- Check inbound: can the system read and post supplier e-invoices?
- Plan archiving of the original XML for statutory retention periods.
- Test with the validator of each community, not only your own checks.

#### Common mistakes

**Body:** Teams often scope only outbound invoices and forget inbound, credit notes, corrections and cancellations, each of which has format specific rules. Another common issue is mapping buyer references: a German public buyer needs a Leitweg-ID, an Italian customer needs a destination code, and a Peppol recipient needs an endpoint ID. Capture these routing fields in the customer master early.

**Cta:** Netray can map your current invoice output and customer routing data against the formats you need, using a read-only extract, so your localization estimate starts from facts.

**Faq:**

#### Is XRechnung the same as ZUGFeRD?

**Answer:** No. XRechnung is a pure XML profile of EN 16931, mainly used for German public buyers. ZUGFeRD is a hybrid with a PDF/A-3 and embedded XML. Recent ZUGFeRD versions contain a profile that is compatible with XRechnung, but the container differs.

#### Do I need Peppol if my ERP already makes UBL files?

**Answer:** A UBL file is only a format. Peppol adds a network, addressing and access points. If customers require delivery through Peppol, you need an access point, either through your ERP vendor, a service provider or your own certified connection.

#### Does the table show when e-invoicing becomes mandatory?

**Answer:** No. Dates are being adjusted in several countries and differ for issuing and receiving. The table describes formats and channels so you can plan the technical scope. Take deadlines from the national authority or your tax adviser.

#### Which format should a manufacturer choose for German B2B customers?

**Answer:** Ask what the customer can process. Many accept ZUGFeRD or XRechnung. The key point is that the invoice must be structured and compatible with EN 16931. Align format, profile and archiving with the customer and your tax adviser.

## Search terms

xrechnung vs zugferd, peppol bis billing 3.0 countries, european e-invoicing formats, fatturapa sdi format, factur-x format, ksef poland e-invoice, en 16931 formats, erp e-invoicing europe

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json