PDF Invoices After Sept 2026: Validity & Dual Flow Management

Key takeaways

• A PDF invoice received by email after 1 September 2026 remains payable, can be booked in the accounts, and still carries VAT deduction rights: the reform changes the transmission method, not the substantive rules (DGFiP, startup guide) (DGFiP: Direction générale des Finances publiques, the French tax authority).
• The number-one risk of dual invoice flows is not fiscal but operational: only one invoice must be kept as the reference copy, with all others marked as copies, duplicates or duplicata (guide fact sheet no. 5).
• The leniency announced by the tax authority is "neither a postponement nor a suspension" (analysis of the DGFiP guide): it protects a documented transition path, not inaction.
• The statutory retention period has risen from 6 to 10 years: law no. 2026-534 of 25 June 2026, Article 36, amended Article L102 B of the French Tax Procedure Code (LPF) (CRCC Paris).

Is a PDF invoice received after 1 September 2026 still valid?

Yes. The practical startup guide published by the DGFiP states that an invoice received by email, as a PDF or on paper can be processed, paid and booked in the accounts as long as it corresponds to a genuine transaction and includes the required particulars, since the reform changes neither the rules governing trade debt nor the conditions for VAT deduction rights (LégiFiscal).

That doesn't strip the obligation of its substance, though. The legal basis remains Article 289 bis of the French General Tax Code (CGI), under which the issuance, transmission and receipt of electronic invoices must go through an approved platform, or PDP (plateforme de dématérialisation partenaire) (Cyplom). And a PDF is not an electronic invoice within the meaning of the reform: three structured formats make up the minimum baseline, Factur-X (a hybrid PDF/XML format combining a human-readable invoice with embedded structured data), UBL and CII, and a plain PDF or a scanned image is not one of them (Les Experts Comptables). In other words, a PDF is an acceptable supporting document, not a compliant flow. Handling it therefore means documenting why it arrived outside the official channel and what you did with it.

Why will you keep receiving "plain" PDFs?

Because three legitimate categories of PDF will persist for several more years. First, suppliers outside the scope: foreign companies not registered in France are covered neither by e-invoicing nor by e-reporting; their invoices are sent as they are today (PDF, email, portal), and it falls to the French customer to declare the transaction through e-reporting (Sellsy).

Second, French SMEs and micro-businesses: receiving structured invoices becomes mandatory for all companies on 1 September 2026, but issuing them only becomes mandatory on that date for large companies and mid-caps, with SMEs and micro-businesses following on 1 September 2027 (Rydge). A 12-employee supplier can therefore legally keep sending a PDF by email for another year.

Third, converted flows: during a transitional phase running until 31 December 2027, companies may upload unstructured PDF invoices to their platform, leaving it to the issuing platform to convert them into the mandated structured format (Revue Fiduciaire). You will therefore receive structured invoices whose data originated from OCR (optical character recognition) processing.

How do you manage dual invoice flows without paying twice?

By designating a single reference document and flagging everything else. During the transition, it is possible to receive the same invoice both through an approved platform and through another channel; the accountant must then check that it is indeed the same invoice by cross-referencing the invoice number, date, supplier, customer, net amount, VAT and gross amount (LégiFiscal, fact sheet no. 5). The main operational risk is duplicate management: the same invoice received or corrected through several channels must never lead to double payment, double booking or a double VAT deduction (Arcanes).

When requesting a correction from a supplier, stick to the facts: it is advisable to identify the invoice precisely (number, date, amount, supplier, customer, original channel) to avoid any duplication once it is corrected (LégiFiscal). A technical deduplication key (issuer's SIREN business identification number + invoice number + gross amount) should be calculated on intake, regardless of the channel.

What role does AI extraction play in this degraded flow?

It is used to produce, from a PDF, the same data that a structured flow would have provided, and to keep evidence of that process. The economics are measurable: the cost of manually processing an invoice is estimated at between €8 and €15, factoring in data entry, verification, reconciliation and error correction (Leveraize), with a data-entry error rate of between 1 and 3% (Facturii).

OCR isn't disappearing with the reform: it remains useful for unstructured documents, expense-claim receipts, foreign invoices, receipts, till slips or documents transmitted outside the standardised flow (Cegid). The generational difference matters, though: traditional OCR needs a template per supplier to know where to look, whereas AI-based extraction without a template locates data through semantic context (Lido), a distinction Sygnet documents in its OCR vs VLM comparison and on its dedicated page on receiving electronic invoices in France. To stay auditable, demand three things from the tool: a confidence score per field, the location of the data within the image, and a threshold that triggers a handover to human review. OCR does not replace human review: it lets you focus verification on sensitive invoices, new suppliers, high amounts or detected anomalies (Cegid). Human-in-the-loop review is not an admission of failure. It's the piece that makes automation defensible.

How do you keep a reliable audit trail on these PDFs?

By keeping the invoice in its original form along with evidence of the controls surrounding it. When the authenticity of origin, the integrity of content and the legibility of invoices are ensured by controls put in place by the company (a "reliable audit trail"), the information, documents, data, processes and documentation describing how they work must be retained (BOFiP) (BOFiP: the official published doctrine of the French tax authority). Two practical rules follow from this: companies that receive both paper and electronic invoices must keep each in its original form, and printing an electronic invoice on paper does not turn it into the original invoice (BOFiP).

A PDF "flattened" into a document management system is therefore no longer sufficient: you need the PDF as received, the original email, the extracted data, the identity of the approver and the timestamp. The guide also requires internal procedures to be updated to cover the handling of invoices received outside the electronic channel, the identification and marking of duplicates, the distinction between technical rejection and a reasoned refusal, status governance, and the systematic retention of error messages (Cyplom). This distinction is not merely theoretical: four statuses are mandatory and reported to the tax authority (Submitted, Rejected, Refused, Paid), with a rejected invoice resulting from a technical issue and a refused invoice from a commercial disagreement (Tiime).

What penalties apply, and how far does the DGFiP's leniency go?

Fines do exist, but their application is being phased in gradually at launch. Failure to issue a compliant electronic invoice is punishable by a €15 fine per invoice, capped at €15,000 per year, and failure to meet an e-reporting obligation by a €250 fine per transmission, also capped at €15,000 per year (Les Experts Comptables). For failing to set up a receiving platform, the law provides for a formal notice giving three months to comply, followed by a €500 fine, rising to €1,000 if the situation persists, renewable every quarter (Open-S).

The leniency is real but conditional: the startup guide introduces leniency in the application of penalties for companies facing genuine difficulties but committed to a credible compliance path (Swift EDI Flow). Hence the practical advice: keep a record of your efforts, quotes, correspondence with your software vendor or accountant, tests carried out, and dates (Open-S).

FAQ

Can I deduct VAT on a PDF invoice received by email in 2026?

Yes, subject to substantive conditions. According to the DGFiP guide, a PDF invoice received by email after 1 September 2026 can still be processed and VAT remains deductible if the transaction is genuine, but the company must correct the flow as soon as possible (Arcanes). Keep the PDF in the form received, the mandatory particulars, and proof of the correction request sent to the supplier.

How long must these PDFs and the extraction evidence be kept?

Ten years is now the single reference period. Law no. 2026-534 of 25 June 2026 extended from 6 to 10 years the retention period for documents that can be requested during a tax audit (CRCC Paris), bringing the tax rule in line with the 10-year period already set by the Commercial Code. Documentation of the reliable audit trail follows the same timeline as the invoices themselves.

Should I refuse a PDF invoice to force my supplier onto an approved platform?

No. Where the supplier is subject to the electronic issuance obligation