For decades, emailing a PDF invoice was the standard of “electronic invoicing” for most businesses in France. It felt digital, it looked official, and it worked for accounting purposes. But under France’s new e-invoicing mandate, a PDF electronic invoice France businesses send by email — no matter how professional it looks — will not satisfy the legal requirement. Understanding exactly why is essential for any business trying to get compliant before enforcement tightens.
What a Standard PDF Invoice Actually Is
A PDF invoice, however carefully formatted, is fundamentally an image of data — not the data itself. It’s designed to be read by a human, not processed automatically by a machine. There’s no structured, standardized way for a receiving system to extract the invoice number, VAT amount, SIREN number, or line items without manual entry or unreliable OCR guesswork. This is precisely the gap the French reform is designed to close.
Sending a PDF by email also means the invoice never passes through the mandated infrastructure — there’s no transmission via a certified Plateforme Agréée (PA), no automatic reporting to the DGFiP, and no compliance trail. From the tax administration’s perspective, that invoice essentially doesn’t exist in the new system, regardless of how correctly it was issued and paid.
What a Compliant PDF Invoice Actually Requires
The confusion here is understandable, because the reform doesn’t ban PDFs outright — it changes what a compliant PDF invoice actually needs to contain. Under the French mandate, an invoice must be a structured electronic invoice, meaning the data is embedded in a machine-readable format that a receiving system can automatically read, validate, and process — not just display.
There are three accepted structured formats:
- UBL 2.1 — a pure XML format with no visual layout, built for pure system-to-system exchange
- CII (Cross-Industry Invoice) — another XML-based format aligned with the EN 16931 European semantic standard
- Factur-X — a hybrid format combining a human-readable PDF with an embedded structured XML data file
Factur-X is the format most businesses are actually adopting, because it bridges the gap between what people are used to seeing and what tax systems now require.
Understanding Factur-X: PDF and XML in One File
Factur-X PDF and XML packaging is genuinely clever, and it’s worth understanding why it exists. A Factur-X file looks, opens, and displays exactly like a normal PDF invoice — anyone can view it in a standard PDF reader and see a familiar, readable layout. But embedded inside that same file is a structured XML data layer containing every required field: invoice number, dates, VAT breakdown, buyer and seller identifiers, line items, and totals.
This means a Factur-X invoice serves two audiences simultaneously: a human opening the file sees a normal invoice, while an ERP or accounting system reading the same file extracts the structured XML data automatically, with no manual re-entry and no OCR guesswork. It’s this dual nature that makes Factur-X the practical middle ground between full XML-only formats and the human-readable PDFs businesses are used to.
Why This Matters Even If You’re Not Issuing Yet
Here’s the detail that catches many businesses off guard: the obligation to receive electronic invoices applies to every VAT-registered business in France, regardless of size, as of 1 September 2026 — well before most SMEs are required to start issuing them. A small business that assumes it has until 2027 to worry about any of this is only half right. If a supplier or customer sends a properly compliant Factur-X or UBL invoice, the receiving business needs the infrastructure to process it correctly — not just open the attached PDF and read it manually.
This is where the old “PDF by email” habit becomes a genuine liability. A business that can only receive invoices by opening PDFs and manually entering the data isn’t equipped for a transaction volume that increasingly arrives as structured data through a Plateforme Agréée or the Peppol network.
What Businesses Need to Do Differently
Moving away from email-attached PDFs means adopting a system — whether a native SAP add-on, an API integration, or a standalone portal — that can generate, validate, transmit, and receive invoices in a genuinely structured format through a certified Plateforme Agréée. The invoice itself may still look familiar if it’s Factur-X, but the underlying mechanism for issuing, exchanging, and reporting it to the DGFiP is fundamentally different from attaching a file to an email.
Businesses that treat this as a formatting update — “we’ll just export a nicer PDF” — are missing the substance of the reform. The requirement isn’t about appearance; it’s about structured, verifiable, machine-readable data flowing through an accredited channel with built-in tax authority visibility.
Getting It Right Before the Deadline Pressure Builds
The businesses best positioned for France’s e-invoicing mandate are the ones that stop thinking of compliance as “sending a better-looking PDF” and start thinking of it as adopting a genuinely structured invoicing infrastructure — one built on Factur-X, UBL, or CII, routed through a certified PA, with both issuance and reception capability in place well ahead of any deadline.