Common Issues in Sending and Receiving e-Invoices in France: Errors, Causes & Solutions

France e-invoice failures usually come from one of four sources: wrong format, wrong routing data, wrong workflow handling, or wrong transmission channel. The fix depends on whether the invoice falls under Chorus Pro public-sector rules or the 2026 B2B reform.

Key Takeaways

• All businesses in France must be able to receive e-invoices from 1 September 2026.
• Large and mid-sized firms must issue e-invoices from 1 September 2026; smaller businesses follow on 1 September 2027.
• Domestic B2B invoices must use UBL, CII, or Factur-X through an approved platform, not emailed PDFs.
• The most common failure points are bad SIREN/SIRET, missing routing details, invalid mandatory fields, and API/configuration mistakes.

How French E-Invoicing Works

France’s e-invoicing system is easiest to understand when split into two channels.

Domestic B2B Reform

For invoices exchanged between VAT taxable businesses established in France, the reform introduces a platform-routed model. Businesses must be able to receive e-invoices from 1 September 2026. Issuance starts on the same date for large companies and mid-sized enterprises, while small businesses and micro-enterprises move to mandatory issuance on 1 September 2027.

This reform also sits alongside e-reporting. That means some transaction and payment data must be transmitted to the tax administration even when a transaction does not fall into the domestic B2B e-invoicing perimeter. This is one reason why scope mistakes create both operational and tax-reporting problems.

Public-Sector Invoicing Through Chorus Pro

Public-sector invoicing follows a different operational route. Chorus Pro remains the reference platform for invoices sent to administrations and public entities. It already handles submission, routing, invoice statuses, and public-sector workflow rules.

This distinction matters because many businesses diagnose the wrong problem. A supplier may assume it is dealing with a general B2B platform error when the real issue is a public-sector routing requirement inside Chorus Pro, such as a missing service code or commitment reference.

What Counts as a Compliant e-Invoice in France

A compliant French B2B e-invoice is not just a digital document. It must use an accepted structured or hybrid format, contain mandatory invoice data in dedicated fields, and be transmitted through an approved platform.

In practice, the core B2B formats are:

• UBL 
• CII 
• Factur-X 

Factur-X is especially important because it combines a human-readable PDF layer with structured XML data. By contrast, an ordinary PDF sent by email, even if generated from accounting software, does not meet the B2B reform definition of a compliant e-invoice.

That distinction is one of the most common reasons businesses think they are “already e-invoicing” when they are not.

What Causes e-Invoice Failures in France?

The most important causes sit upstream, before an invoice ever reaches the recipient’s approval workflow.

Wrong Scope or Wrong Channel

A frequent failure occurs when the invoicing team sends the right commercial transaction through the wrong legal channel. Domestic French B2B invoices, public-sector invoices, exempt transactions, and transactions that belong under e-reporting do not all follow the same operational path.

If a public recipient is involved, Chorus Pro usually governs the process. If the invoice falls under the domestic B2B reform, the sender must use an approved platform and a compliant format. Mixing those channels often leads to non-delivery, recipient confusion, or downstream VAT mismatches.

Routing and Directory Mismatches

France’s model relies heavily on routing data. For B2B reform flows, the central directory indicates which platform handles a recipient and which electronic invoicing address should be used. For public-sector flows, routing can depend on SIRET, code service, and, in some cases, legal commitment numbers.

This is why “invoice not received” often means “invoice not routable.” The sender may believe transmission succeeded, while the recipient never receives the invoice in the correct operational queue.

These issues become more common when businesses select a reception platform but fail to complete directory registration, fail to validate master data, or rely on outdated customer records.

Format and Data Quality Errors

Even when the correct channel is used, format failures remain common. The invoice may be built in the wrong syntax, contain incomplete mandatory fields, use inconsistent totals, or include invalid VAT logic.

In France, structured validation is a feature, not a bug. Platforms and recipients increasingly detect data inconsistencies before payment. That improves control, but it also means weak invoice master data is exposed much earlier than under email-and-PDF processes.

The highest-risk fields are usually:

• Supplier and customer identifiers, especially SIREN or SIRET 
• Invoice dates and numbering 
• VAT amounts and totals 
• Delivery or service-location information where required 
• Public-sector routing fields 

Workflow and API Handling Mistakes

Not every returned invoice should be treated as a rejection. In Chorus Pro, the status itself often tells you what kind of correction is needed.

A recycler usually signals a routing problem. Suspension usually points to missing supporting documents. Rejected is reserved for substantive invoice problems and often requires a new invoice number after correction.

