Factur-X vs PDF Invoice: What French Businesses Must Know Before September 2026

Here's the misunderstanding that keeps tripping businesses up: a PDF is not an e-invoice.

A PDF looks like an invoice. It can be emailed. It can be printed. It has a logo, a date, a VAT number, and a total. But under France's mandatory e-invoicing system starting September 2026, sending a PDF to a French B2B customer will not be legally compliant invoicing. Not for large enterprises from September 2026, not for anyone from September 2028.

If your accounting software generates PDF invoices — even very nice, professional PDF invoices — and it cannot also generate Factur-X, you have a problem to solve before your compliance deadline.

This guide explains what Factur-X actually is, why it matters, which profile you need, and how to tell if your current tools are ready.

The Core Difference: Readable vs. Processable

A standard PDF invoice is designed to be read by a human. It's essentially a formatted image of text. A computer can display it, but it can't reliably extract structured data from it — not the invoice number, not the line items, not the VAT rates. Even with OCR, extraction is unreliable and error-prone.

Factur-X is designed to be processed by a machine. Inside the PDF file, there is an embedded XML file containing the complete invoice data in a structured, standardised format. A machine can read that XML and extract every field — invoice number, seller VAT number, line items, quantities, prices, tax rates, payment terms — without any human involvement.

The clever part: the PDF layer still exists inside a Factur-X file. A human can open the file in any PDF reader and read it like a normal invoice. The XML is invisible to casual users. You get both: human readability and machine processability in a single file.

This is why Factur-X is sometimes described as a "hybrid" format. It's a PDF and an e-invoice simultaneously.

What Is Factur-X, Technically?

