French e-invoicing: six priorities for accountancy firms in 2026

Since the 1st of September 2026, every business registered for VAT in France has had to be able to receive its invoices electronically, while large companies and mid-sized enterprises must also issue them and transmit their e-reporting data. If your firm audits or serves French entities, the preparation phase is behind you. What remains open is what to do with what the reform now produces.

Because mandatory e-invoicing does not only produce compliant invoices. It produces a normalised, timestamped stream that a machine can read directly. That is the raw material artificial intelligence has been waiting for inside an accountancy practice, less because the tools were missing than because the input data was irregular.

The regulatory calendar has already been covered here, in the compliance checklist and in the article on regulatory convergence in 2026. This one deals with what comes next.

What actually changed on the 1st September 2026?

Invoices no longer travel freely from a supplier to its customer. They pass through a plateforme agréée, an approved platform that each business appoints on its own behalf, either directly or through compatible software. The public invoicing portal, now narrowed to the central recipient directory and the data concentrator, no longer handles the exchange itself.

The vocabulary followed. Decree No. 2026-677 of 27 July 2026 established plateforme agréée (PA) as the official designation, replacing the earlier plateforme de dématérialisation partenaire (PDP), and requires platforms to produce a supervisory audit report within two years of registration.

The content of the invoice changed as well, and that is the least discussed point. Four fields became mandatory: the customer's SIREN company identifier, the delivery address where it differs from the billing address, the category of the transaction, and, where applicable, the election to account for VAT on an accruals basis. Those four fields are what will make the data workable later on.

Why is invoice data now usable?

Two sets of data appear at the same moment, having existed until now neither in a uniform shape nor in the same place.

The first is the content of the invoice. The three formats admitted by the reform, Factur-X, UBL and CII, are three renderings of a single European semantic model: the standard EN 16931, published by the European Committee for Standardization and adopted in France by AFNOR. It defines what information an invoice must carry, whatever the file encoding. A field read at one client therefore sits in the same place at the next. Optical character recognition, with its error rate and its manual corrections, stops being the entry point, and the customer's SIREN gives a reliable key for matching counterparties that a company name alone never provided.

The second set is the lifecycle. The reform prescribes four mandatory statuses, transmitted to the tax authority by the platform: déposée (submitted), refusée (refused by the recipient), rejetée (rejected on technical grounds) and encaissée (cash collected). The last one triggers the transmission of payment data where VAT falls due on collection. Recommended statuses sit alongside them, including approuvée (approved) and paiement transmis (payment sent).

Which six priorities should an audit firm act on?

1. Map your clients' approved platforms, then test extraction

Each client appoints its own platform. A firm with two hundred client files therefore faces a mixed landscape it does not control. Before considering any analytical tool, you need to know where the flows land and in what shape.

Go client by client and record the platform chosen, its registration status on the official DGFiP list, and the client's entry in the directory of VAT-registered businesses, without which no invoice will reach it. That official list is updated as registrations come through and it is the only one that counts. A status displayed on a vendor's website is not the directory.

Then take a dozen real invoices per format and check what your production software actually extracts. The gaps you find will make better use cases than a roadmap written in the abstract.

2. Document each client's compliance trail

On 10 July 2026, the French public accounts minister announced a listening and support phase for the start of the reform, set out afterwards in a practical guide from the DGFiP. Penalties will not be applied immediately and automatically to a good-faith business meeting a genuine difficulty. The obligation itself stands: the administration was careful to state that this is neither a postponement nor a suspension.

What concerns the firm comes next. That forbearance rests on the business being able to demonstrate a serious effort, meaning a difficulty that is real, recorded, and followed by corrective steps. Protection therefore depends on a written record. Choice of platform, exchanges with the software vendor, tests carried out, incidents encountered, remediation under way: the firm is best placed to keep that register, and the work can be contracted for. It is worth using the same moment to set out, in the engagement letter, the scope of the data access mandate and how far back it reaches, both of which will determine what can be built in 2028.

3. Build a clean counterparty master file

In most practices, counterparty records have silted up over the years, with duplicates, approximate company names, entities that can no longer be traced. No analytical model will produce anything usable on a base like that. Yet the switchover requires collecting each client's SIREN, which is an opening to deduplicate, group entities belonging to the same parent, and record what remains uncertain, all in a single pass. The work is thankless and its effects show up in every project that follows.

