French e-invoicing: six weeks after go-live, what the field shows

Non-compliant flows, rejections that do not always come from the invoice, standards that keep changing, corrections through credit notes or corrective invoices: what the first weeks of the French reform show, and what to put in place.

The French e-invoicing reform went live in September 2026. Six weeks later, the first real flows give a clear picture of where companies struggle — and it is rarely where they expected.

What the field shows

10 to 20 % of flows were non-compliant in the first week. Depending on the day, a large share of the flows received did not meet the rules: mandatory fields, identifiers, VAT categories… ERP output is rarely compliant on the first try.
A rejection does not always mean a non-compliant invoice. The directory (annuaire), addressing or the interconnection between Plateformes Agréées (PA, the certified e-invoicing platforms) can be the cause. Fixing the invoice is pointless if the problem is the recipient’s address or the buyer’s platform.
Standards and Schematrons keep changing. Today’s validation rules are not those of go-live, and they will change again.
A rejected or refused invoice is corrected with a credit note or a corrective invoice, under a new number. You do not simply resend the same invoice: a new document is needed, consistent with the accounts.
No penalties in 2026. This is the time to make the flows reliable, not to wait.

The Plateforme Agréée carries your invoices — the rest is yours

The PA handles the regulated transport. Everything else stays with you:

Produce a compliant UBL from your ERP, with the required mentions and identifiers.
Check it before sending: XSD, Schematron, the French rules of the XP Z12-012 standard, and the recipient’s presence in the directory.
Understand rejections: tell compliance, addressing, PA interconnection and business refusals apart, because each needs a different action.
Track the lifecycle, mandatory and optional statuses, and carry out the expected action at each step: payment received, credit note, corrective invoice…
File e-reporting for transactions that do not go through domestic B2B e-invoicing.
Keep the proof: source document and UBL archived, every send and every correction traced.

How NomaUBL handles it

NomaUBL sits between your ERP and your Plateforme Agréée and takes care of exactly these points:

XP Z12-012 V1.4 validation and a directory check before every send.
Rejections classified by cause — compliance, addressing, interconnection, business refusal — with the matching corrective action.
The full lifecycle, mandatory and optional statuses, and the actions to take for each status (payment received, credit note, corrective invoice…).
Validation rules kept up to date whenever the standards change.
Source and UBL archived, every send and every correction traced.
The PA is a setting: you can switch platforms without rebuilding everything.
Missing data completed by SQL or API rules, without touching your ERP.

NomaUBL adapts to what you already run — JD Edwards, SAP, NetSuite or a custom ERP — and every installation is single-tenant: on your servers, or hosted by Nomana-IT on OCI or AWS.

To see it all in 1 min 40, watch the presentation video (in French) on the NomaUBL page.

It is not too late

Started with a solution that does not cover everything? With no penalties in 2026, now is the time to make your flows reliable. Let’s talk.