Home › Guides

How to choose and replace an e-invoicing provider

Give every prospective provider the same entity list, transaction population and required outputs. Ask for country-specific answers with evidence. This makes differences in service scope visible before they become implementation gaps.

The steps below are procurement and migration recommendations. National accreditation, retention and reporting obligations need separate verification for the proposed operation.

Define the service you are buying

List the countries, legal entities, registrations, document types, directions and source applications. Separate invoice exchange, authority reporting, archiving and tax-return services.

State expected monthly and peak volumes. Include inbound documents, corrections, attachments and historical retrieval. Identify the support hours and recovery needs of the business.

Request a precise supported-scenario response. "Global network" is too broad for a requirement that names a document type, country and reporting output.

Check the contracting entity and the current register relevant to the service. Record the status and check date. Ask whether an affiliate or subcontractor provides any regulated part of the route.

OpenPeppol's provider register distinguishes service roles and explains the meaning of the country shown in its listing. Use that record for the stated role, then request evidence of the national scenario separately. OpenPeppol, certified providers

For France, check the current approved-platform route and register. DGFiP describes the role of approved platforms in invoice exchange and reporting. DGFiP, approved-platform information

For the UAE, use the current accreditation framework rather than relying on an old preliminary-approval announcement. MoF announced a replacement framework effective from 1 October 2026. UAE Ministry of Finance, October 2026 accreditation update

Compare operating responsibilities

Ask who validates source data, maps documents, maintains formats, registers identifiers, owns credentials and monitors failures. Identify which responses return automatically to the ERP.

Request the documented behavior for rejection, timeout, duplicate submission, delayed response and provider outage. Ask the operator who will handle each event during an ordinary working day.

Include subcontractors in the responsibility map. Outsourcing a technical component should not leave the customer uncertain about the support contact or accountable service provider.

Require a realistic demonstration

Use the same acceptance pack for every provider. Include a normal invoice, inbound document, credit, invalid identifier and uncertain timeout. Add national reporting and special transaction cases where relevant.

Retain the generated document, acknowledgement, resulting ERP status and reconciliation. Check that the proposed ERP connector supports the demonstrated service. A provider's standalone portal demonstration may leave the ERP integration unproven.

Agree what the evidence establishes. A test endpoint may validate a format without proving production onboarding, current accreditation or every business exception.

Compare total cost using one scenario

Request prices for the same entities, profiles, monthly volumes, peaks, directions, archive duration and support requirements. Include implementation, mappings, onboarding, validation, failed transactions, attachments, storage, retrieval and exit services where charged.

Ask what happens when volume rises or a new mandate is added. Record any minimum commitments, overages and charges for national services outside the base exchange plan.

Keep price and evidence separate in the decision record. A low-cost route that leaves a required reporting process manual can still be a valid choice, but the manual work needs an owner and a cost.

Agree the exit before onboarding

Specify export formats for original documents, responses, status histories, attachments and configuration. Ask how participant identifiers and receiving metadata are migrated. Do not assume that every identifier or registration transfers unchanged.

Agree access to pending transactions and historical records after termination. Record assistance fees, timelines, deletion conditions and contacts. Include legal retention and ongoing dispute requirements in the exit plan.

Use this request form:

Migrate one controlled population

Inventory active identifiers, capabilities, source systems and documents in flight. Agree the old and new providers' responsibilities. Record the intended routing boundary.

Rehearse export and import using a test population. Verify document retrieval and links to external responses. Test the new route's discovery, sending, receiving and required reporting.

At cutover, give every document population one owner. Monitor late responses and reconcile submissions across both services. Avoid sending the same production invoice through both routes merely to compare them.

Keep the old service available for the agreed historical and in-flight scope until reconciliation is accepted. Cancel or change routing only through the providers' supported process and agreed authority procedure.

Accept the new operating arrangement

Require evidence that active routing works, pending transactions are accounted for and historical records remain retrievable. Update support contacts, credentials ownership, monitoring and the obligation register.

Keep the contract scope, accreditation checks, tests, cost comparison and migration approval together. That record will be the starting point when the next country, supplier change or renewal arrives.

Use the Peppol implementation guide for transaction-flow checks and the cutover guide for historical evidence.

Vendor documentation is cited only as an example of the level of evidence to ask for; it is not a recommendation or a ranking. This guide is general information, not tax or legal advice. Checked 2026-10-17.

Related: Glossary – abbreviations and terms used in these guides (SAF-T, Peppol, CTC, EN 16931, IFRS and more).

Page last updated: · Markdown version

Newsletter – monthly digest of mandate and ERP support changes. Subscribe on the home page.