France: The Approved Platform Register Was Refreshed on August 19 with 147 Operators Cleared and 16 Still Awaiting Interoperability Testing
Country Update — France | 25 August 2026 | Topic: E-Invoicing / Approved Platform Register
On August 19, 2026 the DGFiP refreshed both of the official lists that together make up the register of approved e-invoicing platforms (plateformes agréées). Thirteen days before the September 1, 2026 obligation takes effect, the register shows 147 operators satisfying all conditions including interoperability testing, and 16 operators whose application file is complete and compliant but whose definitive registration remains conditional on passing those tests.
Background
From September 1, 2026 every business established in France must be able to receive electronic invoices, and the transmission of B2B invoices must pass through an operator registered by the State. The approved platform is the regulated intermediary at the center of the French model: it must issue, transmit and receive invoices in electronic format, extract the data required by the administration, and receive and transmit transaction and payment data.
In early August 2026 the DGFiP split what had been a single register into two separate lists, a change covered in our update of August 11, 2026. The split matters because the two lists carry different legal weight. The first list contains operators that satisfy the entire set of conditions, including interoperability testing.
The second contains operators that have filed a complete and compliant application but whose definitive registration number is still conditional on passing interoperability tests in real conditions. Both are published by the DGFiP, and both are easy to mistake for one another if a buyer looks only at whether a supplier's name appears on “the list”.
The August 19 refresh is the first substantive update of both lists since that split, and the last one likely to be seen before the obligation bites.
The Change
This is an administrative and operational event rather than a legislative one. The legal framework was completed earlier this summer by Decree 2026-677 and the Order of July 27, 2026, and nothing in the August 19 refresh changes the law. What changed is the factual state of the register, and in the French model the register is what determines whether a given counterparty can lawfully transmit or receive an invoice on September 1.
In that sense the refresh is binding in exactly the way a technical artifact is binding: enforcement is by exclusion, not by penalty. An operator on the second list on September 1 cannot yet act as the definitive registered platform for a transaction, however complete its file.
Scope
The DGFiP page “Je consulte la liste des plateformes agréées” was published on July 30, 2024 and last modified on August 19, 2026. Each of the two lists is published in three formats — ODS, XLSX and PDF — and the content is identical across formats.
List one, “Liste des opérateurs satisfaisant à l'ensemble des conditions, incluant les tests d'interopérabilité”, contains 147 operators. The file carries a registration-date column, and two entries — CYCLOPE and LUNDI MATIN — show “à venir” in place of a date. The list includes well-known enterprise and mid-market names such as SAP, Accenture, Sage, OpenText, DocuWare, Odoo, Pennylane and Qonto.
List two, “Liste des opérateurs ayant déposé un dossier complet et conforme et en attente de leur immatriculation définitive conditionnée à la réussite des tests d'interopérabilité”, contains 16 operators: Basikon, BLG, BE FRESH S.a r.l., CENSE, EAGLESSOFT, EY Expertises & Transactions, FACTUREAPP, FISKALTRUST, Insiders Technologies GmbH, KALANDA, MY-EDDY, NUMERIA, RATIOO, SWILE, Taxilla Europe BV and WAKASTELLAR. Five of these are established outside France — in Luxembourg, Belgium and Germany.
The counts of 147 and 16 are derived by counting the rows of the official PDF files; the DGFiP does not state a total on the page or in the files. The files themselves carry no publication date, so the August 19 date comes from the page metadata rather than from the documents.
The same page also links a DGFiP note presenting the two official labels, “plateforme agréée” and “solution compatible” — a distinction that matters commercially, because a compatible solution is not a registered platform and cannot discharge the transmission obligation on its own.
Timeline
- July 30, 2024 — DGFiP register page first published.
- Early August 2026 — the register is split into two lists, distinguishing operators that have completed interoperability testing from those that have not.
- August 19, 2026 — both lists refreshed; register stands at 147 cleared operators and 16 awaiting interoperability testing.
- September 1, 2026 — obligation to be able to receive electronic invoices takes effect, and B2B transmission must run through a registered platform.
Businesses Affected
Every business established in France is affected as a recipient from September 1, 2026. The register refresh matters most to three groups: businesses that have contracted with an operator appearing only on the second list; businesses whose chosen operator carries “à venir” against its registration date; and multinational groups that selected a platform centrally, often on the basis of a vendor claim rather than the DGFiP file.
Suppliers and customers of those businesses are affected indirectly. If a counterparty's platform is not definitively registered, the invoice flow between the two parties will not complete as intended, and the exposure is commercial — unpaid invoices and disputed VAT deduction — before it is ever a penalty question.
Required Actions
- Check your contracted operator against the two official DGFiP files, not against the operator's own marketing. Confirm which of the two lists it appears on, and whether a registration date is stated or shows “à venir”.
- Where your operator appears only on the second list, obtain a written statement of its interoperability-test schedule and put a contingency in place. Sixteen operators in that position thirteen days before go-live is not a trivial number.
- Distinguish “plateforme agréée” from “solution compatible” in your vendor documentation. A compatible solution must sit behind a registered platform.
- Re-check the register in the final week of August. The DGFiP has refreshed these files repeatedly through the summer, and the state of the register on August 31 is the state that governs September 1.
- Retain a dated copy of the ODS or XLSX file you relied on. The register is a rolling document with no version history, so evidence of the position you verified will not be reconstructable later.
Practical Implications
The two-list structure is the DGFiP's way of being transparent about a queue, and reading it correctly is now a due-diligence task rather than a formality. An operator can hold a complete and compliant file and still be unable to act as a definitively registered platform, because the binding gate is the interoperability test in real conditions — a test the operator cannot pass unilaterally, since it depends on exchanges with the public portal and with other platforms.
That is also why the second list should be read as a leading indicator of go-live friction rather than as a list of laggards. Interoperability testing is where the French model's design assumptions meet reality across 163 operators, and the residual 16 are the visible part of that. Groups that have concentrated volume on a single operator, in either list, carry the corresponding concentration risk.
For SAP-based groups the practical question is narrower: whether the operator selected for France is definitively registered, whether the connector in place has been tested against that operator's production endpoints rather than a sandbox, and whether the receiving capability — which is the obligation that actually starts on September 1 — has been proven end to end for inbound documents, not only for outbound.
Expected Next Steps
Further refreshes of both files should be expected in the last days of August and through the autumn as operators clear interoperability testing and move from the second list to the first. The two “à venir” entries on the first list should resolve to dates. Beyond registration, the next artifacts to watch are the FNFE-MPE Schematron packages and any further maintenance release of the DGFiP external specifications, which is where post-go-live corrections will surface first.
How Can KGT Support You?
KGT is a specialist indirect tax technology firm working exclusively inside the SAP landscape. We deliver SAP-integrated e-invoicing add-ons for countries where a local mandate outpaces the standard SAP roadmap, and we implement and run SAP Document and Reporting Compliance (SAP DRC) where the standard solution is the right answer. Because we build and operate both, our advice on which route to take for a given country is not a sales position.
For the development described above, KGT typically helps clients in four ways: assessing the impact on the existing SAP configuration and interface build; carrying out the mapping and regression work against the current official specification version; managing the platform, provider or registration dependency; and running the resulting flows as a managed service, so that each release, schema version and validation change is absorbed for you rather than by you. To discuss what this means for your SAP landscape, contact KGT at
This publication is provided for general informational purposes only and does not constitute tax, legal, or professional advice. Please consult your advisor before acting on any information contained in this update.
