Seamless generation of Factur-X, CII, and UBL e-invoices

Factur-X, CII, and UBL-compliant e-invoices software for France e-invoicing. Integrates with all ERP's market leader

E-Invoicing in France: Twelve Implementation Mistakes to Avoid After the 2026 Go-Live

E-Invoicing in France: Twelve Implementation Mistakes to Avoid After the 2026 Go-Live


Since 1 September 2026, when receiving e-invoices became mandatory for every business and issuing became mandatory for large companies and ETIs, early field feedback points the same way: projects rarely fall behind because of technology. They slip for reasons of method, such as a late start, incomplete customer files or a platform chosen too quickly. These twelve mistakes matter most for SMEs, which will issue e-invoices from 1 September 2027.


The Regulatory Basis: What the French Obligation Requires


In practice, an e-invoicing project covers three flows: issuing structured invoices to customers, receiving suppliers' invoices and sending data to the tax administration. The first two must go through an approved platform. Accepted formats, the timeline and penalties are set by Article 123 of the 2026 Finance Law, covered in our note on the 2026 Finance Law.


Not every transaction follows the same route: consumer sales and international transactions fall under e-reporting, and public-sector invoices are still filed on Chorus Pro. Mapping these three routes at the scoping stage avoids discovering a forgotten flow during testing.


Twelve Implementation Mistakes and How to Prevent Them


These twelve mistakes are listed in the order they usually appear during a project.


Mistake 1: Treating the Deadline as the Starting Point


An e-invoicing project usually takes several months: system audit, ERP configuration, data cleanup, platform selection, testing and training. An SME that waits until summer 2027 to start will not have time to fix rejections before 1 September 2027. It is safer to plan backwards from the deadline, keeping several weeks for testing with trading partners.


Mistake 2: Choosing a Platform Without a Structured Assessment


More than a hundred platforms appear on the list published by the tax administration, with very different offers. A choice based on price alone or a sales demo leads to surprises: no ERP connector, archiving not included, volumes charged above a threshold. A written scoring grid covering integration, formats, archiving, support and international coverage lets you compare offers on the same criteria.


Mistake 3: Assuming the Obligation Does Not Apply to Your Business


Every VAT-registered business established in France is covered, including micro-enterprises under the franchise regime. Size only decides the issuing date. A business that mainly sells to consumers must still be able to receive its suppliers' invoices and send its e-reporting data.


Mistake 4: Choosing a France-Only Solution


The EU's ViDA package, adopted on 11 March 2025 through Directive (EU) 2025/516, makes e-invoicing mandatory for intra-EU B2B transactions from 1 July 2030. For a group operating in several countries, a Peppol-compatible solution that can follow other national regimes avoids multiplying integrations.


Mistake 5: Underestimating Master Data Quality


An e-invoice is checked automatically: a wrong SIREN number, a misconfigured VAT rate or an incomplete address is enough to trigger a rejection. Routing also depends on the central directory, which links each business to its platform. An audit of customer, supplier and item files, followed by a lasting update rule, sharply reduces rejections.


Mistake 6: Leaving the Project to a Single Team


The reform affects purchasing, sales, accounting, tax, IT and customer relations. Leaving the project to a provider or to IT alone overlooks business decisions, such as how to handle rejected invoices or disputes. A cross-functional steering committee with an executive sponsor keeps those decisions inside the business.


Mistake 7: Neglecting Change Management


Accounting teams move from keying in invoices to handling statuses and exceptions. Without training or written procedures, rejections pile up and suppliers chase late payments. Simple procedures, training before go-live and a named point of contact shorten this adjustment period.


Mistake 8: Relying on a Free Public Portal


Many project budgets assumed that a free public portal would be enough for small businesses. That service does not exist: the State limited itself to the directory and data collection, and every business must choose an approved platform, sometimes free for small volumes. A business that learns this late has to compare offers in a rush. The State's changing role is explained in our article on Chorus Pro and the public invoicing portal.


Mistake 9: Running Several Platforms Without a Reason


A business can, in some cases, use several platforms, for example for separate establishments or activities. Without a clear rule, this creates directory inconsistencies, duplicate costs and reconciliation problems. One platform per scope, documented in the directory, remains the simplest setup to manage.


Mistake 10: Planning Only the First Step


The reform rolls out in stages: receiving in 2026, issuing and e-reporting in 2027 for SMEs, then EU obligations in 2030. A solution chosen only to receive invoices may not handle e-reporting for B2C transactions or payments. It is better to check from the start that the platform covers every upcoming obligation.


Mistake 11: Neglecting Archiving and Integrity


Invoices must be kept for six years under the Book of Tax Procedures and ten years under the Commercial Code, in conditions that guarantee their authenticity, integrity and legibility. Not every platform contract includes archiving with evidential value for that period. The options, including electronic signatures and seals, are covered in our article on electronic signatures in e-invoicing.


Mistake 12: Leaving Out Mandatory Mentions


The reform added new mandatory mentions, including the customer's SIREN number, and an approved platform automatically rejects an incomplete invoice. The typical mistake is to fix the invoice template without fixing the customer files that feed it: the field exists but stays empty. The full list is in our guide to mandatory invoice mentions.


A Framework for Structured Implementation


A successful implementation usually follows seven steps, in this order:


  1. Governance: appoint a sponsor, set up a cross-functional committee and plan backwards from the deadline.
  2. Regulatory analysis: map B2B, B2C, international and public-sector flows, and the deadline that applies.
  3. Technical review: check that the ERP can produce the formats and process incoming invoices.
  4. Master data: fix customer, supplier and item files before testing.
  5. Platform choice: compare offers on a written grid that includes future obligations.
  6. Pilot: test with a few real partners before rolling out.
  7. Monitoring: track rejections, statuses and regulatory changes.


The misconceptions that often delay these steps are analysed in our article on seven misconceptions about the reform, and the regulatory background in our article on the compliance framework.


Frequently Asked Questions


What is the most common mistake in an e-invoicing project? Starting too late. Testing with partners and fixing data often take longer than planned.


Can an SME still wait before acting? No. It must already be able to receive e-invoices, and issuing becomes mandatory on 1 September 2027.


How long must e-invoices be kept? Six years under tax law and ten years under the Commercial Code.


Can a business use several approved platforms? Yes, in some cases, but each choice must be documented in the central directory to avoid routing errors.


Conclusion


None of these twelve mistakes is strictly technical: all of them come down to organisation, timing or data quality. For an SME, the most useful step now is to set a start date, an owner and a list of pilot partners, then build the rest of the project around those three decisions.

Accqrate supports this kind of project with an e-invoicing solution that connects to the existing ERP and tracks the status of invoices sent and received.


cta.title1

cta.description1cta.description2
cta.badge1starcta.badge2starcta.badge3
Dashboard Views