List of Approved & Pre-Approved e-Invoicing Providers in France (PA/PDP 2026)

From 1 September 2026, every business in France must be able to receive e-invoices, while issuing becomes mandatory by company size. Domestic B2B e-invoices and required e-reporting must pass through the approved platforms, and unapproved platforms cannot act as the legal transmission route.

Key takeaways

• A PA must support Factur-X, UBL, and CII, and handle cross-platform interoperability for end-to-end delivery.
• Use the official register to confirm the provider’s contracting legal entity and exact status (approved vs candidate), especially close to go-live.
• Prioritise providers that prove lifecycle handling, audit logs, and actionable rejection reasons to reduce failures and payment delays.
• Readiness work is mostly data + process: scenario mapping, master-data clean-up, ERP field mapping, exception ownership, and interoperability testing.

What an Approved Platform (PA) Is in France?

An Approved Platform (PA) or earlier known as PDP (platform dematerialisation platform), is an e-invoicing service provider registered by the French tax administration to handle France’s mandatory e-invoicing and e-reporting flows.  A PA is the compliant “execution layer” that sends and receives structured e-invoices, extracts required data, and transmits mandated datasets to the public infrastructure for the tax administration. 

• France’s administration has explicitly positioned these approved platforms as the indispensable intermediary for invoice exchange between businesses and for transmitting data to the administration.
• PA status confirms the platform has met regulatory requirements and passed technical and interoperability expectations set for the reform.  If a solution provider doesn’t have PA status, it can't legally be used as the intermediary transmission channel

France’s E-Invoicing Architecture and Approved Platform (PA)

France’s model is built around an ecosystem of approved private platforms connected to public components that support routing and the centralisation of required data. Your operational reality is simple: businesses connect to a PA (directly or via an intermediary solution), and the PA handles compliant exchange and required transmissions. 

Core Components of the French Model

• Businesses (issuers and recipients): Companies that must issue and/or receive e-invoices and, where applicable, comply with e-reporting. 
• Approved Platforms (PA): Private platforms registered to exchange e-invoices and transmit required invoice, transaction, and payment data. 
• Public directory and data layer (PPF): The public component that includes the directory used for routing and for associating businesses with their chosen PA and invoicing addresses. 
• Interoperability across platforms: The ecosystem requires PAs to interoperate, enabling invoices to move from one company’s PA to another’s while keeping lifecycle and data expectations consistent. 

France’s approach is often explained as a “Y” shaped flow:

• One branch handles invoice exchange between businesses via approved platforms.
• Another branch ensures required data reaches the administration, via the public layer and the directory-driven routing model.

The key point: a PA sits at the junction of these flows, ensuring both compliant B2B exchange and the mandated data transmissions happen in the required way. 

Pre-Approved vs Approved vs Dematerialisation Operator

There are different names for different e-invoicing solution providers based on legal capability, delivery risk, and which party bears interoperability and transmission obligations.

Portals That People Confuse With “Alternatives”

People confuse B2B reform flows with other e-invoicing contexts such as B2G portals (for example, solutions historically associated with Chorus Pro). That is a different operational context and does not remove the need to align with the e-invoicing mandate for domestic B2B e-invoicing obligations.

Approved and Pre-Approved E-Invoicing Platforms in France (Official List)

ClearTax (DEFMACRO) is a pre-approved candidate platform and supports businesses preparing for France’s 2026 rollout, including platform selection guidance, interoperability-led implementation, and readiness activities such as format mapping, master data clean-up, and lifecycle workflow setup.

Approved Platforms

List of operators meeting all conditions, including interoperability tests:

• @GP
• @iPaidThat
• @N2F PDP
• ABBY
• ACCENTURE
• ADEMICO SOFTWARE
• AGENA 3000
• AGICAP
• ARTEVA
• AVALARA
• AXONAUT
• AZOPIO
• B2BRouter
• BASWARE
• BC SOLUTIONS
• BILLIT
• SECURITY
• CEGEDIM
• CEGID
• CHAINTRUST
• COMARCH SA
• DARVA
• DEXT
• DIGIPHARMACY
• DIGITAL TECHNOLOGIES
• DOCOON
• DOCOON IMMO / FREEDZ
• DOCPROCESS
• DOCUWARE
• Dougs Free Billing
• DOXALLIA
• ECOSIO
• EDICOM Group
• EDICOM France
• EDICS France
• EDT
• EEZI
• powered by VAT IT
•  Effinum by SPEE
• ENERJ
• ENTROPICS
• ESALINK
• ESI
• ESKER
• EURO INFORMATION
• FACNOTE PDP
• FIDUCIAL CLOUD
• FLOWIE
• FULLL
• GENERIX Group
• GESTAV
• SIGMA GROUP
• ICD International
• iEDI ApS
• INDICOM
• INDY
• INFOLOGIC
• INVOPOP
• IOPOLE
• ITESOFT
• jefacture.com
• KLEKOON
• KOLECTO PDP
• LE VILLAGE CONNECTE
• LOGILEC
• MACOMPTA.FR
• MAROSA
• MEDIUS
• MyKinexo PDP
• ONE UP
• OPEN BEE
• OPENTEXT
• PAGERO
• PARAGON
• PENNYLANE
• PITNEY BOWES
• QONTO
• QWEEBY
• SAGE
• SAP
• SCRIBEE
• SEEBURGER
• SELLSY
• SEPTEO
• SEQINO
• SERENSIA by Quadient
• SERES
• SOVOS
• SPENDESK
• SPS COMMERCE
• SRCI
• SUPER PDP
• SYMTRAX
• TENOR
• TESISQUARE SPA
• TESSI Technologies
• TIIME PDP
• TRADESHIFT BABELWAY
• Transalis Limited
• TRESO2
• TUNGSTEN AUTOMATION FRANCE
• TX2 Concept
• VENTYA
• VERYSWING
• VOXEL, an Amadeus company
• WEPROC
• WiseTech GLOBAL
• YOOZ PDP

