Seamless generation of Factur-X, CII, and UBL e-invoices

Factur-X, CII, and UBL-compliant e-invoices software for France e-invoicing. Integrates with all ERP's market leader

PDP, OD, and PPF in France`s E-Invoicing Framework: Roles, Responsibilities, and How They Work Together

Updated On : Oct 15th, 2025 | 25 min read

France`s mandatory e-invoicing framework does not operate through a single centralised platform. It is a multi-participant architecture in which three distinct types of infrastructure, certified private platforms, uncertified service operators, and the state public portal, each play a defined role in ensuring that invoices are created, transmitted, validated, reported, and delivered in compliance with the requirements of the mandate. Understanding the function of each participant, the distinctions between them, and how they interact within the broader system is essential for any business making implementation decisions ahead of the September 2026 go-live.


Why the Framework Uses Multiple Platform Types

The decision to build France`s e-invoicing infrastructure around a combination of certified private platforms and a public state portal reflects a deliberate policy balance between accessibility, resilience, and commercial flexibility. A purely centralised model, in which all invoice flows pass through a single government-operated portal, would concentrate operational risk in a single point of failure and limit the commercial innovation that competition between private platforms can drive. A purely decentralised model, in which each platform operates independently without state oversight, would compromise the tax authority`s ability to collect consistent, accurate transaction data.

France`s framework resolves this tension by placing certified private platforms at the centre of day-to-day invoice exchange while assigning the public portal a directory and data aggregation role that ensures the tax authority receives the information it requires without needing to be the active transmission channel. The result is a system that distributes operational resilience across multiple certified platforms while maintaining centralised fiscal oversight through the state infrastructure.


Partner Dematerialisation Platforms: The Certified Core of the Framework

Partner Dematerialisation Platforms, referred to in French as Plateformes de Dématérialisation Partenaires and abbreviated as PDPs, are government-certified e-invoicing service providers that have met the specific technical, security, and operational standards set by the French tax administration. Certification is not a one-time assessment. PDPs must maintain ongoing compliance with regulatory requirements as the framework evolves, and their certification is subject to review.

Within France`s e-invoicing architecture, PDPs are the primary operational infrastructure for invoice exchange between businesses. A supplier using a certified PDP can issue and receive e-invoices directly with the buyer`s platform without routing the invoice through the public portal. Where both the buyer and the seller use certified PDPs, and where those PDPs have established interoperability, the invoice flows directly between the two platforms. The PPF is not in the transmission path for this exchange. Its role is limited to receiving the invoice data and lifecycle status information that the PDP reports after the exchange has occurred.


What PDPs Are Responsible For

The responsibilities of a certified PDP extend across the full lifecycle of invoice exchange and tax reporting. On the transmission side, a PDP validates the format and content of invoices submitted by its users, ensuring they conform to the applicable structured format standards and carry all m andatory data fields before they are transmitted. It routes outgoing invoices to the buyer`s designated PDP, or to the PPF for onward delivery where the buyer is not using a certified PDP. It receives incoming invoices from other PDPs on behalf of its users and delivers them in the buyer`s preferred format.

Format conversion is an explicit PDP responsibility. Where a seller`s system generates an invoice in one approved format and the buyer requires receipt in a different format, the PDP handles the conversion, maintaining the integrity, authenticity, and completeness of the invoice data throughout that process. This conversion must be performed under strict conditions that ensure no data is lost, altered, or misrepresented in translation between formats.

On the tax reporting side, PDPs extract the required invoice data and lifecycle status information and transmit it to the PPF within the timeframes established by the mandate. This [e-reporting](insert blog 4) function covers not only the B2B invoices exchanged through the platform but also, where the business uses its PDP for this purpose, the e-reporting obligations that apply to B2C transactions, cross-border B2B supplies, exports, and intra-community transactions that fall outside the scope of domestic B2B e-invoicing.

The combination of invoice transmission and tax reporting within a single certified platform is what makes PDPs the operationally dominant infrastructure choice for businesses with significant invoice volumes or complex transaction profiles. A business using a certified PDP has a single point of integration for its complete e-invoicing and e-reporting compliance, rather than separate systems for each obligation.


