By clicking “Accept”, you agree that cookies may be stored on your device in order to improve site navigation, analyze site usage, and help us with our marketing efforts. Check out our for more information.

Guides

E-invoicing in France for large companies: the high-volume compliance guide

#QUOTE-TO-CASH Insights
Opencell #QUOTE-TO-CASH Insights cover: E-invoicing in France, the guide

E-invoicing in France for large companies: the high-volume compliance guide

OpencellNovember 21, 202616 min read

The platform transmits the invoice. It checks neither the price, the discount nor the usage.

Since September 1, 2026, e-invoicing has been a reality for large French companies. According to impots.gouv.fr, every company must be able to receive electronic invoices since that date; issuing them is mandatory for large companies and mid-sized companies, and will be from September 1, 2027 for small and micro businesses.

Most content about the reform is aimed at small businesses: how to choose software, how to send your first invoices. Large companies have a different problem. They issue thousands, sometimes millions of invoices a month, from subscriptions, usage, negotiated contracts and customers organized into groups. For them, the reform is not a change of tool: it is a full-scale test of the quality of their entire billing chain.

E-invoicing has one particularity: it makes errors visible, immediately and traceably, that used to be settled by an exchange of emails. A rejected or refused invoice is no longer a discreet incident, it is a status, measurable, that delays payment.

This guide is for large companies and international groups with French entities. It explains what has changed for large and mid-sized companies, why high volumes change the nature of the topic, and how to organize compliance upstream, from the catalog to usage rating. It does not replace advice from your tax advisers, nor the official specifications.

For the overall framework, see our guide to quote-to-cash.

What changed on September 1, 2026

Since September 1, 2026, large and mid-sized companies in France must issue e-invoices for B2B sales between companies established in France, receive e-invoices and transmit e-reporting data. Invoices go through certified platforms, in Factur-X, CII or UBL format.

The reform rests on three obligations, which apply according to company size:

Obligation Large and mid-sized companies Small and micro businesses
Receive e-invoices Since September 1, 2026 Since September 1, 2026
Issue e-invoices (sales between companies established in France) Since September 1, 2026 From September 1, 2027
Transmit data on other transactions (e-reporting) Since September 1, 2026 From September 1, 2027

Invoices no longer travel by email or post, but through certified platforms. According to a LégiFiscal fact sheet, a certified platform is a dematerialization operator registered by the State; it issues, transmits and receives invoices for its clients and extracts the data the tax authority needs. Each company chooses a single platform to receive its invoices, but can use several to issue them.

Invoices must be produced in a structured format. The same source cites the three accepted formats: Factur-X, a PDF that embeds structured data, and the CII and UBL data formats.

Why high volumes change everything

At high volumes, every data defect repeats on every cycle: recurring invoices replicate errors, usage invoices inherit the quality of consumption data, billing cycles are concentrated, and enterprise customers impose their own rules. A rejection rate of a few percent means thousands of invoices to rework.

For a small business issuing fifty invoices a month, an error is fixed by hand. For a large company issuing hundreds of thousands, every defect is reproduced at scale.

Recurring invoices

Subscriptions produce invoices at each billing date, often on the same day for a large share of customers. Wrong customer data, a badly configured proration rule or a wrongly dated discount repeats at every cycle. Our guide to recurring billing details these mechanisms.

Usage invoices

When part of the invoice depends on usage (minutes, gigabytes, kilowatt-hours, API calls), the e-invoice inherits the quality of the consumption data. A lost session, a meter attached to the wrong contract, a duplicate, and the invoice is wrong before it is even issued. That is the whole point of billing mediation and usage-based billing.

Concentrated billing cycles

Large companies often issue most of their invoices in a few days. A rejection rate of a few percent then represents thousands of invoices to rework at short notice, with a direct impact on cash.

Enterprise customers

Large B2B customers impose their rules: purchase order number, billed entity, cost allocation reference, detail per site. An e-invoice that does not respect them is refused, and the refusal is now tracked.

Situation Effect of an error at a small business Effect at a large company
Wrong customer data One invoice to correct The same error on every cycle, for every customer concerned
Badly configured price rule A few wrong invoices Thousands of invoices to cancel and reissue
Incomplete usage A one-off omission Systematic revenue loss
Spike of rejections at month end A few hours of work A significant delay in collection

The invoice becomes data

An e-invoice is a set of structured data read by several systems. New mandatory mentions include the buyer's SIREN number, the transaction category and, where applicable, the option for VAT on debits. None of this is invented at billing time: it comes from customer master data, the catalog and contracts.

An e-invoice is not a PDF sent through another channel. It is a set of structured data, read by the supplier's platform, the customer's platform, the customer's accounting system and, in part, by the tax authority.

