3 May 2026

France e-Invoicing in Dynamics 365 Finance

Author: Roman Abilkhatov, D365 Finance Solution Architect

What Microsoft's 10.0.48 Preview Delivers (and Two Gotchas Worth Understanding Before You Plan Around It) 

Short answer up front. Microsoft has just released the French e-invoicing and e-reporting feature for Dynamics 365 Finance in preview build 10.0.48. General availability is planned for August 2026. The French mandate enforces from 1 September 2026. So the timing finally works. Barely. Two things should be on the CFO's desk before anyone signs off on the standard build. First, the Microsoft implementation only integrates with one Plateforme Agréée out of the 120 currently registered with the DGFiP. Second, the underlying Electronic Invoicing add-on adds a usage-based meter on top of your existing D365 Finance subscription that scales linearly with invoice volume. 

If you run D365 F&O in France, this is the one to read before you accept the standard configuration as your e-invoicing strategy. 

What France actually requires (and why it's not the same as Italy or Germany) 

The French e-invoicing reform is real and the dates have stopped moving. The French National Assembly rejected another postponement in April 2025. The current timeline is: 

• 1 September 2026. All French B2B taxpayers must be able to receive e-invoices. Large and intermediate enterprises must also issue them and submit e-reporting to the DGFiP. 

• 1 September 2027. Issuance and e-reporting obligations extend to SMEs and micro-enterprises. 

The architecture is what makes France hard. It's not Italy's centralised clearance, where every invoice goes through one government platform (SdI) in one government format (FatturaPA). It's not Germany's "receive only for now" approach with EN 16931-compliant formats like XRechnung and ZUGFeRD. It's a five-corner model: sender → sender's PA → buyer's PA → buyer, with the PAs also pushing extracted tax data to the DGFiP for e-reporting. 

Three formats are accepted under the reform, all aligned to EN 16931: UBL, CII, and Factur-X (the hybrid PDF/A with embedded XML). On top of that, French invoices carry mandatory lifecycle statuses (Deposited 200, Refused 210, Payment Received 212, Rejected 213) which both PAs must round-trip back to the issuer. 

The original "Y-scheme" envisaged a free public portal (the PPF, or Portail Public de Facturation) sitting alongside the private PAs as a default option. The DGFiP has since scaled the PPF back. The PA-only model is now the operational reality. Companies have to pick a Plateforme Agréée, sign a contract, and integrate. Note the terminology: the French government renamed PDP (Plateforme de Dématérialisation Partenaire) to PA (Plateforme Agréée) in the 2025 spec revisions. Microsoft's own release plan still slips and calls them "Plateformes Accréditées". They're not. They're agréées. 

This is the most complex domestic e-invoicing implementation in Europe today. Sales, vendor, project, free-text and prepayment invoices, all with mandatory note prefixes (#PMD#, #PMT#, #AAB#), all with SIREN/SIRET/Branch ID identification logic, all with status lifecycle round-trips, all with separate e-reporting flows for non-domestic B2B and B2C. This is why Microsoft's build matters. And why the gaps in it matter even more. 

What Microsoft's 10.0.48 build delivers 

Per the Dynamics 365 release plan for 2026 wave 1, the French e-invoicing and e-reporting feature has the following availability: 

• Public preview: April 2026 (already released as part of the 10.0.48 preview build, available 24 April 2026 in the Shared Asset Library on Lifecycle Services). 

• General availability: August 2026 (self-update from 5 June 2026; first production autoupdate window opens 3 July 2026). 

Functionally, Microsoft has built more than a thin compliance veneer. The implementation covers: 

• Outbound electronic invoicing for domestic B2B sales orders, free text invoices, project invoices, credit notes (380/381 types) and customer prepayment invoices (386 type). 

• Inbound vendor invoice import in the French UBL-based format. 

• Mandatory lifecycle status round-trip between Dynamics 365 and the PA, including timeout handling and pipeline termination logic. 

• E-reporting flows for non-domestic B2B (cross-border) and all B2C transactions where the buyer has no SIREN. 

• Globalization Studio features named "French electronic invoice (FR)" and "French electronic invoice status (FR)" that ship the Electronic Reporting configurations, the model mappings (UBL Sales e-invoice, UBL Project e-invoice, vendor invoice import), and the response message handling. 

The XML mapping work, the SIREN/SIRET/Branch ID logic with EAS scheme codes (0009, 0002, 0088, 9957), the mandatory note prefix handling, the Azure Key Vault integration. Microsoft has done the heavy lifting. This isn't a PowerPoint promise. It's working code. 

So why isn't this enough? 

Gotcha #1 — One Plateforme Agréée in the box. 120 in the market. 

Read the Microsoft Learn setup guide carefully and one assumption is hardcoded throughout: Edicom is the PA. The Globalization Studio features call out Edicom by name. The Electronic Reporting configurations are named "Edicom invoice status format", "Edicom Response Processing (FR)", "Edicom Vend App Response Processing". The Key Vault token element is for Edicom services. The submission lifecycle status handling references the Ediwin portal directly. 

Here's the problem. As of April 2026 the DGFiP has registered 120 Plateformes Agréées, with a further 21 operators in the testing pipeline. If your French entity has already signed with Docaposte, Pennylane, Esker, Generix, Sage, Symtrax, Cegid, or one of the other 115 platforms, Microsoft's standard build doesn't help you. It helps Edicom. 

Yes, the Electronic Reporting configurations are extensible. Yes, technically you can build a custom integration. But "extensible" isn't a price quote. A custom PA connector means two distinct workstreams. First, the XML format work: extending the Electronic Reporting configurations to produce the exact UBL or CII variant your PA expects, including any PA-specific extensions or attributes. Second, the connectivity work: building the actual call to the PA's API endpoints, handling authentication, request and response parsing, retries, and lifecycle status round-trips. Add Key Vault wiring for the credentials, integration channel configuration, and regression testing across every invoice type Microsoft already supports out of the box for Edicom. That's not a weekend job. In our experience, eight to sixteen weeks of build work depending on the PA's API maturity. 

This isn't unique to France either. Microsoft has used Edicom as their global e-invoicing partner for years. Brazil, Costa Rica, Paraguay and Uruguay all use the same pattern. From Microsoft's perspective it's clean engineering. One partner, one integration model, repeated globally. From the customer's perspective it forces a vendor decision into a procurement choice that should be theirs to make. PA pricing in France varies enormously by volume tier and by service scope, so the choice isn't cosmetic. Locking into Edicom because it's the only one Microsoft preconfigured is not a finance decision. It's an accident. 

Gotcha #2 — The Electronic Invoicing add-on meter that scales with your invoice volume 

The French e-invoicing functionality runs on the Electronic Invoicing add-on. That's a separate Azure microservice with its own licensing meter, sitting on top of your existing D365 Finance subscription. 

Per Microsoft's own Invoice capture documentation on Microsoft Learn: 

• Free tier: 100 transactions per tenant per month. 

• Add-on SKU: $300 USD for 1,000 transactions per tenant per month. 

• Use it or lose it. No monthly roll-over of unused capacity. 

• Buy for peak capacity, not average, because exceeding the purchased volume puts you out of compliance with Microsoft's licensing policy. 

Run the maths. A French legal entity issuing 5,000 outbound invoices per month needs 5 add-on SKUs. That's $1,500 USD per month, or roughly $18,000 USD per year, per entity. A mid-market group with 50,000 invoices per month across French entities is looking at $180,000 USD per year just on the Microsoft microservice meter, before Edicom's fees, before implementation costs, before any custom development. 

A note on what the meter actually counts. Per Microsoft's Usage management dashboard documentation, the meter counts business document submissions to the Electronic Invoicing service, regardless of how many lines each document contains. Resubmissions of the same document don't double-count. But outbound response submissions (for example, payment-received confirmations sent by the seller, or refusal responses sent by the buyer) are counted as separate transactions. In the French scope, that matters: every payment-received response sent to a buyer's PA is a separate transaction unit. Model your monthly volume to include response flows, not just initial invoice submissions. 

This cost is on top of Edicom's own fees. To put real numbers on the table, here's what we've seen in a recent multi-country PA proposal we reviewed for a client (anonymised). The France-specific scope, covering AR, AP, e-reporting and lifecycle status for 2 French legal entities, was quoted at: 

• €37,671 one-time implementation fee 

• €435.60 per month in fixed costs 

• €145 per month in running costs 

That works out at roughly €18,800 implementation per French entity, plus around €7,000 per year in recurring fees, for the Edicom side alone. Layer the Microsoft Electronic Invoicing add-on on top, even at a modest 5,000 invoices per month per entity, and a reasonable Year 1 cost stack for a two-entity French operation looks like this: 

• One-time: €37,671 (Edicom France) plus an estimated €15,000 to €25,000 for Microsoft-side ER configuration, parameter setup, key vault wiring, sandbox testing and UAT. 

• Annual recurring: €6,967 (Edicom France) plus roughly $36,000 USD for the Electronic Invoicing add-on at 5,000 invoices per entity per month. 

• Year 1 floor: somewhere north of €85,000, scaling up sharply with volume. 

For high-volume customers in retail, e-commerce or utilities, the Microsoft meter eventually dominates the cost stack and keeps growing every month for the life of the deployment. 

What CFOs and ERP programme directors should do now 

Stop treating the September 2026 deadline as a future problem. The preview build is already in your shared asset library. The clock on regression testing, PA contracting, Key Vault setup and parallel running is already ticking. 

Inventory your French invoice volume by legal entity, projected at peak month, not average. The Microsoft licensing model penalises spikes because there's no roll-over of unused capacity. If your Black Friday or year-end invoice run triples your monthly volume, you buy for that peak. 

If you're already contracted with a non-Edicom PA, and most French companies that signed in 2024 and 2025 are not on Edicom, treat the Microsoft standard build as a starting point. Scope a custom PA connector now. Don't wait for August 2026 GA to discover that your contracted PA isn't supported. 

Run a proper TCO model on the Electronic Invoicing add-on across your full French invoice volume for three years. Compare it against the cost of routing your e-invoicing flow outside the Microsoft meter (for example, through a non-Edicom PA's own connector that bypasses the add-on entirely). The answers vary depending on volume, entity count and integration topology, but the question is too important to skip. 

Finally, separate the workstreams in your planning. E-invoicing for domestic B2B is one set of flows. E-reporting for cross-border B2B is another. E-reporting for B2C transactional and payment data is a third. They share infrastructure but the data sources differ, the validation rules differ, and each one carries its own go-live risk profile. 

The bottom line 

Microsoft has done real engineering work in 10.0.48. The French electronic invoice features cover sales, projects, free text, prepayments, vendor import, lifecycle status round-trips and e-reporting. That isn't trivial and it isn't cosmetic. If you're running D365 F&O in France with a small invoice volume and you're happy to contract with Edicom, the standard build is a reasonable starting point. 

If you're not, the standard build is where the real architectural work starts, not where it ends. That applies to anyone already contracted with a non-Edicom PA. It applies even more if invoice volume pushes the add-on meter into uncomfortable territory, or if you're rolling out across multiple French entities with different operational profiles. 

The 1 September 2026 deadline is fixed. Microsoft's GA is planned for August 2026. That leaves no slack for second guesses on PA contracts or licensing assumptions made on the back of a sales deck. 

Need help? If you're running D365 F&O in France and you need a custom Plateforme Agréée connector, or a proper TCO analysis on the Electronic Invoicing add-on before your renewal lands, reach out to the Dr Dynamics team. We've built custom PA connectors that generate the required XML through standard Electronic Reporting and submit it to your PA via an X++ web service call from F&O directly, which means no Globalization Studio path and no Electronic Invoicing add-on transactions to license. We can integrate D365 F&O with the Plateforme Agréée you've chosen, not the one Microsoft picked for you. 

Sources 

• Microsoft Learn — Electronic invoicing for France 

• Microsoft Learn — Meet requirements for e-invoicing and e-reporting in France (2026 wave 1 release plan) 

• Microsoft Learn — Service update availability (10.0.48 dates) 

• Microsoft Learn — Invoice capture solution (Electronic Invoicing add-on pricing) 

• Microsoft Learn — Electronic Invoicing service overview 

• impots.gouv.fr — Liste des plateformes agréées 

• economie.gouv.fr — Liste des 101 premières plateformes agréées (16 January 2026) 

• Service Public Entreprendre — Liste des plateformes agréées immatriculées

• European Commission — eInvoicing in France