How D365 layers country and region functionality against a single legal entity, how a tax amount is actually determined through sales tax groups, item tax groups and ledger posting groups, the honest delta from NetSuite's Tax Code/Tax Group/Nexus model on both the Legacy Tax engine and SuiteTax — including the heavy real-world reliance on Avalara — and how Electronic Reporting, e-invoicing and SAF-T answer 'produce this statutory file without code' where a NetSuite shop previously reached for a saved search or an Advanced PDF template.
Every other domain on this site assumes a business event means the same thing regardless of which country it happens in. Localisation is where that assumption stops holding — legally, not just technically.
A D365 legal entity carries a country/region value, and setting it does real work: it activates the parameter forms, number sequences, and locale-aware behaviours Microsoft ships for that country. What it does not do, on its own, is guarantee that every statutory output for that country is ready to use.
D365's indirect-tax framework handles sales tax, VAT, GST and withholding tax through one shared set of building blocks:
NetSuite's tax model runs on one of two engines, and knowing which one a tenant is on changes the starting point of every conversation. The Legacy Tax engine is code-and-group based in a simpler sense than D365: a Tax Code carries a rate and a Tax Control Account — the GL account collected or paid tax posts to — and a Tax Group bundles…
NetSuite has no single, universal withholding-tax mechanism baked into the core product the way its Tax Code framework is; withholding coverage is frequently delivered through a country-specific bundle or SuiteApp layered on top of Customer and Vendor records, with rate, certificate and reporting behaviour that varies by which bundle a…
Three recurring EU obligations sit on top of the tax engine rather than inside it. Intrastat declarations report the physical movement of goods across EU member-state borders, independent of a transaction's invoice-level VAT treatment.
Electronic Reporting (ER) is the framework underneath nearly everything in this section: a declarative, model-driven stack — data model, model mapping, format, format mapping — that produces a statutory output without a bespoke program for it.
A single-country D365 implementation rarely has to face this section at all. A multi-country OneWorld tenant cannot avoid it, and two decisions have to be made early, because both shape the sequencing of every country that follows.
Localisation is the one domain where "it works" and "it works and stays compliant" are genuinely different bars, and where a NetSuite habit — reach for a saved search, install a bundle, bolt on Avalara — has to be re-examined rather than copied, because the D365 side answers the same requirements through a smaller, more structured set of…