E-invoicing: what France's 1 September 2026 mandate changes for a Swiss SME

4 days ago

5 min read

Since 1 September 2026, every VAT-registered business in France must be able to receive structured electronic invoices, and large and mid-sized companies must already issue them. No Swiss law requires anything comparable. Yet if you invoice customers in France or Germany, the question has probably already landed in your inbox. We suggest treating it for what it really is: a matter of flows, data and ERP, far more than a tax matter.

What changed on 1 September, in four facts

France's e-invoicing reform came into force a week ago, after several postponements. Four points matter for a Swiss SME.

Receiving is now mandatory for every VAT-registered French business. Each one must be listed in the national directory and attached to an approved platform that receives invoices on its behalf. A PDF invoice sent by email no longer enters its official circuit, in principle.
Issuing is mandatory for large and mid-sized French companies since 1 September 2026, and will be for French SMEs and micro-businesses from 1 September 2027.
Accepted formats are structured: Factur-X (a readable PDF with an embedded XML file), UBL and CII, all built on the European EN 16931 standard.
The French administration has announced a tolerance phase with no automatic penalties for businesses acting in good faith, as Italy, Poland and Belgium did during their own transitions. It is a delay, not an exemption.

France is not alone. In Germany, receiving structured invoices has been mandatory since January 2025; issuing becomes mandatory in January 2027 for companies above EUR 800,000 in turnover, then in 2028 for everyone. At EU level, the ViDA package makes e-invoicing and digital reporting the default. The shift is structural, not a passing phase.

A Swiss SME is not bound by the law, but it is bound by its customers

Let us restate the Swiss framework, because the confusion is common. There is no e-invoicing obligation between private companies in Switzerland. The standards in place are the QR-bill, now the payment norm (version 2.4 arrives in November 2026), eBill for delivering invoices through e-banking, and mandatory e-invoicing for federal procurement above CHF 5,000, in force since 2016. None of this forces you to produce Factur-X.

What pushes you there is your customers' behaviour. A mid-sized French company that has connected its accounts payable to an approved platform no longer wants to handle a PDF invoice from Geneva as a special case. It will ask, politely at first, for a structured format or for a submission on its platform. If you do not follow, your invoice will be approved late, disputed, or simply paid after the others. The obligation is commercial before it is legal, and it is measured in days of payment delay.

The same logic applies to your suppliers. A German invoice received in XRechnung or ZUGFeRD format can be booked without re-keying, if your ERP can read it. If it cannot, someone types it in again. The reform is a constraint on one side and an opportunity on the other.

The example of an industrial SME in the Jura Arc

Take a precision-machining subcontractor with 40 employees, with deliberately simplified figures. It generates 35% of its revenue in France and 15% in Germany. Its Swiss ERP, in place since 2018, produces around 1,200 invoices a year, 500 of them for French customers, sent as PDFs by email.

In June, two mid-sized French customers announce that from September, invoices will have to go through their approved platform. Management looks at three options.

Manual entry on each customer's portal. At eight minutes per invoice, the 500 annual invoices represent about 65 hours of administrative work, with a risk of error at every copy and a different procedure for every customer.
Upgrading the ERP to produce Factur-X natively. The vendor offers the module in a more recent release. The cost is mostly a project cost: version upgrade, configuration, testing.
Connecting to an exchange operator (the Peppol network or a partner platform) that handles delivery to French approved platforms and the reception of supplier invoices, whatever their format.

The company chose to combine the last two options: the ERP produces the Factur-X file, the operator handles routing, and Swiss customers are offered eBill at the same time. Configuration took a few days. The real workload turned out to be elsewhere: in master data quality. Intra-EU VAT numbers missing or outdated on a third of customer records, billing addresses not aligned with legal entities, inconsistent sales units, payment terms entered as free text. No structured format tolerates these approximations, and this clean-up took most of the time.

One quarter later, the gain shows in three indicators: invoices to France are accepted in under 48 hours instead of several days, re-keying of German supplier invoices has disappeared, and the accountant has recovered the equivalent of half a day a week, now spent on dunning and cash-flow monitoring.

What this asks of your ERP, and above all of your data

If you have customers or suppliers in the European Union, here is the sequence we recommend, in this order.

Map your exposure. Which customers, which countries, what invoice volume, which deadlines (September 2026 for large French accounts, January 2027 for mid-sized German companies, September 2027 for every French business).
Check whether your invoicing tool can produce and read EN 16931 formats. On a recent Swiss solution it is often a module or an option; on an older ERP it is sometimes the argument that triggers the migration.
Clean your business-partner master data: tax identifiers, legal addresses, mandatory mentions, coded payment terms. This step cannot be delegated to the vendor; it belongs to you.
Choose the channel: submission on the customer's platform, an exchange operator, or a native module. An operator spares you from managing one mode per customer.
Secure your archiving. Swiss law, like French law, requires ten years of retention; a structured invoice is easier to archive and retrieve than a PDF lost in a mailbox.

Once the flows are structured, the ground is ready for automation: automatic matching of invoices and purchase orders, reminders triggered by due dates, accounting integration without double entry. For invoices that still arrive as PDFs or images, AI-assisted extraction takes over, with human review on exceptions rather than on every line. This is exactly the kind of project we describe in our SME OS layer: simple, reliable processes that free up time without requiring an eighteen-month programme.

What we take away

French e-invoicing is not a compliance topic for a Swiss SME; it is a customer-relationship and administrative-efficiency topic. Three ideas to keep in mind.

The request will come from your customers, not from the tax authority. Better to anticipate it than to discover it when a large invoice gets stuck.
Prepare once for the EN 16931 standard, rather than chasing every national format as deadlines fall.
The real work is in the data, not in the software. A clean customer master file is the prerequisite for any automation, invoicing included.

If you want to see where your company stands on automation and data, the AI Barometer 2026 gives you a first diagnosis in a few minutes. And if you would rather talk it through directly, get in touch.