Build once, reach every e-invoicing network. The PSB REST API automatically routes to Peppol, other procurement networks such as Coupa, Tungsten, SAP Ariba and Tradeshift, SFTP or email, and transforms between formats without requiring separate development per channel.
Schedule a meeting
The Procurement Service Bus is a gateway with automatic route detection. Submit a document and the PSB determines by itself which channel it uses to reach the recipient: Peppol if the recipient is registered, a procurement network if that is the arrangement, or email or SFTP as fallback. For you it remains one endpoint and one contract.
Send and receive via Peppol BIS, PINT and country-specific CIUS variants. eConnect has been a certified Peppol Access Point since 2014 and is an active participant in OpenPeppol working groups.
Direct routing to other procurement networks including Coupa, Tungsten, SAP Ariba and Tradeshift. eConnect maintains the protocols and format transformations.
For clients not yet on a network: SFTP folders, mailfrom hooks and email with PDF and attachments. Incoming mail is converted by IDR into a structured e-invoice.
Status updates and incoming documents via webhooks (push) or REST polling. Combinable: for example webhooks for status messages and REST for the documents themselves.
One PSB connection gives you simultaneous access to the Peppol network, the major procurement networks and direct channels for clients not yet on a network.
- Peppol BIS Billing 3 for cross-border B2B and B2G within Europe
- PINT as the international Peppol variant for markets like Singapore, Malaysia and UAE
- NLCIUS and SI-UBL for the Dutch public sector
- DICO for construction, SETU for staffing, SEEF for energy
- XRechnung (Germany), Factur-X (France), FatturaPA (Italy), Facturae (Spain), KSeF FA(2) (Poland)
- UBL 2.1 and CII as generic base formats
The PSB transforms automatically between formats based on recipient registration. Your clients are unaware of the underlying complexity.
REST with OAuth2, OpenAPI/Swagger documentation and SDKs in PHP and .NET. Sample code, testing and a separate acceptance environment at no cost.
One consistent approach across all countries and networks. No separate connection per channel, no separate logic per country. What works in the Netherlands also works in Poland.
Compliant by default, predictable price, status messages and CTC reporting included in the document price. No hidden costs per message.
Our design principles for partners and integrators: Smooth, Standard, Solid. Not just a working API, but one that is so predictable that a second integration is faster than the first.
The PSB performs an automatic lookup for each outgoing document. For Peppol recipients via SMP discovery (own SMP with caching, not dependent on others' uptime). For procurement networks via your VPD registrations. If no network route is available, the PSB falls back to SFTP or email according to the per-client configuration. You do not need to make a route choice per document.
In API terms: you do one POST to the document endpoint and receive asynchronous status updates. The PSB determines how the document is delivered.
The main endpoints: send sales invoices, receive purchase invoices, send and receive orders, self-billing, validate XML documents without sending, format transformation between e-invoice formats, IDR for PDF conversion and VPD/Purple Pages for party data lookup. Authentication via OAuth2 at identity.econnect.eu/connect/token. Production base URL: psb.econnect.eu. Acceptance: accp-psb.econnect.eu.
Full reference: PSB API documentation and the OpenAPI specs in Swagger.
No problem: the PSB supports email and SFTP as a fallback channel. A new client can start sending today, even if the recipient is not yet on Peppol or a procurement network. On receipt, IDR converts incoming email or PDF into a structured e-invoice. Once the relationship does have a network registration, the PSB switches over automatically.
For structural supplier activation eConnect offers WeConnect as a proven method (90%+ adoption within three months).
The PSB contains a central format library maintained by eConnect. Changes to BIS Billing 3, NLCIUS, DICO, SETU or a national CIUS are applied centrally and automatically available to all partners. The same applies to protocol changes on procurement networks. As a partner you do not need to release anything: the PSB keeps itself current.
For breaking changes we inform partners proactively via partner sessions and release notes.
Schedule a meeting
PSB API documentation