You want to e-invoice from your own accounting or ERP package, but separate portals, manual uploads or double entry cost time and increase the risk of errors. With a software integration everything stays in the workflow your team already knows: send and receive invoices, track status and Peppol registration, without leaving the environment you trust.
View all integration guides
Organisations that run e-invoicing next to their accounting software quickly see where it breaks. Finance works in the ERP, but invoices go through a separate portal or email. Incoming e-invoices have to be imported by hand. Status updates do not return to the package. With growing volumes or multiple administrations that becomes unsustainable.
A good software integration solves that: your team keeps working in Exact Online, AFAS, Unit4, Dynamics 365 Business Central, SAP or whichever package you use. eConnect handles validation, routing via Peppol and status messages in the background. Smooth, Standard, Solid.
After a one-time configuration, eConnect picks up invoices from your accounting software, validates them for format and business data, and sends them via Peppol, or via an automatic fallback if the recipient is not (yet) on the network. Incoming e-invoices are converted to the format your package expects and offered for booking or matching.
Accounts receivable and payable, approval flows and booking proposals stay in your ERP; eConnect delivers the e-invoicing infrastructure behind it. The same platform processes more than 12 million documents per year for 20.000+ organisations.
More than 30 software packages have a step-by-step integration guide, from Exact Online and AFAS to SAP, Dynamics 365 BC and industry-specific solutions. In total, 100+ standard integrations are available via 100+ software partners.
Software vendors and IT teams build their own integration via the PSB REST API: send and receive invoices, manage Peppol registrations, webhooks for status updates. Start with Getting started and the API documentation.
Do you work with an ERP or sector partner? Software vendors connect via the partner model, with a white-label option, sandbox and typically live within a few weeks.
Whether you are an end user who wants to know if your package is supported, or a software vendor who wants to build in e-invoicing: there is a route that fits your situation.
The same PSB that powers standard integrations also processes API and partner integrations. You get the same validation, network coverage in 15+ countries and operational scale, whichever route you choose.
Direct OAuth connection for cloud software. Invoices are read in or booked automatically. For Exact Online, Dynamics 365 Business Central and Unit4 ERPx.
Native API via App Key and Secret. Set up once, then fully automatic. For AFAS, AccountView, 4PS, Accept, KING Software and more.
Submit PDF or XML by email; eConnect processes and routes. For packages without a direct API, such as Payt and Yoobi.
SFTP, HTTPS or SOAP for SAP and other large ERP landscapes. Guided trajectory with a contract.
CLI tool for on-premise software via a local folder. Suitable for packages without an API and for automation.
Not every package connects in the same way. eConnect supports five integration methods, matching the documentation: Autopilot, connection keys, Email Receiver, enterprise integrations and ClientConnector. Which method fits depends on your software and subscription.
The partners below have a full integration guide in our documentation. We also document integrations for Exact Online, Dynamics 365 Business Central, SAP, Unit4, AFAS, Yuki, AccountView, 4PS, Bloxs, AllSolutions and dozens of other packages. See the full overview.
Is your package not listed? Via the REST API, the Email Receiver or the invoice portal you can often start immediately while a custom integration is being worked out.
For most ready-made integrations a Remote Starter session is enough: set up Peppol registration, configure connection keys or Autopilot and test a trial invoice. Organisations such as Gemeente Nijmegen received their first e-invoice within two days of starting.
With a clear first use case you make your first test call via Getting started within a day. Partners with API experience typically go live within four weeks.
Complex landscapes (multiple administrations, SFTP connections or custom transformations) get a dedicated contact and an agreed implementation plan.
The lead time depends on your package, integration method and IT landscape. In practice it looks like this:
Invoices from your software are picked up automatically, validated and delivered via Peppol. The platform checks whether the recipient is registered and chooses the best route.
Incoming e-invoices are converted to your package format and offered for processing, matching or booking.
Status messages (received, approved, rejected, paid) return to your workflow via webhooks or platform notifications.
Registration, migration from another Access Point and multi-country identifiers are handled centrally, without separate integrations per country.
Regardless of the package or integration method, every invoice follows the same core steps. This is what you notice in practice:
Step-by-step instructions per software package: from connection keys to Autopilot configuration.
Compare Autopilot, connection keys, Email Receiver, enterprise integrations and ClientConnector, including subscription requirements.
OpenAPI specification, authentication, webhooks, SDKs and sandbox for software vendors and developers.
Common error messages per package and how to resolve them.
Want the exact steps per package, or to get started technically right away? The documentation covers both routes.
eConnect has 100+ standard integrations via 100+ software partners. More than 30 packages have a full integration guide in the documentation, including Exact Online, Exact Globe, AFAS, Unit4, AccountView, Yuki, Dynamics 365 Business Central, SAP and Oracle. There are also industry-specific integrations for construction (4PS, Admicom), staffing (Mysolution) and housing associations (Tobias AX).
The integrations work via different methods: Autopilot (OAuth), connection keys, Email Receiver, enterprise integrations (SFTP/HTTPS) and ClientConnector. See the full overview per package.
For most standard integrations the configuration is completed within a few days: create the connection, configure the settings in your accounting software and test a trial invoice. eConnect provides guides and support at every step.
For API integrations or complex enterprise landscapes it can take several weeks. In that case you follow a guided trajectory with a dedicated contact. Software partners typically go live within four weeks.
Yes. When sending, eConnect picks up invoices from your accounting software and routes them via Peppol. When receiving, incoming e-invoices are converted to the format your package expects. Relation management, matching and booking proposals are then handled inside your software, as far as the package and the chosen integration support this.
After the one-time configuration you simply work in your own environment; eConnect handles e-invoicing in the background.
Probably yes. Three options: (1) the Email Receiver for packages that can send PDF or XML by email; (2) your own integration via the REST API, SFTP or HTTPS; (3) start via the free invoice portal while a custom integration is being developed.
Software vendors can also connect via the partner model.
Yes. The PSB REST API provides full access: send and receive invoices, have documents processed, manage Peppol registrations, retrieve status messages and set up webhooks. Authentication via OAuth 2.0; documentation with OpenAPI specification, SDKs and a sandbox.
Partners receive their own API credentials; end customers authenticate with username and password. eConnect also offers a white-label option to offer the platform under your own brand.
That depends on your software and subscription. Cloud packages such as Exact Online and Dynamics 365 Business Central typically use Autopilot. Many SME packages work with connection keys. Packages without a direct API connection can use the Email Receiver or ClientConnector.
Per package, the integration guide states which method applies and which subscription you need.
No matching customer stories.
We look together at which integration, method or API route fits your software and volume. No sales pitch, just a concrete answer.
Schedule a meeting
Ask Cora