How D365 layers country/region functionality — a Microsoft-shipped localisation, an ISV add-on, or something you build — set against Unit4's tax-codes-and-attributes model and its Nordic and public-sector strength; the D365 tax engine in full; withholding tax on both platforms; EU obligations and public-sector VAT recovery; Electronic Reporting and Peppol e-invoicing; and the legal-entity sequencing consequences of a multi-country rollout.
This is the first chapter in the Localisation, Tax & Statutory Reporting domain, so it stands alone rather than building on an earlier part in the same domain the way most other chapters in this path do.
D365 F&O does not ship one monolithic tax and compliance module. It layers functionality in three ways, and knowing which layer a given requirement sits in changes the whole planning conversation:
D365's sales tax engine determines a tax amount from configuration, not from a rule buried in a transaction:
Unit4's Foundation model handles tax with less structural ceremony: tax codes and tax systems configured per Company, referenced from a transaction, with the finer determination logic — which code applies to which customer, vendor or item — frequently pushed into an Attribute or Relation rather than held as a first-class tax object.
Withholding tax — tax deducted at source from a payment, most commonly on payments to suppliers or contractors — exists on both platforms, built from different starting points.
D365 ships built-in support for the recurring EU statutory obligations: Intrastat (movement-of-goods reporting between member states), the EC sales list (cross-border B2B supply reporting), and standard VAT declaration formats, all driven by accurate underlying transaction and item classification rather than a bespoke report built after…
The Electronic Invoicing add-in is a separately provisioned service that connects D365 to national e-invoicing mandates and Peppol — the pan-European access-point network for exchanging structured invoices between buyer and supplier systems, in which each party connects through its own access-point provider rather than exchanging…
The final design question this chapter raises has the largest downstream consequence: how do Unit4 clients map onto D365 legal entities? A Unit4 client is not automatically one D365 legal entity — some Unit4 estates use Company-level attribute overrides within a single client to approximate several statutory jurisdictions, precisely the…
Localisation is the part of a Unit4-to-D365 migration a regulator, not a business owner, ultimately signs off — and it rewards exactly the same honest, country-by-country discipline this whole site applies to everything else.