#20260902002_EN3 min readUpdated: Category: Compliance & Regulations
Format and Transport Are Two Different Questions
In projects, format and transmission channel are often conflated. XRechnung and ZUGFeRD describe how an invoice is structured in terms of content. They say nothing about how the document reaches the recipient. Legally, a simple method like email is sufficient for domestic B2B invoices in Germany — in practice, it is the weakest, as it offers no delivery receipt, no address verification, and no standardized error feedback.
Peppol closes precisely this gap: a standardized network with binding technical profiles, verified participant identifiers, and acknowledged delivery.
The Four-Corner Model
Peppol operates on a four-corner model. Corner one is the sender, corner four the recipient. In between are two Access Points — service providers that feed messages into the network and receive them on behalf of their customers. Senders and recipients do not need to negotiate bilateral exchange agreements; they only interact with their respective Access Point.
Addressing is handled via a Participant ID — in Germany, typically derived from a Leitweg-ID or corporate identifier. A central directory resolves which Access Point is responsible for an identifier and which document types the recipient can accept. It is this directory that makes Peppol far more robust than email: an unregistered recipient is detected before dispatch, not after.
Peppol BIS Billing and Practice in Germany
The invoice profile used across the network is Peppol BIS Billing, a specification of the EN 16931 standard. XRechnung is also such a specification. The two are compatible but not identical: they differ in certain business rules and mandatory fields. Suppliers delivering to public authorities typically work with XRechnung including a Leitweg-ID; those transmitting across Europe additionally require the BIS profile.
In implementation terms, the mapping layer must be capable of generating both specifications from the same data source. To achieve this, we model an internal canonical invoice object and derive the target formats from it — avoiding duplicate maintenance whenever a format version is updated.
The Path to Your First Transmission
Getting started involves five steps: selecting an Access Point, defining and registering the participant ID, enabling document types and profiles, running test transmissions with realistic documents, and finally the go-live with a defined fallback strategy.
The most demanding step is almost always the fourth. Test transmissions with dummy documents run smoothly; errors surface with real data — deviating tax codes, missing buyer references, units of measure not matching the code list, or rounding discrepancies between line-item and header totals. Always plan for a realistic data sample extracted from your production system.
How OXORY Supports You
We connect Peppol directly to the SAP billing process: generating the canonical document, deriving XRechnung or BIS Billing, validating against applicable business rules, transmitting via an Access Point, and returning delivery status to business-user-friendly monitoring.
If you want to evaluate whether Peppol is the right fit for your recipient structure, a brief breakdown of your invoice recipients by country and type is usually enough to clarify the decision in a single conversation.
More articles
— AMS & support
In-House Team or Outsourced AMS? Decision Matrix for SAP Support
— AMS & support
How to Calculate SAP AMS Costs
— Shoring
SAP Shoring or Nearshore? Model and Cost Comparison