Provider Route
Peppol Access Point
A Peppol Access Point is the routing layer that sends and receives Peppol invoice traffic for your ERP or e-invoicing platform. Teams use it when they need a provider to exchange Peppol BIS Billing 3.0 documents, validate routing, and connect their invoice export flow to the Peppol network. The decision is about network access and transport, not about replacing the invoice format itself.
Grounded in official sources listed below. Not a substitute for legal or tax advice.
Quick Answers
- 01 What is a Peppol Access Point?
- A Peppol Access Point is a certified routing service that sends and receives Peppol documents — including Peppol BIS Billing 3.0 invoices — through the Peppol Network. Think of it as the postal service for e-invoices: your ERP sends an invoice to your Access Point, which routes it across the network to the recipient's Access Point, which delivers it to their system.
- 02 Do businesses need their own Access Point?
- Not necessarily. Most businesses subscribe to a commercial Access Point provider rather than running their own. The provider handles connectivity, Peppol ID registration, validation, and delivery confirmation. A business needs its own Access Point only if it has the infrastructure and technical team to operate one and has received Peppol accreditation.
- 03 What is the four-corner model in Peppol?
- The Peppol four-corner model describes the flow: Corner 1 (sender ERP) generates a Peppol BIS 3.0 invoice; Corner 2 (sender Access Point) validates, signs, and sends it; Corner 3 (receiver Access Point) receives and validates it; Corner 4 (receiver ERP) processes the invoice. The two Access Points handle routing, signature verification, and transport — the sender and receiver ERP only interact with their respective Access Point.
- 04 What should ERP teams check first?
- Confirm ERP export support for Peppol BIS Billing 3.0 (UBL 2.1 XML), Peppol invoice field mapping, and whether your ERP has native Peppol connectivity or needs middleware. Then assess Access Point provider options based on your country coverage, ERP integration method, and invoice volume.
Peppol Access Point: how it works, when you need one, and what to check before choosing a provider
A Peppol Access Point is the routing layer that connects your invoice export to the Peppol Network. On its own, generating a Peppol BIS Billing 3.0 invoice from your ERP does not deliver it — you need an Access Point to transmit it to the network, validate it against Peppol rules, and route it to the recipient. The Access Point is the transport and routing layer; Peppol BIS Billing 3.0 is the invoice format that your ERP must generate. Before choosing an Access Point provider, confirm that your ERP can export valid UBL 2.1 XML invoices conforming to Peppol BIS Billing 3.0, and that the provider supports the countries and ERP systems in your operating model. Access Points do not replace EN 16931 compliance, UBL mapping, or your ERP export design — they handle connectivity, delivery receipts, and routing once the invoice is ready.
What is a Peppol Access Point?
When do you need one?
Use a Peppol Access Point when you need a provider to route Peppol invoices from your ERP or middleware into the Peppol network, especially when you want a structured provider selection checklist, ERP integration support, and a controlled way to exchange Peppol BIS Billing 3.0 documents.
Peppol Access Point vs Peppol BIS Billing 3.0
Peppol Access Point is the transport and routing service. Peppol BIS Billing 3.0 is the invoice format/specification that your ERP or middleware must generate. A provider can help with connectivity, validation, and delivery, but it does not replace EN 16931, UBL Invoice mapping, or your ERP export design.
Format, Transport, and Semantic Layers
Comparing Peppol Access Point routing with other routes: Peppol BIS Billing 3.0 (format) vs Peppol Access Point (transport) vs EN 16931 (semantic model). The Access Point is the certified Peppol routing service — it carries the invoice across the Peppol network, not the format itself. Peppol BIS Billing 3.0 is what your ERP generates; the Access Point is how it reaches the Peppol network. EN 16931 is the data model that both Peppol BIS 3 and other formats reference — it defines what information must be in an invoice, not how it gets from A to B.
Provider selection checklist
- Confirm the provider is a real Peppol Access Point provider with the routing coverage you need.
- Check support for Peppol BIS Billing 3.0, EN 16931 alignment, and UBL Invoice input.
- Review ERP integration options, API documentation, and validation tooling.
- Ask how delivery receipts, error handling, and monitoring are exposed to your team.
- Confirm onboarding, participant ID handling, and country coverage for your trading partners.
ERP integration questions
- Can our ERP export the invoice fields required for Peppol BIS Billing 3.0?
- Do we need middleware to map ERP data into UBL Invoice or another compatible syntax?
- How will we validate the invoice before it reaches the Peppol Access Point?
- What does the provider expose for retries, receipts, and troubleshooting?
Country relevance
- Belgium uses Peppol heavily in public-sector and broader e-invoicing workflows.
- Germany teams often compare Peppol routing with XRechnung and SAP-ready ERP exports.
- France may involve Peppol routing alongside Factur-X and PDP route decisions.
- The Netherlands is relevant where cross-border Peppol invoice exchange is part of the operating model.
Common mistakes
- Choosing a provider before confirming the country route and invoice format.
- Confusing Peppol Access Point routing with Peppol BIS Billing 3.0 invoice structure.
- Ignoring ERP export and validation constraints until late in implementation.
- Assuming the access point alone guarantees compliance across every country.
Related standards
Related ERP systems
Related countries
Official Sources
All information on this page is based on the sources listed below. Always verify current requirements with the issuing authorities.
- Peppol BIS Billing 3.0 Standard Body
Invoice specification and validation rules used by Peppol routing
- The Peppol Network Standard Body
Network overview and access point model