Factur-X examples

Example invoices of every Factur-X profile, from MINIMUM to EXTENDED, and the FNFE-MPE examples for the French e-invoicing reform, in CII and UBL. Download the XML, turn a CII example into a Factur-X PDF with the XML inside, or open it in the validator to see what each rule checks

The French reform (FNFE-MPE examples)

  • Factur-X EN 16931 invoice

    FNFE-MPE use case 1: the SIREN, the billing mode and the legal mentions the BR-FR rules ask for

    XML Validate
  • UBL invoice

    The same use case 1 in UBL

  • UBL credit note

    Use case 1 as a credit note: type code 381 and the invoice it corrects

  • Factur-X EXTENDED-CTC-FR invoice

    FNFE-MPE use case 13, with the French EXTENDED rules

    XML Validate
  • EXTENDED-CTC-FR invoice in UBL

    Use case 13 in UBL

  • Factur-X BASIC WL invoice

    A BASIC WL invoice of the FNFE-MPE examples, without lines

    XML Validate

Factur-X / ZUGFeRD profiles

  • MINIMUM

    The header and the totals only; Germany does not count it as an e-invoice

    XML Validate
  • BASIC WL

    The header, the parties and the totals, without lines; Germany does not count it as an e-invoice

    XML Validate
  • BASIC

    With lines, a subset of EN 16931

    XML Validate
  • EN 16931 (COMFORT)

    The full EN 16931 data, the usual profile

    XML Validate
  • EXTENDED

    EN 16931 and further fields, for invoices it cannot hold

    XML Validate

The examples come from FNFE-MPE (Apache License 2.0) and the akretion/factur-x library, the credit note from us. The PDFs are laid out in your browser, with the XML inside

What the examples are

The French reform examples are FNFE-MPE's for the XP Z12-012 standard: use case 1, an invoice with the SIREN, the billing mode (BT-23) and the legal mentions the BR-FR rules ask for, and use case 13, under the EXTENDED-CTC-FR rules, each in CII and UBL. The credit note is use case 1 turned into one by us, as FNFE-MPE publishes no UBL credit note. The profile examples, one per profile of Factur-X 1.09, come with the akretion/factur-x library.

The PDF Factur-X button lays a CII example out on A4 pages as a PDF/A-3 file and attaches the XML as factur-x.xml, in the profile the XML names, as the e-invoice viewer does. To write a Factur-X invoice of your own, use the e-invoice generator.

The profiles

  • MINIMUM and BASIC WL: the header and the totals, without lines; in Germany neither counts as an e-invoice.
  • BASIC: with lines, a subset of EN 16931.
  • EN 16931 (COMFORT in ZUGFeRD): the full EN 16931 data, the profile most invoices use.
  • EXTENDED: EN 16931 and further fields; in France, the EXTENDED-CTC-FR rules apply to it.

Each example passes the schema and the rules of its profile in the validator; the Validate button opens it there.

Questions

Is a Factur-X PDF an e-invoice?

The XML inside is. In the EN 16931, EXTENDED and BASIC profiles it carries a structured invoice; MINIMUM and BASIC WL carry too little and do not count as e-invoices in Germany.

Factur-X or ZUGFeRD: what is the difference?

None in the file: ZUGFeRD 2.x and Factur-X 1.x are the same standard of FeRD and FNFE-MPE, with the same profiles. ZUGFeRD calls EN 16931 COMFORT.

Which examples fit the French reform?

Those of the French reform group: FNFE-MPE wrote them for the XP Z12-012 standard, and they pass the BR-FR rules the approved platforms apply.

Can I use the examples in my tests?

Yes. FNFE-MPE publishes its examples under the Apache License 2.0; the companies in them are made up.

Other tools

  • XML formatter: Pretty-print or minify XML, keeping text, CDATA and comments as written.
  • XML viewer: Read a document as a tree you can fold, search and copy XPaths from.
  • XPath tester: Evaluate XPath 3.1 against a document and see each match with its line.
  • XSD generator: Infer an XML Schema from sample documents, checked against them.
  • XML from XSD: Generate a sample XML document from a schema, validated against it.
  • XSLT transformer: Run XSLT 1.0, 2.0 or 3.0 on a document and see the result, the messages and the files it writes.
  • XML diff: Compare two XML documents as trees: changed, added and removed elements, attributes and text.
  • XML to JSON converter: Convert XML to JSON, with arrays where an element repeats or wherever its XSD allows.
  • JSON to XML converter: Convert JSON to XML: @keys become attributes, arrays repeated elements.
  • XML to CSV converter: Turn a repeating element into CSV rows: invoice lines, products, records.
  • XML to PDF converter: Save any XML as a PDF to read, print or attach: indented, coloured, with line numbers.
  • E-invoice viewer: Read an XRechnung, ZUGFeRD, Factur-X or Peppol invoice as a document, and save it as a PDF.
  • ZUGFeRD validator: Check a ZUGFeRD or Factur-X PDF: the XML inside against its profile's rules, and the PDF around it.
  • XRechnung validator: Check an XRechnung in UBL or CII against EN 16931 and KoSIT's XRechnung rules before you send it.
  • UBL validator: Check a UBL invoice, order or any other UBL 2.1 document against its OASIS schema, and the business rules of the profile it names.
  • Peppol validator: Check a Peppol BIS Billing 3.0 or PINT invoice against the OpenPeppol rules before your access point sends it.
  • P7M viewer: open a .p7m file: Open a signed .p7m file: the PDF, invoice or document inside it, and who signed it.
  • XRechnung examples to download: Example XRechnung and ZUGFeRD invoices to download, one for each common case.
  • E-invoicing mandate in Germany: do I have to?: Find out whether your invoices in Germany must be e-invoices in 2026, 2027 and from 2028.
  • Leitweg-ID check: Check the form and the check digits of a Leitweg-ID, the address of a German public buyer.
  • Peppol lookup: Check whether a company is registered in Peppol, under which ID, and which invoices it can receive.
  • XML validator: check a document against XSD, DTD, RelaxNG or Schematron, up to 1 GB.