eConnect combines sending, receiving, processing and posting in one platform. Where other providers focus on one part of the invoicing process, eConnect offers the full chain. You invoice via Peppol, receive invoices in any format, process them automatically via the Intelligent Document Recogniser (IDR) and post them to your financial software. In addition, eConnect provides access to multiple procurement networks from a single integration, integrations with more than 100 software packages, and support for more than 20 XML standards. ViDA compliance and status messages are included in the document price, with no hidden per-message costs.

eConnect serves organisations of every size. Freelancers and small businesses start for free via the invoice portal. Medium-sized organisations benefit from software integrations and automatic processing. Enterprise organisations use the Procurement Service Bus (PSB) for high volumes, multichannel invoicing and SLA guarantees. In addition, eConnect offers sector-specific solutions for construction (DICO), staffing (SETU), housing associations, government and energy. Software vendors can integrate eConnect as a white-label solution via the REST API.

The fastest route is via the free invoice portal. You create an online account, verify your organisation via iDEAL (or Wero) and can send your first e-invoice within fifteen minutes. Want to send invoices from your own accounting software? For most packages, the integration is operational within a day. For enterprise implementations via the API, the lead time depends on your system landscape, but most projects are completed within a few weeks.

Yes, eConnect has integrations with more than 100 financial software packages, including Exact Online, AFAS, Unit4, Twinfield, SnelStart, AccountView and Dynamics 365 Business Central. The integration is set up once and then works automatically in both directions: invoices you create in your software go via Peppol, and incoming e-invoices appear automatically in your software. Is your package not listed? Then a direct integration via the REST API is possible, or you can use the free invoice portal in the meantime.

In more and more European countries, e-invoicing is becoming mandatory. Belgium introduced a B2B obligation from 1 January 2026 via Peppol. Germany is making e-invoicing mandatory in phases from 2027. France starts in September 2026 for large companies. In the Netherlands, an obligation is expected in line with the European ViDA directive. This directive mandates e-invoicing for all cross-border B2B transactions in the EU from 1 July 2030. Organisations that start now are prepared for these developments and immediately benefit from faster payment, lower costs and fewer errors.

Small organisations often start for free via the invoice portal for outgoing Peppol invoices, while medium-sized teams move up to Basic or Professional for receiving, workflows, email reception and integrations with financial software. Enterprise organisations and software vendors choose the PSB route with full REST API, multichannel networks and white-label where commercially needed.

The right tier depends on volume, the number of entities and whether you only send or also want to automate incoming PDF/XML. Use the product cards on this page as a starting point and bring in a specialist when in doubt. Deep dive on the product page E-invoicing.

Yes: the core advantage is precisely that sending, receiving, converting and routing come together in one platform, including multichannel to Peppol and other networks from the same integration where you license that. As a result, finance does not need a separate portal per network and IT can monitor one chain via the same webhooks and correlation tokens.

In practice, you choose packages and modules (for example email reception with administration detection, IDR for PDF, e-ordering) based on your backlog, and switch on more later. See the cards under Processing invoices and Integration. More on Multichannel.

The basic agreement usually covers one entity; additional KVK-separated organisations are included according to the price list as additional entities, relevant for holdings, municipal cooperations and franchise constructions. Technically, organisations within an environment are separated with roles and memberships, so users only access their own documents.

Plan this in advance with sales, because network registrations (Peppol/SMP) per entity have their own impact on onboarding and lead time. Details are in the commercial price structure; start at Pricing.

In addition to Peppol BIS Billing and the order chain (Order Only and Order Advanced), the platform supports industry-specific flows such as SETU timecards, DICO-related exchange and multichannel routing to networks such as Coupa, Tungsten and Ariba, exactly depending on your package and contract. eConnect publishes capabilities per document family via its own SMP implementation, so it is clear what a party can receive.

For conversion and validation there are separate APIs available (Validate and Transform) to test formats before sending. Technical depth via the API documentation.

Enterprise implementations often follow two phases: first quick production with portal/email and basic Peppol configuration (often a few weeks), then deeper ERP/API integration with OAuth2, webhooks and transformations (often again a few weeks to months, depending on the ERP and test coverage). Smaller integrations with standard software are usually live within days to a few weeks.

Each phase has fixed deliverables, from working delivery to monitoring and acceptance criteria. Want a government scenario with a pilot, then you use a more elaborate step plan with explicit acceptance tests. Background on E-invoicing with eConnect.

Without an SLA subscription (Cloud) you have no contractual response time; with Bronze, Silver or Gold, fixed response times apply for priorities P1 to P4, measured over at least 95% of reports. Telephone support requires an SLA plus pincode; otherwise you work via email or the web form in the support portal.

Escalation runs from Customer Support to Techsupport and, if needed, Development, especially for integration and configuration questions where code context is needed. More on Contact and support routes.

Multichannel means that one integration can reach multiple eDelivery networks, not just Peppol, with automatic routing and format transformation where needed. As a result, you do not need to build a separate connector per major procurement platform if your contract and package support it, and your chain remains observable from a single monitoring dashboard.

It reduces management effort for IT and makes CFO budgeting easier because you receive status messages and evidence files from the same flow. Start at the product card Multichannel.