Pre Approved Platform

List of operators who have submitted a complete and compliant application and are awaiting their final registration, which is conditional upon passing interoperability tests:

• ClearTax
• Aruba SpA
• AXWAY SOFTWARE
• B4VALUE.NET
• CBS Corporate Business Solutions
• CEGI ALFA
• Ecosio InterCom
• a Vertex Company
• EdiEyes Vision Care
• EY EXPERTISE & TRANSACTIONS
• Fonoa Technologies Limited
• GURUSOFT
• IGA INSURANCE
• INFOCERT SPA
• KOLECTO PA
• LUCCA
• MY UNISOFT
• MySupply Aps
• NEOTIMO
• NTT DATA Business Solutions
• NUMERIA
• ODOO
• OpusCapita Solutions -
• a GEP Company
• PAYFLOWS
• SNI
• SOLO
• STORECOVE
• TAXERA
• YourInvoices
• WAKASTELLAR
• XELYA

French tax administration maintains the official list of approved and pre-approved platforms. 

Businesses can use it to verify a provider’s legal entity name, current status (approved vs in-process), and whether it is eligible to support mandated e-invoicing and e-reporting flows in France. 

The Role of a PA (Approved Platform)

In simple terms, Approved Platform or PDP is the middleware that makes your invoicing compliant end-to-end under the reform, not just at the moment of sending.

• Issuance, transmission, and reception: A PA enables suppliers to issue electronic invoices and ensures those nvoices are transmitted to the customer’s receiving route, while also supporting inbound reception for purchase invoices. 
• Format handling and interoperability: It must support the mandated structured formats and exchange invoices across the ecosystem, including with other approved platforms, without breaking data consistency. 
• Invoice data extraction for the administration: Beyond exchanging the invoice, a PA extracts the required invoice data elements and transmits them to the public side of the system for tax purposes. 
• E-reporting collection and transmission: For transactions outside e-invoicing scope that still require reporting (for example certain B2C and cross-border flows), the PA collects the transaction data and payment data and transmits it through the mandated channel. 
• Lifecycle status management: A PA supports the operational lifecycle of invoices (such as processing and status information) so issuers and recipients can track delivery and handle exceptions in a standardised way. 
• Security and traceability controls: It is expected to ensure integrity, secure transmission, and traceable processing, so businesses can demonstrate compliant handling of invoice flows and reporting data. 

PPF and its Role

Portail Public de Facturation (PPF) is the public component of France’s e-invoicing reform. Its role has been refocused mainly on two functions: 

• Runs the central directory (annuaire): it lists in-scope entities and indicates the platform used for receiving invoices and the e-invoicing addresses needed for reliable routing. 
• Acts as a data concentrator for DGFiP: approved platforms send required invoice, transaction, and payment data to the PPF (concentrator), which then supports transmission/processing for the administration. 

How to Choose the Best PA (Approved Platform) for France

Selection should be focused on compliance assurance, low rejection rates, resilient operations, and clean evidence trails. 

Selection Criteria for Compliance Assurance

Use these criteria for shortlisting process -these are legally required for compliance

• Approval and status clarity: Confirm listing on the official approved platform portal and document the platform’s current status.
• Interoperability evidence: Request proof of successful multi-platform interoperability testing and lifecycle handling.
• Format coverage and validation discipline: Confirm stable handling of Factur-X, UBL, and CII, including clear rejection reasons for data issues.
• Security and audit readiness: Assess controls for secure transmission, logs, and evidence retention suitable for regulated financial data.
• Reliability and scale: Evaluate uptime commitments, redundancy, and operational support aligned to month-end peaks.
• ERP integration options: Review APIs, connectors, mapping support, and how exceptions are surfaced to finance teams.
• Implementation depth: Prioritise providers that can support onboarding, testing, and change management, not only connectivity.

Implementation Roadmap: From Selection to Go-Live

Platform selection is only the starting point. Most rollout delays come from inconsistent data and unclear exception ownership, so plan e-invoicing as a joint finance and IT change, not just a connector project.

Step 1: Map in-scope scenarios: Identify which flows you must support (domestic B2B invoices, credit notes, adjustments). This defines the fields, validations, and workflow rules your system and platform must apply in real operations.

Step 2: Fix master data early: Structured invoices fail when business identifiers, addresses, and tax mappings are inconsistent. Clean customer identifiers (such as SIREN where required), standardise billing and delivery addresses, and align product and VAT codes so your chosen format outputs remain stable.

Step 3: Pick the right integration pattern: Choose how invoices will be produced and transmitted based on your system landscape. ERP-native integrations suit standard environments, middleware helps when you have multiple billing sources, and outsourced generation can work if you still control data quality and compliance accountability.

Step 4: Test interoperability and lifecycle events: Go beyond format checks. Validate cross-platform routing, acceptance and rejection handling, correction workflows, and e-reporting data extraction where relevant.

Step 5: Build audit-ready controls: Ensure traceability, integrity, and retrievable evidence so you can reconstruct invoice events across systems and platforms during audits.

Conclusion

France’s 2026 reform rewards disciplined implementation and punishes “format-only” thinking. The organisations that succeed treat the approved platform as part of the tax control environment, not a document delivery tool. If you verify approval status through the official register, prioritise interoperability and lifecycle handling, and fix master data early, you reduce invoice friction, shorten payment cycles, and build a cleaner VAT evidence position for audits.