How Plex's banking, budgeting and multi-location financial analysis translate into D365 ledgers, fiscal calendars, period close, currency revaluation, consolidation companies and Financial Reporting — honestly stating what cannot be assumed about the Plex source.
Once the chart of accounts and dimension model are designed — the work of the previous chapter — the next layer is the ledger itself: the configuration that determines which currency every transaction records in, which fiscal calendar governs period boundaries, how periods open and close, and how multi-entity reporting is consolidated.
A ledger in D365 is the financial backbone of a legal entity. Each legal entity has exactly one ledger, and that ledger carries:
D365 fiscal calendars (FiscalCalendar and FiscalCalendarPeriod) define the period boundaries for the ledger. A calendar can use standard months, 4-4-5 weeks, 13 periods, or any custom period structure. Key design decisions:
Plex's period-close mechanics are not documented in any source available to this adapter. What the programme must discover:
Does the client transact in multiple currencies? How does Plex revalue open foreign-currency balances at period end? What gain/loss accounts does the current revaluation process use?
Plex's Budgeting module is confirmed to exist at a marketing level, but no schema, no budget-control model, and no field-level detail is published anywhere primary. D365 offers two budgeting layers:
Financial consolidation is required only if the topology decision produces multiple D365 legal entities. If all Plex plants sit inside one entity, consolidation is not needed — multi-site reporting is dimensional filtering, covered in the previous chapter.
If the topology produces multiple legal entities, transactions that cross entity boundaries — a plant in one entity supplying goods to a plant in another — require intercompany accounting. D365's intercompany setup requires:
Plex's banking/cash management module is confirmed at a marketing level. D365's Cash and bank management module covers:
The ledger, close, and consolidation layer sits on top of the chart of accounts and dimensions designed in the previous chapter. On this path, the design is driven primarily by understanding the D365 target and asking the right questions during Plex discovery, because the source-side documentation does not exist at a level that enables…