PEPPOL in Germany

Updated On : -- | -- min read

PEPPOL in Germany: Network Architecture, Compliance Role, and What Businesses Need to Understand Before Connecting

Germany's transition to mandatory electronic invoicing has brought two distinct but complementary frameworks into sharp focus: the data standards that define what a compliant invoice must contain, and the network infrastructure that determines how that invoice is securely delivered from one party to another. <a href='[Link to Blog 5]'>XRechnung and EN 16931</a> address the first question. PEPPOL addresses the second. Understanding the distinction between these two dimensions, and how they work together within Germany's evolving e-invoicing landscape, is essential for any business seeking to build a compliant, scalable, and future-ready document exchange capability.

PEPPOL, which stands for Pan-European Public Procurement Online, is a European initiative that provides the technical and governance infrastructure for the secure, standardised exchange of electronic business documents across borders and systems. It is not a file format. It is not a database. It is a network, built on a defined architecture and governed by a certification framework, that allows any participant connected through a certified access point to exchange invoices, orders, and other procurement documents with any other participant on the network, regardless of which software systems they use or which country they operate in.

The Problem PEPPOL Was Built to Solve

Before PEPPOL, the challenge of electronic document exchange was not simply a matter of format standardisation. Even where two organisations agreed on a common invoice format, the question of how to transmit that invoice securely, how to confirm delivery, how to authenticate the identity of the sender and receiver, and how to maintain an auditable record of the exchange remained unresolved without bespoke bilateral integration between the two parties' systems. Scaling this approach across a large supplier or customer base was prohibitively complex and expensive.

PEPPOL resolves this by replacing bilateral integration with a network model in which every participant connects once, through a single certified access point, and gains the ability to exchange documents with every other participant on the network. The analogy to email infrastructure is instructive. A business does not need a direct technical connection to every email recipient. It connects to an email provider, and that provider handles delivery to any other provider's users through shared protocols. PEPPOL operates on the same principle, applied to structured business documents with the additional requirements of identity verification, format validation, and regulatory compliance built into the network architecture.

The Four-Corner Model: How PEPPOL Moves Documents

The foundational architecture of PEPPOL is known as the four-corner model, and understanding it clarifies both how the network operates and why each element of it exists.

The first corner is the document sender, typically a supplier creating an invoice. The sender's responsibility is to produce the invoice in the correct PEPPOL BIS format and submit it to their access point for transmission. The sender does not need to know the technical details of the receiver's systems. They only need to know the receiver's PEPPOL ID.

The second corner is the sender's access point. This is a certified service provider that receives the document from the sender, validates it against the applicable format and content rules, and transmits it securely to the receiver's access point. The sender's access point is responsible for ensuring that the document is technically compliant before it enters the network.

The third corner is the receiver's access point. This certified provider receives the validated document from the sender's access point, authenticates the transmission, and delivers it to the receiver's system in a format that the receiver's infrastructure can process. The two access points communicate directly with each other through PEPPOL's standardised protocols, with no involvement required from either the sender or receiver beyond their respective connections to their own access points.

The fourth corner is the document receiver, typically a buyer or public authority, whose system processes and archives the received document. The receiver's access point handles the delivery, so the receiver's ERP or accounting system only needs to be configured to accept documents in the incoming format.

The elegance of this model is that it removes the need for direct technical integration between any two trading partners. As long as both are connected to certified access points within the PEPPOL network, they can exchange documents without any bespoke configuration between them. This property is what makes PEPPOL genuinely scalable as a network infrastructure rather than merely a bilateral exchange protocol.

PEPPOL BIS 3.0: The Format Standard Within the Network

PEPPOL's network architecture defines how documents move. The PEPPOL BIS, or Business Interoperability Specification, defines what those documents must look like structurally. BIS 3.0 is the current version of this specification and is fully aligned with the EN 16931 European e-invoicing standard, meaning that documents exchanged over PEPPOL in BIS 3.0 format satisfy the <a href='[Link to Blog 7]'>EN 16931 compliance requirements</a> that underpin Germany's mandatory e-invoicing framework.

