E-invoicing 2026: rollout schedule and formats

The reform does not create another French-specific format: it builds on the European standard EN 16931, published on 28 June 2017. This standard is a semantic data model: it describes the ~170 data elements that make up an invoice (the business terms), without prescribing a specific file format. Many experts sum this up as "the what, not the how"^[4]. In practice, the standard is implemented through three syntaxes accepted by the French tax authority.

Factur-X (also known as ZUGFeRD 2.x) is a hybrid format: a human-readable PDF/A-3 with an embedded XML file compliant with the standard. Developed jointly by France and Germany, it is today the most widely used format for French B2B invoicing. It lets an accountant continue to "read" the invoice while enabling automated processing^[5]. UBL (Universal Business Language) and CII (Cross-Industry Invoice) are pure XML streams, favoured by ERP systems for machine-to-machine integration. CII is, in fact, the XML that Factur-X embeds under the hood.

The turning point is this: the "classic" PDF invoice (the one you generate today from your software and attach to an email) will no longer be accepted once the obligation takes effect. It contains no structured data that the tax authority or your customers' accounting software can process. It is this fundamental change in nature, more than the date itself, that forces businesses to rethink their procurement and invoicing workflows.

The reform rolls out in waves, based on the size of the issuing company. The receiving obligation, however, is a universal requirement that hits everyone at the same time. This two-speed structure is what makes the timeline confusing: a small business will need to receive e-invoices from September 2026, but won't be required to issue them until a year later^[6].

In practice, if you are a mid-market company invoicing an SMB, you must issue electronic invoices from 1 September 2026 — and your customer must already be able to receive them, even though they won't be required to issue their own until 2027. This asymmetry is pushing most procurement teams to act early: the chain is only compliant if the receiving end is ready too.

Mandatory e-invoicing only covers domestic B2B transactions (VAT-registered businesses established in France). Everything else falls outside the e-invoice requirement but is subject to e-reporting: sales to consumers (B2C), intra-EU transactions, and international transactions^[3]. In plain terms: you do not send a structured invoice to the tax authority for these flows, but you do transmit the transaction data needed for VAT control.

The data to be reported closely mirrors that of an e-invoice (customer identity, net amount, VAT, date), minus the customer's SIREN number when the customer is not VAT-registered. The reporting frequency follows the company's VAT filing regime: monthly, quarterly, or annual. For transactions where VAT becomes due on collection, a payment e-report supplements the transaction e-report. For finance and procurement teams, this changes the scope significantly: compliance no longer stops at the invoice itself: it encompasses every taxable monetary flow.

The legislature significantly raised the cost of non-compliance. The amount originally envisaged (€15 per invoice) was increased to €50 in the 2026 Finance Act, with a cap of €15,000 per business per year^[7]. With 300 non-compliant invoices, you hit the cap. Beyond that, heavier penalties may apply: an invoice that does not reflect a genuine transaction can be sanctioned at up to 50% of its value, with VAT deduction rights also at risk.

These figures are far from trivial. For a business that invoices regularly, the real risk is not the annual cap but consistency: a misconfigured piece of software, left unchecked for a quarter, can produce dozens of non-compliant invoices before anyone notices. Compliance is won upfront: in how your issuance tool is configured and in choosing a dematerialisation platform that validates formats before sending.

The first step is not technical: it is diagnostic. Map your transaction flows (domestic B2B, B2C, intra-EU, international), identify your wave (2026 or 2027), and audit your issuance and reception software. Many modern ERP systems already produce Factur-X or UBL. The work often centres on reception and accounting integration, which tends to be neglected because it is invisible. On the platform side, the choice between the Public Invoicing Portal (PPF) and an accredited Partner Dematerialisation Platform (PDP) determines your level of service and automation, a topic in its own right, covered in our comparison guide PDP or PPF: which platform to choose.

For procurement teams that already centralise professional spending (fuel, travel, expense reports), the opportunity is twofold: bringing invoicing into compliance and tightening supplier oversight on a foundation of structured data. It is also a good moment to align your business payment tools: the Greenway fuel card and the expense management suite built around it already operate on recoverable, auditable data flows, a useful anchor point when fiscal traceability becomes a daily obligation.