Anyone who wants to build Peppol into an ERP system, accounting package or their own software product faces two choices. The first is architectural: how does your software connect to the Peppol network? The second is practical: which requirements must a service provider’s API meet to make that connection reliable and scalable? This page compares the four common architecture patterns side by side and provides a checklist for assessing an API. Detailed field mapping and validation rules are outside the scope of this page. You can read more about the underlying standard on the page about EN 16931.
Four architecture patterns
No single pattern is always the best choice. The right choice depends on your scale, the desired control over the process and the capacity you have for your own maintenance.
Connector in the software package
A ready-made Peppol connector that is built in as a plugin or module, often offered by a service provider or third party. Suits: going live quickly, little in-house maintenance. Advantage: short time-to-market, proven functionality. Disadvantage: less room for customisation, dependent on the vendor's roadmap.
Connection via a service provider's API
Your software communicates directly with the API of a service provider, which handles the connection to the network. Suits: deciding for yourself how sending, receiving and status follow-up work. Advantage: full control over the process and error handling. Disadvantage: you build and maintain the integration layer yourself.
Your own middleware
A self-built or purchased intermediate layer that connects multiple systems, and possibly multiple service providers, through a single internal interface. Suits: larger organisations with multiple source systems. Advantage: independence from a single provider, central logging. Disadvantage: higher initial investment and more management.
Becoming a service provider yourself
You build or operate an Access Point and SMP yourself and become a member of the network through a Peppol Authority. You have maximum control, but you also bear all the obligations: testing and certification, identification of your end users, availability, security (ISO 27001 in the Netherlands) and the mandatory reporting to OpenPeppol. Suits parties for whom Peppol is a core part of their services. See What is a Peppol Access Point? and Becoming a certified Peppol service provider.
What to look for in an API
If you opt for a connection via an API, directly or through middleware, the quality of that API largely determines how much work the integration takes and how stable it remains. Go through these points for every candidate API.
Sending and receiving
- Validation before sending, with useful error messages.
- How incoming e-invoices reach you (push or pull), including the original file.
- Webhooks or status messages, and support for Invoice Response.
End users
- Registration and management of Peppol IDs via the API.
- Multi-tenant: multiple customers under one connection, each with their own Peppol ID.
- Who carries out the identification of your end users, and whether this can be done via the API.
- Can you take registrations with you to another provider? In the Netherlands, the old provider must cooperate within three working days.
Countries and formats
- Peppol BIS Billing 3.0 and national variants such as XRechnung and NLCIUS.
- How new versions are implemented.
- Whether countries with their own system are covered, such as the plateforme agréée (approved platform) in France.
Technology and management
- A sandbox that simulates the network.
- Versioning policy.
- Rate limits.
- Protection against duplicate sending.
- ISO 27001 or an equivalent certification.
You can read more about formats in E-invoice formats and Peppol document types and standards.
Testing before going live
A working API connection does not yet mean that the entire process works. Test end-to-end in the sandbox with a few regular trading partners before you take a customer live. Check both sending and receiving, the processing of status messages and the handling of rejected documents.
Then roll out in phases. Start with one customer or one document flow, for example only outgoing invoices, and scale up once it runs stably. This keeps errors limited to a small group and lets you learn from practice before your entire customer base moves over.
What this means for integrators
Translate the architecture choice and the API checklist into concrete action points.
- Determine which architecture pattern suits your scale: a single integration or multiple customers and tenants
- Ask every candidate API provider about the availability of a sandbox, error handling and multi-tenant support
- Plan a test phase with real trading partners before going live
- Define how the registration of Peppol IDs is automated in your onboarding process
- Define who carries out the identification of your end customers
Find service providers with an API in the comparison tool (filter on the category Peppol Access Point as a Service).
What this means for software vendors
For software vendors, the choice is also a product decision. Broadly speaking, there are three routes, the same as in Getting started with Peppol: becoming a service provider yourself, building in a service provider’s functionality via an API (possibly white-label, under your own name), or partnering with an external service that you connect to. Becoming a service provider yourself gives maximum control, but you also take on certification and ongoing management. Building in via an API keeps the user experience within your own product and outsources the connection to the network. An external service requires the least investment, but gives you the least control.
Consider what role e-invoicing plays in your proposition: is it a core feature that sets you apart, or a basic facility that simply has to work?
Conclusion
A good Peppol integration starts with a deliberate architecture choice and a critical assessment of the API you build on. Whichever pattern you choose, the questions in the checklist determine how scalable and maintainable your solution will be. You can read more about invoice formats and document types in E-invoice formats and Peppol document types and standards. Looking for service providers with an API? View the comparison tool on Peppol.now.



