French B2B E-Invoicing: Arrhes Exempted Under AFNOR Use Case #24

Context

The upcoming French e-invoicing mandate, part of the EU's broader digital transformation efforts, will require all B2B transactions to be processed through France's Portail Public de Facturation (PPF) or an authorized private e-invoicing platform. However, AFNOR use case #24 introduces a nuanced exception: arrhes—a specific type of advance payment—do not fall under this requirement.

This distinction is legally significant. Under French civil law, arrhes serve as a penalty clause in contractual agreements, allowing either party to withdraw from the contract with forfeiture of the advance. This differs from acomptes, which are simple prepayments without penalty provisions. The AFNOR framework's exclusion of arrhes from e-invoicing obligations stems from their distinct legal treatment as a contractual mechanism rather than a standard payment.

What's Changing

Arrhes vs. Acomptes: Legal and Compliance Distinctions

The exclusion of arrhes applies only when the advance payment meets the legal definition under French civil law. Businesses must ensure they correctly classify transactions to avoid misapplying the exemption.

• Arrhes: Penalties apply if either party terminates the contract. The payer forfeits part or all of the advance, while the recipient must refund double the amount.
• Acomptes: No penalty applies; these are straightforward prepayments toward future invoices.

Misclassifying acomptes as arrhes could lead to compliance risks, as the former remain within the e-invoicing mandate.

Scope Boundaries and AFNOR Use Case #24

AFNOR use case #24 serves as the current reference for determining which transaction types fall within France's mandatory e-invoicing perimeter. The exclusion of arrhes is a deliberate boundary, ensuring that businesses are not required to issue structured e-invoices for these transactions.

This exemption does not, however, create a general exception from the regime. Businesses must still process all other B2B transactions through approved platforms, such as the PPF or authorized private solutions.

Implications for Businesses

Correct Classification of Transactions

The primary compliance challenge is distinguishing between arrhes and acomptes. Businesses that frequently collect advance payments must:

1. Review Contractual Agreements: Ensure that any advance payment with penalty clauses is correctly classified as arrhes.
2. Update Invoicing Systems: Modify workflows to flag arrhes as out-of-scope for e-invoicing, while routing all other B2B transactions through the mandatory system.
3. Train Staff: Educate finance and accounting teams on the legal differences between arrhes and acomptes to avoid misclassification.

Legal Risks of Misapplication

Incorrectly classifying acomptes as arrhes could result in penalties for non-compliance with e-invoicing requirements. Conversely, treating arrhes as acomptes—and thus subjecting them to e-invoicing—would unnecessarily complicate workflows without legal justification.

Businesses should consult with legal and tax advisors to ensure proper classification of advance payments under French civil law.

Outlook

Near-Term Milestones

• September 1, 2026: The mandatory B2B e-invoicing regime takes effect.
• Ongoing AFNOR Review: Future updates to use case frameworks may refine scope boundaries, including potential adjustments to advance payment classifications.

Open Questions

1. Regulatory Clarity: Will additional guidance be issued to clarify the treatment of hybrid advance payment structures that blend elements of arrhes and acomptes?
2. Audit Practices: How will French tax authorities audit businesses to ensure proper classification of advance payments?

Second-Order Effects

The exclusion of arrhes could prompt businesses to reconsider their use of advance payment structures in B2B contracts. Some may prefer acomptes to streamline invoicing processes, while others may retain arrhes for contractual flexibility.