API failures also create avoidable disruption. Many of these come from wrong environment selection, missing technical-account permissions, authentication mistakes, expired certificates in relevant modes, or payloads that do not match expected format rules.

Most Common E-Invoicing Issues in France

The issues below are the ones most businesses actually encounter during sending, receipt, and correction.

Using a PDF Process for a Transaction That Requires Structured E-Invoicing

This is the classic B2B reform mistake. A team generates a normal PDF from its ERP and emails it to the customer, assuming that digital delivery equals e-invoicing. Under the French domestic reform, it does not.

The practical result is predictable: the invoice may be rejected, ignored by the recipient’s automated intake, or remain outside the compliant transmission chain entirely.

Incorrect Recipient Identification

For public-sector invoices, wrong routing data is one of the fastest ways to block payment. A missing SIRET, wrong code service, or wrong engagement number can stop a valid invoice from reaching the correct public service.

For domestic B2B flows, the equivalent problem is stale or incomplete directory data. If the recipient’s platform or invoicing address is missing or outdated, the invoice may appear sent but still fail operationally.

Confusion Between Correctable, Suspended, and Rejected Invoice Statuses

This is one of the most costly workflow mistakes in Chorus Pro.

When a routing issue is treated as a full rejection, the supplier may unnecessarily cancel the original invoice and issue a new number. That creates extra accounting work, reconciliation noise, and payment delay. The same happens when a missing attachment is handled like a substantive invoice defect.

Good control depends on understanding the operational meaning of each status, not just reacting to any returned invoice as a rejection.

Scanned PDFs and Attachment Problems

Chorus Pro can accept certain PDF deposit flows for public-sector invoicing, but scanned PDFs are still problematic. A scanned invoice becomes an image file, which prevents reliable extraction of invoice data and forces manual re-entry.

That increases processing time and introduces new human errors in amounts, identifiers, or references. Missing attachments create a different problem: the invoice content may be fine, but the file package is incomplete, so the workflow is suspended.

Public Works Invoices with the Wrong Cadre de Facturation

Public works invoices have an additional process layer. The selected cadre de facturation identifies both the actor and the nature of the submitted document. If the wrong cadre is chosen, the invoice may enter the wrong workflow, confuse the recipient, or trigger suspension or rejection.

This issue is highly specific, but it matters because public works suppliers often focus on invoice content and overlook workflow classification.

Solutions to Common e-Invoicing Error

Use this sequence to localize a failure before reissuing an invoice.

1. Identify the channel: domestic B2B reform or public-sector Chorus Pro. 
2. Identify the stage: local creation, platform validation, routing, recipient review, or returned workflow. 
3. Read the status precisely: A recycler, Suspendue, and Rejetée do not mean the same thing. 
4. Decide the remedy: correct and resend, add documents, or cancel and reissue. 

The table below shows the most common failure patterns and the fastest corrective path.

Compliance Risks of e-Invoice Errors

Errors in France’s e-invoicing model are not just workflow inconveniences. They create legal, tax, and commercial exposure.

Legal and Tax Exposure

France has a formal penalty framework for invoice omissions, inaccuracies, and failures to comply with electronic invoicing and platform obligations. Even where the invoice problem begins as a technical issue, it can become a compliance issue if mandatory data is incomplete, numbering is mishandled, or transmission rules are bypassed.

The risk is higher when teams correct returned invoices informally, reuse the wrong invoice number after a real rejection, or let platform failures break the audit trail between invoice, transaction data, and payment data.

VAT and Audit Exposure

Structured invoicing makes master data more visible to validation engines and tax controls. If SIREN/SIRET values, VAT data, or identity details are wrong, the issue is easier to detect and harder to explain away.

For businesses using VAT on collections, payment-status reporting adds another control layer. If invoice references and payment data do not align, the inconsistency can affect reporting integrity.

Payment and Working-Capital Exposure

In public-sector workflows, delivery status matters commercially because it affects the payment timeline. If an invoice never reaches the correct recipient or is returned for correction, payment can be delayed even when the underlying goods or services were delivered properly.

This is why French e-invoicing errors should be treated as a treasury and operations issue, not only as a tax-technology issue.

Conclusion

In France, e-invoicing is becoming a control layer for VAT, master data, workflow discipline, and payment timing. Businesses that keep treating invoice failures as isolated back-office exceptions will spend more time reissuing documents, resolving disputes, and fixing avoidable compliance gaps. The better approach is operational: validate formats before sending, keep routing data current, and train teams to interpret returned statuses correctly before they create bigger tax and cash-flow problems.

Government Resources and Official Portals

The following official sources are the most useful references for mandate scope, technical rules, and operational troubleshooting.