Skip to main content
Complyance is Officially Listed as a UAE Approved Accredited Service Provider
PDP vs OD (Opérateur de Dématérialisation) in France E-Invoicing: Key Differences

PDP vs OD (Opérateur de Dématérialisation) in France E-Invoicing: Key Differences

Swathy
Published on Jul 23, 2026

PDP vs OD (Opérateur de Dématérialisation, now also Solution Compatible) explained for France's e-invoicing reform. What each one is, a capabilities comparison, when an OD is enough, when you need a Plateforme Agréée, and how ODs connect through a PA. Complyance guide.

Two roles sit at the heart of France's e-invoicing reform, and confusing them can lead to a compliance gap you will not notice until an invoice fails to reach the tax authority. One is the Plateforme Agréée (PA), formerly called the Plateforme de Dématérialisation Partenaire (PDP), the certified, state-approved platform. The other is the OD, the Opérateur de Dématérialisation, now also called a Solution Compatible (SC), a non-certified operator that plays a real but limited role.

They both handle invoices. But the difference between them decides one crucial thing: who transmits your data to the DGFiP. With the mandate arriving on 1 September 2026, getting this right early keeps your invoicing compliant and your options open.

Let us unpack what an OD (or SC) is, how it differs from a PA, and how to decide which you need, including where a partner like Complyance fits.

What Is an Opérateur de Dématérialisation (OD / SC)?

An Opérateur de Dématérialisation (OD), now also referred to as a Solution Compatible (SC), is a service provider that assists with electronic invoicing (format conversion, e-reporting preparation, and workflow) but is not certified by the DGFiP as an approved platform.

An OD or SC can do plenty of useful work:

  • Create and format invoices for your business
  • Assist with format conversion to structured standards
  • Manage invoice data and workflows
  • Help prepare e-reporting data
  • Connect to a certified platform to get invoices into the ecosystem

But there is a hard limit: an OD or SC does not transmit data to the DGFiP itself. To reach the tax authority and the wider ecosystem, an OD must connect through a Plateforme Agréée (PA). Think of an OD or SC as a capable assistant that still needs a certified gateway to actually deliver.

What Is a Plateforme Agréée (PA / formerly PDP)?

A Plateforme Agréée (PA), formerly a Plateforme de Dématérialisation Partenaire (PDP), is a platform certified by the DGFiP and authorised to:

  • Issue compliant e-invoices in approved formats
  • Receive invoices sent to your business
  • Transmit invoices between platforms across the ecosystem
  • Report the required invoice and e-reporting data to the DGFiP

A PA earns its certification through the DGFiP's immatriculation process, passing security and compliance audits and receiving an official registration number that is time-bound and renewable. France originally planned a hybrid "Y-model" that also allowed invoicing through the public portal, but at the end of 2024 it moved to a strict 5-corner model. Crucially, in that model, certified platforms are the only operators that transmit e-invoices and e-reporting data to the DGFiP, and an OD must connect through a PA to reach the network.

PDP vs OD: Capabilities Compared

The clearest way to see the difference is side by side.

CapabilityPlateforme Agréée (formerly PDP)OD / SC (Opérateur de Dématérialisation)
Certified by the DGFiPYes (official immatriculation)No
Produce and format invoicesYesYes
Assist with format conversionYesYes
Issue compliant e-invoicesYesYes, but must route through a PA
Receive e-invoicesYesOnly via a connected PA
Transmit between platformsYesOnly through a PA
Transmit to the DGFiPYesNo, must connect through a PA
Official registration numberYesNo
Security audit and renewalYes (time-bound, renewable)Not applicable
Can act as your standalone gatewayYesNo

The single most important rows are the last few: only a PA transmits to the DGFiP and can stand alone as your gateway. An OD or SC always needs a PA behind it.

When Is an OD Enough, and When Do You Need a PA?

You do not necessarily have to contract with a PA directly. What matters is that your invoices ultimately reach the DGFiP through a certified platform. Here is how to think about it.

An OD or SC may be enough when:

  • You already work with a software or service provider you like, and it acts as an OD or SC
  • That OD or SC is reliably connected to a certified PA that handles transmission and reporting
  • Your workflows are straightforward and you are comfortable depending on that OD-to-PA chain

You need a PA (directly) when:

  • You want a single, certified gateway that transmits and reports to the DGFiP without an intermediary
  • You need certainty that transmission to the DGFiP is handled by the platform you contract with
  • You want to receive e-invoices from September 2026 through a certified platform you control
  • You handle e-reporting for B2C or cross-border transactions and want it managed end to end
  • You would rather avoid the risk of an OD lacking a solid PA connection

The practical rule: an OD or SC is only compliant if there is a PA behind it. If you want to remove that dependency and simplify your setup, contracting with a PA directly is the cleaner path.

How ODs Connect Through a Plateforme Agréée

An OD or SC does not reach the DGFiP on its own. It hands off to a certified platform. In practice, the flow looks like this:

  • The OD produces, formats, or converts the invoice for your business
  • The OD connects to a PA, passing the invoice to it
  • The PA validates, transmits, and reports, routing the invoice via the Central Directory to the counterparty's platform and transmitting the required data to the DGFiP
  • Lifecycle statuses flow back through the same chain so you can track the invoice through the four mandatory statuses (Déposée, Rejetée, Refusée, Encaissée)

