Solutions > eInvoicing for Dynamics AX
E-invoicing for Dynamics 365 Finance & Operations. Configured properly. Gap closed.
Microsoft ships the e-invoicing framework. We configure it to your country profile and your platform, build the inbound, lifecycle and validation layer it doesn't, and get you live across France, Germany, Belgium, Italy and Poland. All on standard Dynamics, no parallel platform fighting your upgrades.
Five mandates. One ERP. Five different deadlines.
This stopped being a France problem some time ago.
Belgium switched on mandatory structured B2B e-invoicing in January 2026. Poland's KSeF went live for large taxpayers in February 2026 and for all B2B in April. Italy has run everything through SdI since 2019, and its derogation now runs to the end of 2027. Germany already requires you to receive EN 16931 invoices and is phasing in issuing through 2027 and 2028. France switches on its receive obligation for every established business on 1 September 2026, with large and mid-size companies issuing from the same date.
If you run one D365 F&O instance across several of these countries, you are not managing one mandate. You are managing five calendars, five formats, and five platform relationships, against a single finance system and a single close.
That is the job. The good news is that most of the heavy lifting now sits inside the product.
Microsoft ships the framework. That's the easy 80%.
Microsoft has done the hard platform work, and the 2026 Wave 1 release moved it forward again.
Standard Dynamics 365 Finance gives you the Electronic invoicing service, a cloud, multitenant engine that generates, submits and receives electronic documents outside the F&O application, configured rather than coded. It sits under Globalization Studio, which carries the country localisations and the regulatory updates that land in your tenant on Microsoft's cadence. The Electronic Reporting formats for UBL, Factur-X and the country-specific profiles are Microsoft-maintained. The French B2B e-invoicing and e-reporting solution shipped in 2026 Wave 1, in public preview from 29 April 2026 and general availability in August, routing through EDICOM as the certified accredited platform. Germany's xRechnung, Italy's FatturaPA and the European Peppol formats are already generally available. Wave 1 also added a new extensible universal connector for the e-invoicing service, the plug-in point for service providers beyond the standard ones.
So if your roadmap question is "does Microsoft handle e-invoicing," the answer is yes, and you should build on what it ships. We do.
The framework is not the part that fails projects.
The 20% that decides whether you go live
● You run Dynamics AX 4.0, 2009 or 2012 somewhere in your group● You have a mandate deadline in France, Germany, Belgium, Poland, Italy or another EN 16931 country● You want a controlled bridge to compliance, not a rushed D365 programme● Your auditors will ask awkward questions if the XML and the audit trail do not line up
This is the work that stays yours, and the work we do:
Configuring the service to your reality.
The Electronic invoicing service and the ER formats have to be set up against your document types (sales invoices, free text invoices, project invoices), your tax codes, and the exact country profile. A clean demo tenant is not your tenant.
Connecting your platform, not just the default one.
Microsoft's standard French solution routes through EDICOM. If your group has already standardised on Pagero, Generix, Tradeshift, ecosio, Docaposte or another provider across Europe, that is exactly what the new extensible connector is for, and exactly what we configure. You pick the platform. We make Dynamics talk to it.
Inbound vendor invoices into AP.
Receiving a structured supplier invoice and turning it into a pending vendor invoice your AP team can match and approve is real integration work. It does not configure itself.
Lifecycle statuses finance can act on.
Deposited, rejected, refused, cashed. These come back as a stream against every invoice, and they have to land somewhere your finance team can see and act on, with the full audit trail behind them. A "refused" that nobody sees is a compliance gap with a date on it.
Validation before submission, not after.
Catch the EN 16931 and country-CIUS errors before the document leaves Dynamics, and you cut rejection cycles by an order of magnitude. Skip it, and your finance staff spend their week chasing rejected statuses out of a platform portal.
Master data nobody wants to own.
SIREN and SIRET, VAT IDs, IBANs, address fields, mandatory tax codes. This is the single biggest cause of rejections, and it has to be fixed before go-live, not during.
Multi-entity rollout on one pattern.
Five countries on one D365 instance should be one configuration approach extended five times, not five disconnected projects.
Cutover that holds.
Directory and Annuaire registration through your platform, parallel run, hypercare, and a runbook that says who monitors, who fixes, and who reprocesses at 5pm on a Friday.
You're in the right place if...
What we add on top of standard D365
We are a customer-oriented company, and our values drive us to achieve more.
A built-in pre-submission validatorEvery outbound invoice is checked against the EN 16931 ruleset and the country CIUS before it leaves Dynamics. Fewer rejections, less finance firefighting.
Platform-agnostic by design
EDICOM, Pagero, Generix, Tradeshift, ecosio, Docaposte and others. You choose. Switching later costs a configuration pack, not a rebuild.
Inbound AP, properly wired
Structured supplier invoices land as pending vendor invoices, ready for your existing matching and approval flow.
A lifecycle status view that earns its place
Sent, accepted, rejected, refused, cashed, tracked against the source invoice, visible to finance, reprocessable from Dynamics.
Audit trail ready
Generated XMLs and status history stored against the invoice record. Auditors get what they need without a ticket.
Configuration over code
We sit on Microsoft's framework wherever the framework reaches. Wave updates land the way Microsoft intends. Your team doesn't carry a fork.
One pattern, every entity
Built to extend across your country footprint on a single, repeatable configuration.
Fast to pilot
Typical pilot in 6 to 10 weeks, depending on country count and data readiness.
Where it works today
Country
Mandate status (June 2026)
On standard D365
Country
Country
Mandate status (June 2026)
Mandate status (June 2026)
On standard D365
On standard D365
France
Receive for all from 1 Sep 2026; issue for large and mid-size from 1 Sep 2026; SMEs from 1 Sep 2027
Microsoft 2026 Wave 1 solution via EDICOM; we configure, validate and extend to your PA
Country
France
Mandate status (June 2026)
Receive for all from 1 Sep 2026; issue for large and mid-size from 1 Sep 2026; SMEs from 1 Sep 2027
On standard D365
Microsoft 2026 Wave 1 solution via EDICOM; we configure, validate and extend to your PA
Germany
EN 16931 receiving in force since Jan 2025; issuing phases in through 2027 and 2028
xRechnung and Peppol generally available; we configure and operationalise
Country
Germany
Mandate status (June 2026)
EN 16931 receiving in force since Jan 2025; issuing phases in through 2027 and 2028
On standard D365
xRechnung and Peppol generally available; we configure and operationalise
Belgium
Mandatory structured B2B e-invoicing since 1 Jan 2026 (Peppol), three-month tolerance period
Peppol BIS generally available; we configure and connect
Country
Belgium
Mandate status (June 2026)
Mandatory structured B2B e-invoicing since 1 Jan 2026 (Peppol), three-month tolerance period
On standard D365
Peppol BIS generally available; we configure and connect
Italy
SdI mandatory since 2019; EU derogation runs to 31 Dec 2027; tech specs v1.9.1 from 15 May 2026
FatturaPA generally available; we configure and maintain
Country
Italy
Mandate status (June 2026)
SdI mandatory since 2019; EU derogation runs to 31 Dec 2027; tech specs v1.9.1 from 15 May 2026
On standard D365
FatturaPA generally available; we configure and maintain
Poland
KSeF mandatory from 1 Feb 2026 (large taxpayers) and 1 Apr 2026 (all B2B); micro from Jan 2027
We configure submission, validation and lifecycle handling
Country
Poland
Mandate status (June 2026)
KSeF mandatory from 1 Feb 2026 (large taxpayers) and 1 Apr 2026 (all B2B); micro from Jan 2027
On standard D365
We configure submission, validation and lifecycle handling
Other EN 16931 countries
On request
Available
Country
Other EN 16931 countries
Mandate status (June 2026)
On request
On standard D365
Available
It's a data and exception problem, not a format problem
Most e-invoicing projects go sideways for the same reason. Teams scope them as a format conversion exercise. Generate the XML, post it, store the receipt, done.
It is never that.
The hard parts are data quality, exception handling, and who owns the rejection that lands at 5pm on a Friday. Standard Dynamics will happily generate a perfectly valid XML from invalid master data and watch it get refused downstream. The format was fine. The SIRET was wrong.
We build for those realities. Minimal disruption to your posting and approval workflows. Batch-friendly processing with retries. Rejection feedback in plain English, so finance can fix the invoice without opening a platform portal or raising a ticket. Validation that runs before submission, because the cheapest rejection is the one that never reaches your provider.
From standard feature to live across your estate, in four phases
1. Readiness and architecture. Country footprint, document types, volumes, platform choice, target operating model. We confirm what standard Dynamics covers for each country and scope only the gap. Usually a week or two.
2. Configuration and data readiness. We configure the Electronic invoicing service and the ER formats, and run the master-data check early: VAT IDs, SIREN and SIRET, IBANs, address fields, mandatory tax codes. You fix the data while we build.
3. Integration and inbound. Connect your chosen platform, wire inbound vendor invoices into AP, and map the lifecycle statuses into a view finance can act on, with audit trail.
4. Test, cutover, hypercare. End-to-end against your platform's sandbox with real invoice patterns. Controlled go-live with a runbook. Then handover, documentation, and a named contact for escalations.
Proof, not a pitch deck
We have built and now operate a Dynamics e-invoicing solution that spans the full version range, from D365 Finance & Operations back through legacy AX. On D365 F&O it configures and extends Microsoft's standard Electronic invoicing service. For legacy AX, where that framework was never delivered, it provides the equivalent extraction and outbound layer. Same flows, same format compliance, same lifecycle handling.
We are already live on real readiness work, including a multi-entity European group running D365 Finance & Operations across several mandate countries on a single configuration pattern, multinationals with a French branch inside a larger estate, and recovery engagements where a stalled implementation needed a finance-architect-led reset. The solution is tested in production conditions, not against a spec sheet.
And we are independent. When we tell you to build on what Microsoft ships, we are not quietly selling you a platform licence on the side.
Who is building this
Dr Dynamics is an independent Microsoft Dynamics 365 Finance & Operations consultancy based in the UK. The team includes former Microsoft FastTrack engineers and ex-Microsoft localisation programme people. We have worked on AX and D365 F&O projects at EY, Deloitte, Credit Suisse, Starbucks, HPE, Somerset Council and Notting Hill Genesis, among others.
Finance-first. Architecture-led. Microsoft-aligned.
FAQ
Doesn't standard Dynamics already do all of this?
It does most of it, and you should use it. Microsoft ships the framework, the formats and the France solution in 2026 Wave 1. What standard does not do for you is the configuration to your exact setup, the connection to a non-default platform, inbound AP, the lifecycle view your finance team needs, pre-submission validation, and the master-data and cutover work. That is the part we do.
We've standardised on a platform that isn't Microsoft's default. Is that a problem?
No. Microsoft's standard French solution routes through EDICOM, and 2026 Wave 1 added an extensible connector for other providers. If your group runs Pagero, Generix, Tradeshift, ecosio, Docaposte or another platform, we configure Dynamics to it.
We only need one country. Do we pay for all of them?
No. The approach is modular. Configure the countries you need now, extend to others when their mandates land.
What about our auditors?
Full audit trail, generated XMLs stored against the invoice record, status history preserved. We have been through a few statutory audits with this pattern. No drama.
Will this slow down our other D365 work?
It shouldn't. We sit on Microsoft's framework so Wave updates land cleanly, and we scope the e-invoicing work as its own controlled stream with its own cutover.
Can you support us after go-live?
Yes. Support arrangement with a named engineer, an SLA, and a monthly operational review. Separate SOW.
Does it work on-premises?
Microsoft's Electronic invoicing service is cloud-only. The standard solution applies to cloud D365 Finance & Operations. For on-premises or legacy AX estates, we deliver the equivalent layer as a consulting engagement.
Bring your country footprint, your D365 version, your platform shortlist, and whichever mandate date is closest. We will come back with a one-page fastest-path plan within 48 hours, mapping what standard Dynamics covers for you and exactly what we configure on top.
Prefer a human? Call +44 758 315 7122 or email .ku.oc.scimanydrd%40namor