Factur-X is a joint French–German standard, developed by FNFE-MPE (France) and FeRD (Germany) in cooperation with AIFE (the French government's finance IT agency). The German version of the same standard is called ZUGFeRD.

This is not a coincidence of similar standards — they are genuinely the same specification. A Factur-X 1.x file and a ZUGFeRD 2.x file are interoperable: a French business can send a Factur-X invoice to a German customer and their ZUGFeRD-compatible software will process it without modification. Cross-border invoicing between France and Germany is correspondingly simpler than between most other country pairs.

The underlying technical basis is:

PDF/A-3 — the archival variant of PDF, which allows embedding non-PDF files
UN/CEFACT Cross Industry Invoice (CII) — the XML schema used for the structured data
EN 16931 — the European Commission's e-invoice semantic standard that the XML data must conform to

The Factur-X Profiles: Which One Do You Need?

Factur-X is not a single format — it has multiple profiles, each containing a different amount of structured data. This is where businesses most commonly make mistakes.

Profile	Also Called	EN 16931 Compliant	Mandate Compliant	Use Case
Minimum	Factur-X MINIMUM	❌	❌	Internal use only
Basic WL	Factur-X BASIC WL	❌	❌	Very simple transactions
Basic	Factur-X BASIC	❌	❌	Some automated processing
EN 16931	Factur-X CONFORT	✅	✅	Standard B2B invoicing
Extended	Factur-X EXTENDED	✅	✅	Complex B2B with extra fields
XRechnung	Factur-X XRechnung	✅	✅	Cross-border with Germany

For France's B2B mandate: you need the EN 16931 (Confort) profile at minimum.

The Minimum and Basic profiles contain too little structured data to satisfy the mandate's requirements. If your software is generating Factur-X invoices in the Minimum or Basic WL profiles, that's not sufficient. You need to check this specifically.

How to Check Which Profile Your Software Generates

The profile is declared in the XML inside the Factur-X file. You can inspect it yourself:

Open the PDF in a tool like Adobe Acrobat
Look in the Attachments panel for a file named factur-x.xml (or ZUGFeRD-invoice.xml)
Open that XML file in a text editor
Find the element <ram:GuidelineSpecifiedDocumentContextParameter> — it will contain a URN like urn:cen.eu:en16931:2017#conformant#urn:factur-x.eu:1p0:en16931

If you see en16931 or extended in that URN, you're compliant. If you see minimum, basic-wl, or basic, you're not.

Most businesses won't do this manually — ask your software vendor which Factur-X profile their output produces and ask for written confirmation that it meets the EN 16931 standard.

Does Your Current Accounting Software Support Factur-X?

The honest answer is: it depends, and you need to check now rather than assume.

Major French accounting platforms (Cegid, Sage, Pennylane, EBP, Quadient) are generally developing Factur-X output, but the timeline and pricing vary by product version. Some include it in standard subscriptions; others treat it as an add-on feature.

International platforms like QuickBooks, Xero, and FreshBooks have historically lagged on local format compliance. Check their French-market roadmaps specifically — the international version of these platforms may not have the same features as what's marketed to French customers.

ERP systems (SAP, Oracle, Microsoft Dynamics) support Factur-X through either standard updates or third-party add-ons. SAP users should check their support package level; Oracle users should contact their Oracle Account Manager about the French mandate update roadmap.

Key questions to ask your software vendor:

Do you generate Factur-X invoices, and which profile?
Is this included in my current subscription or an add-on?
Does your Factur-X output connect to a certified PDP for mandate routing?
What is your DGFiP certification timeline?

If your vendor cannot answer these questions clearly, treat that as a warning sign.

Do You Still Need to Send the PDF to Your Customer?

Yes — and this is another common confusion. When you send a Factur-X invoice, you are sending a PDF file. Your customer receives a PDF they can open normally. The embedded XML is handled automatically by their accounting software without any extra steps on their side.

What changes is that you send the file through your certified PDP (or the government PPF portal), not simply via email attachment. The PDP handles routing, DGFiP notification, and delivery tracking. Your customer's PDP receives it and routes it to their system.

From a practical workflow perspective for many smaller businesses, the experience will feel similar to "sending an email with a PDF attachment" — but with the PDP handling the compliant infrastructure underneath.

What About Invoices You Receive?

The mandate's receiving obligation is often forgotten in the focusing on the sending side. From 1 September 2026, all VAT-registered businesses in France must be able to receive and process structured e-invoices — even businesses whose own sending obligation doesn't start until 2027 or 2028.

This means your accounts payable process needs to be able to handle incoming Factur-X XML invoices. The most common failure mode is businesses that receive the PDF, ignore the embedded XML, and manually re-key the data into their accounting system — the exact inefficiency the mandate is designed to eliminate.

Your software should automatically extract data from incoming Factur-X invoices. If it doesn't, this is an equal-priority upgrade alongside your outbound invoicing setup.

Factur-X vs. UBL: Do You Need to Know the Difference?

The French mandate also accepts UBL 2.1 and CII (UN/CEFACT) as valid e-invoice formats — the mandate specifies compliance with EN 16931, and Factur-X is one of several EN 16931-compliant formats.

In practice, Factur-X is the de facto standard for most French B2B invoicing, for the same reason ZUGFeRD dominates in Germany: it provides the human-readable PDF layer that businesses are accustomed to. UBL is more common in multi-country supply chain contexts (particularly via Peppol) and for certain industries that already use UBL in their EDI workflows.

If you're buying software that will handle B2B invoicing in France, focus on Factur-X EN 16931 first. If you also deal with Peppol-connected partners or have a significant German business, adding UBL/Peppol support alongside is a sensible investment.

The Practical Checklist

Before September 2026 (or your applicable phase deadline):

Confirm your software generates Factur-X at EN 16931 (Confort) profile or higher
Ask your vendor for written confirmation of the profile and EN 16931 compliance
Test: generate a Factur-X invoice and validate it against the official EN 16931 validator
Confirm your software can receive and parse incoming Factur-X invoices
Select a certified PDP to handle the routing layer (or confirm you'll use PPF)
Run an end-to-end test: send a Factur-X invoice through your PDP to a willing business partner

The DGFiP's official documentation is the authoritative source for format requirements as the mandate specification is finalised.

Summary

	Standard PDF	Factur-X (EN 16931)
Human readable	✅	✅
Machine processable	❌	✅
Valid under France's B2B mandate	❌	✅
Embedded XML data	❌	✅
Compatible with Germany (ZUGFeRD)	❌	✅
Archival format (PDF/A-3)	Usually not	✅

A Factur-X invoice at EN 16931 profile looks exactly like a PDF invoice to anyone reading it. The difference is entirely in the machine-readable layer that your software — and your PDP — needs to create and process.

The deadline isn't as far away as it might seem. If you're still waiting for your software vendor to "add Factur-X support soon", now is the time to press for a specific delivery date.

Verify current format requirements at the DGFiP official portal. This guide is updated as the specification is finalised.