Peppol e-invoicing in Germany sits at the intersection of two regulatory tracks: Germany’s domestic B2B e-invoicing mandate under §14 UStG and the established B2G e-invoicing infrastructure for public sector procurement. Understanding how Peppol e-invoicing in Germany fits into both tracks — and when it is the right solution for your business — requires separating the network (PEPPOL) from the format (XRechnung or PEPPOL BIS Billing 3.0) and understanding how German public authorities use PEPPOL as an accepted delivery channel. This guide covers what PEPPOL is, what the German e-invoicing mandate requires, whether PEPPOL is mandatory, how XRechnung and PEPPOL BIS Billing 3.0 relate, and how to connect.
Peppol e-invoicing in Germany is particularly relevant for businesses that invoice German federal or state government bodies, since PEPPOL is one of the two accepted delivery channels for B2G electronic invoices — the other being direct portal submission via ZRE or OZG-RE. For B2B businesses, PEPPOL is not mandated by Germany’s domestic e-invoicing rules, but it is an accepted transmission channel for XRechnung and PEPPOL BIS Billing 3.0 invoices. The PEPPOL network benefits for German businesses include: standardised electronic delivery to counterparties across 40+ countries; automated delivery confirmation; reduced dependence on email as a transmission channel; and a single technical integration that covers both domestic B2B and cross-border B2B/B2G invoicing within the PEPPOL network.
Key Takeaways
- Peppol E-Invoicing in Germany: Peppol is not the only transmission channel for German B2B e-invoices. Other channels may include email and portal submission, subject to applicable legal requirements.
- PEPPOL BIS Billing 3.0: This is an EN 16931-compliant e-invoice format that can be transmitted through Peppol. XRechnung and ZUGFeRD are also recognised formats when the applicable requirements are met.
- Peppol Access Point Germany: Businesses invoicing German public-sector bodies through Peppol need a suitable access point connection. The ZRE and OZG-RE portals also support electronic invoice submission for relevant public-sector recipients.
- XRechnung via Peppol: XRechnung can be transmitted over the Peppol network when the required specifications are met. The native Peppol invoice specification is PEPPOL BIS Billing 3.0.
- Benefits of the Peppol Network: Peppol supports structured electronic invoice exchange, cross-border interoperability and integration with trading partners through a connected network.
What Is PEPPOL and How Does It Work in the Context of E-Invoicing?
Peppol e-invoicing in Germany uses the Pan-European Public Procurement On-Line network — a global e-business infrastructure governed by OpenPEPPOL, an international non-profit association. PEPPOL operates as a standardised four-corner model: the sender connects to a certified PEPPOL access point (corner 2); the access point routes the invoice to the receiver’s access point (corner 3); the receiver’s access point delivers the invoice to the receiver (corner 4). The sender and receiver do not connect directly — they each connect only to their own accredited access point, which handles routing, format validation, and delivery confirmation. Each participant in the PEPPOL network has a unique identifier called a PEPPOL Participant Identifier or PEPPOL ID, which serves as the network address for invoice delivery.
The PEPPOL network benefits that make it compelling beyond pure compliance include: reliable delivery confirmation (the four-corner model produces a receipt acknowledgement from the receiver’s access point); standardised format (PEPPOL BIS Billing 3.0 is the same format across all 40+ PEPPOL countries, enabling cross-border invoicing without format negotiation); and reduced IT complexity (one PEPPOL access point connection replaces bilateral EDI agreements, email protocols, and portal-specific integrations for each counterparty). For German businesses with significant cross-border B2B invoice flows — exporting goods to Netherlands, Belgium, Scandinavia, or other PEPPOL-connected markets — Peppol e-invoicing in Germany offers a single network connection that covers both domestic and export invoice transmission.
Is PEPPOL Mandatory in Germany?
Peppol e-invoicing in Germany is not mandatory for domestic B2B transactions. The German e-invoicing mandate under §14 UStG requires a compliant E-Rechnung — XRechnung, ZUGFeRD at EN 16931+, or PEPPOL BIS Billing 3.0 — but it does not specify PEPPOL as the required transmission channel. A business can satisfy the mandate by emailing an XRechnung XML file as an attachment, by emailing a ZUGFeRD PDF, or by transmitting via PEPPOL. The transmission channel is the business’s choice; the format compliance is what matters. This means businesses can be fully compliant with the 2027 mandate without any PEPPOL connection at all, as long as the invoice file itself meets EN 16931 requirements.
For B2G (business-to-government) invoicing, the situation is different. German federal government bodies accept invoices only via ZRE (Zentrale Rechnungseingangsplattform des Bundes) or via PEPPOL — and the ZRE portal is itself PEPPOL-connected. XRechnung access point Germany connections to ZRE require either portal registration and manual upload, or a PEPPOL access point integration for automated submission. State government bodies have their own OZG-RE portals, most of which also accept PEPPOL delivery. For businesses invoicing German federal or state authorities in any volume, a PEPPOL access point Germany integration is the most efficient path — manual portal submission scales poorly above a few dozen invoices per month. So while PEPPOL is not legally mandatory for any German invoicing, it becomes functionally necessary at B2G volumes that exceed manual portal submission capacity.
What Does the German E-Invoicing Mandate Actually Require?
The German e-invoicing mandate — §14 UStG as amended by the Wachstumschancengesetz — requires that domestic B2B invoices be issued as E-Rechnungen (structured, machine-readable documents conforming to EN 16931) from the applicable deadline. The three accepted E-Rechnung formats are XRechnung, ZUGFeRD at EN 16931 or Extended profile, and PEPPOL BIS Billing 3.0. All three achieve EN 16931 compliance and are equally valid for German domestic B2B invoicing. The mandate does not specify how the invoice must be transmitted — only that it must be transmitted electronically. PEPPOL e-invoicing setup is therefore an optional transmission method, not a mandated one. Businesses that prefer email transmission can satisfy the mandate without PEPPOL; businesses that prefer PEPPOL transmission can also satisfy it. The mandate is format-driven, not network-driven.
PEPPOL access point Germany connections add value beyond mandate compliance in three scenarios. First: high-volume B2G invoicing where manual portal submission is not scalable. Second: cross-border B2B invoicing to counterparties in PEPPOL-connected markets (Netherlands, Belgium, France, Denmark, Singapore, Australia, and 35+ others) where PEPPOL eliminates format negotiation. Third: supply chain relationships where large corporate buyers mandate PEPPOL delivery from suppliers — automotive and logistics chains in Germany increasingly use PEPPOL as their preferred B2B invoice channel. None of these scenarios makes PEPPOL legally mandatory; they make it commercially necessary in specific business contexts.
XRechnung vs PEPPOL BIS Billing 3.0: How Do They Relate?
XRechnung PEPPOL and PEPPOL BIS Billing 3.0 are closely related but distinct. Both are EN 16931 compliant invoice formats; both can be transmitted via the PEPPOL network; and both contain the same 52 mandatory EN 16931 Business Terms. The difference lies in their scope and German-specific extensions. XRechnung is Germany’s national CIUS (Core Invoice Usage Specification) — a German-specific set of additional rules layered on top of EN 16931. It adds Germany-specific requirements such as the Leitweg-ID for B2G routing and specific German VAT rules. PEPPOL BIS Billing 3.0 is the international PEPPOL CIUS — it applies the same EN 16931 standard with PEPPOL-specific rules applicable across all PEPPOL countries, without the German national extensions.
The practical consequence is that XRechnung PEPPOL transmission requires the receiver to understand and accept the German CIUS extensions. Most German public authorities and large German corporations in the PEPPOL network support XRechnung. Non-German PEPPOL participants may not recognise German CIUS extensions and may prefer standard PEPPOL BIS Billing 3.0. For pure domestic B2B and B2G invoicing in Germany, XRechnung via PEPPOL works correctly. For cross-border invoicing to non-German PEPPOL participants, PEPPOL BIS Billing 3.0 is the safer choice. PEPPOL e-invoicing setup in Germany therefore often involves supporting both formats — XRechnung for domestic B2G, PEPPOL BIS Billing 3.0 for cross-border — depending on your customer geography.
| Feature | XRechnung | PEPPOL BIS Billing 3.0 |
|---|---|---|
| Scope | Germany-specific CIUS; domestic B2B and B2G | International PEPPOL standard; 40+ countries |
| EN 16931 compliance | Yes — German national extension of EN 16931 | Yes — PEPPOL extension of EN 16931 |
| Syntax | UBL 2.1 or UN/CEFACT CII | UBL 2.1 (primary); CII supported |
| German B2G (ZRE) | Required format — accepted on ZRE and OZG-RE portals | Accepted via PEPPOL delivery to ZRE-connected portals |
| German B2B mandate | Satisfies §14 UStG B2B mandate | Satisfies §14 UStG B2B mandate |
| Cross-border (PEPPOL) | May not be recognised by non-German PEPPOL participants | Accepted by all PEPPOL participants globally |
| Leitweg-ID support | Required field for B2G; defined in German CIUS | Not a standard field; requires extension or note field |
Can I Send an XRechnung Over PEPPOL?
XRechnung PEPPOL transmission is technically possible and is used for German B2G invoicing. The PEPPOL network is format-agnostic at the transport level — it routes XML documents between access points without inspecting or transforming their content. Sending an XRechnung via PEPPOL means wrapping the XRechnung XML in a PEPPOL transport envelope (AS4 message exchange protocol) and routing it to the receiver’s PEPPOL access point using their PEPPOL Participant Identifier. The receiver’s access point delivers the XRechnung XML — unchanged — to the receiver. German federal government bodies accept XRechnung delivered via PEPPOL to their ZRE PEPPOL endpoint. XRechnung PEPPOL delivery is therefore the standard method for high-volume B2G invoicing in Germany.
For B2B PEPPOL transmission, the choice between XRechnung and PEPPOL BIS Billing 3.0 depends on the receiver. If the receiver is a German business that specifies XRechnung, send XRechnung. If the receiver is a non-German business or a German business that has registered on PEPPOL with a PEPPOL BIS Billing 3.0 profile, send PEPPOL BIS Billing 3.0. Most PEPPOL access point Germany providers support both formats and can convert between them on transmission — confirm with your access point provider which formats they support and whether they offer format translation services.
How Do I Connect to the PEPPOL Network in Germany?
Peppol e-invoicing setup in Germany requires three steps: choosing an accredited PEPPOL access point, registering your business on the PEPPOL network with a Participant Identifier, and configuring your invoicing system to generate and transmit PEPPOL-compatible invoice files. PEPPOL access points are accredited by OpenPEPPOL and must pass regular re-certification audits. In Germany, access point providers include both specialist e-invoicing platforms (Basware, Tungsten Network, Tradeshift, Seeburger, Schleupen) and ERP-integrated services (SAP Business Network, Lexmark, DocuWare). Smaller businesses often use SaaS invoicing platforms with built-in PEPPOL connectivity rather than a standalone access point integration.
PEPPOL network benefits are accessible quickly once access point registration is complete — typically 2–5 business days for a standard SME onboarding. The PEPPOL Participant Identifier (PEPPOL ID) is assigned during registration and consists of a scheme identifier and a participant identifier (usually the company’s VAT ID or trade register number). After registration, your business appears in the PEPPOL Directory (directory.peppol.eu), where counterparties can look up your PEPPOL ID and send invoices directly. For B2G invoicing, you will also need the Leitweg-ID of the receiving public authority — this is the routing identifier specific to German government procurement, and it is required in the BuyerReference field of every XRechnung or PEPPOL invoice addressed to a German public authority.
How Do I Send E-Invoices to German Government Bodies via PEPPOL?
German public authorities that accept PEPPOL delivery have their PEPPOL Participant Identifiers registered in the German Leitweg-ID directory and on the PEPPOL network. To send an e-invoice to a federal authority via PEPPOL: obtain the authority’s Leitweg-ID from your procurement contact or from the ZRE portal; include the Leitweg-ID in the Buyer Reference field (BT-10) of your XRechnung; transmit via your PEPPOL access point Germany to the federal ZRE PEPPOL endpoint. The ZRE validates the invoice against XRechnung schema and business rules, and the result (accepted or rejected with error codes) is returned to your access point. Peppol e-invoicing in Germany for B2G therefore combines the PEPPOL transport protocol with the XRechnung format and the Leitweg-ID routing mechanism specific to German public sector procurement.
State government authorities use OZG-RE portals, many of which are also PEPPOL-connected. The process is the same: obtain the state authority’s PEPPOL ID or Leitweg-ID from your procurement contact, include it in BT-10 of the XRechnung, and transmit via your PEPPOL access point. Some state portals accept both PEPPOL delivery and direct portal upload; for high volumes, PEPPOL delivery is more efficient. PEPPOL access point Germany providers typically include a directory lookup tool that lets you confirm whether a specific government counterparty is registered on PEPPOL before attempting transmission — use this to avoid sending to non-registered counterparties, which results in undeliverable invoice errors. Advintek Philippines can help businesses explore e-invoicing integration and digital invoice management solutions suited to their requirements.
| Step | Action | Tool or Source | Notes |
|---|---|---|---|
| 1 | Choose a PEPPOL access point | Compare certified providers (Basware, Seeburger, Schleupen, SAP BN) | Check ERP integration, B2G support, pricing model |
| 2 | Register as PEPPOL participant | Your access point provider manages registration | Receive PEPPOL Participant Identifier (PEPPOL ID) |
| 3 | Obtain counterparty PEPPOL ID | PEPPOL Directory, ZRE portal, or procurement contact | For B2G: use Leitweg-ID from German government procurement portal |
| 4 | Generate XRechnung or PEPPOL BIS 3.0 | Your ERP or invoicing platform with PEPPOL access point integration | Validate against EN 16931 before transmission |
| 5 | Transmit via PEPPOL | Access point routes to receiver’s access point automatically | Delivery confirmation returned; check for validation errors |
| 6 | Archive transmitted invoice | GoBD-certified archive — retain original XML for 10 years | Transmission record (timestamp, PEPPOL ID) is part of the archive record |
Frequently Asked Questions
1. Is Peppol e-invoicing in Germany required by the B2B mandate?
No — PEPPOL is not required by the German B2B mandate. The mandate requires a structured E-Rechnung in XRechnung, ZUGFeRD (EN 16931+), or PEPPOL BIS Billing 3.0, but does not specify the transmission channel. Email delivery satisfies the mandate equally.
2. What are the PEPPOL network benefits over email for B2B invoicing?
Structured delivery confirmation, no email bounce risk, cross-border reach to 40+ countries, and standardised format (PEPPOL BIS Billing 3.0) without per-customer format negotiation. For high-volume B2B or B2G, PEPPOL reduces operational overhead significantly compared to email.
3. How long does PEPPOL e-invoicing setup in Germany take?
For SMEs using a SaaS platform with built-in PEPPOL connectivity: 1–2 weeks. For ERP integrations with a standalone access point: 4–8 weeks depending on ERP configuration complexity. B2G-specific setup (Leitweg-ID collection, ZRE registration) adds 1–2 weeks if done in parallel.
4. Can I use PEPPOL BIS Billing 3.0 for domestic German B2B invoicing?
Yes — PEPPOL BIS Billing 3.0 satisfies the German B2B e-invoicing mandate as a compliant EN 16931 format. Both domestic and cross-border B2B invoices can be issued in PEPPOL BIS Billing 3.0 format.
5. What happens if my PEPPOL transmission fails?
Your PEPPOL access point Germany provider returns an error notification with a specific error code. Common errors include invalid PEPPOL ID for the receiver, EN 16931 validation failure, or Schematron rule violations. Correct the error and retransmit; the failed transmission does not constitute invoice delivery.
Source by:
Image by Gemini
