Free tier

← All guides · Formats & conversion

What is a Factur-X invoice? The PDF with the invoice inside it

By the Ingenious AI team · Published 14 November 2026 · Reviewed 14 November 2026

Convert an invoice free

Put this guide into practice now: convert one invoice free — validated UBL 2.1 XML plus a Factur-X PDF, with the acceptance checker for your client’s country. See pricing for bulk conversion, country rule packs and monitored clients.

Short answer

A Factur-X invoice is a human-readable PDF with a machine-readable EN 16931 invoice embedded inside it as an XML attachment (factur-x.xml). Your client reads the PDF; their system extracts and books the XML. It is the French-German hybrid format — the same idea as ZUGFeRD in Germany — and it is one of the two downloads every conversion here produces.

What is Factur-X?

Factur-X is an electronic invoice format that combines a visual PDF invoice with an embedded structured XML representation of the same invoice, conforming to EN 16931. The PDF is the presentation layer; the XML is the data layer. EInvoice Translator builds Factur-X PDFs with ReportLab and embeds the validated UBL 2.1 XML as factur-x.xml, byte-identical to the standalone XML download.

The problem Factur-X solves

Firms receive invoices in two worlds at once. People want to see a document — check the lines, approve the amount, file it. Systems want data — fields they can validate, book and pay without retyping. A plain PDF serves the person and starves the system; a raw XML file serves the system and leaves the person squinting at tags. Factur-X refuses the trade-off: one file, both layers, guaranteed to describe the same invoice.

The guarantee is the important part. In this product, the PDF is generated from the invoice data, the UBL XML is generated from the same data, and the XML is attached to the PDF unchanged. What the approver reads is what the system books — there is no separately maintained copy that can drift. The test suite even proves it mechanically: the embedded XML is extracted back out of the PDF and compared, which is the extract_embedded check in the Factur-X builder.

How the hybrid file is built

The readable page is drawn first: invoice title and number, issue date, seller and buyer blocks, the line table with quantities and unit prices, the VAT total and the amount due, and a note that the structured XML is embedded. Then the PDF gains an attachment named factur-x.xml containing the validated invoice, in the PDF/A-3 style that hybrid formats use, with the attachment marked as the alternative representation of the document.

Because the XML passed validation before embedding, a receiving system that extracts it gets an invoice that already satisfies the EN 16931 core rules. If your data fails validation, no PDF is produced at all — the converter returns the named rule failures instead. That ordering matters: a beautiful PDF wrapping an invalid invoice is worse than no file, because it fails later, inside your client's process, instead of now, in yours.

Factur-X, ZUGFeRD and the German-French connection

Factur-X is the French name and ZUGFeRD the German name for the same hybrid-invoice idea, developed so both countries' invoices could carry EN 16931 data inside a PDF. Germany's e-invoicing channel is EN 16931 in the form of XRechnung or ZUGFeRD; France's reform accepts Factur-X through its platform ecosystem as businesses move to structured issuing — receiving from September 2026, SME issuing from September 2027 in this product's mandate table.

For a supplier, the practical read is: if your client asks for a Factur-X or ZUGFeRD-style invoice, they are asking for the hybrid — a PDF they can file with the structured invoice inside it. Send the Factur-X PDF this product generates, and keep the standalone XML too: some systems prefer to ingest the XML directly, and both files describe the identical invoice.

When a Factur-X PDF is not enough

A hybrid PDF is still delivered as a file — by email, upload or portal. Some channels want pure structured data instead: Peppol sends the invoice as a Peppol BIS document (UBL) through access points, Italy's SdI requires its FatturaPA format, and Poland's KSeF works in its own national system. A Factur-X PDF is not a Peppol transmission and does not become one by being emailed to an access point.

That is why the conversion here always produces both artefacts. The UBL XML is the channel-ready structured invoice — the file you upload in your own Qvalia account for a guided Peppol send. The Factur-X PDF is the human-ready copy and the right format for clients whose process starts from a document. The acceptance checker tells you, per country and date, which world your client is in.

Reading and verifying a Factur-X invoice you receive

On the receiving side, the discipline mirrors the sending side: extract and book the XML, do not retype from the visual page. If the two ever disagreed, the discrepancy itself is the finding — the structured layer is what your system validates and pays against, and a mismatch means the file was not produced by a careful generator.

You can verify a Factur-X file's claim mechanically: open the PDF's attachments and confirm a factur-x.xml is present, then parse it and check the totals against the lines. That is exactly what this product's own builder test does on every generated file. Suppliers who generate carefully welcome the check, because it separates real structured invoicing from a PDF that merely calls itself electronic.

Creating a Factur-X invoice from your current invoice

The workflow is the converter's: enter the invoice — parties, lines, VAT categories and rates — and validation runs against the EN 16931 core rules. On a pass, you download the Factur-X PDF and the UBL XML together. On a failure, you get the rules to fix, in the exception workspace, before any file exists.

For a single invoice that is the whole job, and it is free. Firms converting in volume use Pro's bulk conversion — up to 200 invoices per job — so a whole billing run comes out as validated hybrid PDFs and XML files in one pass, with country rule packs and monitored clients tracking acceptance as mandates move.

Sending a Factur-X invoice: 5 steps

  1. Convert the invoice and confirm validation passes with no rule failures before any file is generated.
  2. Download both outputs: the Factur-X PDF for the human reader and the UBL XML for systems and channels.
  3. Open the PDF once and read it as your client will — parties, lines, VAT and total due all legible and correct.
  4. Send the PDF where your client files documents; send or upload the XML where their system ingests structured invoices.
  5. Archive both files together under the invoice number — the XML is the operative record in mandate countries.

Worked example: a maintenance contract invoice as Factur-X

A facilities firm invoices a French property manager EUR 3,600.00 for a quarter's maintenance: one line, quantity 3 months at EUR 1,200.00, VAT category S at 20%. The converter computes the line extension EUR 3,600.00, tax of EUR 720.00, and a payable amount of EUR 4,320.00. The Factur-X PDF shows the manager exactly that page — lines, VAT, total due EUR 4,320.00 — and carries the same figures as embedded XML.

France's timetable in the mandate table says businesses must receive structured invoices from 1 September 2026. The property manager's system extracts the XML and books EUR 4,320.00 without anyone retyping it — while the manager still approves from the readable page, which is the entire point of the hybrid format.

Frequently asked questions

Is Factur-X the same as ZUGFeRD?

They are the French and German names for the same hybrid approach: a readable PDF carrying an embedded EN 16931 XML invoice. This product labels its output Factur-X and embeds factur-x.xml.

Is a Factur-X invoice a 'real' e-invoice?

Yes — unlike a plain PDF, it contains the structured invoice data in XML, which is what makes an invoice electronic in the EN 16931 sense. The PDF layer is presentation.

Can I just attach an XML file to a normal PDF email instead?

That gives your client two files that can drift apart. Factur-X embeds the XML in the PDF itself, byte-identical to the standalone download here, so the document and the data are one artefact.

Does France accept Factur-X?

Factur-X is France's own hybrid format and features in its reform ecosystem; the mandate table here has French businesses receiving structured invoices from September 2026 and SMEs issuing from September 2027.

How do I know the XML is really inside the PDF?

The builder test extracts it back: the product's own suite pulls factur-x.xml out of generated PDFs and re-reads it. PDF readers also show the attachment in their attachments panel.

Keep going

Run the free tool this guide is about: convert an invoice · acceptance checker · pricing · about EInvoice Translator · all guides

Related guides

← Back