France E-Invoicing & E-Reporting (2026–2027): What’s Changing and How to Comply in NetSuite
France is making structured electronic invoicing and electronic reporting mandatory for business transactions over 2026 and 2027. If your company trades in France, or operates a French subsidiary, this will change how you issue, receive and report invoices — and a plain PDF sent by email will no longer count as a valid invoice. This article summarises what’s coming, who it applies to, and how to become compliant in NetSuite.
Two obligations, often confused
The reform actually has two distinct parts. The first is e-invoicing: the issuing and receiving of domestic business-to-business (B2B) invoices in a structured electronic format, exchanged through approved platforms rather than emailed directly. The second is e-reporting: the transmission of transaction data to the French tax authority (DGFiP) for flows that fall outside domestic B2B invoicing — namely business-to-consumer (B2C) sales, international and cross-border B2B transactions (both sales and purchases), and, for services, payment data. A simple way to remember it: if you sell to a French business it is e-invoicing, and if you sell to consumers or to businesses abroad it is e-reporting.
Who is affected, and when
The obligations phase in according to company size, but one milestone applies to everyone. From 1 September 2026, every company established in France must be able to receive structured e-invoices — even a small business whose own issuing obligation only begins in 2027. Because a supplier can legally send an e-invoice from that date, being able to receive is the immediate priority for all.
The issuing and e-reporting obligations then roll out in two waves:
- 1 September 2026 — large enterprises and mid-size companies (ETI) must issue e-invoices and e-report.
- 1 September 2027 — small and medium-size enterprises (PME) and micro-enterprises (TPE) must issue e-invoices and e-report.
How the French model works
France has adopted a decentralised “Y” model built around approved platforms (Plateformes de Dématérialisation Partenaires, or PDPs — increasingly referred to simply as “approved platforms”). When you issue an invoice, it goes first to your approved platform, which validates and formats it, then routes it to your customer’s platform while also notifying the public portal (PPF) and the tax authority. Accepted structured formats are UBL, CII and Factur-X (a hybrid that embeds structured XML inside a human-readable PDF), all aligned to the European EN 16931 standard. Importantly, your ERP is not itself an approved platform — you must connect to one.
How to get compliant in NetSuite
NetSuite meets the mandate through Avalara acting as the accredited approved platform (PDP), reached from NetSuite via the NetSuite Electronic Business (NSEB) SuiteApp and Oracle Business Network (OBN). Avalara's solution covers both pillars of the reform — e-invoicing and e-reporting (marketed as "E-Invoicing and Live Reporting"). The implementation is a configuration exercise rather than heavy development, and it works on both legacy-tax and SuiteTax accounts. In practice, the setup breaks down as follows:
- Enable the account features: Custom Records, Custom Transactions, Advanced PDF/HTML Templates, Client SuiteScript, Server SuiteScript and Web Services. (SuiteTax not mandatory)
- Install the SuiteApps: the SuiteApps License Client (Bundle 116144, installed first), Electronic Invoicing (Bundle 436209), NetSuite Electronic Business (NSEB), EU Electronic Invoicing, Advanced Localized Features, Localization Assistant, and France Localization.
- Sort out licensing: the two commercial items are the NetSuite Electronic Business Extension and the Electronic Document Processing Cloud Service (usage-based). E-invoicing is free for a single country; an additional country is a paid add-on.
- Provision Avalara and the mandate: register the parent and subsidiaries in Oracle Business Network, complete Avalara provisioning, then create and activate the France mandate.
- Configure documents and master data: set up the France E-Document package, templates and the Avalara certification sending method, and populate the mandatory identifiers — SIREN, SIRET, VAT numbers and the electronic (PEPPOL) address — on subsidiaries, customers and vendors.
- Run the flows: outbound documents are generated, certified via Avalara and sent, with NetSuite tracking each status; inbound documents are polled in from Avalara and reviewed as a draft before becoming a vendor bill; and e-reporting is delivered through Avalara's live-reporting capability.
Getting started
Begin by confirming your company size, which fixes your issuing and e-reporting date, and remember that the receiving obligation applies to everyone from September 2026. Onboard an approved platform early, install the SuiteApps and enable the features, and provision Avalara through OBN. Above all, audit and clean your master data — missing or incorrect identifiers such as SIREN or electronic addresses are the single most common cause of rejected invoices. Test end-to-end before go-live (a sandbox is recommended, though optional — you can also test in production using zero-value or one-cent invoices), and treat the change as a business-process shift that involves finance, tax and IT, not just a software update.
Bottom line
The French e-invoicing and e-reporting mandate is confirmed and phased across 2026–2027: e-invoicing for domestic B2B, and e-reporting for B2C, cross-border and payment data. NetSuite customers can comply through the built-in Avalara integration, but success depends as much on clean master data and early planning as on the technology. Start with the September 2026 receiving obligation, and don't leave it to the last minute.
