XRechnung vs Peppol BIS: format and transport
XRechnung is an invoice format; Peppol BIS is a format plus a transport network. Both are EN 16931 CIUS. A comparison for German and EU-wide e-invoicing.
| XRechnung | German national CIUS of EN 16931 (UBL or CII) |
|---|---|
| Peppol BIS Billing 3.0 | CIUS of EN 16931 in UBL 2.1, + Peppol network (four-corner model) |
| Additional rules | Peppol BIS adds PEPPOL-EN16931 rules on top of the base BR rules |
| Transport | XRechnung transport-agnostic; Peppol BIS via Access Points (AS4) |
XRechnung and Peppol BIS are often compared but address partly different layers: XRechnung is an invoice format, Peppol BIS is a format plus a transport network. Both are CIUS of EN 16931.
Comparison
| Attribute | XRechnung | Peppol BIS Billing 3.0 |
|---|---|---|
| Layer | Format | Format + network |
| Syntax | UBL or CII | UBL 2.1 |
| EN 16931 | Yes (German CIUS) | Yes (CIUS) |
| Extra rules | BR-DE | PEPPOL-EN16931-* |
| Transport | any (portal, email, Peppol …) | Peppol network (AS4, four-corner) |
| Typical use | DE B2G/B2B | EU-wide B2B/B2G exchange |
How they combine
The two are not mutually exclusive: an XRechnung in UBL can be transmitted over the Peppol network, provided it also satisfies the PEPPOL-EN16931 rules. In countries such as Belgium, Peppol BIS is the mandated default route; in Germany, XRechnung is the common format — over various channels.
How invowerk helps
invowerk validates both XRechnung and Peppol BIS invoices against EN 16931 and their respective extra rules and explains every error code in plain language (see /codes). Transport over the Peppol network is handled by your Access Point; the content check runs upstream via API or MCP.