French e-invoicing 2026: certified platforms, reliable audit trail and what really changes for your business

France's e-invoicing reform is often presented as a technology upgrade. That framing is incomplete. The reform restructures the flow of tax data between businesses and the tax authority (DGFiP), but it does not create the reliable audit trail obligation. It makes that obligation more visible, because invoices and transaction data will now be transmitted to the DGFiP in near real time.

For a business owner or CFO, this means two separate workstreams:

1. Selecting and connecting a transmission platform (PDP or PPF).
2. Documenting the evidence chain that links each invoice to the underlying transaction.

Treating these as a single project is the most common preparation mistake.

Source: Direction Générale des Finances Publiques. Verify dates at impots.gouv.fr before any deployment decision.

Even if your company does not yet need to issue electronic invoices, the reception obligation applies from September 2026. Your platform must be operational before that date.

The Public Invoicing Portal (PPF / Chorus Pro)#

The PPF is the free government solution. It handles transmission and reception of invoices in the required formats. It suits companies with low volumes or those seeking a zero-cost platform option.

Known limitations: manual handling for companies without a dedicated ERP connector, limited native integration with market ERP systems, no built-in approval workflow.

Registered Private Platforms (PDP)#

PDPs are private operators registered by the DGFiP. They interface with the PPF and transmit fiscal data on your behalf.

Our assessment: for an SME issuing more than 100 invoices per month with an ERP, the PPF alone generates significant manual workload. A PDP with a native connector is justified when the cost of manual processing exceeds the subscription fee.

Consider a B2B services SME issuing 200 customer invoices per month and receiving 80 supplier invoices.

With PPF only:

• Manual upload and download if no ERP connector is in place.
• Estimated internal effort: 15 to 20 minutes per daily batch, approximately 5 to 7 hours per month.
• Indirect cost at €30/hour fully loaded: €150 to €210 per month.

With a PDP connected to the ERP:

• Average market subscription: €80 to €200 per month depending on volume and features (verify with operator quotes).
• Residual internal effort: rejection monitoring, approximately 1 to 2 hours per month.
• Total cost: €110 to €260 per month, with a saving of 4 to 6 hours and reduced data entry errors.

The direct cost difference is modest. The real gain is data reliability feeding into accounting and VAT returns.

What article 289 V CGI requires#

Article 289 V of the French Tax Code (Code Général des Impôts) sets four cumulative conditions for an invoice to be authentic and legally probative:

1. Authenticity of origin: the issuer of the invoice must be identifiable with certainty.
2. Content integrity: the data must not have been altered since issue.
3. Legibility: the invoice must remain readable throughout the conservation period.
4. Ten-year retention: required under article L102 B of the French Tax Procedures Code (Livre des Procédures Fiscales).

Article 289 bis CGI specifies the conditions for accepting electronically transmitted invoices, including recipient consent and format requirements.

What a reliable audit trail is not#

Simple electronic archiving does not constitute a reliable audit trail. The PAF (piste d'audit fiable) is not a file format question. It is a documentary chain that links, for every invoice, all documents proving the transaction took place.

Minimum recommended chain:

• Signed quote or purchase order
• Delivery note or service completion record
• Invoice issued or received
• Identifiable payment (bank statement, traceable transfer)
• Corresponding accounting entry with matching reference

Without this complete chain, a perfectly formatted electronic invoice can be challenged during a tax audit.

During an accounting audit (vérification de comptabilité), inspectors compare the data in the Fichier des Écritures Comptables (FEC) against invoices issued or received. The reform makes this comparison easier for the administration: transaction data will be available in near real time via e-reporting.

Frequent friction points in audit files:

• Invoices without an associated purchase order in the information system (flows without upstream evidence).
• Credit notes not justified by a returns document or written agreement.
• Deductible VAT on supplier invoices where origin authenticity is insufficient.
• Discrepancy between invoice date, delivery date and accounting entry date.
• Absence of retained versions when an invoice was modified.

The underestimated risk: many companies assume that switching to electronic invoicing automatically resolves their reliable audit trail requirement. It does not. A Factur-X invoice transmitted via a PDP is technically authentic and integral — but if it is not linked to a purchase order and a traceable payment, the PAF remains incomplete.

Three structured formats are recognised under the reform:

• Factur-X: a Franco-German hybrid format (human-readable PDF with embedded XML data). Recommended for businesses wanting a document readable by humans and processable automatically. Multiple profiles of increasing complexity (MINIMUM, BASIC WL, BASIC, EN 16931, EXTENDED).
• UBL (Universal Business Language): an international XML format widely used in European public procurement and B2B e-commerce.
• CII (Cross Industry Invoice): an XML format derived from the UN/CEFACT standard, used notably in EDI environments.

If your ERP or invoicing software natively generates Factur-X EN 16931 or EXTENDED, you are aligned with the most complete requirements. If you currently export plain PDFs, a format migration is needed before September 2026 (large companies) or September 2027 (SMEs).

In migration projects, technical blockers rarely appear at the platform selection stage. They emerge when connecting the ERP to the PDP, or when feeding the PDP's status responses back into the accounting system.

Key 2026 watchpoints:

• Mandatory field mapping: SIREN number, EU VAT number, delivery address, customer order reference — all must be populated in the ERP for the PDP to generate a valid invoice.
• Status management: a transmitted invoice can be accepted, rejected or disputed. The ERP must receive these statuses and trigger a correction workflow. Without this feedback loop, rejected invoices can remain pending without anyone being alerted.
• B2C and cross-border e-reporting: sales outside the e-invoicing scope (B2C, exports) require separate e-reporting. This flow must also be connected to the PDP or PPF.

• Identify your issue obligation date (large companies/ETI: September 2026; SMEs/micro: September 2027).
• Confirm reception capability by September 2026 (all VAT-registered companies).
• Audit customer and supplier master data: SIREN numbers, EU VAT numbers, billing addresses.
• Verify that your software or ERP generates a recognised structured format (Factur-X, UBL, CII).
• Choose between PPF and PDP based on your volume and ERP integration level.
• Configure status feedback (accepted, rejected, disputed) in your system.
• Document the PAF evidence chain for each flow type (standard sales, deposits, credit notes, subscriptions).
• Verify legally probative archiving for 10 years under article L102 B LPF.
• Train commercial and accounting teams on new workflows.
• Run a pilot on a limited scope before full deployment.

For related compliance topics, see our guides on different VAT rates on an invoice, mandatory tax declarations for businesses in 2026 and multi-currency accounting.

Updated 25 May 2026. Thresholds, formats and implementation dates may evolve: verify current data at impots.gouv.fr and DGFiP publications before any operational decision. This article is for information only and does not replace personalised advice adapted to your flows, systems and legal situation.