D365 Finance has native intercompany accounting that handles intercompany journals, purchase/sales orders, and project transactions. Setup requires defining intercompany relationships between legal entities and configuring due-to/due-from accounts. The main design decision is whether intercompany is triggered from the buying entity, the selling entity, or both — get this wrong and you create reconciliation nightmares that follow you into every period close.

Posting profiles control which ledger accounts transactions post to — for customers, vendors, inventory and fixed assets. They are the bridge between sub-ledgers and the general ledger. Get them wrong and your trial balance will never reconcile to your receivables or payables. They are notoriously easy to misconfigure during implementation and painful to fix in production. Map them carefully during design and validate every transaction type in UAT before go-live.

D365 Finance has a native budget control framework that can enforce hard or soft stops at the point of commitment — purchase orders, requisitions, journals. The design choice is granularity: control at department level, cost centre, or full account and dimension combination? The tighter you configure it, the more workflow exceptions you generate. Most organisations start with soft warnings and move to hard stops once finance teams trust the data.

D365 Finance ships with Financial Reporter (formerly Management Reporter) for statement-level reports and the Inquiries workspace for real-time ledger drill-down. For anything more complex — consolidated group reporting, rolling forecasts, board packs — most organisations export to Power BI or a dedicated EPM tool. Financial Reporter is adequate for statutory formats; it is not a substitute for a proper planning and analytics layer.