In short
From 1 September 2026 every business established in France must be able to receive structured e-invoices, and large and mid-size companies must also issue them and produce e-reporting data. SMEs and micro-companies follow on 1 September 2027. France runs a 5-corner model: private accredited platforms (Plateformes Agréées) route the invoices, while the PPF holds the directory and receives regulatory data. Dr Dynamics makes Dynamics 365 F&O and legacy AX ready — including the lifecycle-status loop most projects underestimate.
How engagement works
The 2024 redesign removed invoice handling from the PPF, so private accredited platforms route invoices between seller and buyer and you must contract with one to transact in France. Peppol eDelivery is the default protocol between platforms; the PPF keeps the Annuaire directory and concentrates regulatory data.
F2 is the invoice itself between platforms. F1 is the regulatory extract to the PPF. F6 carries the mandatory lifecycle statuses. F10 is the main e-reporting channel for B2C, cross-border and payment data, with F8/F9 as variants. F13/F14 maintain the directory.
Three formats are accepted, all EN 16931-compliant: UBL 2.1, CII and Factur-X, the hybrid PDF/A-3 with embedded XML. Paper and unstructured PDFs are not valid for B2B transactions in scope. Our flow-by-flow guide walks through all eight flows, and the France readiness case study shows what the validation work looks like in practice.
Microsoft ships the French functionality in D365 F&O 10.0.48. Electronic Reporting produces the UBL 2.1, CII or Factur-X payload that becomes your F2.
The PA connector is yours to build or buy: F1, F2, F6 and F10 traffic out to your accredited platform, and the return traffic back in. Microsoft does not ship it.
The F6 statuses — Déposée, Rejetée, Refusée, Encaissée — must land against the source invoice in Dynamics, with an audit trail. Without that loop you have an open-loop solution that will fail audit.
Platforms
Our 34-check data-readiness validator: a code package your engineer drops into D365 Finance, so your team can run the seller, buyer and payment-terms checks on your own master data — SIRET, VAT and IBAN included — and get a plain-Excel report of every problem and its fix.
Full implementation: configuration, PA connection, inbound AP, the F6 lifecycle mapping, the validation layer, master-data checks and cutover. Typical pilot live in 6–10 weeks.
Post-go-live support with a named engineer, an SLA and a monthly operational review — so the September 2027 SME wave is a configuration task, not a project.
Every business established in France must be able to receive structured e-invoices from that date. Large and mid-size companies must also issue them and produce e-reporting data. SMEs and micro-companies follow on 1 September 2027.
The date was reconfirmed in July 2026 and stands at 1 September 2026, but enforcement is deliberately soft: the DGFiP has said there will be no automatic penalties in Q4 2026, and that companies which are not fully compliant will have their trajectory assessed individually, with support and dialogue first. Treat that as breathing room on enforcement, not a change to the obligation.
Yes, you need one. The 2024 redesign ended the plan for the PPF to handle invoice issuance; private accredited platforms now do the routing, and the PPF is a directory and data concentrator. You must contract with a PA to transact in France, and your entity must be registered in the Annuaire before your first invoice can be routed.
Three, all compliant with EN 16931: UBL 2.1, CII, and Factur-X — the hybrid PDF/A-3 with structured XML embedded. Paper invoices and unstructured PDFs are not valid for B2B transactions in scope. D365 Finance ships Electronic Reporting configurations for all three.
Four are mandatory and must reach the PPF: Déposée (deposited), Rejetée (rejected on technical or format grounds), Refusée (commercially refused by the recipient) and Encaissée (cashed, where VAT on receipts applies, including down payments). Each is a CDAR message, timestamped and stored against the originating invoice for the full ten-year archive. This is usually the largest D365 work item, because it means consuming inbound messages, not just pushing invoices out.
It depends on your VAT regime. Under the standard monthly regime, transaction data goes three times per month (every 10 days) and payment data once per month — two parallel schedules. Under the simplified regime or VAT franchise it is monthly or bimonthly. The deadline is generally 10 days after the end of each period, and it is strict.
No. Microsoft delivers the invoice data model, the ER format configurations, the submission service and the country flow catalogue in D365 F&O 10.0.48. What every customer still needs to build or buy is the PA connector, inbound vendor invoice parsing, the F6 lifecycle status mapping, pre-submission validation, and cutover orchestration including Annuaire registration and master-data preparation.
The gap is bigger, because Microsoft does not deliver Electronic Reporting natively to AX 4.0, AX 2009 or AX 2012. You either migrate to D365 F&O — the September 2026 mandate is the strongest business case for that move we have seen — or run a parallel compliance layer until you do. Our connector covers the full range from AX 4.0 through D365 F&O.
English. Dr Dynamics delivers to French entities from the UK, and the project language — meetings, workshops and documentation — is English. The solution itself is of course French: Factur-X, the PA connection, the F6 statuses and the e-reporting flows.
Bring your PA shortlist, your Dynamics version and whichever September question is keeping you up at night. We will come back with a one-page fastest-path plan within 48 hours. The enforcement date does not move because a project plan slipped.
DR DYNAMICS