Portability Risks in France's E-Invoicing Ecosystem: Regulators Flag Recurring Errors

As the operational demands of France's e-invoicing reform grow, the process of transferring customers between approved platforms (PA) — known as "portabilité" — has become a pressing concern. AIFE and DGFiP addressed recurring missteps in cross-platform transfers through concrete case studies, while also reiterating expectations for the reform's live operational phase.

Three Portability Scenarios to Avoid

A feedback analysis (RETEX) shared by the administration highlights three risky patterns observed in the field:

Case 1 – Appropriation Without a Mandate: A platform claims a directory (Annuaire) entry without any contractual relationship or authorization from the customer. This creates a risk of invoices being routed to an unauthorized platform, or invoices being issued without request. The administration's guidance is clear: check the existing directory status and review the scope of the formal agreement before any appropriation.

Case 2 – Non-Compliant Addressing Plan: An address at a given granularity is claimed by one platform, while another, unauthorized platform simultaneously claims a different line for the same customer. This leads to configuration that doesn't match the company's actual choice and creates routing ambiguity. The key warning: a formal agreement covering one level of addressing does not legitimize action at other levels — the entire addressing plan must be checked, and alignment with other linked platforms must be verified.

Case 3 – Issuance ≠ Reception Mismatch: Flows are issued from one platform while the customer's addresses are attached to another. The administration reminds platforms that a customer can legitimately use different platforms for reception and for issuance — the invoicing authorization mandate and its effective period should be the reference point whenever a receiving platform questions issued flows.

Process and Best Practices

The portability process, as defined in the document shared by SIM in early August, follows five steps: formal agreement → notification of the former platform → acceptance/rejection → directory update → PEPPOL SML synchronization.

The administration recommends a four-step checklist for platforms: verify the mandate's validity (customer details, addresses concerned, effective date), check the existing directory status (existing lines, current reception platform), clarify the actual need (first designation or platform change?), and apply the correct method — particularly notifying the former platform before taking over lines in a mobility scenario. The underlying principle remains unchanged: line appropriation must respect the mobility process and the scope defined by the formal agreement.

Renewed Reminders on Reform Launch Practices

The administration also updated its expectations for the live rollout. Platforms are asked to test their flows on the QUAL environment first rather than sending them directly to PROD — with particular attention to using the correct environment application code (QUAL is coded 10, PROD is coded 09). A notable new element: the administration explicitly stated that temporary connection suspensions may be imposed in cases of major non-conformity repeated over several days.

The previously announced 3-day precaution window for directory-line effective dates was confirmed to apply to both start and end dates.

Two core expectations remain unchanged: flow allotment (a maximum of 1,000 files per flow — while survey results show strong commitment, the administration is now asking platforms to demonstrate this concretely) and connection to Chorus Pro, mandatory for G2B flows from public entities. As of September 7, only 55 platforms were connected to Chorus Pro in the PROD environment — indicating a significant portion of the ecosystem has yet to complete this required step.

Support Channels

The administration offers a two-tier support model: business questions from customers should be directed to the SIE or DGFiP's national assistance line (0 806 807 807), while platforms experiencing issues with PPF usage are asked to open a support ticket rather than send an email, for better traceability. General questions can be addressed through AIFE's documentation portal and the collaborative site moderated by DGFiP and AIFE (lab.chorus-pro.gouv.fr/group/90). Weekly follow-up meetings continue every Tuesday at 2:00 PM through the end of September.

For an SAP-focused perspective, read the related France e-invoicing portability analysis on sapeinvoice.com.

Related E-Invoicing Resources

Read the original article and explore Docnova e-invoicing insights.

For SAP-integrated compliance, visit the Melasoft SAP e-invoicing solution.