Chart of accounts, financial dimensions and account structures — what upgrades and what must be reconciled
How the AX 2012 ledger, chart of accounts, main accounts, financial dimensions, account structures and advanced rules carry forward into D365 — what genuinely upgrades unchanged, what demands re-validation, and the dimension clean-up that the upgrade is the right moment for.
What you will be able to do
Distinguish what in the AX 2012 chart-of-accounts and dimension model is genuinely identity-mapped from what requires active reconciliation after upgrade
Explain the DimensionAttribute / DimensionAttributeValue / default-dimension machinery and what survives the data upgrade
Identify why account structures and advanced rules must be retested rather than trusted after upgrade
Design a dimension clean-up strategy that exploits the upgrade as the right moment
Trace the data-upgrade path for the ledger, chart of accounts, fiscal calendars and dimensions
Introduction
AX 2012 and D365 Finance & Operations share a common financial architecture. The ledger, chart of accounts, main accounts, account structures, advanced rules, financial dimensions, dimension sets, and fiscal calendars all exist on both sides under the same names and broadly the same semantics.
The ledger and chart of accounts: what is genuinely identity-mapped
The AX 2012 ledger record (Ledger table, configured through General ledger > Setup > Ledger) holds four attributes: the chart of accounts, the accounting currency, the reporting currency (optional), and the fiscal calendar. All four carry forward to D365 under the same object names and the same assignment to legal entities.
Financial dimensions and the DimensionAttribute framework
AX 2012's financial-dimension framework is built on a set of tables that store dimension definitions, values, and combinations:
Account structures and advanced rules: why retesting is mandatory
Account structures define the valid combinations of main account and financial dimensions. Advanced rules extend those structures with conditional logic — for example, "if the main account is in the 6xxxxx range, require the Project dimension." Both carry forward by name and configuration, and the data upgrade migrates them intact.
Fiscal calendars and ledger calendars
AX 2012 fiscal calendars (FiscalCalendar, FiscalCalendarYear, FiscalCalendarPeriod) define period boundaries. Ledger calendars attach those calendars to a specific ledger and carry period status (Open, On hold, Closed, Permanently closed). Both carry forward unchanged.
The data-upgrade path: artefact by artefact
The following table summarises the upgrade treatment for each artefact covered in this chapter and maps it to the canonical migration wave.
Reconciliation: proving the upgrade worked
The reconciliation for the finance foundation is not a trial-balance check — that comes later, in Wave 7 when GL opening balances are loaded or validated. The Wave 1 reconciliation proves that the configuration itself is intact and will produce correct postings.
Knowledge check
Summary
The AX 2012 finance core — ledger, chart of accounts, main accounts, financial dimensions, account structures, advanced rules and fiscal calendars — is genuinely identity-mapped in the upgrade. Microsoft's data-upgrade tooling carries it forward under the same names and the same relationships.