Interoperability Between PDPs

Because France`s business population will distribute its platform choices across multiple certified PDPs, the ability of one PDP to exchange invoices with any other is a structural requirement of the framework. This interoperability must be established through defined technical protocols that all certified platforms support. The PPF directory plays a critical enabling role here by allowing any PDP to look up which platform a given recipient has designated for invoice receipt, ensuring that invoices can be routed correctly across the network without requiring bilateral arrangements between every possible pair of platforms.

Businesses evaluating PDP options should confirm that a prospective platform has demonstrated interoperability with the broader certified PDP network and not merely with a limited set of partner platforms. Restricted interoperability would limit the business`s ability to receive invoices from suppliers using different platforms, which in a diverse supplier base would create gaps in the received invoice flow.


Dematerialisation Operators: The Non-Certified Service Layer

Dematerialisation Operators, known in French as Opérateurs de Dématérialisation and abbreviated as ODs, occupy a different position in France`s e-invoicing ecosystem. They provide e-invoicing related services to businesses but have not been certified by the French government. This absence of certification is the defining characteristic that distinguishes ODs from PDPs and determines the scope of what ODs can and cannot do within the framework.

An OD can assist businesses with preparing and formatting invoices, converting invoice data into the approved structured formats such as Factur-X, CII, and UBL 2.1, and supporting the e-invoicing process from a service perspective. However, an OD cannot directly transmit or receive invoices within the certified network. To complete an invoice exchange, an OD must route the invoice through either the PPF or a certified PDP. The OD functions as a preparatory and conversion layer that feeds into the transmission infrastructure rather than as a transmission participant in its own right.

Unlike PDPs, which must conform to the specific certification requirements that limit their operational scope to the certified framework, ODs can connect with a wider range of dematerialisation services and platforms. An OD must establish a connection with the PPF or a PDP to manage invoice flows and lifecycle status updates, making its operational effectiveness dependent on the reliability and capability of the transmission infrastructure it connects to.

The practical implication for businesses considering an OD is that the OD relationship introduces an additional dependency into the transmission chain. Where a PDP directly manages transmission and reporting, an OD-assisted process requires a subsequent handoff to a PDP or the PPF to complete the exchange. For businesses with simple invoicing needs and low volumes, an OD may provide a cost-effective entry point into structured e-invoicing. For businesses with complex transaction profiles, high volumes, or significant e-reporting obligations, the additional transmission step and the absence of direct certification introduce considerations that favour a certified PDP.


The Public Invoicing Portal: Directory, Data Hub, and Fallback Channel

The Portail Public de Facturation, universally abbreviated as PPF, is the French state`s infrastructure contribution to the e-invoicing framework. Operated by the government and directly connected to Chorus Pro, the existing mandatory portal for business-to-government invoicing, the PPF serves multiple functions within the mandate architecture, though its role has been redefined since France`s original framework design.


The Central Directory Function

The PPF`s most structurally important function is the administration of the Central Directory, a centralised database in which all businesses subject to the e-invoicing mandate must register and declare their chosen platform. The Central Directory is the routing intelligence of the entire framework. When a PDP needs to deliver an invoice to a buyer, it queries the Central Directory to determine which PDP the buyer has designated as its receiving platform. Without this lookup capability, the interoperability of the PDP network would require bilateral routing knowledge that is neither scalable nor maintainable across a large business population.

The Central Directory identifies businesses primarily through their SIREN number, the nine-digit identifier that designates a legal entity in France. Where more granular identification is required, for example to direct invoices to a specific establishment within a multi-site business, the directory may use the SIRET, the fourteen-digit extension that identifies individual business establishments.

