The French Directorate General of Public Finances has published a new practical guide explaining how businesses should manage operational difficulties during the launch of France’s mandatory e-invoicing and e-reporting reform.
The guide provides welcome flexibility for the start-up period, but it does not change the legal timetable.
Key points from the DGFiP guidance
1. The September 2026 deadline remains unchanged
All businesses within the scope of the reform must be able to receive electronic invoices from 1 September 2026. Large enterprises and mid-sized enterprises subject to the issuance obligation must also issue their in-scope invoices through an approved platform from that date.
2. The guidance introduces a pragmatic start-up approach
Sanctions should not be applied automatically where a company encounters genuine and documented implementation difficulties and follows them with corrective action.
However, this should not be interpreted as a postponement, suspension of the obligations or a general penalty-free period.
3. Business continuity should be maintained
A genuine invoice received through email, PDF or paper should not be rejected solely because it was not transmitted through the expected electronic channel. Businesses should continue processing invoices and payments while resolving the underlying electronic invoicing issue.
4. Alternative channels may be used temporarily
Email, PDF, customer portals or existing EDI channels may support continuity where the electronic process is unavailable, but they do not permanently replace the mandatory e-invoicing channel.
5. Businesses should not wait for every flow to be fully ready
Companies should not wait until every entity, customer and ERP flow is fully stabilised. Ready flows should go live, while remaining gaps are documented and corrected.
6. Documentation will be critical
Businesses should retain clear and dated evidence of their implementation efforts, including:
- approved platform selection and contracting;
- testing and deployment plans;
- support tickets and error messages;
- correspondence with technology providers;
- temporary business continuity procedures; and
- corrective and regularisation measures.
A general statement that the company is still preparing will not be sufficient.
7. Technical rejection and buyer refusal must be treated differently
A platform rejection generally indicates a validation, formatting or routing issue that should be corrected and resubmitted.
A buyer refusal is a separate invoice lifecycle event and should not automatically result in a new invoice, credit note or internal cancellation without first analysing the reason.
8. Temporary e-reporting failures do not invalidate the transaction
Businesses should continue their commercial and accounting operations where transaction or payment data cannot temporarily be transmitted.
The missing or incorrect data must nevertheless be documented, reconciled and transmitted or corrected as soon as possible.
What businesses should do now
The message from the DGFiP is clear: companies are not expected to achieve perfect implementation from day one, but they must be able to demonstrate active preparation, controlled contingency procedures and timely corrective action.
The reform has not been postponed. Businesses should continue preparing their ERP systems, invoice processes, master data, approved platform connections and e-reporting controls for the September 2026 deadline.
Official DGFiP practical guide: https://www.impots.gouv.fr/sites/default/files/media/1_metier/2_professionnel/EV/2_gestion/290_fact…
