France’s next tax reform is being discussed as an invoicing project. That is too narrow. What France is really doing is redesigning how transaction data moves through the economy, who creates it, who validates it, who transmits it, and when the tax authority sees it. For retailers and the companies that supply them with POS, ERP, billing and accounting systems, this is not a back-office adjustment. It is a product and architecture issue.
The timeline is now concrete. From 1 September 2026, all companies must be able to receive electronic invoices. On the same date, large companies and mid-sized companies must also issue them. SMEs and micro-enterprises follow for issuance on 1 September 2027. The reform applies to domestic B2B transactions between taxable persons established in France. Transactions outside that scope do not disappear; they move into the companion regime of e-reporting.
That distinction matters. In France, domestic B2B becomes mandatory e-invoicing. B2C and cross-border B2B generally fall into e-reporting, meaning relevant transaction data must still be transmitted electronically to the administration even when an e-invoice is not required. This is why many companies that assume the reform is “just for invoicing” are underestimating the operational impact. A retailer can have limited domestic B2B exposure and still face substantial reporting obligations because so much of retail is B2C.
The second big change is the operating model. France is requiring businesses to work through state-registered approved platforms. Those platforms must be able to issue, transmit and receive e-invoices, extract the required invoice data for the tax administration, and also receive and transmit transaction data. In practical terms, that means companies will not solve this reform by tweaking a PDF template or adding one export file. They will need a platform strategy. Their current software vendors will need one too.
France is also being specific about formats. The accepted core invoice formats are CII, UBL, and Factur-X, aligned with the European EN 16931 standard. A scanned invoice or a simple PDF emailed to a customer may still be readable to a human, but it does not satisfy the logic of the reform. France wants structured invoice data that can be routed, validated, and reused. That means ERP and billing providers need to think less about document presentation and more about structured-data generation, lifecycle statuses, interoperability and exception handling.
For retailers, the sharper disruption may come from e-reporting, not e-invoicing. The official material is explicit: for many B2C transactions, the data is reported in aggregated daily form, not line by line, and without personal data. The required elements include the seller’s VAT identification, the taxable amount and VAT amount by rate, the transaction type, the number of daily transactions, and the transaction date. The frequency depends on the VAT regime: three times a month for monthly VAT filers, once a month for quarterly filers, and every two months for annual or no-return cases.
That sounds technical, but it has a very practical consequence: the POS is no longer just a record-keeper. It becomes a data-preparation and compliance engine. To work properly in France’s new regime, retail systems will need clean VAT mapping, daily aggregation logic, controls around corrections and cancellations, and a reliable connection to an approved platform that can forward the required information to the administration. Any weakness in the upstream transaction model, bad VAT assignment, inconsistent tender handling, poor treatment of returns, incomplete status management—will eventually show up downstream in reporting.
At the same time, France is not abandoning its older anti-fraud logic around cash systems. Businesses that record payments from private customers through a cash register system remain subject to the long-standing requirements of inalterability, security, retention and archiving. In February 2026, the French government reversed a planned move that would have eliminated self-certification for cash-register software from September 2026. Self-certification remains possible. But that should not be mistaken for deregulation. The sanction for not being able to justify compliance remains €7,500 per software or system, and the taxpayer has 60 days to come into compliance before the exposure can arise again.
That combination is what makes France strategically important. On one side, the country is building a modern e-invoicing and e-reporting framework based on approved platforms and structured data flows. On the other, it is still insisting that cash systems preserve data integrity in a way that supports tax audit. Put differently, France is not choosing between “old fiscalization” and “new digital reporting.” It is layering the two. And that raises the bar for software providers. A compliant French solution now has to think about transaction integrity, invoice structure, reporting logic and platform connectivity as one connected design problem.
The business conclusion is straightforward. Retailers should stop asking whether France is “just an invoicing project” and start asking whether their technology stack can produce structured invoice data, aggregated VAT reporting, sales-event visibility, and audit-proof transaction records without manual repair work. Software vendors should ask a harder question still: whether their products were built for a world in which compliance is periodic, connected and machine-readable or for a world that no longer exists.
France is not merely digitizing tax paperwork. It is redefining what retail software must be able to do. And companies that treat this as a legal deadline instead of a product deadline are likely to discover the difference too late.