Before: Five entities, five trial balances exported to Excel, intercompany balances matched by email, and a consolidation workbook that only one person understands. Day six of the close, and the CFO is asking why revenue moved.
After: Entities post in one environment or feed one consolidation company, intercompany balances are reconciled during the month, and the controller reviews exceptions instead of rebuilding numbers. Business Central supports much of this process. It does not remove the need for close discipline.
Table of Contents
Key takeaways
The close slows down where data is re-keyed, not where it is calculated. Target export-and-paste steps first.
Business Central consolidation combines general ledger data from subsidiaries (business units) into a separate consolidated company. Microsoft documents that eliminations are entered manually and previewed before posting.
Intercompany and bank reconciliation done weekly removes the day-one backlog.
A shared chart of accounts and dimension structure matters more than any tool.
Automate in this order: master data, reconciliations, consolidation, then reporting.
Dynamics 365 Finance becomes relevant when the entity count, transaction volume, or consolidation rules outgrow Business Central.
Why does the multi-entity close take so long?
Most delays trace to four causes:
Inconsistent charts of accounts across acquired companies, so mapping is done by hand each month
Intercompany transactions recorded at different times or amounts in each entity
Spreadsheet consolidation with manual currency translation and eliminations
Late reconciliations for bank, subledger, and inventory
Fixing these is a process and data problem first. Software then locks the improvement in.
How does consolidation work in Business Central?
Microsoft describes consolidation as combining general ledger entries from two or more subsidiaries into a separate consolidated company, which is a container for consolidated data rather than a live operating company.
Key mechanics from the documentation:
Each subsidiary is set up as a business unit, and its chart of accounts can differ from the consolidated company's.
Business units can sit in different Business Central environments. Data moves by file export or through an API.
Exchange rates must be set up when a unit reports in a different currency.
Eliminations are entered as journal lines, previewed on a tentative trial balance, then posted.
The Consolidated Trial Balance report shows business unit totals, eliminations, and the consolidated result.
Note what this means: consolidation is supported, but elimination entries are not fully automatic out of the box. Partners often add ISV tools or Power BI layers for richer consolidation and reporting.
Which close tasks should you automate first?
| Close task | Automation approach | Effort | Impact |
|---|---|---|---|
| Bank reconciliation | Bank feeds and matching | Low | High |
| Master data alignment | Sync master data across companies | Low | High |
| Recurring journals and allocations | Recurring general journals, allocation accounts | Low | Medium |
| Intercompany | Intercompany postings and weekly matching | Medium | High |
| Consolidation | Business units, consolidation runs, eliminations journal | Medium | High |
| Management reporting | Power BI over Business Central | Medium | High |
| Accrual proposals | Copilot and agent assistance, with review | Medium | Medium |
A practical month-end close checklist
Searchers looking for a month-end close checklist want order and ownership. A workable sequence:
Day -5 to 0: Reconcile bank and credit cards; clear unmatched intercompany items; close purchase and sales cutoff.
Day 1: Post accruals, depreciation, and recurring journals; reconcile subledgers (AR, AP, inventory) to the general ledger.
Day 2: Lock periods in each entity; run intercompany matching report.
Day 3: Translate currencies, run consolidation, post eliminations.
Day 4: Review variances by entity and dimension; sign off.
Day 5: Publish the reporting pack.
Targets vary by company. Treat the day counts as a planning template, not a benchmark.
When Business Central is enough and when it is not
Business Central usually fits companies with a handful to a few dozen entities, moderate transaction volumes, and straightforward consolidation rules. Dynamics 365 Finance is worth evaluating when you need very high volumes, complex ownership structures, advanced intercompany workflows, or enterprise-scale financial reporting.
Read the comparison in Business Central vs Finance and Supply Chain and the overview of Dynamics 365 Finance reporting.
What should an implementation partner cover?
Chart of accounts and dimension redesign before migration
Entity structure decision: one company with dimensions, several companies, or several environments
Intercompany setup and testing
Consolidation design, including currency and elimination rules
Close calendar, task ownership, and controls (segregation of duties, approvals)
Reporting design in Power BI, with an audit trail to source entries
Common mistakes
Migrating a messy chart of accounts "as is"
Treating consolidation as a reporting task rather than a design decision
Automating before agreeing to close ownership
Ignoring audit requirements for journals created by automation
The final word
Financial close automation in Microsoft Dynamics 365 Business Central means standardizing the chart of accounts and dimensions, reconciling bank and intercompany balances continuously, and using the built-in consolidation feature to combine entities into a consolidated company. This automation shortens the close by eliminating the need for rework. Some steps, such as eliminations and judgment-based accruals, still need human review.
Why Choose Dynamics Square USA for Financial Close Automation?
Dynamics Square is a Microsoft Solutions Partner, founded in 2011, with 14+ years of experience delivering Microsoft Dynamics solutions. Our team of 150+ Microsoft Certified Consultants has supported 500+ implementation projects across the USA, UK, and Canada.
We help multi-entity businesses streamline financial close processes with Business Central through chart of accounts standardization, intercompany automation, consolidation setup, reconciliation workflows, and Power BI reporting. With the right implementation strategy, Dynamics Square USA helps reduce manual effort, improve financial visibility, and build a scalable financial management system.
Connect with our USA team to streamline your multi-entity financial close with Business Central.
Frequently Asked Questions
It is the use of software rules, integrations, and workflows to reduce manual steps in the period-end close, including reconciliations, journals, intercompany matching, consolidation, and reporting. Reviewers still approve exceptions and judgments, but they stop rebuilding data by hand.
Yes. Business Central consolidates general ledger data from multiple companies or environments into a consolidated company using business units, with currency translation and an eliminations journal. Eliminations are entered and previewed before posting, so plan review steps.
Results depend on your starting process, entity count, and data quality. Cutting rework from spreadsheets and late reconciliations commonly shortens a close, but no partner should promise a specific number of days before reviewing your environment.
Business Central includes intercompany functionality that posts matching entries between companies. Setup, partner mappings, and testing matter. Complex cross-border or high-volume intercompany scenarios may need ISV tools or Dynamics 365 Finance.
Consider it when transaction volumes, entity complexity, regulatory reporting, or global operations exceed what Business Central handles comfortably. A fit-gap and performance review should drive the decision, not company size alone.
