Dynamics 365 e-invoicing: the questions CFOs and IT leaders ask

Which European e-invoicing mandates affect Dynamics 365 customers, and when?

Belgium has required structured B2B e-invoicing over Peppol since 1 January 2026, and its three-month no-penalty tolerance window closed on 31 March. Poland’s KSeF became mandatory for the largest taxpayers on 1 February 2026 and for the rest of the VAT-registered population on 1 April, with penalties deferred until January 2027. From 1 September 2026, every business established in France must be able to receive e-invoices; large and mid-size companies must issue them too from that date, and SMEs follow on 1 September 2027. Germany has required businesses to receive EN 16931 invoices since January 2025 and phases in issuing from 1 January 2027 for companies with prior-year turnover above €800k, then 1 January 2028 for everyone else. Italy has been on SdI since 2019, with an EU derogation now running to the end of 2027, and the Netherlands is still in consultation with a 2030 Peppol target. Country-by-country detail lives on our e-invoicing hub.

What does standard Dynamics 365 F&O give you out of the box?

More than most teams expect, and it should be the foundation you build on. The core in-licence capability is Electronic Reporting: the standard, configuration-driven engine that generates the formats behind each mandate, with Microsoft maintaining the base configurations — UBL and the individual country profiles. The notable gap is the hybrid PDF formats: Microsoft does not ship Factur-X or ZUGFeRD — we cover both as part of our package. Microsoft also offers a separate route, the Electronic invoicing add-on: a multitenant cloud engine under Globalization Studio, licensed separately with per-document capacity, cloud-only, and routed through Microsoft’s default platform choices — France’s add-on solution, for example, arrived with 2026 Wave 1 via EDICOM. Our solutions deliberately do not depend on it: standard Electronic Reporting plus a direct connection to your own e-invoicing provider covers the same mandates without the extra licence.

If standard Dynamics does so much, what work is actually left?

The part that decides whether you go live. The formats have to be configured for your document types, your tax setup and the precise profile of each country — the configuration that suits a demo tenant will not suit yours — and Dynamics has to be connected to your e-invoicing platform so documents go out and statuses come back without manual chasing. Inbound structured supplier invoices have to become pending vendor invoices your AP team can match and approve, which is integration work rather than a setting. The status messages the network sends back need to land somewhere finance can see and act on. Add pre-submission validation, master data remediation, and a cutover plan covering directory registration, parallel running and hypercare, and you have the real scope of the project. None of it configures itself.

Do we need a PDP or a Peppol access point, and how do we choose?

It depends on the country. France has no single government portal to plug into: since the 2024 redesign of the model, the Portail Public de Facturation acts as a directory and data concentrator while accredited private platforms do the routing, so most companies need a certified platform — a PDP — sitting between D365 and the tax authority. Choosing one, negotiating the contract and running end-to-end testing typically takes four to six months. Belgium runs on Peppol, so you need an access point, through Microsoft or a third-party provider. The platform names you will hear most often are EDICOM, ecosio, Pagero, Generix, Tradeshift, Docaposte and B2Brouter. Shortlist against your volumes and geographies, and insist on an integration design where a later change of platform means reworking configuration rather than rebuilding the integration.

We’re still on Dynamics AX — do we have to migrate before the mandates hit?

Not necessarily, but the gap is wider than on D365 because Microsoft never delivered Electronic Reporting to AX 4.0, 2009 or 2012 — there is no standard capability to configure. That leaves two honest options: migrate to D365 F&O cloud, for which a hard mandate deadline is one of the strongest business cases there is, or run a compliance layer alongside AX until you do. Our retrofit solution for legacy AX takes the second route: it supplies the extraction and outbound layer that Electronic Reporting would otherwise provide, covering the same flows, format rules and lifecycle behaviour as its D365 counterpart, across the full version range from AX 4.0 through 2012 R3 — no upgrade project required.

Why do invoices that leave D365 cleanly still get rejected?

Because the standard flow validates too late. Microsoft applies validation rules when the invoice is generated, which catches the obvious gaps, but the EN 16931 and Peppol BIS Billing rules that bite at the receiver’s access point are a different matter: a price carrying more decimal places than the standard allows, a missing buyer reference, a free-text invoice with no item name, empty contact elements left in the file. None of these stop the invoice leaving D365, and every one of them bounces later, leaving finance in a loop of send, wait, reject, decode, fix, resend — with invoice numbering integrity at risk on every hurried resubmission. Moving validation before submission, inside D365, stops that loop before it starts.

How much does master data matter?

It is the single biggest cause of rejections. Dynamics will happily produce a schema-valid XML from wrong master data, and the network will refuse it downstream: the file passed, the SIRET inside it did not. VAT IDs, SIREN and SIRET numbers, IBANs, address fields and mandatory tax codes on customer and vendor records all have to be right before go-live, not during it. Run the master-data audit at the start of the project, so the data is being fixed while the configuration is being built rather than blocking the cutover.

What are invoice lifecycle statuses, and why can’t we ignore them?

Under the French model, every invoice generates a stream of status messages, four of which are mandatory and must reach the tax administration: deposited, rejected, refused and cashed — the last covering VAT-on-receipts cases, including down payments. Each message must be timestamped and stored against the originating invoice for the full ten-year archive. That makes lifecycle handling the biggest D365 work item in the whole reform: your environment has to consume the inbound messages, map them onto the source invoice and present them so finance can act — a refused invoice needs reissuing, and a cashed status closes the VAT timing question. Push invoices out without consuming what comes back and you are running open-loop, which will not survive an audit.