We've been exchanging e-invoices in the France e-invoicing pilot. Here's the top things we've learned

For the last few weeks, ecosio has been live in the France e-invoicing pilot, exchanging real invoices on behalf of our customers. The process we went through to be live and exchanging e-invoices on behalf of our customers has taught us far more than any specification ever could. Below are the top lessons we’ve learned and what they mean for your own readiness before the September mandate, along with some insights directly from the pilot feedback meeting given by AIFE on the 7th of July.

TL;DR: what this covers

1. Compliance on paper is not the same as exchanging invoices in production
2. Registration, platform connection, and invoice exchange are three separate milestones
3. Master data quality is the root of most early failures
4. Testing your real use cases matters more than testing the easy ones
5. The pilot lowers risk, but you still need a plan for early issues

1 – Compliance on paper is not the same as production

It is easy to feel ready when every requirement has a tick next to it. A specification is met, a connection is set up, and a test invoice goes through. On a slide, the project looks finished.

Live flows tell a different story. When you send real invoices, in real volumes, with real trading partners, the edge cases appear quickly. A small data issue that slips through a quick test can stop a genuine invoice from being accepted.

That gap between theoretical compliance and a working technical connection is the single biggest thing the pilot has shown us. The good news is that you can close it now, while the stakes are still low.

2 – Registration, connection, and exchange are three different milestones

One early lesson is that being in the system is not the same as being operational. Three steps that sound similar are actually separate:

1. First, you register in the central directory, known in France as the Annuaire.
2. Second, your Accredited Platform, or PA, connects to your ERP, the enterprise system that holds your invoices.
3. Third, you exchange a real invoice and receive the lifecycle statuses back.

Each step can succeed while the next one still fails. An invoice is only truly done once it has been issued, routed, accepted, and acknowledged. If you measure readiness by directory registration alone, you will overestimate how prepared you are.

The PA sitting in the middle of those milestones does far more than move files, so the kind of PA you choose matters more than it first appears: A simple platform can act as a transmission channel that moves an invoice from A to B. A strong, future-ready PA works as a compliance and operational partner, and in the French model that partner can either put you ahead of the pack or hold you back.

When you assess a provider, look well beyond whether it can send and receive an invoice:

• Expertise and industry knowledge: because the French mandate is detailed and still evolving
• Strong integrations: because your PA has to connect to your ERP to collect invoices and send the lifecycle statuses back
• Data security, storage, and reliability: because invoice and tax data are highly sensitive
• Compliance and technical regulatory support: because your obligations do not end once the connection is live, and expert help matters as the rules change
• Ongoing support, flexibility, transparent pricing, and scalability: so you can handle growth and future mandates without hidden costs

So the question to ask is not whether a provider can send and receive an invoice. It is whether it can help you operate reliably under the French model, manage exceptions, support your use cases as they change, and scale to other mandates. That is the standard we hold ourselves to at ecosio, and it is the standard you should expect from any PA you rely on for France.

3 – Master data is where most problems begin

Many e-invoicing issues start before an invoice is even sent. In the pilot, poor master data has been the most common source of friction, and the wider survey data backs this up. Poor data quality was cited by 41 % of companies testing their setups, ahead of format and mapping difficulties at 39% and master data gaps at 37 %.

Your core identifiers have to be reliable in your own systems. That means clean customer and supplier records, correct SIREN and SIRET numbers, which are the French business identifiers, accurate routing data, and valid VAT details.

Routing deserves special attention. To receive invoices correctly, you need to give trading partners the exact routing address held in the central directory. In France that address follows one of these formats:

• SIREN
• SIREN and a routing suffix
• SIREN and SIRET
• SIREN, SIRET, and a routing code

If you exchange through the Peppol network, the same routing address is used, preceded by the French prefix 0225. Get this wrong and the result is not a minor technical error. A missing tax identifier can fail validation, a wrong entity can misroute an invoice, and incorrect VAT inputs can distort totals and reporting.

