Ledger currencies, posting layers, parallel accounting, consolidation and the reporting stack — what genuinely changes
How AX 2012's ledger currencies, posting layers, parallel-accounting patterns, period-close process, consolidation, intercompany accounting and Management Reporter translate into D365 — the small number of areas in the finance model where the upgrade demands real design decisions rather than reconciliation alone.
What you will be able to do
Explain how AX 2012's accounting and reporting currencies map to D365's two-currency ledger model and what happens when a third currency requirement exists
Describe the ten posting layers in D365 and how AX 2012 posting-layer usage maps to them
State plainly that no general-ledger multi-book feature exists in finance and operations apps, and explain how parallel accounting requirements are met instead
Trace the period-close and year-end close process from AX 2012 to D365 and identify what must be re-validated
Distinguish what in AX 2012 consolidation and intercompany accounting is identity-mapped from what demands configuration reconciliation
Map Management Reporter definitions to D365 Financial Reporting and identify what the upgrade carries forward
Introduction
Part 1 of this domain established that the AX 2012 chart of accounts, financial dimensions and account structures are identity-mapped in the upgrade. This chapter covers the remainder of the finance model — currencies, posting layers, parallel accounting, period close, consolidation, intercompany accounting and the reporting stack — and…
Currencies and exchange rates: what carries forward
The AX 2012 ledger record holds an accounting currency (mandatory) and an optional reporting currency, maintained live on every transaction. D365 preserves this model exactly: a D365 ledger has exactly two configurable currencies — accounting and reporting — and both are effectively permanent once transactions exist.
Posting layers: ten, not three
AX 2012 R2 and R3 expose Current, Operations and Tax as posting layers in routine use. D365 exposes the same three plus seven Custom layers, for a total of ten posting layers.
Period close, year-end close and the close schedule
AX 2012 controls which periods are open for posting through ledger-calendar period status: Open, On hold, Closed or Permanently closed — per module, per legal entity. D365 uses identical status values and the same per-module, per-legal-entity granularity. The upgrade carries forward period status unchanged.
Consolidation and elimination
AX 2012 consolidation uses a consolidation company (a legal entity flagged for consolidation purposes) that combines balances from one or more source legal entities. Elimination rules remove intercompany activity. Both carry forward to D365 under the same object names.
Intercompany accounting
AX 2012 intercompany accounting — due-to/due-from accounts, intercompany journal setup, and automatic intercompany voucher creation — is identity-mapped to D365. The configuration carries forward.
The reporting stack: Management Reporter to Financial Reporting
AX 2012 uses Management Reporter for financial statement design — row definitions, column definitions and tree definitions. D365 renames this to Financial Reporting and the data upgrade migrates definitions forward.
The GL opening-balance treatment (Wave 7)
In an in-place upgrade (Mode A), GL history carries forward as part of the database upgrade — the GeneralJournalEntry and GeneralJournalAccountEntry tables are migrated with full transaction history. No separate GL opening-balance load is required.
Knowledge check
Summary
The AX 2012 ledger model — currencies, posting layers, year-end close, consolidation, intercompany and Financial Reporting — carries forward to D365 with remarkably little structural change. This is the same-vendor advantage at its strongest: the architecture did not change, and the upgrade tooling is designed to preserve it.