How D365 layers country and region functionality on top of 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 LN's Financial-Company-owned, IMS-driven tax model, and how Electronic Reporting, e-invoicing and SAF-T answer 'how do we produce this statutory file without code' — for a product whose own company model splits legal identity from operations in a way D365 does not.
Every domain so far in this path has compared how LN and D365 model the business itself — organisation, finance, postings, development. Localisation is different in kind: it is the one part of the estate where the customer does not get to choose the requirement.
D365 F&O's starting point is a single legal entity with a primary address country/region. Setting that value is not cosmetic — it activates the country-specific features, forms and processes associated with that country for the entity automatically.
D365's indirect-tax framework covers sales tax, VAT, GST and withholding tax through one shared set of building blocks, related to each other in a fixed way:
LN has no dedicated tax module comparable to a SAP tax procedure or a D365 tax engine as a named, isolated component. Tax codes are maintained per country within the tcmcs common data layer — the same family of tables that carries site, warehouse and other shared reference data across a Logistic Company — and, critically, a tax-relevant…
LN handles withholding-style deductions as business-partner-level configuration within common data, settled through the relevant AP or AR sub-ledger at payment or invoice time depending on the country's requirement — country-specific rate tables and certificate or receipt tracking are typically layered on through customisation or…
Three recurring EU statutory obligations sit on top of the tax engine rather than inside it, on both platforms. Intrastat declarations report the physical movement of goods across EU member-state borders, independent of the invoice-level VAT treatment of the transaction.
Electronic Reporting (ER) is the framework underneath nearly everything else in this section: a declarative, model-driven stack — data model, model mapping, format, format mapping — that produces a statutory output without a custom program written specifically for it.
A single-country D365 implementation rarely has to make this decision explicitly. A multi-country LN estate cannot avoid it, and LN's own company model makes the question sharper than it is for most source platforms, because the conceptual model already names the answer's trigger condition: escalate to full company-unbundling Pattern C —…
Localisation is the one domain on this site where "it works" and "it works and stays compliant" are genuinely different bars, and where currentness is as much a part of the job as correctness.