PEPPOL BIS 3.0 applies the Universal Business Language 2.1 syntax, one of the two XML syntaxes recognised under EN 16931. It defines the data model for invoices, credit notes, and order documents exchanged through the network, including all mandatory fields, validation rules, and code lists that ensure consistency across systems and jurisdictions. Because BIS 3.0 is both PEPPOL-compliant and EN 16931-compliant, an invoice created in this format can be transmitted through the PEPPOL network and simultaneously satisfy Germany's domestic <a href='[Link to Blog 6]'>e-invoicing mandate</a> requirements.

For Germany specifically, BIS 3.0 can carry an XRechnung-compliant invoice, meaning that the content requirements of Germany's mandatory B2G format can be fulfilled within the PEPPOL transmission framework. The XRechnung standard adds German-specific mandatory fields to the EN 16931 core model, most notably the Leitweg-ID routing code that directs invoices to the correct public authority within Germany's government receiving infrastructure. Where an invoice is destined for a German federal authority and is transmitted through PEPPOL, the BIS 3.0 format carries the XRechnung-compliant content, combining the delivery capability of the network with the content requirements of the national standard.

PEPPOL IDs: Identity Within the Network

Every participant in the PEPPOL network is identified by a unique PEPPOL ID, which serves as the electronic address to which documents are routed within the four-corner model. Without a valid PEPPOL ID, a business cannot send or receive documents through the network. The PEPPOL ID is the network's equivalent of an email address, without which communication cannot be initiated or received.

In Germany, the PEPPOL ID format for business participants uses the country scheme code 9930, which designates Germany, combined with the company's VAT identification number. A representative example would be formatted as 9930:DE123456789, where 9930 is the German country scheme identifier and DE123456789 is the organisation's <a href='[Link to Blog 8]'>USt-IdNr</a>. This structure ties the PEPPOL identity directly to the business's established tax identification, providing a verifiable link between the network participant and the registered legal entity.

The registration process for obtaining a PEPPOL ID involves selecting a certified access point provider recognised by OpenPEPPOL, the international not-for-profit association that governs the PEPPOL network, submitting the organisation's legal name, VAT number, and relevant contact information, and undergoing identity verification by the provider. Once registration is complete and the PEPPOL ID is assigned, it is registered in the PEPPOL Service Metadata Publisher directory, which access points query to locate the correct receiver access point for any given PEPPOL ID. This directory lookup is the mechanism that allows any sender to route a document to any receiver on the network without needing advance knowledge of the receiver's technical infrastructure.

Every document transmitted through the network carries both a sender ID and a receiver ID. The sender ID identifies the organisation initiating the transmission, and the receiver ID identifies the intended recipient. This dual-identification structure provides a legally verifiable audit trail for every transaction, which is particularly relevant in a business-to-government context where the integrity of the invoicing record has direct fiscal implications.

PEPPOL and XRechnung: Understanding the Relationship

A point of consistent confusion in Germany's e-invoicing landscape is the relationship between PEPPOL and XRechnung. They are not alternatives or competitors. They operate at fundamentally different layers of the invoicing process and are designed to work together rather than in place of each other.

XRechnung is a content standard. It defines the data that a German public sector invoice must contain, the XML structure in which that data must be expressed, and the validation rules that ensure completeness and accuracy. It answers the question of what the invoice looks like.

PEPPOL is a transmission network. It defines how a document moves from sender to receiver, how the participants in that exchange are identified and authenticated, and how the integrity of the transmission is assured. It answers the question of how the invoice travels.

An invoice submitted to a German federal authority can be XRechnung-compliant in its content and PEPPOL-transmitted in its delivery. The two standards address different aspects of the same transaction and are not in conflict. Germany's government receiving infrastructure, including the ZRE portal for federal invoices and the OZG-RE portal for state-level submissions, accepts PEPPOL-transmitted XRechnung invoices, making this combination the standard approach for B2G invoicing at scale.

For businesses operating across multiple EU jurisdictions, PEPPOL's cross-border reach extends this logic beyond Germany. Because PEPPOL is a pan-European network operating on common standards, a business connected to the network in Germany can use the same infrastructure to exchange documents with counterparties in Sweden, the Netherlands, Belgium, or any other PEPPOL-enabled jurisdiction. The format details may vary by country, but the network architecture and access point model remain consistent, making PEPPOL a single investment that serves a multi-jurisdictional document exchange requirement.

Who Should Be Using PEPPOL in Germany

