How M3's per-CONO chart of accounts, seven accounting dimensions, and FAM-driven accounting events translate into D365's shared chart of accounts, main account plus financial dimensions, account structures, and advanced rules.
M3's financial model rests on a simple but consequential design decision: the chart of accounts and its dimension structure belong to the Company (CONO). Each CONO is a self-contained accounting universe with its own account master, its own dimension slot semantics, and its own fiscal calendar.
M3's chart of accounts is owned per CONO. The account string is a concatenation of up to seven segments, configured per CONO at initial setup:
In D365 F&O the chart of accounts is a shared object: MainAccount records are defined once and then attached to one or more legal entities through LedgerChartOfAccounts. Each legal entity then has its own account structure (DimensionHierarchy) that defines which financial dimensions are required, optional, or forbidden for each range of…
The most detailed part of the finance modelling workstream is the per-CONO dimension semantics audit. For each CONO, the team must document what each dimension slot actually represents in the posted data, then produce a mapping to target D365 financial dimensions.
M3 supports a base (accounting) currency per CONO and a reporting currency for FX translation. D365 offers the same two slots on the ledger: an accounting currency and an optional reporting currency.
M3 closes a period per CONO through a sequence of sub-module cutoffs — AR (ARS), AP (APS), inventory (MMS/MWS), production (MFS), project (where applicable) — followed by allocations, inventory revaluation (CAS), currency revaluation, GL close, and inter-CONO eliminations.
The simplest way to learn the M3 finance migration is to practise decomposing a posted account string. The posted line in FGLEDG is not just an account number; it is a code string whose first code part is the natural account and whose remaining code parts carry the management dimensions the FAM function derived at posting time.
M3's financial model — a per-CONO chart with a seven-segment account string and FAM-driven dimension validation — translates into D365's shared chart of accounts, main accounts, financial dimensions, account structures, and advanced rules.