Check Factur-X invoices (PDF or XML) against EN 16931 and the French réforme requirements — SIREN, SIRET, VAT. No upload.
Factur-X is the Franco-German standard for hybrid e-invoices: a PDF/A-3 with embedded CII XML, developed by FNFE-MPE (France) and FeRD (Germany). Technically identical to ZUGFeRD 2.x, Factur-X is one of the core formats (“socle”) of the French e-invoicing réforme — alongside UBL and CII.
France requires every company to receive e-invoices from September 1, 2026; large and mid-size companies must issue from the same date, small companies follow in 2027. Unlike Germany, exchange runs through accredited platforms (PDP) — formal correctness decides whether an invoice is accepted at all.
Beyond EN 16931, the réforme demands French identifiers: the seller’s SIREN/SIRET, from 09/2026 the buyer’s SIREN, and consistent VAT numbers (FR + 2 check characters + SIREN). Billhorse implements exactly these checks (BH-FR-01 through BH-FR-05) — with explainer pages in French, German and English.
If your product has customers in France, Factur-X is not optional. The browser validator is the quick check; the developer API brings the same validation into your pipeline — including ?lang=fr, so your French end users see error messages in their language.
From September 1, 2026, every French company must be able to receive e-invoices; large and mid-size companies must also issue from that date. Small companies (PME/TPE) follow on September 1, 2027. Exchange happens through accredited platforms (PDP).
Yes — for invoices from French sellers it checks SIREN/SIRET (format and consistency), the VAT number format (FR + 2 characters + SIREN) and, from 09/2026, the buyer SIREN. Rules BH-FR-01 through BH-FR-05 each have their own explainer page.
Yes — since ZUGFeRD 2.0 both are technically identical: a PDF/A-3 with embedded CII XML. A correctly generated Factur-X works in both countries, which is exactly why Billhorse covers both rule sets.
No. Extraction and validation run as WebAssembly entirely in your browser — safe to use with real invoice data.
Validation and parsing as a developer API: same engine, normalized JSON, messages in three languages. Self-hosted available.
Explore the API