How the D365 ledger object, posting layers, currency and revaluation model, and consolidation companies replace LN's Financial Company / Group Company parallel-books approach and IMS-derived postings — with an honest account of what a posting layer cannot do and the real workarounds.
Part 1 of this domain resolved LN's financial coding block into D365 main accounts, financial dimensions, and account structures. This chapter picks up where that stopped: the ledger as a container, what happens to parallel accounting requirements that LN satisfied through its Financial Company and Group Company model, how currency and…
A D365 legal entity is linked to exactly one ledger. The ledger bundles four things: the chart of accounts, the fiscal calendar, the accounting currency, and an optional reporting currency.
LN's approach to parallel books for group-versus-statutory GAAP is not a single named feature; it is typically achieved either by carrying an extra GAAP-difference dimension or a set of mirror accounts inside one Financial Company, or by standing up a dedicated group-reporting Financial Company whose postings are derived through the…
Part 1 already established the accounting-currency and reporting-currency pair on the ledger. This unit goes one level deeper: transaction currency, rate types, and revaluation, and how they compare with LN's currency systems.
A fiscal calendar can be shared across legal entities or defined per entity, and — critically — period status is tracked per ledger, not globally. This means one legal entity can close October while another is still posting into it, exactly as an LN Financial Company's period status is independent of any other Financial Company's.
Part 1 introduced the basic mapping of an LN Group Company to a D365 consolidation legal entity. This unit goes deeper into how that consolidation actually gets populated and how elimination works, because the mechanism matters as much as the destination.
This is the single most reusable table in this chapter. Apply it whenever a requirement is framed as "we need to separate X" without yet naming the mechanism.
Consider a group with a Dutch parent (EUR, IFRS group reporting) and two subsidiaries that were previously separate LN Financial Companies rolling up into one Group Company: a UK entity (GBP, UK statutory GAAP) and a US entity (USD, US GAAP).
The D365 ledger — chart of accounts, fiscal calendar, accounting currency, and an optional reporting currency, bound to exactly one legal entity — replaces LN's Financial Company as the accounting container, and its currency and calendar choices should be treated as permanent from the moment real transactions post.