Consolidations in Dynamics 365 Finance

For multi-entity groups, consolidated financial statements show the group as a single economic entity. F&O's Consolidation module handles much of this natively — collecting subsidiary data, translating currencies, aggregating to a consolidation company. For groups with simpler structures, F&O alone may suffice; for complex groups, dedicated consolidation platforms (OneStream, BPC, Tagetik, Anaplan) layer on top.

The architecture.

• Subsidiary legal entities — each with its own ledger.
• Consolidation company — a dedicated F&O legal entity for consolidated results.
• Consolidation account groups — the chart of accounts for consolidated reporting.
• Account mappings — subsidiary accounts to consolidation accounts.

The consolidation company doesn't operate transactional business — it's a reporting entity.

Consolidation methods.

• Purchase (acquisition) — full consolidation; subsidiary fully owned or majority-owned.
• Equity — for significant influence (typically 20–50%); single line "investment in associate."
• Proportional — for joint ventures.
• Pooling of interests — historical method.

Each method affects how subsidiary numbers flow into consolidated.

Currency translation. For multi-currency groups:

• Closing rate — balance sheet items.
• Average rate — P&L items.
• Historical rate — equity items.

Translation differences accumulate as Cumulative Translation Adjustment (CTA) in equity — IFRS / US GAAP requirement.

The consolidation process.

1. Subsidiary periodic closes complete.
2. Consolidation company runs the consolidation routine.
3. Subsidiary balances pulled (via direct database read in same tenant or file import across tenants).
4. Currency translation applied.
5. Account mapping applied.
6. Consolidation entries posted to consolidation company.

This is automated; the manual steps are typically the elimination journals (next).

Eliminations. Cross-entity transactions need elimination:

• Intercompany sales / COGS — reverse on both sides.
• Intercompany AR / AP — net to zero.
• Intercompany dividends — eliminate.
• Investment in subsidiary — eliminate against subsidiary equity.
• Unrealised intercompany profit in inventory — defer.
• Goodwill calculation — recognised at acquisition.

F&O can record elimination journals, but doesn't automate them — elimination rules are manual.

Intercompany reconciliation. Before eliminations:

• AR of Entity A toward Entity B = AP of Entity B toward Entity A.
• Sales of Entity A to Entity B = COGS of Entity B from Entity A.

If they don't match, the elimination won't net to zero; investigate.

Mature finance teams reconcile intercompany monthly as a pre-consolidation step.

Account mappings. Subsidiary accounts often differ from group:

• Subsidiary local chart for statutory reporting.
• Group consolidation chart for IFRS or US GAAP.
• Mapping rules per subsidiary.

The mapping is maintained per subsidiary; new accounts must be mapped or they go to a "unmapped" suspense.

Minority interest (non-controlling interest, NCI). For partially-owned subsidiaries:

• Subsidiary's profits split between parent's share and NCI.
• NCI shown as separate equity line.
• F&O can capture but elimination logic is manual.

Goodwill. Difference between acquisition cost and net assets acquired:

• Recognised on consolidation.
• Tested for impairment annually.
• Manual journal entries in consolidation company.

Reporting at consolidation.

• Consolidated trial balance.
• Consolidated P&L.
• Consolidated balance sheet.
• Consolidated cash flow statement — requires additional analysis.
• Notes and disclosures — for IFRS / GAAP reporting.

Cash flow at group level is the hardest — F&O has cash flow at entity level; group cash flow typically built in Excel or Power BI.

Comparison with dedicated consolidation tools.

• OneStream, BPC, Tagetik — purpose-built; full eliminations automation, multi-method support, disclosure management.
• F&O native — basic consolidation; manual eliminations; limited disclosure features.

For groups with fewer than 10 entities and simple intercompany flows, F&O native is sufficient. For groups with 50+ entities, complex eliminations, M&A activity, dedicated tools win.

Multi-tenant scenarios. When subsidiaries are on separate F&O tenants:

• File-based import for consolidation.
• More complex; longer cycle.
• Greater opportunity for reconciliation gaps.

Single-tenant multi-entity consolidation is significantly easier.

Common pitfalls.

• Manual eliminations not automated. Each cycle re-types the same eliminations; errors creep in.
• Account mapping drift. New subsidiary accounts unmapped; sit in suspense.
• Currency rate errors. Wrong rate applied; consolidation off by material amounts.
• No reconciliation discipline. Intercompany not reconciled before consolidation; eliminations imbalanced.
• Late close cascades. Subsidiary close delayed; consolidation delayed.

Operational rhythm.

• Monthly — consolidation cycle.
• Quarterly — full review with audit-level rigour.
• Year-end — audited consolidated financial statements.

For quarterly reporting companies (most public companies), the rhythm is rigorous; first 5 business days of next month is a typical target for monthly consolidation.

Strategic positioning. F&O consolidation is functional and improving each wave. For most multi-entity groups using F&O across all entities, it covers the core need. For complex groups with frequent M&A, multi-currency exposure, or sophisticated disclosure needs, augmenting with a dedicated consolidation platform is common. The decision: scope of complexity vs investment in tooling. F&O's strength is integration with the source data; dedicated tools' strength is the depth of consolidation features. Combined intelligently, the architecture serves both operational accuracy and reporting demands.