Who this is for: CFOs and controllers at US companies with a French subsidiary, especially those running NetSuite, who need to know what the 1 September 2026 e-invoicing mandate actually requires and how to be compliant without rebuilding their ERP.
France is switching all domestic B2B invoicing to a state-supervised electronic system, and the first deadline applies to every VAT-registered French entity at once. If your subsidiary issues or receives a single French B2B invoice, this reform reaches you. The uncomfortable part for NetSuite shops: compliance is not a setting you switch on.
Table of Contents
What the mandate requires, and when
The reform has two halves. E-invoicing covers domestic French B2B invoices, which must flow through certified platforms in structured formats. E-reporting covers everything else, international B2B and B2C transaction data transmitted to the administration on a schedule. The official framework is on the impots.gouv.fr e-invoicing pages.
Date | Who | Obligation |
1 September 2026 | Every VAT-registered French entity, all sizes | Must be able to RECEIVE electronic invoices via a certified platform |
1 September 2026 | Large companies and mid-size (ETI) | Must also ISSUE e-invoices and transmit e-reporting data |
1 September 2027 | Small, micro and auto-entrepreneurs | Issuing and e-reporting obligations extend to everyone else |
Note what the first row means: even if your French subsidiary is small, from 1 September 2026 its suppliers may send invoices only through the system, so it must be connected to receive them. Waiting for the 2027 line is not an option for reception.
The plumbing: platforms, formats, statuses
- Invoices route through a Plateforme Agréée (PA), a government-certified private platform, connected to the public directory. Each entity registers with a chosen PA.
- Accepted formats are Factur-X (hybrid PDF with embedded XML), UBL 2.1 and CII, all conforming to the European semantic standard EN 16931. A PDF attached to an email stops counting as an invoice.
- The system tracks lifecycle statuses (deposited, rejected, refused, payment received). Your process must handle statuses coming back, not just documents going out.
Why standard NetSuite is not compliant
NetSuite generates invoices, PDFs them and emails them. That entire flow becomes non-conforming for domestic French B2B. Specifically:
- No native PA connection. NetSuite does not ship connected to any French certified platform. Connectivity comes from a localization SuiteApp, a middleware integration, or a partner platform, each of which must be selected, contracted and configured.
- No native Factur-X output. The structured XML with EN 16931 semantics, French VAT categories, SIREN identifiers and payment terms has to be produced correctly, field by field.
- Status handling does not exist in the defau< AR/AP flow. Rejected and refused statuses must land somewhere your team actually works.
- E-reporting is a separate feed with its own calendar, covering the international transactions a US-owned subsidiary has plenty of, intercompany charges included.
Your realistic options, compared
Route | What it involves | Fits |
PA with a NetSuite connector | Contract a certified platform that publishes a NetSuite integration; map fields; test statuses | Mid-size subs with IT capacity and clean master data |
Localization layer in NetSuite | Deploy the France localization SuiteApp plus a PA link; heavier configuration, tighter ERP fit | Groups standardizing on NetSuite long term |
Outsource the invoice flow | Your accounting firm operates the PA connection and statutory layer around your ERP exports | Lean finance teams that want the deadline handled without a project |
A 30-minute readiness check
Question | Why it matters |
Is the French entity large/ETI, or small? | Decides whether you must ISSUE from September 2026 or only receive |
Which PA will you register with? | Skipping it invites a formal notice, then a €500 fine after three months to comply and €1,000 per further quarter |
Can your invoice data populate EN 16931? | Missing SIREN, VAT rates or payment terms in NetSuite master data is the usual blocker |
Who processes rejected statuses? | A refused invoice nobody sees becomes unpaid revenue |
Is e-reporting scoped? | Cross-border and intercompany flows still must be reported even though they are not e-invoiced |
The pena<ies, and the pragmatic path if you are behind
Individually the fines look modest, and the 2026 finance law just raised them: €50 per non-compliant invoice and €500 per missed e-reporting transmission, each capped at €15,000 per year, plus €500 for remaining without a certified platform after a formal notice and three months to comply, then €1,000 per further quarter, doubled on repeat offence. The real risk is operational, suppliers whose invoices you cannot receive and customers whose platforms refuse yours.
If September is close and nothing is in place, sequence it: register the entity with a PA (reception compliance first, it is the universal 2026 duty), then solve issuing for large/ETI entities, then wire e-reporting. Reception alone can be live in weeks; a full issuing integration is a quarter-long project.
How the public directory routes your invoices
Underneath the platforms sits a public directory (annuaire) keyed on French company identifiers. When a supplier issues an invoice to your subsidiary, their platform looks your entity up in the directory to learn which PA delivers your mail. Registration is what makes you reachable.
- Registration is per legal entity, tied to SIREN and, where routing requires it, SIRET or finer addressing points. A group with three French entities makes three registrations, and each can use a different PA.
- Your customers do the same lookup in reverse. Once your issuing obligation starts, invoices reach customers through their declared platform, whether or not their AP inbox is watched. Chasing payment starts with confirming the invoice reached a platform someone reads.
- Changing PA later is possible, the directory updates, but mid-year switches mean re-testing every integration. Choosing carefully once beats migrating twice.
E-reporting: the half that US groups forget
E-invoicing gets the headlines because it changes the document itself. E-reporting is quieter and touches a US-owned subsidiary more often, because it covers exactly the flows such a group lives on:
- Cross-border B2B, both directions. The management fee from Delaware, the license roya<y to the parent, the recharge to the German affiliate: none travels as a French e-invoice, all must be reported as transaction data.
- B2C sales into France, including SaaS subscriptions sold to French consumers.
- Payment data on services, since French VAT on services is generally due on collection, the administration wants to know when you were paid, not only when you billed.
Transmission frequency follows your VAT filing regime. The practical consequence: someone, in-house or outsourced, owns a recurring extraction from NetSuite that has nothing to do with the invoice PDF flow you run today.
Choosing a PA: five questions before signing
The official government comparator already lists well over a hundred certified platforms, which is exactly why a shortlist discipline matters:
Question | What a good answer looks like |
Does it publish a maintained NetSuite integration? | A named connector with references, not a promise that the API is open |
Does it handle both directions plus e-reporting? | One contract covering issue, receive and report beats stitching three vendors |
How are lifecycle statuses surfaced? | Webhooks or exports your AR team can work from, not a portal nobody opens |
What happens at volume? | Pricing per invoice at your real AR/AP volumes, tested, not estimated |
Who supports you in English? | A US controller will end up on these calls; anglophone support is not a luxury |
A realistic countdown to 1 September
When | What must be done |
Now | Confirm entity size category; shortlist PAs; audit NetSuite master data (SIREN, VAT numbers, rates, payment terms) |
8 to 6 weeks out | Sign the PA; register in the directory; reception flow live and tested with two pilot suppliers |
6 to 3 weeks out | Issuing flow mapped to Factur-X for large/ETI entities; status handling wired into AR routines |
Final weeks | E-reporting extraction scheduled; finance team trained on rejected/refused statuses; fallback contact at the PA identified |
Special cases US groups actually hit
- A US entity registered for French VAT without a French establishment sits outside the domestic e-invoicing channel but squarely inside e-reporting. Registration alone does not put you on the invoice rails; it does put you on the data rails.
- Invoices in dollars are still allowed. Currency is a field, not a problem, but the VAT amount converts to €s and the structured file must carry it correctly. This is a mapping detail that surfaces late in testing.
- Self-billing (autofacturation), common in intercompany setups, survives the reform, but the self-billed invoice follows the same platform and format rules as any other. If the parent self-bills for the subsidiary, that flow needs wiring too.
- Credit notes and corrections travel the same channel with their own document codes. A process that fixes billing errors by emailing revised PDFs stops working the same day the original PDFs do.
What changes at month-end close
The reform quietly rewires the close. Revenue cut-off gains a new input, because an invoice refused on the platform is not just a collections problem but a question mark over the receivable. AP accrues from what arrived on the platform, not what someone forwarded from an inbox. And every document that transits the system feeds the same trail a French tax audit walks: the platform archive on one side and, on the other, the accounting entries your ERP must be able to hand over in the statutory FEC file. Companies that treat September as a formatting exercise discover in December that their close calendar assumed information flows that no longer exist.
Getting compliant without derailing your roadmap
Expand CPA is a Franco-American accounting firm with offices in Paris, New York and Tel Aviv. We act as the French statutory layer around US ERPs: choosing and contracting the PA, mapping NetSuite output to Factur-X, running reception and statuses, and handling the e-reporting calendar, so the mandate is met without pausing your product roadmap. We already handle the adjacent plumbing, from French VAT registration to intra-community numbers. If your subsidiary is not connected yet, talk to us this month, not in August.
Frequently Asked Questions
Does the mandate apply to invoices from our US parent to the French subsidiary?
Cross-border invoices are not in the e-invoicing channel, but they fall under e-reporting, so the French entity must still transmit the transaction data on schedule.
Our subsidiary is tiny. Are we exempt until 2027?
Only for issuing. Reception via a certified platform is mandatory for every VAT-registered entity from 1 September 2026.
Can we keep sending PDFs by email in the meantime?
To French B2B customers, no, once your issuing obligation starts. A plain PDF no longer counts as a valid invoice in the domestic B2B flow.
Related Expand CPA guides
- French VAT registration for foreign companies
- The French intra-community VAT number
- Creating a subsidiary in France
Disclaimer: Deadlines, platform requirements and pena<y amounts are set by regulation and have moved before. Figures verified August 2026 against impots.gouv.fr and economie.gouv.fr. General information, not tax advice.
