Factur-X diagnosis — rejected e-invoice

Since September 2026 every French company must receive structured e-invoices through an accredited platform, and issue them since 2027. The result: millions of plain-PDF invoices are rejected every week with a terse message — wrong format, missing attachment, BR-CO-10 rule violated. This diagnosis breaks the check into five layers, in the order platforms apply them: the PDF/A-3 container (metadata, colour profile), the embedded Factur-X XML (presence, relationship, syntax), the document structure (mandatory sections, MINIMUM to EXTENDED profile), the EN 16931 business rules (totals, VAT, identifiers) and the French base (SIREN/SIRET). Each layer returns a clear verdict — pass, deviation, blocking — with the faulty field (BT code) and the corrective action. The analysis runs entirely in your browser: the invoice, often sensitive, never leaves your device. The verdict is indicative: definitive compliance is judged by your platform at transmission time.

FAQ

My invoice was rejected — where do I start?

Drop the rejected file into the diagnosis: it identifies the failing layer and suggests the fix. In most rejections the cause is a plain PDF exported without any Factur-X structure.

How is this different from a validator?

A validator says “valid or not”. The diagnosis explains why an invoice was rejected: layer by layer, with the faulty field (BT code), the violated rule and the correction — built for the post-rejection moment.

Is my invoice uploaded anywhere?

No. The diagnosis runs in your browser, like every Document Flare tool. No file, no extract, no metadata ever leaves your device.

Is the verdict a compliance guarantee?

No — it is an indicative first-line diagnosis. Definitive compliance is judged by your accredited platform when the invoice is transmitted.

Which profiles are recognised?

MINIMUM, MINIMUM TTC, BASIC without lines, BASIC, EN 16931 (COMFORT) and EXTENDED, in CII syntax D16B and D22B. ZUGFeRD and XRechnung flavours are detected too.

  1. Drop the invoice your platform rejected
  2. Read the layer-by-layer report — the failing layer explains the rejection
  3. Apply the suggested correction (BT field, rule)
  4. Re-test the corrected invoice before resubmitting