Infinite IT Solutions Blog | EDI | e-Invoicing Compliance

How to Choose an EDI Provider in 2027: 10 Criteria for Companies Facing E-Invoicing Mandates

Written by Admin | Nov 16, 2026, 8:32:10 AM

Choosing an EDI provider used to be a supply-chain decision: which retailers it already connects to, how fast it onboards suppliers, what it charges per document. From 2027 it is also a tax-compliance decision. Germany's issuing obligation starts on 1 January 2027, Poland's KSeF covers every business from the same day, France extends its mandate to SMEs in September 2027, Spain follows in October 2027 and the UAE phases in through 2027. Each of these regimes decides whether your EDIFACT or X12 invoice still counts as a legal invoice, and most of them say it only does if structured EN 16931 data can be extracted from it or sent in parallel. This guide gives CFOs, IT managers and compliance officers ten criteria for selecting an EDI provider that will still be compliant in 2028, a mandate-by-mandate view of what changes, and a short list of questions to put in your RFP.

Why the EDI provider decision changed in 2026–2027

Classic EDI was built on bilateral agreements. You and your trading partner agreed a message standard (GS1 EANCOM, EDIFACT D96A, ANSI X12), a transport (AS2, OFTP2, a VAN) and a mapping, and the invoice that travelled over that channel was accepted as the invoice. Tax authorities were not in the loop.

Continuous transaction controls (CTC) and structured-invoice mandates change that. Under a clearance model such as Poland's KSeF, the invoice only exists legally once the national platform has accepted it and assigned an identifier. Under a decentralised model such as Germany's or Belgium's, the invoice is only valid if it conforms to the EN 16931 semantic model, which EDIFACT on its own does not. Under a platform model such as France's, invoices must travel through an accredited platform that also sends e-reporting data to the tax administration. For a deeper comparison of these models, see our explainer on continuous transaction controls vs periodic e-reporting.

The practical consequence is that an EDI provider now has to do two jobs: keep the operational document flow (orders, despatch advices, invoices, remittance advices) running with your partners, and make sure the invoice leg of that flow satisfies each country's e-invoicing rules. Providers that only do the first job will leave you with a second vendor, a second integration and a second set of mappings to maintain. If you are still unsure whether EDI and e-invoicing are the same obligation, start with EDI invoicing vs e-invoicing: do you need both.

What the 2026–2028 mandates mean for your EDI setup

The table below summarises the mandates most likely to affect EDI-heavy companies in the EU and GCC, and what each one requires from the EDI channel. Dates were verified in November 2026; our Compliance Tracker carries the live status, and the European Commission's ViDA page is the primary source for the EU-level timeline.

CountryKey datesWhat it means for EDI invoices
GermanyReceiving mandatory since 1 Jan 2025. Issuing mandatory from 1 Jan 2027 for businesses with prior-year turnover above EUR 800,000, and from 1 Jan 2028 for all others.Legacy EDI formats that are not EN 16931-compliant may be used until 31 Dec 2027 only if both parties agree. From 1 Jan 2028 the EDI process must extract data that conforms to EN 16931 (e.g., XRechnung, ZUGFeRD, Peppol BIS).
BelgiumDomestic B2B structured e-invoicing mandatory since 1 Jan 2026. Near-real-time e-reporting bill submitted to Parliament on 27 Oct 2026, planned entry into force 1 Jan 2028.Peppol BIS over the Peppol network is the default; another EN 16931-compliant format is allowed only by mutual agreement. From 2028 both supplier and customer will report transaction data via Peppol within a deadline capped at five calendar days.
FranceSince 1 Sep 2026 all French-established businesses must receive e-invoices; large and mid-sized companies must also issue and e-report. SMEs and micro-enterprises issue from 1 Sep 2027.Invoices must be exchanged in Factur-X, UBL 2.1 or CII through an accredited platform (plateforme agréée). An EDI invoice has to be converted and routed through such a platform; the EDI channel alone does not satisfy the mandate.
PolandKSeF mandatory from 1 Feb 2026 for taxpayers with 2024 sales above PLN 200 million, from 1 Apr 2026 for other taxpayers, and from 1 Jan 2027 for everyone (the PLN 10,000 monthly exclusion ends).The structured invoice must be submitted to KSeF and receives a KSeF number; the EDI invoice becomes a copy or a commercial message. Your provider must integrate with the KSeF API and return the KSeF identifier to the ERP and to partners.
SpainB2B e-invoicing from 6 Oct 2027 for businesses with turnover above EUR 8 million, and from 6 Oct 2028 for the rest.EDIFACT is an accepted syntax alongside UBL, CII and Facturae, but invoices must follow EN 16931 and private platforms must send a UBL copy to the public platform (SPFE). Status reporting (acceptance, rejection, payment) is mandatory.
UAEPilot from 1 Jul 2026; mandatory from 1 Jan 2027 for revenue of AED 50 million or more, 1 Jul 2027 for other businesses and 1 Oct 2027 for government entities.Invoices and credit notes must be exchanged through an Accredited Service Provider (ASP) and reported to the Federal Tax Authority; electronic documents must be stored within the UAE.
EU (ViDA)Adopted 11 Mar 2025. Member states may impose domestic e-invoicing without EU derogation since April 2025. Intra-EU B2B e-invoicing and digital reporting from 1 Jul 2030; existing national systems to be harmonised by 1 Jan 2035.Cross-border EU invoices will have to comply with EN 16931 and be reported transaction by transaction, so any EDI channel used for intra-EU trade will need an EN 16931 output by 2030 at the latest.