Left unchecked, these issues flow straight into your P&L through delayed payments, slower cash turnover, audit stress, and possible compliance exposure. Treat master data as core preparation, not a side task.

4 – Test the invoice use cases that actually matter

It is tempting to send one clean invoice, watch it succeed, and declare the project ready. Real operations are rarely that simple.

Before testing, scope your flows. Which invoice types do you really use? Do you handle credit notes, self-billing, factoring, or expense claims? How do corrections and disputes work in practice? The French standards body, AFNOR, sets specific rules for many of these scenarios around references, corrections, and lifecycle events.

The lesson from the pilot is clear. Test the cases that are operationally relevant to your business, not only the easiest ones. If a scenario is common for you today, it belongs in your readiness plan, so that it fails in testing rather than after go-live.

This is also where the right partner matters. A capable PA should already have test examples and help you validate your key use cases, rather than leaving you to work them out alone. Learn more about ecosio Global E-invoicing Compliance.

5 – Plan for day-one issues before they reach your finance team

The pilot lowers risk, but it does not remove it. You may not be able to test every use case with every partner, and some partners will not be ready yet. Even after thorough testing, expect a few issues on day one.

From what we have seen, most early problems fall into three buckets:

• Validation: where invoices are rejected because structured data and VAT logic have to be precise, not just the totals
• Routing and reachability: where identifiers and onboarding decide whether an invoice can find the buyer endpoint
• Operations: where credit notes, exceptions, duplicates, and missing status feedback create queues your finance team cannot clear fast enough

The teams that cope best share one process across Tax, IT, and the business to spot, resolve, and evidence an issue quickly. It also helps to have continuity measures ready, such as queuing messages when an ERP is briefly unavailable, pre-configured fallback channels, and a way to view, download, and action invoices manually if needed.

None of this replaces preparation, but it turns a first-week scramble into a controlled process.

There is a further lesson for larger businesses: From September 2026 you will exchange e-invoices under the French mandate, but many of your smaller suppliers are not yet in scope. Small and micro companies only have to issue e-invoices from September 2027, so until then you need to keep a separate flow for these long-tail suppliers and carry on receiving and processing their invoices without breaking your compliant process.

This is where early supplier onboarding matters. Even if your own systems are ready, smaller suppliers may still send invoices through PDFs, email, or other inconsistent channels until they are fully under scope of the France e-invoicing mandate for structured e-invoicing. ecosio supplier activation helps you bring those suppliers into one managed process, using Flow for suppliers without EDI capabilities, you can reduce exceptions and keep invoice flows consistent before and after the 2027 deadline. Learn more about ecosio supplier activation.

Treat the pilot as your grace period

The pilot is the safest time to find and fix problems. There may be some flexibility after September, but you should not build your readiness plan around it. Testing now helps you uncover issues while there is still time to fix them before the deadline.

If you are preparing for September, put these actions at the centre of your plan:

• Test in production now, not just in a sandbox
• Validate your data against real transactions
• Rehearse your use cases and your exception handling
• Build a readiness plan you can evidence

Your France e-invoicing pilot readiness checklist

The pilot has real momentum. Directory flow conformance recently reached 98.9 %, up from 62 % in March, and declarative flows passing rose to 90.2 %, up from 37 %. Confidence is rising too, with 87.5 % of surveyed large and mid-sized companies expecting to be ready for the 1 September deadline.

If you want to make the most of the pilot, work through these six areas:

1. Identify your tiger team so Tax, IT, and the business share ownership
2. Confirm your Accredited Platform and check it can support your use cases
3. Clean and validate your master data before you test
4. Scope and test the invoice use cases that matter to your business
5. Keep a separate process for flows that only come into scope in 2027
6. Join the pilot and rehearse what happens when something goes wrong

You can read the official requirements and timelines directly from the French tax authority on impots.gouv.fr.

Ready to close the gap?

The pilot is your grace period. The sooner you test in real conditions, the calmer September will be. Learn more about how ecosio supports global e-invoicing compliance, and let’s talk about getting your flows ready.