France E-Invoicing & E-Reporting: Compliance Guide & Penalties

Key takeaways

• Since 1 September 2026, every French VAT-registered business must be able to receive structured electronic invoices through an approved platform, and large companies and ETIs must also issue them; SMEs and micro-enterprises follow on 1 September 2027.
• A PDF sent by email is not an electronic invoice under the reform, no matter how clean it looks.
• Failing to issue in electronic form costs 50 € per invoice, capped at 15 000 € per calendar year, after the 2026 Finance Law raised the old 15 € figure.
• AI helps most on the messy edges of compliance (reading what suppliers actually send, matching invoices to orders, spotting fakes), not on the regulated transport layer itself.

What does AI-powered e-invoice compliance actually mean?

It means using document AI to handle everything the mandate does not: reading non-compliant files that still arrive, extracting data from hybrid formats, checking an invoice against a purchase order, and flagging suspicious documents before they reach the payment run. The legal transmission itself is handled by an approved platform, not by AI.

The French rules are now settled. Businesses must connect to a certified PA (Plateforme Agréée) service provider, previously called PDP; domestic invoices must be issued in structured electronic format, while cross-border B2B, domestic B2C and payments are reported through e-reporting to the government platform. The approved platform is the only intermediary recognised by the tax authorities for issuing, receiving and transmitting e-invoices, though companies may use a "Compatible Solution" connected to an approved platform.

So AI does not make you compliant. It makes compliance survivable. Take a 40-person accounting firm processing 300 supplier invoices a month across 60 clients: some arrive as Factur-X through the platform, some as scanned paper from a foreign supplier, some as PDFs from a plumber who has not understood anything yet. Three intake channels, one ledger.

Why is compliance harder than just signing up with a platform?

Because the platform solves routing, not data quality, and routing breaks when your master data is wrong. A wrong SIREN blocks the delivery of an invoice, and nobody finds out until a supplier calls about an unpaid bill.