Registration with the Central Directory is mandatory for all businesses within the mandate`s scope. A business that has not registered cannot be found by sending platforms attempting to route invoices to it, which means it cannot receive e-invoices through the certified network. Registration is therefore a prerequisite for compliance rather than an optional administrative step.


The Data Hub Function

In addition to its directory role, the PPF serves as the central aggregation point for invoice data and e-reporting information transmitted by certified PDPs. PDPs report invoice data, lifecycle statuses, and e-reporting transaction data to the PPF, which aggregates this information and forwards it to the Direction Générale des Finances Publiques, the French tax authority. This data flow gives the tax authority comprehensive visibility into commercial transactions without needing to be directly involved in the invoice exchange process.

The PPF`s data hub role is the mechanism through which the mandate`s fiscal objectives are achieved. The tax authority receives structured, validated transaction data from the entire certified platform network through a single aggregation point, enabling the VAT compliance monitoring, fraud detection, and eventual return pre-population that the mandate is designed to support.


Direct Access for Low-Volume Users

For businesses that choose not to engage a certified PDP or an OD, the PPF provides a direct access channel through a web portal and through API and EDI integration. This channel is intended primarily for very small businesses or low-volume invoicers for whom the cost of a certified PDP subscription may not be proportionate to their invoicing activity. The PPF`s direct access service is provided free of charge, reflecting the government`s commitment to ensuring that no business is excluded from the framework on cost grounds.

Businesses using the PPF directly must generate their invoices in the approved structured formats, as the PPF does not provide the same format conversion capabilities available from certified PDPs. The manual web portal mode is accessible without technical integration, while API and EDI access enable automation for businesses with the technical capability to integrate directly with the state infrastructure.


Compatibility with Chorus Pro

The PPF is directly connected to Chorus Pro, which remains the mandatory submission channel for [business-to-government invoices](insert blog 2). This connection ensures continuity between the B2G invoicing infrastructure that businesses already use and the new B2B mandate framework. For businesses already integrated with Chorus Pro for their public sector invoicing, the transition to the PPF-anchored B2B framework involves extending familiar technical concepts and data standards to their private sector invoice flows rather than building an entirely separate capability.


Choosing the Right Route: PDP, OD, or PPF Direct Access

Every business subject to France`s e-invoicing mandate must make a deliberate choice about which infrastructure route to use and must declare that choice in the PPF Central Directory. The choice has operational, financial, and compliance implications that warrant structured evaluation rather t han a default decision.

A certified PDP is the appropriate choice for businesses with significant invoice volumes, complex transaction profiles involving both e-invoicing and e-reporting obligations, cross-border activity, o r ERP systems that benefit from direct integration with a certified platform. The PDP`s combined transmission and reporting capability, format conversion services, and [lifecycle status management](insert blog 1) provide a comprehensive compliance infrastructure within a single relationship. The certification requirement ensures a defined standard of service and regulatory a lignment that non-certified alternatives cannot provide.

An OD-assisted approach may suit businesses that require support with format preparation and conversion but whose transaction volumes and complexity do not justify a full PDP engagement. Businesses using an OD must understand that the OD`s role is preparatory and that a PDP or the PPF must still be engaged for the transmission and reporting stages. The OD relationship does not in itself fulfil the mandate`s transmission requirements.

Direct PPF access is the lowest-friction entry point for very small businesses with minimal invoice volumes and no requirement for automated ERP integration. It requires that the business can generate invoices in the approved structured formats, accepts the limitations of manual or basic API access, and does not require the service level commitments and integration support that a certified PDP provides.

Regardless of which route a business selects, registration in the PPF Central Directory using the SIREN or SIRET identifier is non-negotiable. Without that registration, the business is invisible to the certified platform network and cannot participate in compliant e-invoice exchange. Completing this registration well in advance of the September 2026 deadline, rather than at the last moment, avoids the risk of directory processing delays affecting the business`s ability to receive invoices from the point the mandate takes effect.

For organisations managing France`s e-invoicing infrastructure decisions alongside equivalent compliance requirements in Germany, Italy, Belgium, and other European jurisdictions where mandates are active or imminent, the complexity of navigating multiple platform frameworks, certification standards, and registration requirements is best addressed with specialist support. Platforms such as Accqrate provide the multi-jurisdictional expertise and technical infrastructure needed to make these implementation decisions with confidence and to maintain ongoing compliance as France`s framework continues to evolve toward its full operational state.


cta.title1

cta.description1cta.description2
cta.badge1starcta.badge2starcta.badge3
Dashboard Views