EDI to PEPPOL Migration 2026: E-Invoicing Compliance Guide for Manufacturers

“We’ve been exchanging EDI with our customers for 20 years. E-invoicing? Already done.”

ERP consultants specialising in document automation hear this every week from well-equipped manufacturers: food producers, automotive sub-contractors, logistics providers. The statement is built on a real, understandable — and potentially very costly — misconception.

EDI (Electronic Data Interchange) and regulatory e-invoicing are two distinct things. One has been managing your operational flows with trading partners for decades. The other is a tax compliance obligation, and your current EDI system almost certainly does not satisfy it on its own.

This guide is written for CIOs and CFOs at manufacturing companies that already use EDI and must now plan their migration to a compliant e-invoicing flow.

Understanding Classic EDI: What It Does — and What It Doesn’t

EDIFACT/GS1 Messages: ORDERS, DESADV, INVOIC

EDIFACT EDI is a structured messaging standard developed by the United Nations from the 1980s onwards. In retail and industrial sectors, it relies on normalised messages: ORDERS (purchase order), ORDRSP (order acknowledgement), DESADV (despatch advice), INVOIC (invoice), REMADV (remittance advice).

These messages travel via specialist EDI operators (Generix Group, Edicom, OpenText Trading Grid, formerly GXS) that maintain VAN (Value Added Networks) or direct AS2 connections between trading partners.

The system works well for what it was designed to do: synchronise logistics and commercial flows at high speed between partners who have signed bilateral interoperability agreements.

What EDI Handles Well

From an operational standpoint, EDI remains superior to most alternatives for high-volume B2B exchange. It handles consignment references, transport identifiers, package IDs, supply chain traceability data, and quantity tolerance rules between goods received and purchase orders. For manufacturers shipping 500 pallets a day to 40 retail chains, this level of precision is not incidental — it underpins all supplier/customer reconciliations.

What EDI Cannot Do: The Legal Invoice Format

The fundamental gap in EDIFACT INVOIC is exactly what will create problems for you.

An EDIFACT INVOIC message is not an electronic invoice under EU Directive 2014/55/EU, nor under the equivalent obligations now being rolled out across Europe. To be accepted as a legally valid electronic invoice, a document must:

Comply with the European semantic standard EN 16931 (which defines mandatory fields, business rules, and normalised vocabulary)
Transit via an Accredited Platform (AP) or equivalent national gateway
Enable e-reporting to the tax authority (transmission of transaction data to the administration)

A standard EDIFACT INVOIC satisfies none of these three requirements. Certain specific versions (EDIFACT D16B, officially mapped to EN 16931 by CEN) can be accepted by an Accredited Platform, provided the platform performs the necessary conversion before transmission. But your current EDI operator must be qualified to do so.

PEPPOL and Regulatory E-Invoicing: What Changes

PEPPOL BIS Billing 3.0: The European Interoperability Standard

PEPPOL (Pan-European Public Procurement On-Line) is a network infrastructure enabling the exchange of structured electronic documents between European companies. PEPPOL BIS Billing 3.0 is the technical profile for B2B electronic invoicing on this network: it implements EN 16931 in UBL 2.1.

In practice, PEPPOL works as a routing network: each company connects via a certified PEPPOL Access Point (their operator or accredited platform), which can then exchange with any other PEPPOL Access Point across 40+ countries. No more bilateral agreements with every individual partner — if both parties are on the PEPPOL network, they can exchange.

PEPPOL is now one of the interoperability networks that Accredited Platforms can use to exchange invoices with each other, both domestically and across Europe.

The Regulatory Framework: Accredited Platforms, Not a Direct PEPPOL Obligation

Most EU member states are adopting a “Y-model” approach: companies route invoices through private Accredited Platforms (APs) or national public portals. APs communicate with each other — often via the PEPPOL network.

An important point to clarify: public portals generally do not handle direct invoice exchange between businesses. Their role is centred on e-reporting data transmission to the tax authority and on serving companies without an AP. For significant B2B volumes, a private AP is effectively mandatory.

The Legal Gap: INVOIC Is Not a Legal Invoice

To state it plainly: your EDIFACT INVOIC message, however perfectly structured, is not a legally valid electronic invoice format from the mandatory implementation date in your jurisdiction. It must be converted (by your AP operator) into Factur-X, UBL, or CII format to be legally transmissible and archivable.

This conversion is not automatic. It requires a qualified operator, a mapping configuration, and compliance testing with your partners.

The 4 EDI + E-Invoicing Coexistence Scenarios

Scenario 1: My ERP Emits Factur-X/UBL via an AP, and I Keep EDI for Logistics Flows

This is the target scenario for most manufacturers with a modern ERP (SAP S/4HANA, Sage X3, Sage 100, Dynamics 365, Access Financials). You configure your ERP to emit invoices in Factur-X or UBL, route them via a certified AP, and keep your existing EDI flows (ORDERS, DESADV, REMADV) unchanged.

This scenario assumes your ERP has a native connector to an AP, or that an e-invoicing module is available. Verify this with your ERP vendor first.

Scenario 2: My EDI Operator Is Also an Accredited Platform

Generix Group, OpenText, and other established EDI operators have obtained or applied for AP qualification. Generix Group, for example, has been a certified PEPPOL Access Point since 2018 and is positioned as an AP for e-invoicing compliance.

In this scenario, you may be able to centralise your EDI flows and e-invoicing through the same operator. Advantage: a single contractual relationship and unified visibility. Risk: dependency on a single vendor for critical flows.

Scenario 3: I Am a Sub-Contractor to a Large Retail or Automotive Group

If your main customer imposes a specific EDI standard (GS1, GALIA, VDA, EDIFACT), they too will need to adapt for their invoice flows. Contact your customer directly about their roadmap: some large buyers will issue instructions to suppliers on new invoicing modalities.

