AFNOR Factoring Status Codes 225–228 and Post-Emission Creditor Change Mechanics Under the French E-Invoicing Mandate
The AFNOR Commission's 2026 e-invoicing compliance framework introduces four distinct status codes (225–228) to govern factoring arrangements, addressing a structural mismatch between creditor subrogation timing and the French mandate's invoice immutability rule. These codes are critical for approved platforms (PAs) and vendors navigating the mandatory B2B e-invoicing regime effective September 1, 2026.
Key takeaways
- The AFNOR Commission published 44 use-case scenarios for 2026 e-invoicing compliance, including factoring as use-case #10.
- Four AFNOR-defined status codes (225–228) govern factoring workflows, addressing the timing mismatch between creditor subrogation and invoice emission.
- Approved platforms must handle all four status codes to ensure compliance with the French e-invoicing mandate effective September 1, 2026.
- Vendors must hold an active factoring contract before declaring a cession via lifecycle status update on an approved platform.
- The confidential/non-confidential distinction (codes 226 vs. 225) is the primary operational decision point for vendors and their platforms.
Context
Among the 44 use-case scenarios published by the AFNOR Commission for 2026 e-invoicing compliance, use-case #10 (affacturage/factoring) presents a technically distinct workflow that has received limited coverage in trade press. The core complexity arises from a structural mismatch: creditor subrogation in factoring arrangements occurs post-emission rather than at invoice creation, yet the French mandate prohibits modification of emitted invoices. This tension is resolved through a lifecycle status update mechanism governed by four dedicated AFNOR status codes (225–228), which approved platforms must implement and manage.
The French e-invoicing mandate, effective from September 1, 2026, requires all B2B invoices to be issued and received through approved platforms. These platforms handle transmission, control, and tracking of invoices. The immutability rule for emitted invoices is a hard constraint that shapes the entire workflow, necessitating that all factoring changes are recorded exclusively as lifecycle status updates rather than as new or amended invoices.
Status Code Mechanics
The four AFNOR-defined status codes governing factoring workflows are:
- Status 225 (non-confidential factoring): Triggers transmission to the buyer of the factor's SIREN number, role code 'DL', email address, and new bank details (IBAN, BIC, and account holder name). The buyer and their approved platform are notified.
- Status 226 (confidential factoring): The cession is recorded on the seller's side and on the approved platform but is NOT transmitted to the buyer or the buyer's approved platform. This preserves commercial confidentiality of the factoring arrangement.
- Status 227 (payment account change only): Records a change to payment account details without a full creditor subrogation notification.
- Status 228 (cancellation): Records cancellation of a factoring arrangement.
These status codes address the timing mismatch between creditor subrogation and invoice emission, ensuring compliance with the immutability rule. The confidential/non-confidential distinction (codes 226 vs. 225) is the primary operational decision point for vendors and their platforms.
Operational Prerequisites and Platform Obligations
A vendor must hold an active factoring contract with the factor before declaring a cession via lifecycle status update on an approved platform. Approved platforms became mandatory intermediaries for B2B invoice emission and receipt as of the Phase 1 reception requirement effective September 1, 2026.
Because emitted invoices cannot be modified post-hoc, all factoring changes are recorded exclusively as lifecycle status updates rather than as new or amended invoices. Platform readiness to handle all four status codes is a compliance prerequisite ahead of the September 1, 2026 deadline.
Implications for Draft Writers
The confidential/non-confidential distinction (codes 226 vs. 225) is the primary operational decision point for vendors and their platforms. The immutability rule for emitted invoices is a hard constraint that shapes the entire workflow.
Platform readiness to handle all four status codes is a compliance prerequisite ahead of the September 1, 2026 deadline. Vendors must ensure that their approved platforms are capable of managing these status codes to avoid compliance issues.
Outlook / What to Watch
As the September 1, 2026 deadline approaches, vendors and approved platforms must prioritize the implementation of the AFNOR status codes for factoring arrangements. Future developments may include additional use-case scenarios or refinements to the existing status codes based on industry feedback and operational experience.
Open questions remain about the practical implementation of these status codes, particularly regarding the handling of confidential factoring arrangements and the management of payment account changes. Monitoring the AFNOR Commission's updates and industry best practices will be crucial for ensuring ongoing compliance.
Frequently asked questions
- What are the four AFNOR-defined status codes for factoring arrangements?
- The four status codes are 225 (non-confidential factoring), 226 (confidential factoring), 227 (payment account change only), and 228 (cancellation). These codes govern the specific mechanics of factoring arrangements under the French e-invoicing mandate.
- Why is the immutability rule for emitted invoices important in factoring arrangements?
- The immutability rule prohibits the modification of emitted invoices, necessitating that all factoring changes be recorded as lifecycle status updates rather than as new or amended invoices. This rule ensures the integrity and traceability of financial transactions.
- What operational prerequisites must vendors meet before declaring a cession via lifecycle status update?
- Vendors must hold an active factoring contract with the factor before declaring a cession via lifecycle status update on an approved platform. This prerequisite ensures that the factoring arrangement is valid and legally binding.
- How do approved platforms handle factoring arrangements under the French e-invoicing mandate?
- Approved platforms act as mandatory intermediaries for B2B invoice emission and receipt, handling transmission, control, and tracking. They must implement and manage the four AFNOR status codes to ensure compliance with the mandate.
- What are the implications of the confidential/non-confidential distinction in factoring arrangements?
- The confidential/non-confidential distinction (codes 226 vs. 225) is the primary operational decision point for vendors and their platforms. It determines whether the factoring arrangement details are transmitted to the buyer or kept confidential.
