Add Peppol and e‑invoicing to your accounting, ERP or industry software. One REST API gives access to 15+ countries and every network. With REST API experience you are live within four weeks.
Schedule a meeting
View the API docs
Three integration models, one underlying platform. You connect your software to the eConnect Procurement Service Bus (PSB) via a standard connection, a direct REST API integration, or a combination. The choice depends on your technical preference and what your end users expect. This way you open up the Peppol network without operating, certifying or maintaining your own Access Point.
Standard connections for the most-used accounting and ERP packages. Set up once, after which document exchange runs automatically. No development work required.
Modern REST API with OAuth2, OpenAPI/Swagger documentation and SDKs in PHP and .NET. For deep integration or custom workflow support.
Document exchange via SFTP folders, mailfrom hooks or webhooks. Status updates and inbound documents are pushed directly to your endpoints.
Choose the integration method that fits your technical preference and end-user requirements.
One integration gives access to Peppol, other procurement networks such as Coupa, Tungsten, SAP Ariba and Tradeshift, and email. The PSB chooses the correct channel automatically. Format transformation and protocol maintenance are managed.
Country-specific rules and standard updates actively tracked. Changes in NLCIUS, Peppol BIS, DICO, SETU and CTC models are applied automatically.
Send a PDF, scan or receipt and receive a validated e-invoice in return. The IDR processes 100% of all invoices with line recognition and supplier identification.
The Validate API checks XML documents without sending. The Transform API converts between e-invoice formats. Both are also usable standalone.
The Procurement Service Bus offers software partners a complete package of e-invoicing functionality.
We chose eConnect for multiple reasons, from the competitive pricing to the quality of your API, which we found to be one of the best among tested providers.
The partner model supports a range of profiles, from standard accounting software to white-label PSB candidates. Per type, see the most important benefit.
In six fixed steps, with go-live typically within four weeks for partners with REST API experience. The partner process runs from introduction, partner contract and technical session to the acceptance environment (accp-psb.econnect.eu) with OAuth2 credentials, a pilot with a test customer and production rollout.
During the technical session you receive an API walkthrough and help with OAuth2 setup. SDKs in PHP and .NET cover the most common integration patterns: send invoice, retrieve status, handle webhook, call transformation. Our OpenAPI/Swagger documentation is always current and publicly available via docs.econnect.eu/bouwen/api, so your technical team can already estimate the scope before the first conversation.
The PSB offers endpoints for, among other things, sending sales invoices, receiving purchase invoices, sending and receiving orders, self-billing, validation of XML documents, format transformation between e-invoice formats, IDR for PDF conversion and VPD/Purple Pages for party data lookup. All endpoints are documented via OpenAPI/Swagger and reachable under psb.econnect.eu (production) or accp-psb.econnect.eu (acceptance).
Authentication runs via OAuth2 on identity.econnect.eu/connect/token. Document notifications can be pushed via webhooks or handled via SFTP exchange.
No. With a standard connection or REST API integration you send via the Peppol Access Point of eConnect. You have no Peppol certificate of your own, no annual OpenPeppol contribution and no periodic audits. eConnect takes care of the PKI infrastructure, the relationship with the Peppol authorities and all country-specific accreditations.
In concrete terms this saves you an application track of six to twelve months, a multi-year commitment to OpenPeppol and a dedicated compliance team for 15+ countries. If you want to offer Peppol explicitly under your own brand with your own login domain and look and feel, then a white-label connection on the PSB is the logical next step. There you continue to operate under the Peppol certificate of eConnect, so without the fixed costs of your own Access Point.
eConnect offers compliance as a managed service: regulation in 15+ countries is actively tracked and changes in standards, formats or CTC requirements are pushed centrally to the PSB. For the Netherlands, Belgium, France, Poland, Italy, Spain, Germany and other markets this is part of the managed service.
For partners this means: you do not have to build or maintain country-specific knowledge yourself. The same integration works for both domestic and cross-border flows.
Three communication models for inbound documents and status updates. Webhooks push events directly to your endpoints as soon as something happens; suitable for real-time processing. SFTP places inbound documents in a directory and picks up outbound documents from another directory; suitable when your architecture already uses SFTP file exchange. Polling via REST API lets your software periodically ask for new documents or status updates; suitable when webhooks or SFTP are not possible.
The three models can be combined, for example webhooks for status updates and REST for sending.
The commercial agreements are recorded in a partner contract and depend on the integration type, the volume and the audience. We discuss in a personal conversation which terms suit your situation. Schedule a meeting to discuss the options.
In thirty minutes we discuss which integration route fits, how long the implementation takes and which partner terms apply for your situation.
Schedule a meeting
Read the integration path