Rejected E-Invoices: Causes, Fixes, and Impact on Payment

Key takeaways

• A "rejected" status means your certified platform blocked the invoice before transmission: your client never received it, and the payment deadline has not started running.
• A standard PDF sent by email is not an electronic invoice under the reform: only UBL, CII or Factur-X (a hybrid PDF/XML e-invoicing format) formats are accepted; an unstructured PDF is rejected.
• The number one cause of rejections during rollout is not technical: it's a missing, incorrect or inactive recipient SIREN (the French business registration number).
• Rejection cancels neither the debt nor the claim: a "rejected" status describes a transmission incident, it does not determine whether the service was performed or whether payment is due.

Why was my PDF invoice rejected?

Because a PDF, however flawless it looks, doesn't contain the structured data the platform needs to read. An electronic invoice contains machine-readable data (Factur-X, UBL); a plain PDF doesn't meet that standard. The whole pathway has changed: no domestic B2B invoice travels directly between two companies anymore. Every document now passes through platforms registered by the government, which simultaneously forward the tax data to the DGFiP (Direction générale des finances publiques, the French tax authority).

Before sending, the platform runs a battery of checks: technical format, mandatory fields, absence of duplication with an invoice already processed. If any of these checks fails, the platform must reject the invoice and flag it as "Rejected," with a mandatory reason attached. This status is sent to the tax authority and made available to the seller, but never to the buyer, since the buyer never received the invoice in the first place.

In other words: no one will chase you about it. It's up to you to monitor your statuses.

A rejected invoice isn't a late invoice, it's an invoice that doesn't yet exist for your client.

What should I do in the hour after a rejection?

Read the rejection reason, fix it at the source, resubmit. In that order, and without waiting until month-end.

The reason code is standardized and points to the cause. The most common ones are a format that doesn't comply with the core standard (Factur-X, UBL, CII), missing or incorrect mandatory fields, a recipient not found in the central directory, an incorrect SIREN or VAT number, or an unreadable file. The tax authority also cites identification errors on either party's side and routing difficulties.

Take an accounting firm of 40 people billing 300 clients a month. If one client's SIREN is mistyped in the system, it's not one invoice that fails, it's twelve a year for that client, and none of them get paid. The useful fix happens in the client record, not in the document itself.

If cash flow is at stake, there's a safety valve. A copy can be sent temporarily through another channel to keep business running, provided this exceptional transmission is clearly linked back to the invoice in question, to avoid any double processing. This is a stopgap, not a working method. The company must in any case limit how often these incidents recur and demonstrate an active effort toward compliance.

Rejection or refusal: what's the difference, and who has to act?

Rejection comes from the machine, refusal comes from your client. Confusing the two costs days. Treating one as the other wastes time. Rejection is issued by the platform during automated checks: the invoice is never transmitted to the recipient and must be corrected and resubmitted.

A "refused" status, by contrast, means the buyer has disputed the invoice and sent a reason to the supplier; depending on how far processing has gone, the fix is either a corrective invoice or a credit note. The right to dispute an invoice hasn't disappeared with digitalization: Article L441-9 of the French Commercial Code still guarantees the right to refuse a document that doesn't match the contractual terms.

On the buyer's side, a good reason code looks like this: "Net amount of €3,200 instead of €2,800 per quote no. 2026-0142 dated 15/03/2026."

Can my client refuse to pay because the invoice was rejected?

No, not on the basis of the status alone. A "rejected," "in error," or "not delivered" status describes an incident in the transmission chain; on its own, it doesn't determine whether the sale went through, whether the service was performed, or whether payment is due. Symmetrically, the supplier can't simply claim that their platform sent the file and leave it at that.

Evidence remains a matter of free proof. In a recent case, the court ruled that proof that a commercial service was performed is not subject to any particular form and can result from any evidence capable of convincing the judge, with the expected sign-off able to be given by any method that identifies its author and guarantees the integrity of the validation (Bordeaux Court of Appeal, 4th commercial chamber, 20 May 2026, no. 25/01502).