New mentions

The reform adds mandatory mentions. According to Fiducial, they include the business buyer's SIREN number (the French company identification number), the category of the transaction (supply of goods, provision of services or mixed transaction) and, where applicable, the mention of the option to pay VAT on debits. The delivery address must still be specified when it differs from the billing address.

Where the data comes from

None of this information is invented at the moment of billing:

  • the customer's SIREN and electronic billing address come from customer master data;
  • the transaction category comes from the offer catalog: every product must be qualified;
  • the VAT rules come from the catalog, the contract and the customer profile;
  • the amounts come from prices, discounts, contracts and rated usage.

If customer master data is incomplete or the catalog is not qualified, the e-invoice will be incomplete or wrong, however good the platform.

Lifecycle statuses and what they cost

Four lifecycle statuses are mandatory: submitted, rejected, refused and collected. A rejected invoice must be corrected and reissued; a refused one requires a credit note and a new invoice. Both delay payment, but statuses also make billing quality measurable for the first time.

Every e-invoice follows a lifecycle, materialized by statuses exchanged between platforms. Four statuses are mandatory, according to Pennylane: submitted, rejected, refused and collected.

Status What it means Consequence
Submitted The invoice has been transmitted to the platform The cycle begins
Rejected The invoice is blocked before reaching the customer, for a formal reason Correction and reissue
Refused The customer disputes the invoice Credit note, then new invoice
Collected Payment has been received Useful in particular when VAT is due on receipt

The cost of a rejection or refusal

A rejected invoice must be corrected and reissued. A refused invoice requires a credit note and a new invoice, with a new approval cycle at the customer. In both cases, the payment due date moves back. At scale, the effect on average payment time is direct, as our guide to reducing DSO explains.

New visibility

Statuses also have an advantage: what used to get lost in email inboxes becomes measurable. Rejection rate by reason, refusal rate by customer, time between submission and collection: these indicators make it possible, for the first time, to manage billing quality end to end. The statuses still have to flow back into the billing system and trigger an action.

Multi-entity customers, SIREN and the directory

For an e-invoice to reach the right place, the supplier must know the right recipient entity and its electronic billing address. Group customers, organizational changes and multi-entity suppliers make customer master data and account hierarchies a compliance issue.

For an e-invoice to arrive in the right place, the supplier must know the right recipient entity and its electronic billing address. According to LégiFiscal, a central directory, open since September 18, 2025, lists the companies and public entities concerned and supports interoperability between platforms.

For a large company, three difficulties come up often:

  • group customers: a parent company and dozens of subsidiaries, each with its own SIREN; the invoice must target the right entity, the one that ordered and pays;
  • organizational changes: mergers, disposals, relocations, which change entities and their addresses;
  • suppliers that are themselves multi-entity: each French issuing entity has its own obligations, platform and numbering.

An entity error, once corrected by a simple exchange, becomes a rejection or a refusal. The quality of customer master data and account hierarchies therefore becomes a compliance issue.

E-reporting for consumer and cross-border sales

Sales to consumers, sales to foreign customers and some payments fall under e-reporting: the company transmits transaction and payment data to the tax authority through its platform. Billing must feed both e-invoicing and e-reporting from the same data.

Not every transaction gives rise to an e-invoice between French companies. Sales to consumers, sales to foreign customers and some collections fall under e-reporting: the company transmits transaction and payment data to the tax authority through its platform.

According to impots.gouv.fr, the frequency depends on the VAT regime: under the standard monthly regime, transaction data is transmitted every ten days and payment data monthly.

For large companies selling both to businesses and to consumers, as in telecoms, energy or digital services, billing must therefore feed two flows from the same data: e-invoicing and e-reporting. Our guide to e-reporting in France details these obligations.

Compliance is won upstream

The certified platform transmits, checks the format and exchanges statuses. It does not check that the price is right, the discount still valid, all usage billed or the right customer targeted. Those errors are born upstream, across the quote-to-cash chain.

The certified platform is essential: it transmits, checks the format, exchanges statuses. But it does not check that the price applied is right, that the discount is still valid, that all usage has been billed or that the right customer is targeted. These errors are born upstream, all along the quote-to-cash chain.

Step What must be made reliable Error avoided
Customer master data SIREN, entity, electronic billing address, purchase orders Rejection, refusal for wrong entity
Catalog Product qualification, transaction category, VAT rules Missing or wrong mentions
Contracts and orders Negotiated prices, dated discounts, amendments Refusal for disputed price
Usage Complete collection, checks, attachment to the right contract Incomplete invoice, revenue leakage
Rating Application of tiers, included volumes, proration Wrong amount
Pre-issue checks Comparison with the previous invoice, alerts on gaps Errors caught before the customer sees them

