惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

MongoDB | Blog
MongoDB | Blog
B
Blog RSS Feed
MyScale Blog
MyScale Blog
M
MIT News - Artificial intelligence
H
Hackread – Cybersecurity News, Data Breaches, AI and More
J
Java Code Geeks
U
Unit 42
Blog — PlanetScale
Blog — PlanetScale
L
LangChain Blog
C
Check Point Blog
WordPress大学
WordPress大学
Last Week in AI
Last Week in AI
人人都是产品经理
人人都是产品经理
T
Tailwind CSS Blog
Vercel News
Vercel News
腾讯CDC
GbyAI
GbyAI
有赞技术团队
有赞技术团队
S
SegmentFault 最新的问题
H
Help Net Security
博客园 - 三生石上(FineUI控件)
D
DataBreaches.Net
Microsoft Security Blog
Microsoft Security Blog
小众软件
小众软件

Tradeshift

ZATCA E-Invoicing Data: Saudi Arabia's New Financing Edge AI & B2B Commerce in Saudi Arabia: Beyond ZATCA AP Auditor Agent: Tailored AI for Invoice Risk | Tradeshift Worldwide E-Invoicing Compliance in 2026: What Global Businesses Need to Know Worldwide E-Invoicing Compliance in 2026: What Global Businesses Need to Know DBNAlliance vs. Peppol: What America's E-Invoicing Network Means for Compliance DBNAlliance vs. Peppol: What America's E-Invoicing Network Means for Compliance From Touch-Free Processing to Actionable Intelligence | Tradeshift France's E-Invoicing Mandate: FNFE-MPE's Go-Live Check-Lists Explained | Tradeshift UK Late Payments Bill Meets the E-Invoicing Mandate: Why It's a Platform Decision UK Late Payments Bill Meets the E-Invoicing Mandate: Why It's a Platform Decision AI Coding Assistant Case Study: Tradeshift's Unblocked France's E-Invoicing Mandate: The Final Stretch Before September 2026 | Tradeshift France's E-Invoicing Mandate: The Final Stretch Before September 2026 | Tradeshift Ada 2.0: Tradeshift's AI Invoice Coding Engine, Upgraded UAE E-Invoicing Mandate 2026: Voluntary Phase Live, What's Changed | Tradeshift UAE E-Invoicing Mandate 2026: Voluntary Phase Live, What's Changed | Tradeshift Tradeshift Named Strong Performer in Forrester Wave™: APIA, Q2 2026 Tradeshift Named Strong Performer in Forrester Wave™: APIA, Q2 2026 Tradeshift Named a Strong Performer in The Forrester Wave™: APIA Software, Q2 2026 Tradeshift Named a Strong Performer in The Forrester Wave™: APIA Software, Q2 2026 Spain's B2B E-Invoicing Mandate in 2027: Updated Timelines and How to Prepare | Tradeshift Spain's B2B E-Invoicing Mandate in 2027: Updated Timelines and How to Prepare | Tradeshift AI Document Intelligence: Smarter Invoice Extraction for AP Teams | Tradeshift More Analytics for Sellers: New Reports & Dashboards Now Available on Tradeshift Catching What Others Miss: Anomaly Detection in AP Analytics UK e-invoicing in 2026: from mandate to blueprint UK E-Invoicing Mandate: What Has Changed in 2026? Germany’s 2027 E-Invoicing Deadline Is Closer Than You Think: What It Means for Every Side of the Transaction Germany 2027 E-Invoicing Mandate: Buyer & Seller Guide
France's E-Invoicing Mandate: FNFE-MPE's Go-Live Check-Li...
nohasharmy · 2026-08-03 · via Tradeshift

What the three new check-lists mean for buyers, suppliers, and Plateformes Agréées weeks before September 1, 2026, plus how one Tradeshift customer got there in 24 days.

With roughly four weeks left before France’s e-invoicing reform takes effect on September 1, 2026, the FNFE-MPE (Forum National de la Facture Électronique et des Marchés Publics Électroniques) has published a three-part Check-List Démarrage designed to be the last practical pre-flight check before go-live. It arrives as a direct companion to the DGFiP’s own Guide pratique de démarrage, published July 10, 2026, and it is deliberately narrow: not a re-explanation of the mandate, but a short list of the operational details most likely to break in the first weeks of production.

Coming so soon after our last update on the pilot phase and technical specifications, this check-list is a useful marker of where the ecosystem’s attention has shifted: from “are the standards finished?” to “will reception, routing, and status handling actually work on day one?”

Why a check-list, and why now

The DGFiP’s guide, released July 10, rests on three principles that FNFE-MPE’s check-lists inherit directly: the legal calendar is not moving, business continuity is preserved (a PDF, email, or paper invoice tied to a real transaction stays valid, payable, and VAT-deductible), and the resulting tolerance at start-up is not a disguised exemption. Genuine compliance efforts won’t be penalized, but inertia or durable avoidance will be treated differently.

FNFE-MPE built its three-part check-list on top of that foundation, aimed at three audiences that all need to read each other’s obligations: 

  • Taxable persons (Volet A)
  • Plateformes Agréées, or PAs (Volet B)
  • Large companies and ETIs handling issuance and e-reporting (Volet C)

The logic is simple: a buyer should know what to expect from its supplier’s PA, and a supplier should know what its buyer needs to have in place to receive.