Do not assume your customer has resolved the problem for you. Verify that your current INVOIC transmission channel will be replaced or complemented by a Factur-X/UBL flow via AP before the applicable deadline.

Scenario 4: I Have No Legacy EDI and Am Starting from Scratch

If you have until now invoiced by email PDF and have no EDI at all, your situation is different. You do not need to manage a migration — just an initial setup. The goal is to choose an AP compatible with your ERP, configure Factur-X or UBL emission, and activate e-reporting. Technically simpler, but you still need to act before the deadline that applies to your company size.

EDI to PEPPOL Migration Roadmap: 5 Steps

Step 1: Map Your Current EDI Flows

Start with an inventory: which EDI messages do you send and receive (ORDERS, INVOIC, DESADV…)? With how many partners? Which EDI operator (VAN) do you use? What are your monthly volumes?

The goal is to precisely identify the “invoice” flows (INVOIC) that must be migrated as a priority, as opposed to logistics flows (ORDERS, DESADV) that can remain on classic EDI after the reform.

Step 2: Identify Which INVOIC Flows to Migrate

Not all your INVOIC messages are equivalent. Some concern domestic B2B relationships subject to VAT — those are the ones the mandate targets. Others concern intercompany flows, non-EU exports, or foreign counterparties: different rules apply.

With your EDI operator and CFO, list the commercial relationships affected by the obligation deadline applicable to your company size (large enterprises typically first, then SMEs the following year).

Step 3: Choose Between Your ERP as Emitter or an External PA Operator

Two architectures are possible:

ERP-centric architecture: your ERP generates Factur-X or UBL directly and transmits it via API to an AP. This gives better control over data quality and accounting integration. Relevant if your ERP is up to date and has a certified module.

AP-centric architecture: your EDI/AP operator receives your standard INVOIC and converts it to legal format before transmission. This minimises changes on the ERP side, but creates a dependency on the quality of mapping performed by the operator.

In both cases, verify that your AP can handle e-reporting to the tax authority — it is a joint obligation alongside e-invoicing.

Step 4: Test Factur-X/UBL Schemas with Pilot Partners

Do not go live without real-world testing. Identify 2 to 4 trading partners (clients or suppliers) already equipped with an AP and propose a 6–8 week pilot. Verify:

Schematron validity of emitted files (EN 16931)
Correct reception and integration in their ERP
Correct e-reporting data transmission to the tax authority
Archiving with probative value (legal retention period: at least 10 years)

A failed test in a pilot is a manageable problem. A failed test in production on 5,000 invoices/month is a crisis.

Step 5: Progressively Decommission the Classic INVOIC EDI Channel

Once the Factur-X/UBL flow is live and stable with your key partners, plan a gradual shutdown of the EDIFACT INVOIC channel. Keep your ORDERS, ORDRSP, and DESADV flows on EDI — they are not covered by the e-invoicing mandate and remain superior for logistics flows.

Temporary coexistence (EDI + Factur-X) is unavoidable during the transition period, particularly if some of your partners are not yet ready. Anticipate this duality in your organisation.

Market Operators and Tools

Legacy EDI Operators with AP Extension

Generix Group: a French EDI operator with deep roots in retail supply chains, certified AP and PEPPOL Access Point since 2018. Can route EDI INVOIC flows to Factur-X on the supplier side. Positioned for mid-market and enterprise.

OpenText Trading Grid: a global solution for large multinationals, handling EDI + e-invoicing + country-by-country regulatory compliance. Relevant if you manage subsidiaries across multiple European countries.

Quadient (formerly Neopost, integrating Vialink): an AP operator with strong document dematerialisation expertise and an established EDI history.

ERPs with Native AP Connector

The main ERP vendors have developed certified connectors or modules for e-invoicing compliance:

SAP S/4HANA: DRC (Document and Reporting Compliance) module with certified AP connectors
Sage X3 and Sage 100: e-invoicing modules available (verify version requirements)
Odoo: community and official modules for e-invoicing compliance
Microsoft Dynamics 365: e-invoicing integration via Business Central and Finance
Access Financials / Access Group: growing compliance module ecosystem for UK and EU markets

Check with your ERP integrator for minimum version requirements and module cost.

Certified Accredited Platforms

The list of certified Accredited Platforms is published and updated by each country’s tax authority. At the time of writing, several dozen operators have obtained or are in the process of obtaining AP certification. Consult this list before selecting your operator — a non-certified AP will not allow you to satisfy the legal obligation.

Key Risks to Watch

Do not confuse EDI archiving with legally probative archiving. Your current EDI invoices may be archived by your operator, but this does not satisfy the legal obligation for fiscal invoice archiving (10+ years, with probative value). Your AP must offer a compliant archiving service.

Intercompany flows are also in scope. If you issue invoices between subsidiaries that are subject to VAT, these flows fall within the mandate’s scope. This is not limited to external customer invoices.

Plan for team training. The EDI-to-AP migration does not only concern the IT department. Sales administration and accounts payable teams must understand the new processes: what is an invoice acknowledgement from the AP? How is a rejection handled? Who manages e-reporting disputes?

ViDA in Europe by 2030. The EU ViDA (VAT in the Digital Age) directive sets out Digital Reporting Requirements at EU scale by 2030. PEPPOL is a leading candidate standard. If you have subsidiaries in Belgium, the Netherlands, Germany, or the Nordic countries (already advanced on PEPPOL B2G), your migration to PEPPOL BIS Billing 3.0 is a durable investment well beyond any single national reform.

Is Your EDI Compatible with Mandatory E-Invoicing? A 2026 Migration Guide

Understanding Classic EDI: What It Does — and What It Doesn’t