These causes of rejection look very much like the causes of revenue leakage: a customer referenced wrongly, a forgotten discount, incomplete usage, an amendment not carried over. The reform does not create them, it reveals them.

Organizing the project with your certified platform

Split roles between billing, the certified platform, ERP and business teams; map flows, measure data quality, fix master data, connect and test on real cases, then manage rejection and refusal rates. Companies that use the reform to make their chain reliable gain lasting benefits.

Splitting roles

Player Role
Billing system Produce accurate, complete invoices with all required data, and integrate returned statuses
Certified platform Transmit invoices, check their format, exchange statuses, transmit e-reporting
ERP and accounting Record invoices issued and received, reconcile payments
Business teams Keep customer, catalog and contract master data up to date

The steps

  1. Map the flows: issuing entities, volumes, customer types, billing cycles, sales falling under e-reporting.
  2. Measure data quality: share of customers without SIREN, unqualified products, incomplete contracts.
  3. Fix master data before connecting the flows.
  4. Connect and test with the certified platform, on real cycles and difficult cases: credit notes, corrective invoices, group customers, usage.
  5. Manage after go-live: rejection and refusal rates by reason, lead times, collections.

Seizing the opportunity

Companies that treated the reform as a simple connection to a platform often discovered their data problems at the first rejections. Those that used it to make their chain reliable gain lasting benefits: fewer disputes, faster collections, reliable billing data for finance. Our guide to billing automation details this approach.

Common mistakes

  • Reducing the reform to choosing a platform, when invoice quality depends on upstream data.
  • Neglecting customer master data: missing SIRENs, poorly identified entities, outdated addresses.
  • Forgetting to qualify the catalog: transaction category and VAT rules missing from product records.
  • Testing on simple cases instead of real ones: credit notes, usage invoices, group customers.
  • Ignoring returned statuses: a rejection not handled automatically becomes a payment delay.
  • Separating e-invoicing and e-reporting, when they must start from the same data.
  • Underestimating peaks at month end, when a small proportion of rejections represents a large volume.

Where Opencell fits

Opencell covers the offer and price catalog, orders, subscriptions, usage collection and rating, billing, payment collection and dunning. It integrates with CRM, ERP and e-invoicing platforms through more than 200 APIs and connectors. See the platform.

Frequently asked questions about e-invoicing in France

Since when must large companies issue e-invoices in France?

Since September 1, 2026, for their sales to other companies established in France. Since that date, they must also receive e-invoices and transmit e-reporting data for their other transactions.

Which e-invoice formats are accepted?

Three structured formats are accepted: Factur-X, which combines a PDF and structured data, and the CII and UBL data formats.

What are the mandatory e-invoice statuses?

Four statuses are mandatory: submitted, rejected, refused and collected. Other statuses exist and can be exchanged between platforms.

What is the difference between a rejected and a refused invoice?

A rejected invoice is blocked before reaching the customer, for a formal problem; it must be corrected and reissued. A refused invoice is disputed by the customer; it requires a credit note then a new invoice.

Does the certified platform check invoice content?

It checks the format and some data, transmits invoices and exchanges statuses. It does not check that the price, discount or usage billed is correct: that responsibility remains with the company and its billing system.

What is e-reporting?

It is the transmission to the tax authority of data on transactions that do not give rise to an e-invoice between French companies, such as sales to consumers or international sales, as well as some payment data.

The invoice only reflects the chain behind it

E-invoicing does not correct errors: it makes them visible, traceable and costly. For a large company billing high volumes of subscriptions and usage, compliance is built all along the chain, from quote to cash.

Key takeaways:

  • large and mid-sized companies have issued and received e-invoices since September 1, 2026,
  • invoices go through certified platforms, in Factur-X, CII or UBL format,
  • the new mentions come from customer master data, the catalog and contracts,
  • four mandatory statuses make every rejection and refusal visible,
  • high volumes turn every data defect into a cash problem,
  • the platform transmits, but invoice quality is decided upstream.

Choosing the platform takes a few weeks. Data quality is built across the whole chain.

Go further with Opencell

Opencell is an agile, open source monetization platform that automates quote-to-cash, from quote to cash collection, for subscription and usage-based services. It produces complete, accurate invoice data for certified platforms and integrates with them, with ERP and CRM through more than 200 APIs and connectors. Born in telecoms in 2007, it manages €14 billion in revenue for around fifty customers.

Billing high volumes in France and want e-invoices right first time?

Optimize your recurring revenues with Opencell

Get a demo