In practice: keep the purchase order, the validation email, the delivery confirmation. That's also why a reliable audit trail on your document flows is worth more than a folder full of PDFs.

How much is really at stake in case of non-compliance?

Fines tripled in February 2026, but the immediate risk remains cash flow. Article 123 of the 2026 Finance Act raises the fine per invoice not issued in electronic format from €15 to €50, with the annual cap staying at €15,000 per company per calendar year. The fine for failing to transmit transaction and payment data (e-reporting) rises from €250 to €500 per breach.

For lacking a platform altogether, the penalty escalates. Failing to use a certified platform to receive your invoices triggers a formal notice; without correction within 3 months, the fine is €500, then €1,000 per additional quarter. That's a maximum exposure of roughly €3,500 over a year.

Worth noting on the buyer's side too: a non-compliant invoice weakens the right to deduct VAT, which the tax authority can challenge during an audit.

Finally, the rollout year is lenient, but conditionally so. The DGFiP stated in its July 2026 practical start-up guide that no penalty will be applied to companies facing implementation difficulties, provided they are genuinely on track toward compliance, the authority distinguishing these cases from inaction or persistent refusal; this leniency is neither a postponement nor a suspension of the obligation. So keep a record of your efforts: platform choice, correspondence with your provider, connection timeline.

How can I avoid the next rejection?

By cleaning up your client database before touching the file format. In the vast majority of cases, the cause isn't technical but related to data quality: missing or incorrect SIREN, recipient not found in the directory, missing mandatory field, inconsistent VAT rate, non-compliant format, duplicate numbering.

Four concrete steps:

1. Check every client's SIREN against the official source and make the field mandatory in your software. An invalid SIREN prevents address resolution in the directory: the invoice is rejected on submission or lands on the wrong platform, the client never receives it, and therefore never pays it.
2. Add the new mandatory fields. Decree no. 2022-1299 adds four mandatory fields: the client's SIREN, the delivery address if it differs from the billing address, the transaction category (goods, services, or mixed), and the option for VAT payment based on cash receipts (débits).
3. Don't trust appearances. A number typed into the text area of the PDF but missing from the underlying XML file triggers a rejection, even though the document looks complete on screen. That's the whole logic behind the hybrid Factur-X format.
4. Test before going live. Run every file through a validator before your first production use. Your platform's validation rules and the standard's rules don't fully overlap: a file can be perfectly valid under EN 16931 and still get rejected under French-specific rules.

Sygnet works on automated extraction and verification of accounting documents, including reconciliation between received invoices and client records; more detail is available on its e-invoicing in France page.

FAQ

Can I still send my invoices as PDFs by email to my business clients?

No, not as an invoice. A plain PDF sent by email doesn't meet the requirement. The invoice must go through the public portal or a certified platform; direct email sending is not accepted. You can still send a courtesy copy to your contact, but the legally valid document is the one that goes through the platform.

My client isn't set up for this: should I keep sending them a PDF?

The lack of readiness is on their end, not yours. A buyer who isn't set up cannot demand a paper or PDF invoice, nor can they issue a "Refused" status, since they aren't connected to a platform. Remind them of the deadline: since 1 September 2026, every VAT-registered company established in France must be able to receive electronic invoices, regardless of size.

Do I need to issue a credit note for a rejected invoice?

No. A rejected invoice never reached its recipient: you correct the data and resubmit. Rejection doesn't mean the invoice is cancelled or that the business relationship is called into question. A credit note or corrective invoice applies to cases of refusal by the client, depending on how far processing has gone.

How much time do I have to make the correction?

No specific administrative deadline is set, but the intent behind the system is clear: since 1 September 2026, a rejection must be treated as a technical or functional incident, not as grounds to halt invoicing for an extended period. The real clock that matters is the payment one: as long as the status remains "rejected," your contractual payment deadline hasn't started running.