Key points from AIFE’s third launch-monitoring update on 22 September 2026
Three weeks after the launch of the electronic invoicing reform (RFE) on 1 September 2026, AIFE shared an initial data-based assessment and several operational points of attention with the Accredited Platforms (PA). The momentum is positive, but avoidable errors are still weighing on volumes.
Volumes and Compliance
Between 1 and 21 September, nearly 8.38 million compliant F1 files were received by the PPF. According to AIFE, compliance is improving, and the vast majority of PAs have a rate above 90%. For e-reporting (F10), the cumulative total reached 7,488 compliant files, with a clear acceleration linked to declarations covering completed periods, particularly August, and the opening of the September ten-day period on the 11th. Finally, 63% of large enterprises (GE) and 41% of mid-sized enterprises (ETI) have already issued an electronic invoice flow.
Main Errors
From 18 to 20 September, most F1 rejections (142,923 failed files) came from a single PA that used F10 tags in F1 flows. Apart from this anomaly, the main reasons were duplicates (failure of the uniqueness check), missing mandatory data (BT-22, BT-31, BT-47, BT-119 to BT-121), VAT inconsistencies and invalid SIREN numbers. For F10, the anomalies mainly concerned data completeness, including 839 failed files linked to a missing StartDate (TT-17/TT-89) for the same PA. These were followed by codes outside the reference standards (ISO 3166, UNTDID 2475 and units of measure), formatting errors and business rules relating to credit notes.
Directory Point of Attention
When a PA closes a company’s last active line, for example following contract termination, the company is left without a directory line. This causes technical rejections and makes it more difficult for a new PA to take over. The recommended practice is to recreate a default line at SIREN level with platform 9998, effective on D+1, after hiding any future-dated line. This process applies only to offboarding without a new PA; portability follows the SIM process.
F2 Lifecycle
An F2 lifecycle status marked “rejected” is itself rejected by the PPF if the source tags are not compliant. PAs must therefore check the MDT-2/BT-23, MDT-87/BT-1, MDT-91/BT-3, MDT-100/BT-2 and MDT-129/BT-30 mappings beforehand. In the event of non-compliance, they must send an inadmissibility notice to the issuing client rather than a lifecycle status.
B2G and G2B
25,331 B2G invoices were transmitted through 10,610 flows via the new PA channel, currently distributed across 6 PAs. On the G2B side, connectivity is stagnating: only 63 of 150 PAs are connected to Chorus Pro, compared with 62 one week earlier. From 18 to 20 September, 310 submitted invoices remained pending for 28 unconnected PAs, which will be contacted by AIFE. Connection to Chorus Pro is mandatory.
Reminders and Expectations
- PROD is not a sandbox: flows must first be tested in QUAL. Particular attention must be paid to the environment code (QUAL: 10, PROD: 09) and the FULL/BASE profiles. Temporary connection suspensions may be imposed in the event of repeated major non-compliance.
- A three-day precautionary period applies to the effective start and end dates of directory lines.
- Flow batching is mandatory. Sending must be triggered when the last flow is more than one hour old or the maximum number of objects has been reached (F1: 1,000, F6: 2,000, F10: 100, F13: 1). Other limits are 1 GB per flow, less than 100 MB per file, and 1,000 flows per hour per sender.
- PAs using SFTP must retrieve their OUTBOX regularly and in full, or their connection sessions may be throttled.