For the format side of this question, including which ZUGFeRD and XRechnung profiles count as e-invoices in Germany, read XRechnung vs ZUGFeRD vs Factur-X.

Managed EDI service, EDI software or VAN: which model are you buying?

Before comparing vendors, decide which operating model you want, because the ten criteria below weigh differently for each.

Managed EDI service (fully outsourced). The provider runs the platform, builds and maintains mappings, onboards partners and monitors traffic. You integrate once with your ERP and consume the service. This model carries the mandate risk best, because compliance updates are the provider's job, and it is the model most mid-sized and large companies in Europe choose when they trade in several countries.

EDI software (in-house). You license a translator and integration platform and run it yourself. It offers the most control and can be cheaper at very high volumes, but every new mandate, schema version or partner change lands on your team. The total cost over five years is usually dominated by people, not licences.

Value-added network (VAN) or messaging only. A VAN moves EDI messages between mailboxes and interconnects with other networks, but it does not translate, validate against tax rules or talk to KSeF, an accredited French platform or a UAE ASP. A VAN can be part of a solution, not the whole of it.

Most buyers in 2027 land on a managed service with a Peppol-certified access point and national CTC connectors, because that is the only model where one contract covers both the partner flow and the tax flow.

10 criteria for choosing an EDI provider in 2027

1. E-invoicing compliance is part of the service, not a partner referral

Ask the provider to show, country by country, how an invoice leaves your ERP and reaches both the trading partner and the tax authority. Look for native connectors to KSeF, an accredited platform status in France, ASP accreditation in the UAE, ZATCA integration for Saudi Arabia and a certified Peppol access point for Belgium, Germany and the wider network. If the answer for any of your countries is "we work with a partner for that", you are buying two vendors with one invoice.

2. EN 16931 mapping and validation from your EDI formats

The core technical requirement across Germany, Belgium, France, Spain and ViDA is that structured EN 16931 data can be produced from, or alongside, the EDI message. Ask for a worked example: an EANCOM INVOIC mapped to XRechnung or Peppol BIS Billing 3.0, with the validation report (Schematron business rules) attached. A provider that cannot show this today will struggle to deliver it before Germany's 1 January 2028 deadline for EDI processes. Our guide to EN 16931 explains what the semantic model requires.

3. Certifications and national accreditations

Peppol access point certification from OpenPeppol is the baseline for Europe. Beyond it, check the registrations that matter in your footprint: accredited platform (PA) in France, Accredited Service Provider in the UAE, registered delivery service provider in Slovakia, and solution-provider status with the relevant GS1 member organisations. These registrations are public, so verify them on the authority's list rather than on the vendor's website. We covered the Peppol side in detail in how to choose a Peppol access point provider.

4. Standards and protocol coverage

Your partners will not all move at the same pace. A provider should support EDIFACT (including GS1 EANCOM subsets), ANSI X12 for North American partners, XML and JSON over API, and the transports those partners use: AS2, AS4 (the Peppol transport), OFTP2 for automotive, SFTP and VAN interconnects. Ask specifically about AS4, because it is the protocol behind Peppol and several national platforms, and some older EDI stacks still lack it.

5. ERP integration depth

The integration with SAP (ECC and S/4HANA), Microsoft Dynamics 365, Oracle or your industry ERP decides how much manual work remains. Look for pre-built adapters, support for IDoc, OData or REST interfaces, and the ability to write back status information such as KSeF numbers, Peppol delivery receipts, French invoice lifecycle statuses and Spanish acceptance or payment statuses. Writing status back into the ERP is what lets finance teams see rejections before they become disputes.

6. Partner onboarding and community management