4. Read rejections and refusals as an advisory signal

A rejection flags an anomaly picked up by a platform during its checks. A refusal flags a disagreement from the recipient. Both are now traced, dated and countable.

Where a client's rejection rate stays high over time, the cause is rarely the invoice itself: it lies in the process, the customer master file or the configuration. The firm is the only party with a comparative view across a whole portfolio, and therefore the only one able to place one client against the others. These indicators also belong in the permanent file and in the risk assessment, where they carry more recent and finer information than the prior year's financial statements.

The reading is only worth something if it is produced regularly and set out in terms the business owner understands. On those conditions it is advisory work and it bills as such.

5. Move from sampling to full-population testing

Sampling was born of a physical constraint: you could not examine every entry. That constraint eases once the data arrives standardised at source.

Full-population testing means scoring every journal entry against explicit rules, then surfacing those that depart from normal behaviour. Round-sum amounts, entries posted outside working hours, approval routes bypassed, no match against a received invoice. Start with rules that are simple and legible rather than with an opaque model, on a single type of engagement.

The time saved matters less than the ability to run these checks as the year goes along rather than at the close, and so to smooth a workload whose seasonality everyone knows. One qualification is needed, though: these systems produce signals, not conclusions. Professional judgement and the audit opinion remain wholly with the auditor.

6. Write the data rule, and reread the vendor contract

Professional confidentiality does not sit well with client data being fed into a consumer generative AI service. The CNCC, the French statutory auditors' body, and the national institute of chartered accountants are explicit on the point. Their guidance notes and model charters carry no force of law, but they are the benchmark an inspection will apply. Compliant patterns exist: API access with an explicit no-training clause, or a private environment.

An obligation already bears on the firm alongside this. Article 4 of the EU AI Act has required a sufficient level of AI literacy among staff since 2 February 2025, proportionate to their role. Since 2 August 2026, national authorities have held their enforcement powers. No assessment of knowledge is required; a documented training plan is the supporting evidence.

One point remains for the partners. The EU directive on liability for defective products, to be transposed by 9 December 2026 at the latest, brings software and AI systems within the scope of products and eases a claimant's access to evidence held by the supplier. It does not transfer the firm's own professional liability, which remains whole; it strengthens the firm's position towards its vendor. Accuracy warranties, incident notification, logging, indemnities: these are clauses better negotiated at signature.

Where to begin?

The six priorities do not run in parallel. The first two are organisational and can start now, client by client. The third calls for a dedicated campaign. The last three need a decision from the top, because they commit the firm's engagement model and not merely its tooling.

The obstacle is rarely technical. More often it sits in the coordination between the partners, the production teams and IT, each working to its own calendar. That question of change management is what the RESONANCE™ approach addresses first, ahead of the tool.

The online assessment is free and carries no obligation.

Assess your firm's digital maturity

Advisory work is delivered to firms across France and Europe, from a base near Toulouse in the Occitanie region.

Frequently asked questions

Is a PDF sent by email an electronic invoice?

No. The invoice must be issued in a structured format conforming to the EN 16931 model, meaning Factur-X, UBL or CII, and must pass through an approved platform. An ordinary PDF or a scanned paper document does not meet those conditions.

Does the firm choose its clients' approved platform?

No. Each business appoints its own. The firm's role is to inform that choice, then to check the registration status on the official DGFiP list before any contract is signed.

Does the administration's forbearance remove the need to comply?

No. The obligation is neither postponed nor suspended. The forbearance applies to the enforcement of penalties and presupposes a difficulty that is real, documented and followed by corrective steps.

Is there a professional standard governing AI use in a practice?

No standard in the regulatory sense. The CNCC and the national institute of chartered accountants have published guidance notes and model charters that set out expected practice. The EU AI Act, by contrast, applies directly.

How do you tell whether any of this is working?

In the places where data used to be reconstructed by hand: the share of invoices posted without rework, the delay between receipt and posting, the proportion of anomalies caught before review rather than during it. These observations are worth something compared against themselves, on a stable scope.