Legacy master data, ERP integration, validation and reporting flows emerge as the real challenges in France’s new regime
France’s first weeks of mandatory e-invoicing have exposed problems with missing data, invalid identifiers, VAT inconsistencies, platform configuration, routing and e-reporting.
Compliance rates are improving rapidly. But the early experience raises a wider question for governments designing e-invoicing and continuous transaction control regimes: how much data should they demand beyond the traditional VAT invoice?
France goes deeper than the traditional VAT invoice
France combines B2B e-invoicing with transaction and payment e-reporting, detailed validations, a central directory, the Public Invoicing Portal (PPF) and a large network of Approved Platforms (PAs).
This gives the tax authority richer and more timely information. But it also means businesses may have to assemble data from ERP fields, customer and supplier master data, payment systems and other processes.
The further reporting moves beyond information naturally required to create the VAT invoice, the greater the integration challenge.
E-invoicing is exposing legacy data weaknesses
Missing mandatory fields accounted for around 32% of non-compliant flows during one early monitoring period. Other problems included invalid SIREN identifiers, VAT inconsistencies and duplicate transactions.
Much of this is not really an e-invoicing problem. It is exposing weaknesses in existing business data.
Customer records and tax identifiers that could previously be interpreted or corrected manually must now pass automated transaction-level validation. Data that businesses have tolerated for years suddenly has to be complete, structured and consistent.
That is also one of the benefits of digital reporting. Rejections can expose bad master data or VAT inconsistencies before they travel further through the compliance process.
Not all the problems are data
France’s architecture also introduces multiple technical dependencies.
One Authorised Platform incorrectly included F10 e-reporting tags in F1 invoice flows, accounting for most of 142,923 failed F1 files over three days. Problems have also emerged around directory management, routing and Chorus Pro connectivity.
The challenge therefore runs across the chain:
source data → ERP mapping → platform → routing → reporting
Businesses and practitioners have also reported repeated rejection and resubmission of flows and difficulties with tax identifiers, master data and legacy manual processes.
A lesson for VAT in the Digital Age
France provides an interesting comparison with the EU’s VAT in the Digital Age reforms, which move towards structured electronic invoices and transaction-level digital reporting for intra-EU transactions from July 2030.
France shows the potential benefits of going further, but also the cost.
Every additional national data field, validation or reporting flow potentially requires businesses to find, transform and reconcile more information. A common invoice syntax delivers only limited harmonisation if each country then requires different enrichment around it.
September 2027 will be the bigger French test
From 1 September 2027, SMEs and micro-enterprises become subject to mandatory e-invoice issuance and e-reporting.
Large businesses generally have greater resources for ERP integration, tax governance and master-data remediation. Yet they and their technology providers are already encountering problems.
Extending the model across France’s much larger SME population will be an important test of its scalability.
It’s not formats. It’s data.
Creating a structured electronic invoice may prove to be the relatively straightforward part of digital VAT reform.
The harder task is ensuring that the underlying information can be sourced, validated and reconciled across ERP systems, master data, payments, VAT determination, e-invoicing and reporting.
France’s early experience suggests a useful question for other tax authorities: how much data beyond the VAT invoice is really needed?
