Business Central vs Dynamics GP vs QuickBooks Online for ERP & Core Accounting

For a company with 8 legal entities spanning the US and Canada, Business Central natively supports multi-entity financial consolidation through a dedicated consolidated company architecture. Each subsidiary is configured as a 'business unit' within a parent consolidated company, and Business Central can pull GL entries across entities even if they run in separate Business Central environments, use different charts of accounts, or transact in different currencies (USD and CAD in this buyer's case). Intercompany transactions are tracked through a built-in intercompany module that logs all posted intercompany sales, purchases, and journal entries between entities, supporting reconciliation before consolidation. However, the mechanism that produces consolidated financial statements is the 'Run Consolidation' batch job: a controller must explicitly trigger this job (or schedule it) to transfer subsidiary GL entries into the consolidated company before any consolidated P&L, balance sheet, or trial balance can be generated. The Consolidated Trial Balance reports are explicitly designed to be run after all consolidation steps are complete, meaning the output always reflects the state of the last consolidation run rather than live posted transactions. The Company Hub extension provides a cross-entity KPI dashboard that can be refreshed on demand, but it delivers financial KPI snapshots rather than full GAAP-compliant consolidated financial statements.

For a $180M company running 8 legal entities across the US and Canada, Dynamics GP offers two native paths toward consolidated financial statements, neither of which delivers the real-time, on-demand experience the buyer requires. The first path is the Intercompany Processing module: when using Intercompany Processing, users post transactions across companies and can print consolidated financial statements. However, this is a transaction-posting mechanism, not a live roll-up. The second and more common path is Management Reporter (the GP-standard reporting tool): Management Reporter provides real-time access to financial data and the ability to build and customize reports with minimal technical training, with support for GAAP compliance. In practice, though, if an organization develops a logical consolidation account code design, they can use Dynamics GP and Management Reporter to manage the consolidation process -- but this requires deliberate design work and a manually-initiated report generation step against a data mart, not a persistent live view. Critically, Dynamics GP on its own is not built to handle the complexity of multi-companies, and achieving real-time consolidated reporting across separate entities requires a third-party ISV add-on such as Binary Stream's Multi-Entity Management (MEM), which is sourced and licensed from a separate vendor. Furthermore, Microsoft announced GP 18.5 as the last release with major new features, with the product moving to routine maintenance with regulatory and security updates only, meaning no architectural improvements to consolidation are forthcoming.

For a company running 8 legal entities like yours, standard QuickBooks Online provides no native multi-entity consolidation at all. QuickBooks Online treats every company as a separate, isolated file with no built-in way to produce consolidated financial statements across entities. The real-time consolidation capability exists only in Intuit Enterprise Suite (IES), Intuit's separately licensed, higher-tier product above QBO Advanced. IES allows you to view consolidated, real-time KPI performance across all entities, covering profit and loss, sales, expenses, accounts receivable, and accounts payable. Within IES, the multi-entity hub delivers a live overview view on demand via a Refresh action. However, the consolidated statement workflow with intercompany eliminations has a material gap: you can run consolidated reports natively inside IES or use Spreadsheet Sync to work with the data in Excel or Google Sheets, and elimination adjustments are entered manually in the Spreadsheet Sync spreadsheet; those manual adjustments are not posted back to Intuit Enterprise Suite. This means that for a buyer who needs intercompany eliminations (which your 8-entity, 12-day-close scenario requires), the consolidated statements that flow back into the platform do not reflect the elimination entries: those live only in a spreadsheet outside IES.

For a controller at a $180M professional services and distribution company preparing for audited financials, Business Central's native Financial Reporting feature (formerly Account Schedules) provides genuine self-service report creation for financial statement-type output. The controller opens the Financial Reports page, chooses New, then builds custom row definitions (specifying G/L account ranges, formulas, and totaling types) and column definitions (period comparisons, budget-vs.-actual, percentage-of-budget) without IT involvement. Business Central lets users create custom reports using financial reporting; the controller can choose New, give the report a name and description, and then specify default settings including row definition, column definition, and analysis views. Reports can be viewed on-screen with drill-through to underlying GL entries, exported to PDF, or pushed to Excel templates. After setting up definitions, the Financial Reporting feature offers multiple ways to view reports: on-screen with drill-through to underlying numbers, as PDF documents, or as Excel files using a chosen template or layout. Excel layouts extend self-service further: controllers can create their own report layouts in Excel from scratch or based on existing layouts, and can include multiple worksheets, interactive elements, pivot tables, and slicers. Power BI integration is also available: Power BI retrieves Business Central data so users can build dashboards and reports, and provides a flexible alternative to reports built in Business Central, enabling drill-down, customization, and merging data from different companies. However, the native Financial Reporting feature is scoped to GL-based financial statements. For custom operational reports that span new data combinations or tables not already exposed in the standard reporting framework, report development requires defining the dataset and designing the layout using SQL Server Report Builder or Microsoft RDLC Report Designer, which requires AL coding in Visual Studio Code and developer involvement well beyond a controller's self-service reach.

For a controller at a company like yours running 8 legal entities, Dynamics GP offers several layered reporting tools. SmartList is included with GP and lets everyday users create real-time data queries for all master and transactional records, with the ability to add columns or shift column order without IT involvement. SmartList Designer, a free tool from Microsoft, extends this by letting users join tables to create SmartLists that cannot be built by simply adding fields to out-of-the-box SmartLists. For financial statements specifically, Management Reporter uses a familiar row-and-column structure similar to Excel and handles financial reporting such as cash flow, balance sheets, and income statements without IT assistance. However, SmartLists and custom SmartLists built with SmartList Designer do not cross companies out of the box, meaning your controller cannot build consolidated custom reports spanning all 8 entities using GP's native tools. Cross-company SmartList capability requires SmartList Builder from eOne Solutions, a separately purchased ISV add-on that enables multi-company SmartLists from a different vendor your organization would need to source and integrate independently. Beyond the reporting gap, new Dynamics GP subscription licenses can no longer be purchased as of April 2026, and product enhancements, regulatory and tax updates, and technical support end December 31, 2029, which is a material strategic risk for a buyer pursuing audited financials on a 12-month timeline.

For a controller at a company like yours with 8 legal entities seeking to build custom reports without IT help, QuickBooks Online Advanced includes a dedicated Custom Report Builder that is entirely self-service. The controller navigates to Reports > Custom reports, selects 'Create new report,' and chooses either a guided report creation wizard or a blank canvas to manually add, remove, and reorder data columns; apply filters by account, customer, or vendor; group and pivot data; and visualize results as charts. Reports can be saved, named, shared with other users, scheduled for automated email delivery, and exported to Excel, Google Sheets, PDF, or CSV without any IT or vendor involvement. However, the Custom Report Builder operates within a single QBO company file. Because each of your 8 legal entities requires its own separate QBO subscription, the tool cannot pull data across entity files: a consolidated custom P&L or balance sheet spanning all entities cannot be built natively in the report builder. The controller would need to use Spreadsheet Sync (which pushes QBO data into Excel) and manually assemble the multi-entity view outside the platform.

For a company like yours operating 8 legal entities across the US and Canada, Business Central addresses this requirement through two complementary mechanisms. First, each legal entity is configured as its own company within a shared Business Central environment, and administrators can standardize the core chart of accounts structure across all entities by replicating the same account numbering scheme; consolidation then maps each subsidiary's GL accounts to a parent consolidation company's COA for group reporting. Second, Business Central's dimension system serves as the segment layer: each company is configured with up to 2 global dimensions (always available as filters on reports, batch jobs, and ledger entries) and up to 8 shortcut dimensions (available as fields on journal and document lines), all set up per company via the General Ledger Setup page. Entity-specific sub-segments are handled by defining distinct dimension values per company, so a US entity can carry a 'State' dimension value set while a Canadian entity carries 'Province' values on the same dimension code. For intercompany transactions, Business Central's native intercompany setup requires each entity to map its own chart of accounts and dimensions to a shared intercompany COA; the intercompany dimensions are also automatically synchronized from a designated synchronization partner, so a consistent shared framework propagates across partners without manual re-entry.

For your 8 US and Canadian entities, the QuickBooks route that fits is Intuit Enterprise Suite, not standard QuickBooks Online, where each company file keeps its own isolated chart of accounts. In Enterprise Suite, the parent company administrator can set up a Shared Chart of Accounts and manage it for multiple related entities from a single interface. An AI-assisted setup recommends a standardized chart for multi-entity companies, including a shared chart across all or multiple child entities. The segment layer is Dimensions. You can nest up to five levels of sub-values. The help article describes two paths: adding a dimension for a single entity, or adding shared dimensions for multiple entities. That lets you keep shared group segments and add entity-specific sub-segments. A third-party source reports up to 20 custom dimensions, applied at the transaction line level including payables and receivables. This sits inside one multi-entity environment, which is compatible with your consolidation and eliminations steps.

For a company like yours with 8 legal entities, Dynamics GP uses a two-layer account structure. At installation, an administrator defines a system-wide 'account framework' that sets the maximum number of segments (up to 10) and maximum account length (up to 66 characters); this framework applies to all companies in your Dynamics GP system and represents the maximum length of your accounts, number of segments, and segment lengths. Within those bounds, an account format is the structure of each account in a particular company, covering the length of the accounts, the number of segments, and segment lengths; each company you set up can have a different account format, as long as it fits within the maximums you specified for the account framework. This means your 8 entities can share common segment positions (e.g., segment 1 = entity, segment 2 = natural account, segment 3 = department) while each entity uses its own segment values as sub-segments. An account segment is a portion of the account format that can be used to represent a specific aspect of a business; for example, accounts can be divided into segments that represent business locations, divisions, or profit centers. Additionally, the Analytical Accounting module lets you set up dimension codes and account classes that provide greater flexibility in analyzing transaction data beyond the base segment structure. However, this is not a single unified COA shared across entities: each entity maintains its own separate chart of accounts that must independently conform to the system framework. There is no true master COA object that all entities inherit from, which means account maintenance must be managed company by company and any cross-entity standardization is enforced by convention rather than by a shared record.