AIFE’s Third RFE Launch-Monitoring Update: Volumes Rise, Errors Persist

• AIFE’s first three weeks of the French e-invoicing reform showed strong uptake: 8.38 million compliant F1 files and 7,488 compliant e-reporting (F10) files were received, with most platforms now above a 90% compliance rate; 63% of large enterprises and 41% of mid-sized enterprises have already issued an e-invoice flow.
• Main rejection causes were duplicate filings, missing mandatory fields, VAT inconsistencies, invalid SIREN numbers, and a platform error that incorrectly used F10 tags in F1 flows; for F10, major issues included missing StartDate data, non-standard codes, formatting errors, and credit note rule breaches.
• If a platform offboards a company’s last active directory line, the company can be left without a valid directory entry; AIFE recommends recreating a default SIREN-level line on platform 9998 effective D+1 after hiding any future-dated line, unless the move is a portability case under SIM.
• For F2 lifecycle messages, a “rejected” status itself may be rejected if source tags are non-compliant; platforms should verify required mappings first and send an inadmissibility notice to the issuer instead of a lifecycle rejection status.
• B2G invoicing through the new platform channel is progressing, but G2B connection to Chorus Pro remains mandatory and still incomplete for many platforms, with pending invoices held up for unconnected PAs; production testing must be done in QUAL, not PROD, and repeated major non-compliance can lead to temporary suspension.

Source: docnova.ai

Note that this post was (partially) written with the help of AI. It is always useful to review the original source material, and where needed to obtain (local) advice from a specialist.

---

---