From January 1, 2025, businesses in Germany must have been able to receive structured e-invoices, but mandatory B2B e-invoice issuance starts from 2027. Unsurprisingly, many businesses are looking at Peppol Access Points to send and receive e-invoices.
Key Takeaways
- Germany requires businesses to issue EN 16931-compliant e-invoices from January 1, 2027.
- While a Peppol Access Point is not mandatory, it remains a widely used option for structured invoice exchange.
- KoSIT serves as Germany's Peppol Authority and maintains the XRechnung standard.
- Public sector invoices typically require XRechnung and a Leitweg-ID.
- Businesses can connect through certified providers without operating their own Peppol Access Point.
A Peppol Access Point links your organization to the Peppol eDelivery Network. Without it, you cannot exchange documents through Peppol. It handles the secure sending and receiving of invoices and other business documents using agreed standards.
Germany does not mandate Peppol. But for many businesses, it is the easiest path to compliant invoice exchange.
Businesses preparing for Germany's phased B2B e-invoicing rollout may choose to use a Peppol Access Point to issue structured invoices efficiently.
The issuance requirement applies:
Although not mandatory, Peppol is widely adopted for standardized domestic and cross-border invoice exchange.
From January 1, 2025, businesses must be able to receive e-invoices. They can also check if Peppol fits their invoice volumes, supplier base, and digitalization goals.
Businesses that invoice federal, state, or local government entities frequently use Peppol because many public sector organizations are reachable through the network.
These invoices often require:
For organizations serving government customers, Peppol is often essential, even when not mandatory.
The Peppol network operates through a four-corner model that allows participants to exchange invoices without establishing direct technical connections with every trading partner.
Corner | Participant | Role |
| Corner 1 | Sender | Creates and issues the invoice |
| Corner 2 | Sender Access Point | Validates and transmits the invoice |
| Corner 3 | Receiver Access Point | Receives and delivers the invoice |
| Corner 4 | Receiver | Receives and processes the invoice |
Several standards support invoice exchange through Peppol:
Standard | Purpose |
| EN 16931 | European standard for electronic invoicing |
| Peppol BIS Billing 3.0 | Common invoice specification used within the Peppol network |
| UBL 2.1 XML | Primary syntax used by Peppol BIS Billing |
| SMP (Service Metadata Publisher) | Stores participant information and routing details |
| MLR (Message Level Response) | Supports transmission acknowledgments within the network |
Despite Germany's B2B e-invoicing rules not requiring Peppol, ignoring it may be impractical for your business.
Peppol Access Points are one of the most practical ways to exchange EN 16931-compliant invoices. They provide a standardized framework for transmission and validation. Their importance is even greater in public sector invoicing, where many authorities are accessible through the Peppol network and require XRechnung-compliant invoices.
Peppol participants must meet technical and security requirements established by OpenPeppol. This creates a controlled network where organizations can exchange invoices through verified endpoints rather than open email channels.
Another biggest strength of Peppol is that it replaces countless one-off integrations with a single standardized connection. Instead of building separate invoice exchange links for every customer and supplier, organizations connect once to the Peppol network and can transact with all reachable participants.
Structured invoice data should eliminate most manual invoice entry. When invoice information is exchanged in a structured format, details such as supplier information, tax amounts, purchase order references, and payment terms can move directly into ERP and accounting systems. There is no need to re-key. This cuts down transcription errors and speeds up invoice processing.
Peppol supports invoice exchange across multiple countries through a single network connection. This eliminates the need for multiple bilateral EDI arrangements and simplifies international invoicing.
Germany may have adopted XRechnung as its national e-invoicing standard for public procurement, but compliance is only part. Peppol Access Points help businesses exchange XRechnung-compliant invoices, connect with public authorities, support Leitweg-ID requirements, and improve invoice routing accuracy.
These two concepts are related. But they are not the same.
Aspect | Peppol Access Point | Service Provider |
| Definition | Certified gateway connected to the Peppol network | Company providing e-invoicing services |
| Primary Role | Transmits documents through Peppol | Delivers solutions and customer services |
| Network Connectivity | Direct connection to Peppol network | May connect through its own or a partner Access Point |
| Certification Requirement | Required | Not always required |
| Customer Support | Limited technical focus | Typically provides onboarding and support |
| ERP Integration | Connectivity-focused | Integration-focused |
| End User Interaction | Often indirect | Usually direct |
Germany does not have a centralized registration process for businesses joining the Peppol network. Instead, you select a certified provider and complete onboarding through that provider.
Providers can be very different. It is worth checking a few things before making a choice:
If your business operates internationally, you should also assess whether the provider supports invoice exchange across many countries.
You need a Peppol participant identifier to exchange documents through the network.
Common identification schemes include:
If you are a public sector entity, your identifier may be linked to your Leitweg-ID through the 0204 scheme. Your provider will assist with participant registration and metadata publication.
Providers generally request:
Most providers offer many integration approaches:
Integration Method | Suitable For |
| Web Portal | Low invoice volumes |
| ERP Connector | Businesses using supported ERP systems |
| API Integration | High-volume or customized environments |
| File-Based Upload | Batch invoice processing |
Before production activation, your provider will typically perform testing to verify:
After setup, you're ready. You can exchange invoices with customers, suppliers, and public authorities through Peppol.