Suppliers invoicing French companies must prepare for mandatory electronic invoicing, which phases in from September 2026 for receiving invoices and for large and mid-sized companies issuing them, with smaller firms following in 2027. Preparation means confirming your customers' platform requirements, choosing a structured invoice format, and checking that your invoicing software can send and receive those files.
Key takeaways
- Receiving electronic invoices becomes mandatory for all French businesses first, so your buyers may expect structured files before you are required to issue them.
- Issuing obligations depend on company size and follow a staggered timetable set in French law.
- Invoices generally travel through accredited platforms, not as plain PDF attachments sent by email.
- Your invoicing data must be complete and consistent, because structured formats expose gaps that a PDF hides.
What does the reform require?
The reform moves domestic business-to-business invoicing in France from paper and PDF exchange towards structured electronic invoices that can be processed automatically. Its legal basis sits in French law that implements EU VAT rules, and the timetable is set nationally. This article is general information and not legal or tax advice.
The official reference points are the French tax administration portal at impots.gouv.fr, which publishes the phase-in dates and technical guidance, and the EU law database EUR-Lex, where the underlying VAT Directive 2006/112/EC can be read. Read the current official text rather than secondary summaries, since dates and details have been amended over time.
The practical change is that an invoice becomes a data message. A buyer's system needs to read fields such as seller and buyer identifiers, VAT breakdown and payment terms without manual re-keying. If your invoice exists only as a formatted document, your customers may reject it or process it by hand.
Which suppliers are affected and when?
Every French business needs to be able to receive electronic invoices from the start of the reform, so as a supplier you should first check what your customers now expect. Issuing obligations are staged by company size, with large and mid-sized companies moving first and smaller companies later. Confirm the exact dates for your category on the official French site, because they are set by law and may change.
Check your customer mix
Suppliers with a mix of French customers of different sizes face overlapping timetables. You may be required to issue structured invoices to some buyers before others are ready to receive them through the same route. Map your French customers by size and by whether they are domestic or foreign before choosing a rollout order.
Check cross-border and consumer sales
Sales to consumers and most cross-border transactions are handled differently from domestic B2B invoices. They are covered by a separate reporting regime, described in a later section. Do not assume that the B2B timetable applies to them without checking the official rules.
Which formats and platforms can you use?
Structured formats are the core of the reform, and the platform route is how invoices reach the buyer's system. Choose a format your invoicing tool can generate correctly, and a platform that can transmit it to your customers' platforms. Both choices should be confirmed against the official French guidance on the impots.gouv.fr portal before you commit.
Structured formats
Formats such as Factur-X, UBL and UN/CEFACT CII are the families commonly discussed for French e-invoicing. Factur-X combines a human-readable PDF with embedded structured data, which can ease the transition for teams that still need a visual invoice. Pure XML formats are fully machine-readable but are harder to check by eye. The right choice depends on how your buyers' systems ingest data.
Accredited platforms
Invoices are exchanged through platforms that the French system recognises, so you usually need a contract with one before you can comply. Compare platforms on supported formats, connection options to your ERP or accounting software, error reporting, and how they handle invoices to buyers who are not yet on the same platform. Ask each provider to show you its own documentation, not only a sales deck.
How does e-reporting differ from e-invoicing?
E-reporting means transmitting transaction data to the tax authority rather than sending the invoice to the buyer's platform. It applies to categories such as business-to-consumer sales and many cross-border transactions. The buyer never receives a structured invoice through the platform in these cases, so your reporting process must be designed separately.
Plan for both flows if you sell to consumers or abroad. A single invoice may need to be issued in a structured format for one customer and reported as transaction data for another. Your invoicing software should tag each invoice with the correct regime from the start, not reconstruct it later at period end.
How should you prepare your invoicing process?
Start with a short audit of your current invoice flow, then fix the data before you change the format. Most delays come from inconsistent customer master data, missing VAT numbers and invoice numbering that differs across systems, rather than from the file format itself. Work through the following steps in order.
- List every system that produces an invoice, including ERP, CRM, e-commerce and manual templates.
- Verify customer identifiers, VAT numbers and billing addresses in your master data.
- Confirm invoice numbering is unique, sequential and consistent across all sources.
- Select a structured format and a platform, and confirm both with the official guidance.
- Connect your invoicing system to the platform and test with sample invoices.
- Define how invoices to consumers and foreign buyers will be routed and reported.
- Train finance and sales staff on exceptions, rejections and where to find status updates.
Integration is usually the hardest step. If your invoices are created in one system and booked in another, every hand-off is a place where data can change. Reducing manual copying between tools is often more valuable than any single format decision. For teams facing this, a guide on system integration and API engineering on the Rui Codex blog covers the underlying patterns.
What are the trade-offs between preparation approaches?
The main choice is between using the invoicing features of your existing software and connecting a separate platform through an integration layer. Each approach works well in some setups and fails in others. The table below compares them on qualitative criteria only.
| Approach | Strengths | Where it fails |
|---|---|---|
| Native invoicing module in existing software | Single system to maintain and fewer hand-offs | Depends on the vendor shipping support on the required timetable and formats |
| Separate platform with a custom connector | Works across mixed software estates and gives control over mapping | Connector logic must be maintained when either side changes its data model |
| Manual upload through a portal | Little upfront setup for very low volumes | Does not scale, invites keying errors and leaves no clean audit trail |
A custom connector is worth the effort when invoices originate in several systems or when you already maintain integrations between them. It is harder to justify for a single system with low volume, where a vendor-supported module may be simpler. In both cases, the test of the approach is whether a rejected invoice can be traced back to its source within minutes.
Hypothetical examples of supplier preparation
Here are two hypothetical scenarios:
Scenario one: A supplier of industrial spare parts issues invoices from an ERP and a separate order tool. Its customer master data has duplicate records with different VAT numbers, so the first test batch is rejected. The team fixes the master data before changing the format, and the rejections stop once identifiers are consistent.
Scenario two: A software services firm invoices mostly French businesses but also sells online to consumers. It tags each invoice by regime at creation, so B2B invoices go through the platform and consumer sales are reported as transaction data. The split is simple because it was designed before go-live.
How can technical support help with the rollout?
Rui Codex offers technical implementation support for invoicing integrations, including connecting ERP, CRM and accounting data to a platform and testing the resulting files. Rui Codex does not provide legal, tax or compliance advice, so the regulatory questions should go to your tax adviser. The founder, Selman Altinay, leads Rui Codex with 200+ projects delivered and 12+ years of hands-on experience. You can review the integration services at ERP and CRM integration services or the general integrations offering.
Frequently Asked Questions
Do all French suppliers have to send e-invoices?
Not every supplier is affected on the same date. All businesses must be able to receive electronic invoices from September 2026, while the obligation to issue them depends on company size and phases in from September 2026 for large and mid-sized companies and from September 2027 for smaller ones. Check the current official schedule on impots.gouv.fr before planning your rollout.
Which invoice formats are accepted under the reform?
The reform relies on structured electronic formats rather than image-based PDFs alone. Factur-X, UBL and UN/CEFACT CII are the formats commonly discussed for French e-invoicing, and your platform should produce and read at least one of them. Confirm the exact list with your chosen provider and the official French guidance before committing.
Can I send invoices directly to a customer's email inbox?
Generally no, because the reform routes domestic B2B invoices through accredited platforms rather than plain email attachments. Suppliers typically send invoices through an approved platform, which transmits them to the buyer's platform and handles required reporting. Verify the rules for your specific transaction types against the official guidance.
Does the reform affect sales to consumers or foreign customers?
Business-to-consumer sales and many cross-border transactions fall under e-reporting rather than full B2B e-invoicing. E-reporting means transmitting transaction data to the tax authority, not sending the invoice to the buyer's platform. The details depend on the transaction, so confirm them against the official text and your tax adviser's guidance.
Conclusion
The French reform changes how invoices move, not only how they look. Suppliers who start with clean customer data, a confirmed format and a tested platform connection will face fewer surprises than those who wait for the deadline. Map your customers, separate B2B invoices from consumer and cross-border sales, and test with real sample data. To discuss your rollout, request a project consultation at https://ruicodex.com/Contact or email info@ruicodex.com.
Sources
- EUR-Lex, the official EU law database - Publications Office of the European Union
- impots.gouv.fr, the French tax administration portal - Direction générale des Finances publiques