France E-Invoicing Soft Launch: What 'No Fines' Really Means
France's tax authority won't fine businesses on a 'serious compliance trajectory'. What that means, what evidence to keep, and why it isn't a postponement.
France’s e-invoicing reform went live on 1 September 2026, and the headline most people took from the tax authority’s guidance was: no fines if you’re trying. That’s roughly right, but it leaves out the part that matters. The leniency is conditional, you have to be able to prove you qualify, and the deadlines haven’t moved.
The guidance is the DGFiP’s Facturation électronique : guide pratique de démarrage au 1er septembre 2026 (“E-invoicing: a practical start-up guide for 1 September 2026”). It was published in July 2026 and answers 29 questions. You can read the full guide on impots.gouv.fr. Here’s what it actually says.
The three principles
The guide opens with three principles, and the rest of the guide follows from them.
- The legal calendar stands (le maintien du calendrier légal). Since 1 September 2026, every business in scope must be able to receive e-invoices, and large and mid-sized companies must issue them through an approved platform (plateforme agréée). Small businesses issue from 1 September 2027.
- Business carries on (la continuité économique). The reform changes how invoices travel. It doesn’t change whether a sale happened, whether money is owed, how the invoice is booked or whether you can deduct the VAT.
- Carrying on is not an exemption. The guide says this continuity “ne doit pas être confondue avec une dispense d’application de la réforme” (must not be confused with an exemption from the reform). If you’re required to issue e-invoices, a PDF still isn’t the target. When the electronic route fails, you’re expected to send the same invoice electronically later, or regularise it as soon as you can.
Then comes the line everyone quoted. During the start-up phase, sanctions won’t be applied to businesses having difficulties “mais qui sont engagées dans une trajectoire sérieuse de mise en conformité” (but which are committed to a serious compliance trajectory). The administration will separate these cases from “inertie, évitement ou refus durable” (inertia, avoidance or a lasting refusal). And the approach “ne constitue ni un report ni une suspension de l’obligation” (is neither a postponement nor a suspension of the obligation).
What counts as a “serious compliance trajectory”
Question 27 is the one to read twice. A serious trajectory doesn’t mean everything works on day one. It means you’ve identified your obligations, started the work and organised how you deal with problems. The guide lists the kind of evidence it has in mind:
- A chosen or signed-up approved platform
- Emails and messages with your software provider, accountant, bank or platform
- A timetable for connection, configuration or rollout
- A list of the invoice flows already running electronically, and of those still being fixed
- Tests done or scheduled
- Support tickets, error messages and incident notices
- The temporary workarounds you used to keep trading
- Your plan to regularise invoices or data that missed the electronic route
- Written instructions to your billing, accounting and payments teams
Then the warning: “une simple déclaration d’intention ne suffit pas” (a simple statement of intent is not enough). Your evidence has to be concrete, dated and consistent.
In practice, keep a simple compliance log: one document or folder per month with the platform contract, test results, tickets and a short note of what broke and how you fixed it. Questions 6 and 16 add specific items for invoices handled “in degraded conditions”: the invoice itself, related commercial documents, exchanges with the supplier or platform, proof of the incident or rejection, and anything that shows you avoided paying twice.
The guide also says it doesn’t want to create extra admin. The log exists so that, if the tax authority asks, you can show you didn’t ignore your obligations.
PDF and paper invoices you receive are still valid
This is the most useful part for finance teams. Question 3 asks whether an invoice received by email, PDF or paper after 1 September 2026 can be processed, paid and its VAT deducted. The answer is yes, as long as it relates to a real transaction and contains what you need to process it.
The guide is clear that the right to deduct VAT (article 271 of the French tax code) is still judged on the usual substance and form rules. The fact that an invoice didn’t arrive through the electronic circuit “ne prive pas automatiquement l’entreprise de son droit à déduction” (does not automatically deprive the business of its right to deduct).
You may ask a supplier that should have e-invoiced to resend it electronically, but that request is optional at this stage. It is not a condition for paying or deducting. It also must not be used to block a commercial relationship or delay a payment that’s due.
Three related points:
- Duplicates. If the same invoice arrives by email and through the platform, pick one reference copy, mark the others as copies, and make sure it isn’t paid or deducted twice (questions 5 and 15). A resent invoice can be labelled “copie de continuité” (continuity copy).
- Small suppliers. A customer can’t force an SME or micro-business to e-invoice before its own date of 1 September 2027. It also can’t refuse to pay an invoice just because it isn’t electronic (question 20).
- Refused invoices. A buyer can only refuse an e-invoice on the grounds set by the standard, such as a regulatory error or a wrongly addressed invoice. Refusal isn’t a tool for commercial disputes (question 12).
When a platform or the state directory goes down
Questions 13, 25 and 26 cover outages, and the message is the same each time: keep trading, document everything, regularise afterwards.
- Your platform or your customer’s is down. Record the error messages, timestamps and support tickets. If you need to avoid blocking a payment, send the invoice by another channel. Once the incident is over, send the same invoice electronically, or regularise it, without creating a duplicate.
- Your software provider or platform causes the problem. The guide says a business “n’a pas vocation à être sanctionnée du seul fait d’une défaillance imputable à un tiers” (is not meant to be penalised simply because of a third party’s failure), provided it did what was in its power. You chose a solution, reported the problem, followed it up and used workarounds.
- The state’s directory or data hub fails. Platforms can fall back on copies of directory data they already hold, and on technical addresses such as Peppol addresses. The guide says plainly that a business doesn’t have to fix a failure in a public tool itself. It only has to show it noticed, limited the damage and didn’t use the outage as an excuse to delay.
Why this is not a postponement
The guide repeats this many times. Question 29 asks whether sanctions will be applied automatically after a delay, technical incident or correction. The answer is no: not in an “immédiate, automatique et aveugle” (immediate, automatic and blind) way, where the difficulty is real, documented and being fixed. But it continues: “Le calendrier demeure applicable” (the calendar remains in force).
The fines are still in the tax code:
- €50 per invoice not issued electronically, capped at €15,000 a year (article 1737)
- €500 per missing e-reporting transmission, capped at €15,000 a year (article 1788 D)
- For businesses with no platform to receive invoices, a formal notice first, then a €500 fine three months later (article 1737 IV bis)
The guide also lists what the tolerance doesn’t cover: ignoring the obligation for a long time, taking no steps, refusing to join the system, deliberately running parallel channels without regularising, and using start-up problems as a pretext to block payments.
Two more things to note. You don’t have to report every rejected invoice to the tax authority. But if it contacts you, you’re expected to answer completely, with documents (question 28). And the guide doesn’t say when the start-up phase ends. Nothing in it promises the same tolerance for small businesses when they start issuing in September 2027.
What foreign sellers should take from it
If your business is based outside France and has no French establishment, most of this guide isn’t about you. Businesses not established in France for VAT aren’t covered by e-invoicing at all, French VAT number or not. But three points matter:
- Your French customers will keep paying your PDFs. As a foreign supplier, your invoices sit outside e-invoicing anyway. The guide removes any excuse for a French buyer to hold up payment over the format of an invoice. The buyer reports your invoice data itself.
- The e-reporting answers apply to large foreign companies now. Large and mid-sized foreign businesses with French-VAT sales outside OSS have had to e-report since September 2026. Questions 21 to 24 are written for them: a temporary e-reporting problem doesn’t invalidate your invoices, but you must keep the data, document the problem and send it as soon as you can.
- Smaller foreign sellers start in September 2027, with no promise of leniency. If you hold stock in France or sell to French consumers on a French VAT return, your e-reporting date is most likely 1 September 2027. Choose a platform early and keep a log from day one.
Our guide to France e-invoicing for foreign companies shows who has to receive, issue or e-report, situation by situation, with worked examples. For the reform as a whole, see e-invoicing in France.
Not sure whether you’re in scope at all? Our free France e-invoicing checker works it out from a few questions.
FAQ
Has France postponed e-invoicing?
No. The tax authority’s start-up guide opens with the ‘maintenance of the legal calendar’ and says its lenient approach is ‘neither a postponement nor a suspension of the obligation’. Since 1 September 2026, every business in scope must be able to receive e-invoices, and large and mid-sized companies must issue them.
Will I be fined if my French e-invoicing isn’t working yet?
Not during the start-up phase, if you are on a ‘serious compliance trajectory’: you’ve chosen a platform, you’re fixing problems and you can prove it with dated records. The tax authority says it will treat inertia, avoidance or a lasting refusal differently, and the fines in the tax code still exist.
Can I still pay a PDF invoice and deduct the VAT in France?
Yes. The start-up guide says an invoice received by email, PDF or paper for a real transaction must not be set aside for that reason alone. The right to deduct VAT is still judged on the usual conditions, and asking the supplier to resend it electronically is optional and not a condition of payment.
What happens if my e-invoicing platform goes down?
Keep trading. Document the outage, send the invoice by another channel if you need to avoid blocking payment, then send the same invoice electronically once the platform is back. The tax authority says a business is not meant to be fined just because a third party failed, as long as it did its own part.
How long does France’s e-invoicing start-up phase last?
The guide doesn’t say. It describes the start-up phase of September 2026 without giving an end date, and it doesn’t promise the same tolerance for the September 2027 deadline. Plan as if the leniency could end at any point.
Does the soft launch apply to foreign companies?
Businesses with no establishment in France aren’t covered by e-invoicing, so most of the guide doesn’t concern them. Its e-reporting answers do apply to large and mid-sized foreign companies, which have had to e-report since September 2026. Smaller foreign sellers start e-reporting in September 2027.