How Sage X3's multi-ledger architecture — statutory, analytical and budget ledgers, legislation-driven configuration, multi-currency handling, intercompany accounting and consolidation across a multi-company Folder — maps onto D365's one-ledger-per-legal-entity model with posting layers, reporting currency, separate legal entities and the Consolidations module.
Sage X3's ledger architecture is more flexible than most mid-market ERPs acknowledge: a single folder can maintain multiple ledger types (statutory, analytical, budget), each configured with its own currency, calendar and analytical axis set. Legislation codes drive country-specific statutory behaviour at the company level.
The statutory ledger is the primary book of record per X3 company — the equivalent of a D365 primary ledger. It carries the local (statutory) currency, the fiscal calendar and the chart of accounts. Every posted transaction hits this ledger.
Sage X3 uses legislation codes to drive localised statutory behaviour at the company level. A legislation code configures:
Local currency — the statutory reporting currency of the company Group currency — the reporting currency of the parent for consolidation Reporting currency — an additional currency for management or regulatory purposes
Statutory and tax depreciation differ (different rates or methods) Local GAAP and group GAAP require different treatments for the same transaction Management accounting requires entries that should not appear in statutory books Regulatory requirements demand a separate set of adjustments
In X3, intercompany transactions between companies in the same folder are resolved through Intercompany Automatic Journals. When one company posts a transaction that affects another company, the Automatic Journal creates reciprocal entries in both companies using partner-specific Accounting Codes to determine the due-to/due-from accounts.
X3 consolidation within a multi-company folder is typically configuration-driven: the platform combines trial balances across companies, translates currencies where required and eliminates intercompany activity using configured rules.
X3 period close is controlled at the ledger or folder level: periods are opened and closed in sequence, controlling which periods accept postings. Year-end processing rolls balance-sheet balances forward and closes profit-and-loss accounts to retained earnings.
The ledger-regime translation from X3 to D365 is architecturally significant: X3's multi-ledger flexibility collapses into a single-ledger-per-legal-entity model where parallel accounting is expressed through mechanisms distributed across the platform rather than through named parallel books.