One integration with the Procurement Service Bus (PSB). Your software connects once. The API routes to Peppol, CTC and email, and to other networks or local clearance. No separate connection per channel.
Schedule a meeting
API documentation
The PSB is a certified Peppol Access Point and SMP, connected to the major procurement networks. On sending, the platform automatically determines the best route via #PeppolFirst: Peppol if the recipient is registered, otherwise another structured channel or email. The integrator does not have to choose a channel per invoice; the PSB does that itself based on the SMP lookup and the delivery options API.
Send and receive via the Peppol network in 65 countries. Including BIS Billing, PINT profiles and country-specific CIUS validations.
For European CTC and clearance countries where eConnect serves active customers: Germany (XRechnung, B2B mandate and customers such as Conrad), Italy (SdI/FatturaPA), Poland (KSeF), France (PPF/Factur-X) and Belgium (Peppol B2B). The PSB handles mapping, clearance and CTC reporting via the same API. More about CTC models.
Routing to other procurement networks such as Coupa, Tungsten and SAP Ariba via the same integration.
Without a central API you build a separate connection per country and per channel: Peppol here, clearance there, a procurement network elsewhere. That means multiple integrations, contracts and release cycles: exactly what took Conrad Benelux two years with a previous party.
Via the PSB you get the same endpoint, the same authentication and the same webhooks for every network. The platform absorbs mapping, validation and routing per country: from XRechnung in Germany to FatturaPA via SdI. See the full country overview for mandates, formats and deadlines.
Status messages, evidence files, CTC reports and Invoice Response Messages are included in the document price. With most competitors, every technical message counts as a separate transaction, so the real cost comes out three to four times higher. At eConnect you pay only for the document itself, regardless of how many messages are exchanged behind the scenes. That makes multi-country rollouts predictable in cost.
Modern REST API with OAuth2 authentication, idempotency and standardized error handling.
Full interactive documentation with a live request builder. Test directly from the browser.
Push notifications for incoming documents, status changes and validation results. Batch hooks for high volumes.
A full test environment with the same endpoints as production. Including test tenants and sample data.
The PSB is designed for partners and enterprises that want to integrate themselves. Fully documented, tested and with an acceptance environment.
Building a Peppol integration without a safe test environment means every failed mapping or webhook retry can reach real recipients. The eConnect sandbox is a full acceptance environment on the Peppol test network: identical API behavior, the same OAuth2 flow and webhook topics, but documents never leave the test network and never reach production parties.
You get OAuth2 credentials, your own accp- endpoints, a registered test party and the complete PSB API (validate, transform, send, receive, Peppol registration). Smooth, Standard, Solid: test mapping, error handling and status logic without operational risk, then switch to production by changing endpoints and credentials. No second integration.
Request a sandbox account
Getting started guide
When your API becomes the backbone of customer processes, every second of downtime counts double. Without redundant infrastructure and automatic recovery paths you build failover, monitoring and retry logic yourself, while invoices in production cannot wait.
The PSB runs on several redundant Access Points with automatic retries, load balancing and minute-level monitoring. Smooth, Standard, Solid: the same service bus architecture that processes more than 12 million documents a year. Availability and scale · PSB architecture
Building in a separate e-invoicing party per country costs development time and support capacity you would rather put into your own product. Software vendors that integrate the PSB under their own brand (white-label) offer e-invoicing as a built-in feature without building an Access Point themselves. The end customer sees your product name, not eConnect's, while compliance, mandates and standard changes run through the engine.
The smooth engine, your engine too?
A direct Peppol integration means you build or rent a certified Access Point yourself, maintain an SMP, manage PKI certificates, keep up with all BIS and PINT validations and adapt your code with every standard change. The PSB API bundles all of this behind one endpoint. You integrate once, and eConnect takes care of certification, governance, validation rules and standard changes. All Peppol Authorities are already arranged for you, with active participation in OpenPeppol working groups and the experience as co-founder of SimplerInvoicing (which has since grown into the NPa).
Alongside Peppol, the PSB supports the major procurement networks, local clearance platforms (XRechnung in Germany, SdI in Italy, KSeF in Poland, PPF in France, Peppol B2B in Belgium) and bilateral connections via SFTP, HTTPS or SOAP for enterprise connections. All exchanges run via the same API with the same authentication and the same semantic model. See the country overview for mandates and formats per country.
A first working integration is typically ready within a few days for partners who have experience with REST APIs. For a production-ready delivery we usually count on a few weeks, depending on complexity and the number of document types. eConnect offers an acceptance environment with test tenants and sample data, plus personal guidance during the integration track.
Per document sent or received you pay one rate, regardless of how many technical messages are exchanged along the way. Included are: SML/SMP lookup, AS4 transport, validation, status messages, Invoice Response Messages, MLS, evidence files and CTC reports where applicable. No surprises on the invoice. For multi-country rollouts this pricing model is typically three to four times cheaper than competitors that invoice per technical message.
Yes. For software vendors and partners a white-label option is available in which the PSB is delivered under your brand and house style. The end customer sees your product name, not eConnect's. Especially relevant for ERP and accounting packages that want to offer e-invoicing as a built-in feature without building the Peppol infrastructure themselves.
With every standard change (new PINT version, new BIS, PKI rollover, SML migration) eConnect adapts the implementation. For you as integrator, nothing changes in endpoints, payloads or authentication. New Peppol profiles and country-specific validations are added this way, without partners having to adapt their integration. The same principle applies to future networks and mandates.
Schedule a meeting with our API specialists, or dive straight into the documentation.
Schedule a meeting
API documentation
Getting started guide
Ask Cora a question