A quick reminder of the model underneath all three volets: France did not build a single central clearance platform. It chose a decentralized “Y-model”: every business selects its own PA, PAs interconnect through a central directory (the Annuaire) managed by the PPF (Portail Public de Facturation), and the tax authority receives normalized transaction data without ever touching invoice content directly. The PPF stopped transmitting invoices for private companies back in October 2024; today its job is to be the directory and fiscal concentrator that makes the Annuaire the single source of truth for who is a taxable person and which PA manages which reception address.

Volet A: for every VAT-registered business (reception)

This volet applies to all entities listed in the PPF directory, regardless of size, and it concentrates on four points that FNFE-MPE flags as the most common sources of go-live friction (full Volet A checklist here):

  • Rational choice of reception addresses. Favor a single address per SIREN rather than multiplying reception addresses without a genuine business reason. Address proliferation is explicitly called out as bad practice.
  • Connection to a PA. Be under contract with, and technically connected to, an Accredited Platform, and be correctly registered in the Annuaire.
  • Duplicate management. Anticipate and handle duplicate invoices, flagged as a primary operational risk at launch.
  • Lifecycle statuses. Use invoice lifecycle statuses correctly, with strict, disciplined use of the “Rejected” (Refusée) status rather than applying it loosely.

Volet B: for Plateformes Agréées

Volet B sets the bar every PA is expected to clear, and it doubles as a reference for buyers and suppliers who want to sanity-check their own platform’s readiness (full Volet B checklist here):

  • Contracting and identity checks. At onboarding, the PA must verify the identity of the signatory and their authority to bind the taxable person, a step that can be delegated to a distributor or a mandated trusted third party, such as an accountant subscribing on a client’s behalf.
  • Reception contracting and directory accuracy. For reception, the PA needs a formal signed agreement and must keep the Annuaire updated with the reception addresses it manages, following good addressing practice rather than defaulting to unnecessary catch-all addresses.
  • Portability without interruption. When a business changes PA, outgoing and incoming platforms must coordinate the switch without any service break, per the Service d’Immatriculation (SIM) rules.
  • Directory as source of truth, synced daily with Peppol. PAs must treat the Annuaire as authoritative and guarantee daily synchronization with the Peppol directories for any addresses they manage on the Peppol network.
  • Formats and status messages. Full support for the socle formats and the AFNOR XP Z12-012 standard, plus correct handling of status messages (CDAR): reception and emission addresses, transmission and processing statuses, human-readable presentation, and lifecycle-status management.

Volet C: for issuance and e-reporting (large companies and ETIs)

Volet C targets the companies with an immediate issuance obligation on September 1: large enterprises and ETIs, though FNFE-MPE notes any SME or micro-business anticipating its 2027 deadline can use it too (full Volet C checklist here):

  • Compliant outbound flows in the socle formats: Factur-X, UBL, and CII.
  • Status returns, notably correct handling of the BT-34 electronic address field.
  • Preparation for rejections and disputes in the invoice lifecycle.
  • The e-reporting streams, covering transaction and payment data for flows outside domestic B2B, such as B2C and cross-border.

What this means for compliance owners right now

With about four weeks to go, the most useful way to use FNFE-MPE’s check-lists is as a cross-check across counterparties rather than a solo exercise. A buyer should confirm its own Volet A reception readiness and use Volet B to verify that its suppliers’ PAs are actually meeting their directory-sync and status-message obligations. An issuer should validate Volet C format and e-reporting readiness while confirming, on the other side, that its customers can genuinely receive. 

Combined with the DGFiP’s start-up tolerance, the message from both the tax authority and the ecosystem’s own standards body is consistent: document a serious compliance trajectory, secure conformance testing before production, and treat duplicate handling and lifecycle statuses as the first two things to get right.

A go-live measured in days, not months

Checklists like these matter because go-lives are where mandates actually succeed or stall. So it’s worth pairing this update with a real example.

A global toy and games manufacturer, a UK-headquartered group selling across multiple well-known children’s brands in Europe and beyond, came to Tradeshift needing straightforward compliance coverage for the French mandate: correctly receiving e-invoices, connected to a registered PA, with the Annuaire, duplicate handling, and lifecycle statuses all in place. That’s exactly what Volet A and Volet B are designed to cover.

They were live in 24 days.

That speed came from three things working together: a proven PA, a team that has done this many times before, and a customer with a clear, well-scoped requirement. When the goal is compliance, full stop (receive correctly, connect to the right PA, get the statuses right), that combination is what makes a fast go-live possible, without cutting corners on the parts FNFE-MPE’s check-lists are warning everyone about.

It’s also a useful reminder: getting to “compliant” fast doesn’t mean settling for a narrow tool. Tradeshift’s platform covers that first, urgent need (reception, PA connectivity, e-reporting) as a fast, self-contained project. But the same platform also extends well beyond compliance into AI-powered AP automation: invoice coding, matching, exception handling, and analytics for businesses whose accounts payable operations are more complex than a single mandate. Customers can start with compliance and grow into automation on the same platform, at their own pace, without a re-platforming project down the line.

How Tradeshift Supports Compliance in France

Tradeshift is a registered Plateforme Agréée in France, aligned with the September 2026 mandate and the latest AFNOR and AIFE specifications. Because the same globally compliant e-invoicing platform also covers mandates in Germany, Belgium, Poland, Spain, Romania, and beyond, French compliance is one configuration on an existing platform rather than a standalone project, and, as the go-live above shows, it can move as fast as the business needs it to.

If you are already a Tradeshift customer

Your Customer Success Manager can walk you through what these check-lists mean for your specific setup and confirm there’s nothing outstanding ahead of September 1.

If you are not yet a Tradeshift customer

Get in touch with the Tradeshift team to talk through your French compliance timeline, including how fast a go-live focused purely on compliance can realistically be.