Several failure points show up in practice. Accounts created but never activated are one of the three causes of blockage observed since 1 September 2026, along with missing data and addressing errors in the directory. New mandatory fields add another: a "starter" dataset applies from go-live, including four new mandatory mentions from 1 September 2026 (the customer's SIREN, the transaction type, the VAT-on-collection option where relevant, and the delivery address where it differs from the billing address), with a fuller "target" dataset, including a new price-adjustment field, becoming mandatory from 1 September 2027.

Then there is archiving. E-invoices must be kept six years for VAT purposes and ten years for accounting and commercial law. That is a retention policy, a storage decision and a GDPR question all at once.

The platform solves routing, not data quality, and routing breaks when your master data is wrong.

What are the penalties, and is anyone actually enforcing them?

The headline figures: 50 € per non-compliant invoice, capped at 15 000 € per calendar year (raised from 15 € by article 123 of the 2026 Finance Law), and 500 € per missing e-reporting transmission, also capped at 15 000 € a year. Approved platforms face heavier exposure: 750 € per missed transmission, up to 100 000 € per calendar year.

Receiving is policed differently. A company that fails to use an approved platform to receive invoices can be formally served notice to comply within three months; failing that, a fine of 500 €, then 1 000 € if non-compliance persists.

Enforcement at launch is lenient but not absent. France granted no formal grace period, but minister David Amiel confirmed a soft-landing approach: penalties will not be applied automatically at launch to businesses acting in good faith. DGFiP's tolerance covers documented, active compliance efforts only, not a blanket extension. Translation for a finance director: keep written evidence of your project, your platform contract and your test runs.

Commercial risk often bites first. A supplier who sends you an e-invoice you cannot receive may suspend delivery or charge handling fees.

Which parts of compliance should you automate, and which should a human own?

Automate extraction and reconciliation; keep validation, tax treatment and exception handling with a named person. The split matters because the fine attaches to your company, not to your software vendor.

One practical note: the obligation to e-report international incoming invoices at line-item level has been removed for both EU and non-EU purchases, and businesses no longer need to file blank e-reports when no taxable transaction occurred. That removes a real chunk of extraction work for import-heavy companies. If you are scoping an automation project, check what the rules no longer ask for before you build.

Teams comparing an in-house pipeline with a vendor will find the trade-offs laid out in Sygnet's build vs buy guide for document processing.

How do you handle invoices that still arrive as PDFs?

You treat them as a parallel intake channel with its own controls, because they will keep arriving for years. Companies are expected to continue receiving PDF or paper invoices from suppliers not subject to e-invoicing mandates in their home countries. Domestic SMEs also keep sending PDFs until their own issuing obligation starts in September 2027.

Here the economics favour automation. A paper invoice costs around €12 to process, against €3 for an electronic one. For our 300-invoice-a-month firm, if 90 of those are still unstructured, the processing gap is roughly 810 € a month, before counting error correction.

What a careful setup looks like: extract header and line data automatically, validate the supplier SIREN and VAT number against your master file, compare totals and VAT rates against the arithmetic on the document, and route anything outside tolerance to a human queue. Measure the error rate per field rather than per document, because a 2% failure on the VAT amount matters far more than a 2% failure on the supplier's phone number. Sygnet publishes a checklist for evaluating extraction accuracy that sets out how to build that test set.

Does structured invoicing make fraud less likely?

Partly. Structured data and platform routing cut out the classic fake-PDF-by-email scam for domestic B2B flows, since traditional unstructured formats (paper, basic PDF, email attachments) are no longer sufficient for mandated B2B flows. The fraud simply moves.

The attack surface shifts to three places: invoices from suppliers outside the mandate, bank-detail change requests, and the gap between a legitimate invoice and a legitimate order. Generative tools have made convincing fake documents cheap to produce, which is why detection controls now sit on the intake side rather than on visual inspection. Practical defences are unglamorous: never change supplier bank details from an emailed document alone, cross-check every new supplier's SIREN, and flag duplicate invoice numbers across the whole ledger rather than per supplier.

Structured invoicing kills the fake PDF for domestic flows, then pushes fraud toward the channels the mandate does not cover.

Sygnet's guide to detecting AI-generated fake invoices goes through the specific signals worth monitoring.

What should a business that is behind do in the next 30 days?

Confirm three things, in this order: your platform is registered and your account is actually activated, your receiving address is correct in the national directory, and your client and supplier SIREN data is clean.

Verify the platform is genuinely registered by DGFiP, not merely "in the process of registration," since registration guarantees legal conformity and service continuity. The list of the first 101 certified approved platforms has been published, so there is a verifiable reference to check against.

Then integration. If your accountant works on Pennylane, Cegid, Sage or ACD, prefer a platform that integrates natively, otherwise you pay twice: once for the platform, once for importing into your accounts. Accounting firms carry an extra role here: DGFiP formally recognises the central role of chartered accountants in the reform, and companies can mandate their accountant, via an "opt-in" mandate, to register their receiving addresses in the administration's directory.

Training is cheap. One to two hours generally suffices for internal accountants and salespeople who issue invoices. Sygnet's overview of e-invoicing in France covers the document-side implications in more detail.

FAQ

Is a PDF invoice sent by email still valid in France?

No, not for transactions inside the mandate. Simple PDF invoices sent by email no longer meet regulatory requirements from your applicable deadline; only invoices transmitted via an approved platform in a recognised structured format (Factur-X, UBL or CII) are valid. Factur-X is the hybrid option: a PDF/A-3 file carrying both human-readable content and structured data, which is why most small businesses end up on it.

My company is an SME. Do I really have to do anything before September 2027?

Yes. Your issuing obligation starts in September 2027, but reception has been mandatory for all VAT-registered businesses since 1 September 2026. Even businesses under the VAT franchise regime are covered by the reception obligation. If you cannot receive, your suppliers' invoices bounce and your VAT deduction evidence becomes a problem.

Does Chorus Pro disappear?

No. Chorus Pro, operated by the AIFE, remains in 2026 the mandatory channel for invoices sent to public sector bodies, and it coexists with the new approved-platform architecture. If you sell to both private companies and local authorities, expect to run two channels for now.

Can AI software be held responsible if an invoice is non-compliant?

Not in the eyes of the tax authority. The fine lands on the taxable person, which is why extraction tools should produce an audit trail (source file, extracted values, confidence, who approved what) rather than silently posting entries. Keep human approval on anything affecting VAT treatment, and document your controls so a good-faith defence is more than a claim.