Since 1 September 2026, VAT-taxable businesses established in France and covered by the reform must be able to receive electronic invoices. Large and mid-sized companies must also issue them for in-scope domestic B2B transactions. SMEs and micro-companies follow on 1 September 2027. Statutory exclusions still apply.
That changes what an invoice error costs. A PDF with a typo used to reach the customer anyway. Now electronic invoices pass through an accredited platform (plateforme agréée, PA) that runs automated invoice controls. If validation fails, delivery can be blocked before the customer’s accounts payable team sees the document, delaying approval and payment.
This guide covers the most common electronic invoice errors in France, why they happen, and how to stop them before they hurt your cash flow.
How invoice control works in France
An invoice travels from your platform to your customer’s platform, with the central directory (annuaire) used to identify the recipient’s electronic address. It can encounter two different outcomes:
- Rejected (status 213, “Rejetée”): a platform stops the invoice during technical validation, before it is made available to the customer.
- Refused (status 210, “Refusée”): the invoice was delivered, but the customer refuses it for a business reason, such as a wrong VAT rate, an incorrect total, a duplicate or a missing order number. A reason code accompanies the refusal.
A rejection is an incident to resolve, rather than automatic cancellation of the invoice or the underlying commercial debt. Identify the cause, correct the electronic document as appropriate and resend it with a clear audit trail. Keep the rejection message, the correction and exchanges with your customer or provider.
The most common causes of electronic invoice rejection fall into five groups.
1. Format and syntax errors
France’s core exchange formats are UBL, UN/CEFACT CII and Factur-X, using EN 16931 and the applicable French specifications. A structurally invalid file can be rejected before its business data is processed. See our Factur-X, UBL and CII format comparison for the differences.
Common Factur-X validation errors
- The PDF does not meet the required PDF/A-3 packaging rules.
- The XML is missing, or its file name and embedding relationship do not match the relevant Factur-X specification.
- The selected profile does not provide the structured data needed for the intended exchange. EN 16931 or EXTENDED is a practical choice for full structured invoice data; confirm any lighter-profile or transitional route with your PA against current French specifications.
- The visible PDF and embedded XML disagree. Generate both from the same source data and preserve their consistency to avoid validation problems and disputes.
Common UBL errors
- The XML fails schema validation: wrong element order, missing required tags or invalid namespaces.
- The CustomizationID or other profile identifiers do not match the applicable specification.
- Code lists are wrong: invalid invoice type, currency, unit of measure or country codes.
- Dates are not in the required format (YYYY-MM-DD), or numeric precision does not meet the relevant rules.
2. Missing mandatory invoice data
Existing legal invoice requirements still apply, including the invoice number, issue date, party identification, applicable VAT details and amounts. The reform introduces four additional mandatory mentions, where applicable:
- The customer’s SIREN number.
- The delivery address, if it differs from the billing address.
- The nature of the operation: goods, services or both.
- The “VAT on debits” mention, if the supplier has opted for that VAT accounting method.
These requirements follow the issuance timetable: 1 September 2026 for large and mid-sized companies, and 1 September 2027 for SMEs and micro-companies. Missing mandatory invoice data can lead to validation failures, and older ERP templates often lack fields for the new mentions.
3. Business rule and calculation errors
A file can be correctly formatted and still fail EN 16931 or French business rules. Typical problems include:
- Line totals do not reconcile with the invoice net total.
- The total including VAT does not equal the net total plus VAT, adjusted for applicable charges and allowances.
- The VAT breakdown is incomplete or VAT does not reconcile with its taxable base.
- A VAT exemption is used without the required exemption reason or code.
- Rounding differs between line level and document level.
- A credit note omits a required reference to the original invoice, where applicable.
Some errors trigger platform rejection; others lead to customer refusal. The outcome depends on the applicable validation rule and the customer’s checks.
4. Identification and routing errors
The invoice must reach the right company on the right platform. Delivery can be blocked when:
- The buyer’s SIREN is wrong or missing.
- The electronic address or routing identifier is incorrect or outdated.
- The recipient’s platform registration or directory entry is not ready.
- The invoice is addressed to the wrong entity within a group, such as the parent instead of a subsidiary.
- Duplicate invoice checks flag an existing invoice number.
Routing problems are not always caused by the sender. If the issue sits with the recipient’s platform or directory entry, contact your provider or customer instead of repeatedly resending the same file.
5. Customer-side refusal reasons
Some issues are only caught by the customer. Common refusal reasons include an unknown transaction, an incorrect or missing purchase order number, a missing contract reference, double invoicing or an ended contract. If customers rely on PO matching, make their required order references part of your invoicing process.
How to prevent electronic invoice rejection: a checklist
- Validate every file against EN 16931 and the applicable French rules before sending.
- Choose an appropriate Factur-X profile and generate the PDF and XML from the same data.
- Update invoice templates with the four new mandatory mentions, where applicable.
- Check customer SIRENs and electronic addresses against the directory, and clean master data.
- Recalculate totals and VAT breakdowns automatically and check rounding.
- Require PO numbers and contract references where customers need them.
- Monitor rejected, refused and disputed lifecycle statuses daily.
- Keep a record of every rejection, its cause and the corrected electronic document.
Frequently asked questions
What is the difference between a rejected and a refused invoice?
A rejected invoice (status 213) is stopped by a platform during validation, before it is made available to the customer. A refused invoice (status 210) was delivered but the customer declined it for a business reason, with a reason code.
Is a rejected invoice legally issued?
Rejection means the electronic delivery or validation has failed. It does not by itself cancel the underlying transaction or commercial debt. Diagnose the cause, correct and resend through the electronic channel with traceability; do not assume automatic cancellation or create an unlinked duplicate.
Can I send a PDF by email if my e-invoice is rejected?
DGFiP’s practical guidance provides for a temporary copy through another channel when an incident blocks access or payment, with clear links to the original invoice to prevent duplicate processing. This does not replace resolving the incident and completing the required electronic exchange.
Which formats are accepted in France?
The core formats are UBL, UN/CEFACT CII and Factur-X, subject to the applicable EN 16931, French and platform requirements. Check the exact version and profile supported by your PA.
Are there penalties for invoice errors?
Penalties can apply to failures to meet electronic invoicing obligations. A technical rejection and a failure to issue electronically are not automatically the same situation. Document incidents, corrective action and exchanges with your provider, and follow current DGFiP guidance for the circumstances concerned.
Stop errors before they reach the platform
Most electronic invoice errors in France are preventable: they come from outdated templates, incomplete master data or files that were never validated before sending. A compliance platform such as Docnova helps check format, mandatory data and business rules before transmission, so teams can fix problems earlier.
If your invoices originate in SAP, explore SAP integration with an Approved Platform to keep validation and status feedback connected to your ERP. For the wider French reform, read our guide to e-reporting transactions in France.