eliDocs
/
Format Reference

Factur-X (1.09.2)

The Franco-German hybrid PDF/A-3 + CII e-invoice format — what Beliq emits across the five profiles plus the EXTENDED-CTC-FR overlay for the French B2B reform.

Factur-X is a hybrid e-invoice format that pairs a PDF/A-3 document (human-readable) with embedded UN/CEFACT CII D22B XML (machine-readable). It is jointly maintained by FNFE-MPE (France) and FeRD (Germany), and the same artefacts are published as ZUGFeRD 2.x by FeRD — the two are technically the same format under two regional labels.

Beliq validates against Factur-X 1.09.2 / ZUGFeRD 2.x (published 2026-08-04). It was announced on 2026-08-20 as a breaking ruleset bump for 2026-11-20 and brought forward to 2026-09-10, so latest resolves to it now and a document you send today is judged under it. 1.08 stays retained on the previous channel until 2027-05-16. What changed, rule by rule, is in ruleset versioning and the changelog.

Profiles

Profiles

Factur-X 1.09.2 ships five EN-16931-aligned profiles plus a French CTC overlay. All five are supported in Beliq.

Profile Beliq value What it carries
MINIMUM minimum Header-only structured data (invoice number, dates, totals). Originally aligned with Chorus Pro minimum requirements.
BASIC_WL basicwl Basic without line items — header-level data only.
BASIC basic Header data plus essential invoice lines.
EN 16931 (Comfort) en16931 Full EN 16931 compliance — recommended for most use cases.
EXTENDED extended EN 16931 plus additional EXTENDED-only fields.
EXTENDED-CTC-FR (overlay) extended-ctc-fr EXTENDED + the French B2B reform CTC overlay (BR-FR-CTC + EXTENDED-CTC-FR Schematron). The official French reference profile for the e-invoicing reform.
What Beliq emits

What Beliq emits

When you call POST /v1/generate with standard: "facturx":

  • output: "pdf" → a PDF/A-3 document with embedded CII D22B XML, attached under the standard filename factur-x.xml.
  • output: "xml" → the same CII D22B XML without the PDF envelope.

The profile field selects one of the values in the table above; verify: true (the default) runs the full profile-specific Schematron before the response is returned.

The full request schema is on POST /v1/generate, and a French curl walk-through is in the France guide.

French B2B reform — CTC overlay

French B2B reform — CTC overlay

France’s B2B e-invoicing reform requires invoices to flow through certified Plateformes Agréées (PA). Beliq generates Factur-X documents that pass the BR-FR-CTC Flux 2 Schematron and the EXTENDED-CTC-FR overlay for the reform, documented in detail in the France guide, French B2B reform section. Beliq is not a registered Plateforme Agréée (PA); transmission is handled by your PA partner.

Schematron sources

Schematron sources

For the BASIC_WL, EN 16931 and EXTENDED profiles, the per-profile Schematron and XSDs come directly from the FNFE-MPE / FeRD 1.09.2 joint pack. For the MINIMUM and BASIC profiles, FNFE-MPE distributes artefacts behind an email-request information pack; Beliq sources those two profiles from Mustangproject core-2.25.0 (Apache-2.0) — the FNFE-MPE-recommended downstream consumer that republishes the same artefacts at matching upstream tags. The exact pin is recorded with SHA-pinned per-file paths (see France guide — MINIMUM and BASIC — secondary source for the full disclosure).

Validation pipeline

Validation pipeline

Every Factur-X document Beliq generates or validates passes through:

  1. CII D22B XSD — structural validity, including the per-profile XSD subset where applicable.
  2. The Schematron arm the document’s CustomizationID selects. MINIMUM, BASIC_WL, BASIC and EXTENDED declare a URN carrying a factur-x.eu fragment and run the Factur-X 1.09.2 profile Schematron (FNFE-MPE / FeRD or Mustang per profile, as above). The EN 16931 profile declares the bare urn:cen.eu:en16931:2017, which a plain EN 16931 CII document carries too, so it runs the generic EN 16931 Schematron instead.
  3. France BR-FR-CTC Flux 2 Schematron — only when a Flux 2 BusinessProcess code (S8 / B8 / M8) is present or franceCtc=true is requested.
  4. France EXTENDED-CTC-FR Schematron — additionally when (3) applies and the document is in the EXTENDED profile.

The EN 16931 profile is the default when no profile is given, so it is the common path. The rulesetArtifacts on your response names the arm that ran; GET /v1/rulesets publishes the pins those artefacts come from.

For output: "pdf", the engine also runs Mustang to embed the XML and VeraPDF to validate the PDF/A-3b envelope. Pinned versions are on the validation artifacts page.

What Beliq does NOT do

What Beliq does NOT do

  • Operate a Plateforme Agréée (PA). Beliq’s Factur-X output is given to your PA partner for transmission.
  • Implement the AIFE Annuaire (recipient lookup), CDAR message envelope, or e-reporting flows (Flux 8 / 9 / 10).
Related