EDI value comes from the number of partners actually connected. Ask how long onboarding takes for a new retailer or supplier, whether the provider already has connections to your largest customers, and what options exist for small partners who have no EDI capability (web EDI portal, PDF-to-EDI conversion, Peppol delivery). Request onboarding metrics from a reference customer of similar size rather than averages.

7. Document scope beyond the invoice

Mandates focus on invoices, but operations depend on orders, order responses, despatch advices, receiving advices and inventory reports. A provider that handles only the invoice leg leaves the rest of your supply-chain messaging elsewhere. Despatch advices in particular are a frequent source of integration problems; our article on advance shipment notifications for suppliers explains why.

8. Security, archiving and data residency

Ask for ISO 27001 certification, the hosting location of your data and the archiving service. Retention periods differ: Germany now requires invoices to be kept for 8 years, Belgium for 7 years and France for 10 years, while the UAE requires electronic invoicing documents to be stored within the country. A provider should archive both the legal invoice (the XML that was cleared or delivered) and the EDI message, with an audit trail linking the two and an export route if you leave.

9. Monitoring, status messages, SLAs and support

Under clearance models, an invoice that fails validation is not an invoice. You need a dashboard that shows rejections and their reason codes, alerts that reach the right team, and support hours that match the time zones of your partners and tax authorities. Put the SLA in the contract: availability, time to acknowledge an incident, and time to deploy a mandatory schema change (for example a new KSeF schema version) before its legal start date.

10. Pricing model, total cost and exit terms

Compare the full five-year cost: setup, mapping development, per-document or per-partner fees, mandatory compliance updates, archiving and support. Clarify who owns the mappings and whether you can export them, and how data is returned at the end of the contract. A low per-document price with chargeable compliance updates can cost more than a flat managed-service fee once three or four mandates land in the same year.

Questions to put in your EDI RFP

Use these to turn the criteria into evidence. Which of our countries are covered natively, and with which accreditation in each? Show an EANCOM INVOIC converted to Peppol BIS Billing 3.0 with its validation report. How do you return KSeF numbers and Peppol delivery statuses to our ERP? What is the median onboarding time for a new retail partner, and how many of our top 20 partners are already connected? Which transports do you support, including AS4 and OFTP2? Where is data hosted and archived, and for how long per country? What is your SLA for deploying a mandatory schema change? Who owns the mappings, and what does the exit process look like? What is the five-year cost at our document volumes, including compliance updates?

FAQ

What does an EDI provider do?

An EDI provider translates business documents such as orders, despatch advices and invoices between your ERP format and the standard your trading partners use (EDIFACT, X12, XML), transmits them over agreed protocols such as AS2, AS4 or OFTP2, and monitors delivery. Managed EDI providers also build and maintain the mappings, onboard partners and, increasingly, connect to national e-invoicing platforms.

Can EDI invoices still be used under the German e-invoicing mandate?

Yes, with conditions. Until 31 December 2027, EDI formats that are not EN 16931-compliant may still be used if both parties agree. From 1 January 2028, an EDI process is acceptable only if data conforming to EN 16931 can be extracted from it, so most companies add an XRechnung, ZUGFeRD or Peppol BIS output to their EDI flow.

What is the difference between an EDI provider and a Peppol access point?

A Peppol access point is a certified gateway to the Peppol network that exchanges standardised documents such as Peppol BIS Billing 3.0 invoices with any other access point. An EDI provider covers a wider set of standards, transports and bilateral partner connections. Many EDI providers operate their own certified access point, which lets one service handle both partner EDI and Peppol-based e-invoicing.

How much does an EDI provider cost?

Pricing usually combines a setup and mapping fee, a recurring platform or per-partner fee, and per-document charges. Compliance updates, archiving and support may be bundled or charged separately. Compare the total cost over five years at your document volumes, including the cost of mandatory e-invoicing changes, rather than the per-document rate alone.

Conclusion: choose for 2028, not for today

An EDI provider selected in 2026 or 2027 will be in place when Germany's EDI transition ends, when Belgium starts e-reporting and when ViDA's intra-EU rules arrive in 2030. The right choice is a provider that treats e-invoicing compliance as part of the EDI service, proves EN 16931 extraction from your actual message formats, holds the accreditations your footprint needs, and writes compliance updates into the SLA. For the full regulatory picture, see The Complete Guide to Global E-Invoicing Compliance, and for details of our managed EDI and e-invoicing service, visit our Electronic Data Interchange (EDI) page.

If you are shortlisting EDI providers for 2027, contact Infinite IT Solutions for a country-by-country assessment of your current EDI flows against the mandates in this article.