What Changed After the 2024 Reform
July 2024 marked an important turning point for France’s e-invoicing reform, as the DGFiP changed the role of the Portail Public de Facturation (PPF). Originally planned as a free national invoicing platform, the PPF was repositioned as a directory hub for invoice routing and data concentration only. With no free public path to compliance, businesses must now evaluate a reliable France e-invoicing solution to ensure readiness, regulatory alignment, and seamless invoice exchange under the upcoming mandate.
Private certified platforms, called Plateformes de Dématérialisation Partenaires (PDPs), are now the active infrastructure for issuing and receiving e-invoices. The architecture follows a four-corner model: issuer → issuer’s PDP → recipient’s PDP → recipient.
The legal basis rests on Article 289 bis of the Code Général des Impôts, Decree 2022-1299, and Article 91 of Finance Law 2024. After multiple delays since 2020, the mandate is now set for 2026–2027. That delay history has created organizational fatigue — not more time.
E-Invoicing vs. E-Reporting: Two Distinct Obligations
These are frequently conflated, and that confusion is the most common scoping error in readiness plans. E-invoicing covers domestic B2B transactions between French VAT-registered entities. E-reporting is a separate obligation covering B2C sales, cross-border B2B flows where the counterpart isn’t French VAT-registered, and payment status data sent to DGFiP. Full B2B invoicing compliance does not satisfy e-reporting obligations.
The Compliance Calendar
- September 1, 2026: Mandatory e-invoice issuance for large and mid-size enterprises. Universal reception capability required for all French businesses.
- September 1, 2027: Issuance obligation extends to SMEs and micro-enterprises.
- February 2026: Voluntary testing window opens — treat this as a hard internal deadline, not an early-mover opportunity.
The most common misreading: SMEs assume they have until 2027. They don’t — not for reception. All businesses must be capable of receiving compliant e-invoices by September 2026, which requires directory registration regardless of company size. Directory registration is the first actionable step and the most consistently overlooked planning error across readiness assessments.
The February 2026 testing window should be used to confirm: PDP connectivity with named trading partners, SIRET directory registration for your entity and suppliers, correct ERP XML extraction (not PDF), a supplier onboarding dry run covering at least the top 20% of invoice volume by value, and a lifecycle status reconciliation drill tracing every mandatory status from Deposited through Payment Received.
How the Mandate Disrupts AP and AR Processes
Invoices must be issued in one of three structured formats: Factur-X (a hybrid PDF/A-3 with embedded XML), UBL 2.1, or UN/CEFACT CII. AP systems must extract and process the XML layer — not the visual PDF. Routing relies on the national PDP directory, not email addresses or legacy EDI identifiers. Supplier master data must be validated against the INSEE SIRENE directory before any platform goes live.
Rejection and refusal are not the same status. Rejected occurs at the platform level due to technical failure. Refused is a commercial decision by the buyer. Both stop payment. AP and AR teams need defined escalation processes, SLA commitments from their PDP, and new dispute resolution workflows before go-live. Organizations that skip this redesign will see DSO drift materially in the first quarter of operation.
The 10 Mandatory Invoice Lifecycle Statuses
Always verify against the current DGFiP Cahier des charges, which has been updated since the 2024 reform.
- Deposited — Invoice placed into issuer’s PDP
- Sent — Transmitted to recipient’s PDP
- Made Available — Accessible to the recipient
- Acknowledged — Receipt confirmed by recipient
- Rejected — Technical or structural failure at platform level
- Refused — Buyer’s commercial decision not to accept
- Approved for Payment — Validated for payment by recipient
- Payment Received — Funds confirmed by issuer
- Cancelled — Invoice cancelled by issuer
- Abandoned — Invoice deposited but not transmitted within the platform’s inactivity window
Recommended statuses (In Dispute, Partially Paid) should be treated as standard in shared services environments, not optional. Status communication gaps can trigger audit scrutiny.
E-Reporting: Frequency and Data Requirements
E-reporting transmissions occur every 10 days under the standard VAT regime, aligned to the monthly VAT declaration calendar. Quarterly filers operate on an alternate schedule. Transmissions go through the same PDP infrastructure and are routed to DGFiP via the PPF concentrator.
Required data fields include: transaction date, amount excluding VAT, VAT rate applied, VAT amount, transaction nature, and counterpart country for cross-border flows. Payment status reporting requires payment date and amount paid. Validate all field specifications against the current Cahier des charges before go-live.
EU ViDA Interaction
France’s mandate predates ViDA and operates under national law. ViDA measures begin incrementally from 2028, with full intra-community reporting requirements expected by 2030. PDP certification under the French framework does not imply ViDA readiness. When evaluating PDPs, explicitly ask whether ViDA-aligned reporting capability is on the product roadmap and on what timeline. Signing a PDP contract without ViDA visibility creates serious re-platforming risk before 2030.
Three Implementation Challenges That Determine Go-Live Success
Master Data.
Every invoice transaction is anchored to SIREN (9-digit legal entity identifier) and SIRET (14-digit establishment identifier). An invoice sent to an incorrect or inactive SIRET is rejected at the platform before it reaches the recipient. Run a full vendor master audit against the INSEE SIRENE directory. Allow at least three months for remediation at scale. SIRET validation is not a one-time exercise — it’s an ongoing data hygiene requirement.
ERP Integration.
After go-live, PDF processing of in-scope transactions is not permitted. ERPs must generate structured XML in the correct format, transmit to the PDP via API or SFTP, receive lifecycle status updates and reflect them accurately in the invoice record, and trigger workflows at key status transitions. A common failure mode is an ERP that generates Factur-X output but fails to populate the embedded XML fields correctly, or a PDP connector that transmits outbound invoices but cannot return status updates in a digestible format. Test the full round trip — not just outbound. Each SIRET in a shared services configuration must be independently registered and linked to a PDP reception channel.
PDP Selection.
Certified PDPs will be available in volume by 2026. The selection criteria that matter: platform resilience under month-end volumes and high rejection rates; depth of ERP integration (bi-directional data enrichment, validation, and synchronization — not just connectivity); lifecycle status management built into the operational workflow; scalability to future mandates including ViDA; and total cost of ownership including exception handling, supplier integration, and regulatory update costs. A PDP that doesn’t automate validation and reconciliation transfers operational burden to your finance team.
12-Month Readiness Roadmap
Months 1–3 (Assessment):
Map all invoice-generating events including credit notes, cancellations, and cross-border variations. Conduct field-level audit of SIREN/SIRET coverage, tax breakdowns, and lifecycle tracking fields. Produce a data gap register and a current-to-future-state process deviation map.
Months 4–6 (Design):
Select a PDP that scales beyond France. Define the integration model (API, batch, or hybrid), data ownership between ERP and PDP, rejection handling workflows, dispute resolution flows, and status-triggered accounting events. Lifecycle statuses must sync to the ERP — a PDP-only view creates an operational blind spot.
Months 7–9 (Build and Integrate):
Implement format mapping across UBL, CII, and Factur-X. Build real-time validation loops, lifecycle status ingestion into the ERP, and multi-entity orchestration. Establish the ERP → PDP → Status → ERP feedback loop. Without it, finance loses control.
Months 10–12 (Test and Deploy):
Simulate high-volume month-end runs, rejection scenarios, cross-border reporting flows, and failed supplier onboarding. Run supplier and customer onboarding in parallel with internal finance training covering new workflows, exception handling, and status interpretation. Errors at go-live are inevitable. The measure of readiness is how quickly your system can identify, fix, and recover.