Decree No. 2026-677 Locks France’s E-Invoicing Framework: What FBA Sellers Using French FCs Actually Need to Check Before the September Mandate Window
Decree No. 2026-677 Locks France’s E-Invoicing Framework: What FBA Sellers Using French FCs Actually Need to Check Before the September Mandate Window
FBA Prep France
We streamline your French Amazon operations by handling FBA prep, managing removal orders, and forwarding shipments to any French Fulfillment Center for FBA and Vendor accounts.
If your business is VAT-registered or established in France, a new decree just tightened the rules around how you send and receive invoices — and it has nothing to do with which Amazon FC your inventory sits in. Decree No. 2026-677 and the accompanying Order of 27 July 2026 were published July 28 and took effect July 29, 2026, completing a piece of France’s e-invoicing framework: how businesses switch between accredited invoicing platforms (PA) without losing invoice history, and which AFNOR-anchored formats now count as compliant. This is not a warehouse or FC issue. It is a finance and systems issue that sits alongside your logistics setup. The practical question for any FBA seller with a French VAT registration is simple: which platform do you or your accountant use, does it meet the new format standard, and is your data portable if you switch providers before the September 1, 2026 receiving-obligation deadline.
What Decree No. 2026-677 Actually Regulates
The decree does not introduce new invoice-data fields or change VAT rate logic. Its core subject is platform (PA) portability — the mechanics of moving your invoicing history when you change from one accredited platform to another — plus data continuity guarantees so a switch does not create a gap in your invoice trail. Alongside this, the Order of 27 July 2026 anchors the technical format requirements to AFNOR standards, specifically the XP Z12-012, XP Z12-013, and XP Z12-014 specifications.
For a seller running e-invoicing EU compliance across multiple markets, the practical takeaway is narrower than it sounds: confirm your platform is accredited, confirm it supports the AFNOR format family, and confirm that switching platforms later would not strand your historical invoices in a format your new provider cannot read. This matters most if you are consolidating accounting systems ahead of the September deadline, since a rushed platform migration is exactly the scenario this decree is meant to de-risk.
Who the Obligation Actually Attaches To
The receiving obligation that starts September 1, 2026 applies to businesses that are VAT-registered or established in France — not to sellers who simply route inventory through a French fulfillment center. Using Amazon FC forwarding in France or storing stock at a prep site near Cergy or Brétigny does not, on its own, create an e-invoicing obligation under this framework. The trigger is your tax registration status, not your warehouse address.
This distinction matters because sellers sometimes assume that FC location determines compliance scope. It does not. If your business has no French VAT registration and no French establishment, this decree’s receiving obligation is not the thing to check first — your VAT registration status across markets is.
What Happens If You Confuse the Two
Treating FC usage as the compliance trigger creates two failure directions. First, a seller who is VAT-registered in France but assumes the FC-location logic applies elsewhere may skip checking their actual obligation, arriving at September 1 with no accredited platform confirmed. Second, a seller with no French VAT registration may spend time and budget preparing for an obligation that does not apply to them yet, while missing other markets where it does.
Either mistake burns time an accounting team does not have this close to a hard receiving-obligation date. The fix is procedural: pull your current VAT registration list per country, cross-check it against this decree’s scope, and treat FC usage as a separate, unrelated logistics decision.
One practical checkpoint sits ahead of everything else: ask your accountant or finance lead which accredited platform (PA) currently issues and receives your invoices, and whether that platform has confirmed AFNOR-anchored format support for XP Z12-012/013/014. If they cannot answer this in one conversation, that is the gap to close first — not a warehouse or FBA prep services question, but a systems-and-provider question that sits upstream of any fulfillment decision.
The Separate 10-Year Retention Extension
A related but distinct change is worth tracking alongside the decree: Law No. 2026-534 extends the document retention window for certain business records to 10 years, up from the 6-year assumption many finance teams have operated under. This is a different legal instrument from Decree No. 2026-677 — it does not govern platform switching or invoice formats, it governs how long you keep the documents once issued or received.
The two changes are easy to conflate because they land in the same compliance conversation and around the same timeframe. But an operator checking platform accreditation under the decree should not assume that also resolves retention policy. These are two separate line items on a readiness checklist, each needing its own owner and its own confirmation step before September.
What to Confirm on Platform Readiness
Start with your current PA relationship. Confirm accreditation status, confirm AFNOR format support, and ask specifically what happens to historical invoice data if you were to switch providers later in the year. Portability was the point of this decree — a platform that cannot demonstrate a clean export path for your invoice history is a weak link regardless of its other features.
What to Confirm on Retention Policy
Separately, check your internal document retention policy against the new 10-year window under Law No. 2026-534. If your finance team or archive system was built around a 6-year assumption, that policy — and possibly your archive storage contract — needs updating. This is not a platform question; it is a records-management question that sits with whoever owns your document archive.
Owner Map: Who Confirms What Before September
In practice, three roles need to sign off separately. Your accountant or finance controller confirms VAT registration status and whether the receiving obligation applies at all. Your invoicing platform provider confirms AFNOR-anchored format compliance and portability terms in writing. Your records or archive owner confirms retention policy matches the 10-year window rather than the older 6-year default.
None of these three checks depends on where your inventory physically sits, whether that is pre-Amazon storage in France or a multi-country FC spread. Keeping the owner map separate from your logistics setup prevents the common error of routing a finance compliance question to a warehouse operations contact who has no visibility into invoicing platforms.
Where Readiness Efforts Tend to Go Wrong
The most common mistake is treating this as a single compliance project when it is actually two, running on different clocks with different owners. A seller might confirm platform accreditation, feel confident, and never touch the retention policy — or update retention documentation while leaving an unaccredited or format-mismatched platform in place. Both leave a gap.
A second, quieter mistake is assuming that because a business uses French FCs for fulfillment, it must have a French e-invoicing obligation. As covered above, that is not the applicability test. Some multi-market FBA sellers spend review time on the wrong trigger condition and miss checking their actual VAT registration footprint across the markets where they do have obligations. Given that consolidated CGI article text and updated AIFE/DGFiP technical specifications are still pending publication, treating this as a fixed, closed checklist rather than a live one is itself a risk — plan for a short recheck once those references are finalized.
Confirm With Your Platform Provider
- Current PA accreditation status and renewal date
- Confirmed support for XP Z12-012/013/014 formats
- Written export/portability process for invoice history
- Timeline for any pending format updates before September 1
Confirm With Your Finance and Records Owner
- Which entities are VAT-registered or established in France
- Whether the September 1 receiving obligation applies to each entity
- Retention policy updated to the 10-year window under Law No. 2026-534
- Archive storage contract terms matching the new retention period
Sequencing the Readiness Work Before September 1
Start with applicability, not platform features. Pull your VAT registration list across every market where you sell, and mark which entities are established or VAT-registered in France specifically. Only for those entities does the September 1 receiving obligation apply under this decree.
Next, contact your invoicing platform provider directly and ask for written confirmation of AFNOR-anchored format support and portability terms — do not assume an existing relationship already covers this, since the format standards were only finalized with the July 2026 order. Then hand the retention question to whoever owns your document archive, separately, with the explicit instruction to check against the 10-year window rather than the older assumption. Sequence matters here: applicability first, platform second, retention third, because each depends on knowing the previous answer before it can be resolved cleanly.
None of this readiness work touches your Amazon FC forwarding setup directly, but it runs in parallel with it. A seller finalizing inbound plans for French Amazon FCs this quarter can treat the e-invoicing check as a separate finance-track item running on its own timeline, owned by finance rather than operations, so neither workstream blocks the other.
Check One
Confirm VAT registration or establishment status in France before assuming this decree applies to your business.
Check Two
Confirm your PA supports AFNOR-anchored formats and can export invoice history cleanly if you switch providers.
Check Three
Confirm retention policy reflects the 10-year window under Law No. 2026-534, not the older 6-year assumption.
What to Lock In Before the September Window
Decree No. 2026-677 is narrower than it first sounds — it governs platform portability and AFNOR-anchored formats, not invoice-data fields or FC-based triggers. The applicability test is VAT registration or establishment in France, and the retention extension under Law No. 2026-534 is a separate instrument that needs its own owner and its own check. Given that consolidated CGI text and updated AIFE/DGFiP technical specifications are still pending, treat this readiness list as current but not final, and plan a short recheck once those references land.
For the logistics side of your operation — forwarding to Amazon France, storage, and prep — that workflow runs independently of this compliance track, and coordinating both without letting one block the other is the practical goal here.
This article covers the operational and readiness angle only — confirm your specific legal and tax obligations with your accountant or a qualified advisor familiar with French e-invoicing rules, since applicability depends on your exact VAT registration and entity structure. If your FBA operation also needs a review of French FC forwarding, storage, or prep workflows running alongside this compliance track, FLEX. can walk through the logistics side so your inbound planning and your finance readiness do not collide against the same September deadline.
Contact FBA France team to review your French FC forwarding and prep workflows ahead of the September deadline.
