Localisation, tax configuration and statutory reporting on the same-lineage path
How country/region localisation, the sales tax engine, Electronic Reporting and electronic invoicing carry forward from AX 2012 — and the honest list of localisations, country versions and deprecated features that do not survive the upgrade and must be discovered before an upgrade date is committed.
What you will be able to do
Explain how country/region localisation worked in AX 2012 versus how it works in D365 through feature management and regulatory updates
Trace how the AX 2012 sales tax framework (tax groups, item sales tax groups, tax codes) maps forward with the residue that requires re-validation
Describe the move from AX 2012 SSRS-based statutory reporting to Electronic Reporting and identify which reports require rebuild
Inventory every AX 2012 localisation and deprecated-feature risk that can block or degrade an upgrade, using the Upgrade analyzer and deprecated-features list
Produce a localisation readiness checklist a programme can run before committing to an upgrade date
Introduction
An AX 2012 upgrade is the one path on this site where the tax configuration mostly survives the move. Sales tax codes, sales tax groups, item sales tax groups, ledger posting groups and withholding tax codes are identity-mapped by the data upgrade.
How country/region localisation works: AX 2012 versus D365
In AX 2012, country/region localisation was delivered as compiled X++ code in country-specific model layers within the AOT. A legal entity's primary address country/region activated the relevant country-specific forms, processes and configuration options for that company.
The sales tax framework: identity-mapped records, changed runtime
The AX 2012 sales tax framework and the D365 sales tax framework share the same logical structure:
Statutory reporting and Electronic Reporting
Standard SSRS report designs delivered with the country layer (VAT declarations, Intrastat, payment advices). Custom SSRS reports built by the customer or their partner for requirements the standard did not cover. Custom X++ extraction programs for structured data files (SAF-T, XML tax filings, flat-file bank submissions).
Electronic invoicing
Electronic invoicing in D365 is an add-on service built on top of Electronic Reporting. It handles real-time or near-real-time submission of invoices to a government authority or clearance platform, depending on the country mandate.
Deprecated and removed localisations: the honest part
Microsoft publishes a list of deprecated and removed features with each D365 release. For an AX 2012 upgrade, this list is the single most important localisation-risk document. A feature that existed in AX 2012's country layer and has been deprecated or removed in the target D365 release has no automatic upgrade path.
The localisation readiness checklist
A programme should not commit to an upgrade date until the following checklist produces no unresolved blockers:
Wave sequencing for localisation work
Localisation configuration is canonical Wave 1 work on this site — it is part of the financial foundation that must be locked before any transactional data can be loaded or validated. Specifically:
Knowledge check
Summary
The same-lineage upgrade preserves localisation configuration structurally — sales tax codes, groups, posting groups and withholding-tax setup carry forward as identity-mapped records.