The question of who should be connected to PEPPOL in Germany is partly defined by legal obligation and partly by operational logic. The mandatory dimension applies directly to suppliers invoicing German federal or state authorities. Business-to-government invoicing through PEPPOL is the established and expected delivery channel for public sector transactions, and suppliers without PEPPOL connectivity face the alternative of using the government portals directly, which is viable for low volumes but becomes operationally inefficient at scale.

Beyond the B2G mandatory context, the operational case for PEPPOL connectivity extends to private sector businesses engaged in EU-wide commerce. As Germany's <a href='[Link to Blog 6]'>B2B e-invoicing mandate</a> progressively extends mandatory issuance requirements through 2027 and 2028, and as other EU member states implement their own equivalent mandates, PEPPOL's position as the shared cross-border infrastructure becomes increasingly relevant for any business with a substantial European trading partner base.

Accounting software vendors and ERP solution providers building e-invoicing automation into their products for German and European markets treat PEPPOL integration as a standard capability requirement rather than an optional enhancement. Multinational corporations managing document exchange across subsidiaries in multiple EU countries use PEPPOL connectivity to standardise that exchange on a single network rather than maintaining separate bilateral integrations for each trading relationship.

The Operational Benefits of PEPPOL Connectivity

The compliance dimension of PEPPOL is the most frequently discussed, but the operational benefits extend substantially beyond regulatory adherence. The standardisation that PEPPOL enforces through its BIS format and access point validation means that documents entering an organisation's systems through the network have already been validated for format compliance and content completeness before arrival.

This upstream validation removes a significant category of processing work from the accounts payable function and reduces the error rate in automated invoice matching and posting.

The network's encryption and authentication mechanisms, enforced through the certified access point framework, provide a level of transmission security that email-based invoice delivery cannot match. Identity verification through PEPPOL IDs creates an auditable record of who sent what to whom and when, which is valuable both for internal audit purposes and for demonstrating compliance to fiscal authorities in the event of a tax examination.

Cost reduction across the full document exchange lifecycle is a consistently reported outcome of PEPPOL adoption. The elimination of paper, postage, and manual data entry costs is the most immediately visible component, but the more substantial savings typically come from the reduction in exception handling, payment delays, and supplier query management that accompany manual and PDF-based invoicing processes. Automated validation and straight-through processing, enabled by PEPPOL's structured format requirements, accelerate payment cycles and improve cash flow predictability for both buyers and suppliers.

Connecting to PEPPOL: A Structured Implementation Approach

Implementing PEPPOL connectivity follows a logical sequence that applies regardless of a business's size or sector. The starting point is establishing whether the primary use case is B2G, B2B, or both, since this determines which format profiles and receiving infrastructure are relevant and informs the selection of an appropriate access point provider.

Selecting a certified access point from the OpenPEPPOL-accredited provider list is the first operational decision. The choice of provider should be evaluated on the basis of format support, geographic coverage, system integration capabilities, and service level commitments, particularly around delivery confirmation and error handling. A provider that supports both XRechnung and BIS 3.0 and that has established connections to Germany's government receiving portals is a practical prerequisite for any business with B2G invoicing requirements.

ERP and accounting system integration is the technical step that determines whether the investment in PEPPOL connectivity delivers its full operational benefit. A PEPPOL connection that routes documents through a certified access point but requires manual data export from the ERP and manual import at the receiving end captures only the transmission benefit of the network without realising the automation and processing efficiency that full integration enables. Configuring the ERP to generate BIS 3.0-compliant documents automatically and to ingest incoming PEPPOL documents directly into the accounts payable workflow is the configuration that unlocks the full value of network participation.

Testing before live deployment is not a discretionary step. Sending trial invoices through the access point to validate format compliance, routing accuracy, and end-to-end delivery confirmation before processing real transactions prevents the operational disruption that format errors or routing failures in live invoicing create. Most access point providers offer testing environments for this purpose.

For organisations navigating Germany's <a href='[Link to Blog 6]'>e-invoicing mandate</a> and PEPPOL adoption alongside compliance obligations in other European jurisdictions, the technical and regulatory complexity of managing multiple format standards, national requirements, and network configurations simultaneously is a material operational challenge. Platforms such as Accqrate are designed to address that challenge, providing the infrastructure and regulatory expertise that enable businesses to participate in the PEPPOL network and meet their German and European e-invoicing obligations with confidence and operational efficiency.