Design the D365 chart of accounts, financial dimensions, account structures and ledger configuration for a SYSPRO estate where the finance modules are documented but the account-determination internals are not.
There is a specific discipline this module has to maintain, and it is worth stating before anything else.
D365 separates accounting identity into constructs that a mid-market source system usually blends.
The redesign starts with an extract, not a workshop — but the extract is not the design.
The most reliable way to get dimension design wrong is to derive it from the structure of the source account code. Those structural decisions were made under constraints that no longer apply, by people who may no longer be available, and they have drifted since.
SYSPRO estates typically enforce some validation on account usage — which codes are legitimate, which combinations are meaningful, which accounts are restricted. The target expresses that intent through account structures and advanced rules.
Accounting and reporting currency. Two slots. Establish which currency each company genuinely accounts in, and what the group reporting currency is. Where the estate has a third view — a management reporting currency, a parent-group currency, a historical presentation currency — place it deliberately.
The finance and posting notes name four mandatory discovery outputs. They are the deliverable of this module, and the posting crosswalk cannot start without them.
Finance design on a SYSPRO path is well-supported on structure and deliberately incomplete on determination.