France E-Invoice Reception Lint

It reads a Factur-X, UBL or CII invoice XML open in your editor and runs 12 checks for the mentions a French platform rejects on. It verifies the Luhn check digit of the seller and buyer SIREN, recomputes the FR intra-EU VAT key from the SIREN, re-adds BT-109 plus BT-110 against BT-112, and reports every failure with a line number.

Developers who generate invoice XML for French companies: billing engineers at SaaS vendors invoicing France, ERP and accounting-software integrators wiring up a PDP, and teams porting a German XRechnung mapping to France. If you have never had to print the 40 EUR recovery indemnity on an invoice, this is the tool that tells you that you must.

A free EN 16931 validator checks the European semantic model. France added mandatory mentions on top of it: the buyer SIREN, the delivery address, the category of operation, and the VAT-on-debits option. A chatbot will list those mentions but will not recompute a Luhn check digit, a mod-97 VAT key, or your totals — and a PDP recomputes all three.

Free, with no key: check the invoice open in the editor against all 12 rules and get every finding with its line number. That is a complete answer for that file. The licensed part is scope, not depth: sweep every invoice in the workspace and write one dated reception-readiness report. Same rules, more files.

An e-invoicing integrator bills about 95 US dollars an hour to map and re-test one invoice profile, and a rejected invoice comes back for a human to re-issue. CGI article 1737 fines 15 EUR per missing or wrong mandatory mention, with an annual cap of 15000 EUR. The licence is 29 US dollars once.