France’s last minute practical guide

What French businesses should know before 1 September 2026
As France prepares for the introduction of mandatory electronic invoicing on 1 September 2026, the French tax administration (DGFiP) has published a practical guide designed to help businesses navigate the transition.
The document sends an important message: while the legal deadlines remain unchanged, the priority during the rollout is to maintain business continuity while making a genuine effort to comply.
For businesses, ERP providers and Plateformes Agréées (PAs), this provides valuable insight into how the French authorities expect the first months of the reform to work in practice.
Plateformes Agréées (PAs) are the accredited service providers authorised to exchange e-invoices and e-reporting data within the French e-invoicing framework.
The deadline remains unchanged
The guide makes it clear that the reform is proceeding as planned.
From 1 September 2026:
- All businesses must be able to receive electronic invoices.
- Large enterprises and mid-sized enterprises (ETIs) must also issue electronic invoices through an accredited Plateforme Agréée (PA).
- Electronic reporting obligations will begin alongside the rollout for businesses that are in scope.
There is no indication of a postponement. Companies should continue preparing for the planned implementation dates.
Business continuity comes first
Perhaps the most reassuring aspect of the guide is its emphasis on keeping businesses operating, even if technical issues occur during the transition.
If an invoice relates to a legitimate commercial transaction and contains the required information, businesses should continue to process and pay it - even if it temporarily arrives outside the new electronic invoicing framework.
This reflects a pragmatic approach from the French administration: the objective is to modernise invoice exchange, not to interrupt trade because of temporary implementation challenges.
Temporary fallback procedures are acceptable
The guide recognises that no nationwide digital transformation is entirely free from technical issues.
If problems arise - for example due to routing issues, onboarding delays or system integration challenges - companies may temporarily exchange invoices through traditional channels such as PDF or email to ensure that business continues.
However, these fallback methods are intended to be temporary. Businesses are expected to resolve the underlying issue promptly and return to the compliant electronic process as soon as possible.
Compliance is about demonstrating genuine effort
Another important takeaway is the DGFiP’s focus on good-faith compliance.
Rather than expecting every company to operate flawlessly from day one, DGFiP encourages organisations to:
- actively work towards compliance,
- resolve technical issues quickly,
- document incidents and corrective actions,
- collaborate with their software providers and Plateforme Agréée (PA).
Maintaining evidence such as support tickets, incident logs and correspondence can demonstrate that a business has taken reasonable steps to comply should questions arise later.
Start where you’re ready
The guide also acknowledges that many organisations operate multiple ERP systems, subsidiaries and business units.
Instead of delaying implementation until every part of the organisation is ready, companies are encouraged to begin electronic invoicing with the processes that are already prepared and expand progressively.
This phased approach allows businesses to gain operational experience while continuing their broader rollout.
Receiving invoices outside the network
One practical clarification addresses a question many businesses have raised.
- If a supplier temporarily sends an invoice by email or PDF instead of through the electronic invoicing network, the recipient does not need to reject the invoice solely because it arrived through the wrong channel.
Provided the invoice is otherwise valid, it may still be processed, paid and accounted for. The supplier should subsequently regularise the electronic exchange where appropriate, but payment should not be delayed simply because of a temporary transmission issue.
What this means for businesses choosing a Plateforme Agréée
For organisations evaluating technology providers, the guide highlights the importance of working with a partner that supports more than just invoice transmission.
A capable Plateforme Agréée should help customers:
- monitor invoice delivery and lifecycle events,
- quickly identify routing or validation issues,
- provide clear audit trails,
- support temporary fallback procedures where appropriate,
- guide customers back to full compliance once issues are resolved.
The first months of the reform are likely to be as much about operational support as technical connectivity.
Arratech’s perspective
At Arratech, we see DGFiP’s guidance as a positive signal for the French e-invoicing ecosystem.
The success of the reform will depend not only on technology, but also on collaboration between businesses, ERPs and software providers and accredited Plateformes Agréées.
The practical guide recognises this by encouraging a pragmatic transition that balances regulatory compliance with uninterrupted business operations.
For organisations preparing for France’s e-invoicing mandate, the message is clear: continue preparing for the September 2026 deadline, implement electronic invoicing where you’re ready, document any implementation issues, and work closely with your software and PA partners to achieve full compliance.
That’s exactly the type of transition support we believe every business should expect from its Plateforme Agréée.

Frequently Asked Questions
Frequently Asked Questions on France e-Invoicing mandate
Partially, but not fully. France's architecture is different from pure Peppol markets like Belgium or Germany. In France, invoice exchange must route through a registered Approved Platform (PA) — there is no direct peer-to-peer Peppol exchange without a PA intermediary.
Your existing Peppol connectivity and EN 16931 XML invoice generation are still relevant; Peppol BIS (UBL 2.1) and CII are both accepted formats in France. But you will also need to support Factur-X (a hybrid format combining XML and embedded PDF), and you will need to connect to a PA that is formally registered by the DGFiP.
The more significant addition is e-reporting: France requires separate data submissions to the DGFiP for B2B, B2C and cross-border transactions. This is not part of standard Peppol implementations and requires its own data pipeline from your platform.
Working with Arratech means we connect to the French PA ecosystem on your behalf, handle format conversion and e-reporting data generation, and ensure your existing Peppol integration extends cleanly to the French market.
In earlier versions of the French reform, the intermediary was called a Plateforme de Dématérialisation Partenaire. The terminology was updated and the formal registration regime is now called Plateforme Agréée (PA) — Approved Platform.
The substance is the same: a PA is a formally DGFiP-accredited intermediary platform authorised to route e-invoices between businesses and report transaction data to the tax authority. PA accreditation requires meeting strict technical and security criteria, including interoperability testing with other PAs.
If you encounter documentation referring to PDPs, this is the same concept under the new naming convention. All formally registered platforms operating from September 2026 will carry the PA designation.
It depends on the definition of mid-size. France uses the ETI classification (Entreprises de Taille Intermédiaire) for the September 2026 phase, covering companies with 250 to 4,999 employees and revenue above €50 million. Large companies are also in scope from September 2026.
SMEs (fewer than 250 employees, revenue below €50 million) have until September 2027. Micro-enterprises have until September 2028.
However - and this is critical - all businesses, regardless of size, must be able to receive e-invoices from September 1, 2026. Even if your customers have until 2027 to issue e-invoices, they need to be connected to a PA to receive them from large company suppliers from day one. Build receive capability first.
More than a typical Peppol market extension, because France requires formal DGFiP registration as an Approved Platform — which is a separate accreditation process from Peppol certification. However, your existing infrastructure gives you a significant head start. Keep in mind only PAs are allowed to operate Peppol Access Points in France. There are also infrastructure, data and operations location requirements; no domestic invoice data can leave France.
The work specific to France includes: PA registration with DGFiP (including interoperability testing), Factur-X format support alongside your existing UBL 2.1 and CII, e-reporting pipeline development, and integration with Chorus Pro as the DGFiP central repository.
The practical question is whether to pursue PA registration yourself or connect via an already-registered PA. For most Access Points, the fastest route is to partner with a PA that is already registered and operational. Arratech operates as a PA-connected Access Point for France — your customers get French mandate compliance through the same Arratech API they already use for Peppol markets.