So even when you interact mainly with an OD, a PA is doing the regulated heavy lifting in the background. If that PA connection is weak or missing, the whole chain breaks, which is exactly why the certified platform matters so much.

Decision Guidance: Choosing Your Setup

A short way to decide.

1. Map who transmits to the DGFiP. Trace your invoice all the way to the tax authority. There must be a certified PA at the end of that path.

2. Check the OD-to-PA link (if you use an OD). If you rely on an OD or SC, confirm exactly which PA it connects to and how reliable that link is.

3. Weigh simplicity vs dependency. An OD adds a link in the chain. A direct PA relationship removes it. Fewer links usually means fewer points of failure.

4. Confirm full coverage. Whatever setup you choose, make sure it covers e-invoicing (domestic B2B) and e-reporting (B2C and cross-border), the required formats, and the four mandatory lifecycle statuses.

5. Plan for the deadlines. Reception is mandatory for everyone from 1 September 2026, with issuing and e-reporting starting for large and medium-sized companies then, and extending to small and micro-enterprises from 1 September 2027. Choose and test early.

Why Choose Complyance as Your Plateforme Agréée?

If you would rather have a certified platform as your direct gateway, with no dependency on someone else's PA link, Complyance is an Approved Platform (PA) for France, built for exactly that.

1. A certified-platform gateway

Complyance is designed to issue, receive, transmit, and report so you have a clean, direct route to the DGFiP.

2. Built for the required formats and statuses

Full support for Factur-X, UBL 2.1, and CII, plus the four mandatory lifecycle statuses the French model depends on.

3. Both e-invoicing and e-reporting

Domestic B2B invoicing and cross-border and B2C e-reporting handled together, with no gaps to patch later.

4. Developer-friendly and OD-friendly

Clear APIs and integrations mean whether you connect systems directly or work through an operator, the path is smooth.

5. Compliance without complexity

Automated validation, error detection, and audit-ready records, backed by expert support for complex cases.

Ready to remove the guesswork?

Complyance gives your developer, IT, finance, and operations teams a direct, certified gateway and expert support for a smooth transition to the 2026-2027 mandate.

Conclusion: PDP or OD? Make Sure a PA Is Always in the Chain

The difference is simple once it clicks: a Plateforme Agréée is the certified platform that transmits and reports to the DGFiP, while an OD or SC is a capable but non-certified operator that must connect through a PA. An OD can be part of your setup, but only if a PA stands behind it. Before you finalise, check:

  • Trace your invoice path to a certified PA at the DGFiP end
  • If you use an OD or SC, confirm which PA it connects through
  • Verify Factur-X, UBL 2.1, and CII support plus the four mandatory lifecycle statuses
  • Confirm both e-invoicing and e-reporting are covered
  • Decide whether a direct PA relationship simplifies your setup
  • Test in a sandbox ahead of 1 September 2026

Keep a certified PA in the chain, and your invoices always have a compliant route to the tax authority.

Share

Frequently Asked Questions

A Plateforme Agréée (PA), formerly Plateforme de Dématérialisation Partenaire (PDP), is a platform certified by the DGFiP that can issue, receive, transmit, and report invoices to the tax authority. An OD (Opérateur de Dématérialisation), now also called a Solution Compatible (SC), is a non-certified operator that assists with formatting and e-reporting but must connect through a PA to reach the DGFiP.

No. An OD or SC is not certified, so it does not transmit data to the tax authority itself. It must connect through a certified PA, which handles the actual transmission and reporting.

An OD or SC can be part of a compliant setup, but only if it connects to a certified PA that handles transmission and reporting. If you want a single, direct gateway without depending on someone else's PA link, contracting with a PA directly is the simpler and safer choice.

The OD produces, formats, or converts your invoice, then passes it to a certified PA. The PA validates it, routes it through the Central Directory, transmits it to the recipient's platform, and reports the required data to the DGFiP. Lifecycle statuses flow back through the same chain.

Because certified platforms are the operators that transmit and report to the DGFiP. If your setup relies on an OD or SC without a solid PA connection behind it, your invoices may not reach the tax authority, which is a compliance gap. Confirming a certified PA sits in your chain protects you.

Yes. Complyance is an Approved Platform (PA) for France, built to serve as your certified gateway: issuing, receiving, transmitting, and reporting invoices in the required formats, handling the four mandatory lifecycle statuses and e-reporting, and giving you a direct route to the DGFiP without depending on a third party's PA link.

About the Author

Swathy

Swathy

Content Marketer

I’m a Content Marketer at Complyance, focused on e-invoicing. Over the years, I’ve created a wide range of content, including blog posts, whitepapers, and product guides, which have supported Complyance’s growth across markets such as the UAE and EU regions. My goal is to deliver content that is comprehensive, clear, accurate, and easy to understand, no matter how complex the topic.

Related Posts

Complyance Logo

One API for Global E-invoicing