Plateforme Agréée vs Solution Compatible: The Difference That Matters in France
Published August 2026 by Solarc Labs
A Plateforme Agréée is the regulated intermediary
DGFiP describes a Plateforme Agréée as an operator registered by the tax administration and authorized to perform the regulated e-invoicing and e-reporting functions assigned to that layer. Businesses use a PA directly, or use a compatible solution that is connected to one, for the exchange and reporting path required by the reform. The official list matters because “e-invoicing ready” marketing language is not the same thing as being a registered PA.
A Solution Compatible can be useful without being the regulated platform
A Solution Compatible can sit closer to the company workflow: invoicing software, ERP integration, accounting tooling or another operational system. Official guidance distinguishes it from a PA because the compatible solution is not itself registered as the official intermediary and cannot simply assume the PA’s regulated role. It must be connected to the appropriate PA path for the regulated exchange. For buyers, the practical question is therefore not “PA or software?” in the abstract. It is which component owns each responsibility and whether the connections between them are actually ready.
ERP teams should draw the boundary before testing
A clean cutover architecture separates at least three concerns: source data and mapping inside the ERP or billing system; compatibility or orchestration logic between systems; and the regulated PA transmission layer. When those responsibilities are blurred, a successful platform onboarding can be mistaken for proof that the source invoices themselves are technically clean. Write down the owner of each layer before testing. That makes a defect easier to route and prevents the wrong supplier from being asked to prove a capability outside its scope.
Independent preflight is a fourth job, not a replacement PA
A corpus preflight can test representative structured invoices before production, cluster repeat failures and produce evidence for remediation. That is useful precisely because it is a different job from transmission. InvoiceBatch FR is not a Plateforme Agréée, does not transmit invoices to recipient platforms, and does not send fiscal data to the administration. Its purpose is to reduce upstream uncertainty before the regulated exchange layer is asked to carry real production traffic.
Use official registration evidence when evaluating platform claims
When a provider says it is a Plateforme Agréée, verify that claim against the DGFiP list rather than relying on a sales page. When a provider says it is a Solution Compatible, ask which PA connection is used, which responsibilities stay with the compatible solution, and which operational states are exposed back to the ERP or finance team. That procurement discipline is more valuable than a generic feature checklist because it tests the legal and technical boundary that determines who can actually perform the regulated exchange.
Primary sources
Sources used for this article
Continue the job