Business Central numbers you can consolidate and defend

You cannot get one trusted, consolidated view across your Business Central companies because BC's built-in reporting works company by company and month-end Excel does not scale. A growing or acquisitive business ends up with numbers that will not agree across entities and a group figure nobody is sure they can defend. A governed model over Business Central turns that into one live, reconciled view.

Most teams that come to us are not short of reports. They have outgrown them.

Business Central runs the business well. But its reporting is shaped around one company at a time, and as you grow, acquire, or simply ask harder questions of the numbers, the gaps show. Finance rebuilds the month-end in Excel because the standard reports will not consolidate. Two reports show two different figures for the same thing. The group view exists only in a spreadsheet one person maintains, and would stall if they left.

If you moved from NAV to Business Central, you may have felt this sharply. The reporting that worked on the old system did not come across, and rebuilding it on Business Central is a different job with a different data path.

None of this means Business Central is the wrong system. It means the reporting layer on top of it has to be built deliberately, so the numbers reconcile and consolidate every time, not just in the month you last checked them.

For the plain-English version, talk to us about why Business Central numbers do not reconcile across companies.

The free Business Central Power BI apps are a genuinely good starting point, but they are template models scoped to standard BC schema and a single company's data, so you still need a governed build the moment you want to reconcile to your own finance-owned figures or see a consolidated view across companies. They get you started; they do not get you to a trusted group number.

Let us be fair to the free apps first, because they are better than most people expect.

What the free apps give you. Business Central ships free, embeddable Power BI template apps across nine functional areas, including Finance, Sales, Purchasing, Inventory and Projects, generally available from the BC 2024 release wave 2. The Finance app alone carries pre-built reports for the income statement, balance sheet, budget comparison, liquidity, profitability and aged receivables and payables. For a single company that wants a quick, tidy set of dashboards, they are a real head start, and where they fit, we will tell you to use them. The apps are free, but each user still needs a paid Power BI licence to work with them.

Where they stop. Each app is a template semantic model built on standard Business Central schema and one company's data. That means three things. It reports the metrics Microsoft defined, not the ones your finance team defines and defends. It does not reconcile to your finance-owned figure, because that figure was never built into it. And it does not consolidate across your companies, because it only ever sees one at a time. The moment your real question is what the group looks like and whether you can defend it, the templates run out of road.

A governed build starts where the free apps stop. It extends the model to your definitions, reconciles it to the number finance signs off, and consolidates your companies into one live view. Same platform, a very different level of trust. There is more on exactly where BC's built-in reporting stops below.

Business Central's built-in reporting is genuinely capable, Financial Reports over your chart of accounts, up to eight shortcut dimensions, and in-client Data Analysis mode, but it is built to report one company against standard schema, so it stops exactly where a growing or acquisitive business needs a live, governed, multi-company view. Those four seams are where a governed Power BI model earns its place.

Business Central is not short of reporting, and any honest page has to say so. Financial Reports, the feature account schedules became, builds your income statement, balance sheet and cash flow straight over the chart of accounts, with dimension filters, budget-versus-actual and drill-down to source, no coding needed. Dimensions and up to eight shortcut dimensions let finance slice by department, project or region. Data Analysis mode gives quick, in-client pivots for a fast fact-check. For everyday, single-company questions, that is often enough.

It runs out of road at four seams.

• Per-company shape. Business Central's default reporting works one company at a time. A group view is not a setting you switch on; it is a separate, deliberate mechanism, covered next. Until you build for it, the whole group lives in a spreadsheet.
• Beyond the templated apps. The free Power BI apps are template models on standard BC schema and one company's data. They report Microsoft's metrics, not the ones your finance team defines, and they are not reconciled back to the figure finance actually signs off.
• Dimensions across companies and over time. Eight shortcut dimensions are powerful inside one company. Rolling them up across companies that use different dimension codes, and keeping history straight when a cost centre is re-mapped, is exactly the logic templated reports do not carry.
• Governed, owned, not one-person-fragile. A lean team is acutely exposed to the single-spreadsheet-owner risk. A governed model with defined ownership, refresh and security is the run-state fix, so trustworthy reporting does not walk out of the door with one person.

Each seam is the same underlying point: the built-in tools were shaped to report one company against standard schema, and your real questions have grown past that. For the governed model applied to Business Central, see the Power BI build for Dynamics 365.

Business Central consolidates by mapping each subsidiary's accounts and dimensions into a separate consolidated company and eliminating intercompany entries, but that is a batch, accountant-run, trial-balance-level process, not a live group view. A governed Power BI model encodes that same mapping and those same eliminations once, so finance gets a live, reconciled group view instead of re-running the batch every month.

This is the strongest single reason a Business Central group builds a governed model, so it is worth being precise about how BC actually does it.

To combine companies, Business Central uses a consolidated company: a separate container, with no live trading of its own, that you transfer each subsidiary's general ledger entries into. To make that work, per subsidiary, you map each posting account to a consolidated account so companies with different charts of accounts roll up, set up currency translation where currencies differ, and eliminate the intercompany transactions so the group total is not overstated. Subsidiaries can even live in different BC environments or other systems. The output is the Consolidated Trial Balance.

That mechanism is correct, and it is a lot of careful accounting. But notice what it is: a batch run, driven by an accountant, that produces a trial-balance-level snapshot. It is not a live, dimension-rich view the board can self-serve, and every account and dimension mapping is a place two numbers can silently drift apart.

A governed Power BI model does that reconciliation once and keeps it. It encodes the account mapping, the currency translation and the intercompany eliminations into the model itself, so the group view is live, dimension-rich, and reconciles the same way every time, not re-derived by hand each month-end. That is the difference between a group figure you produce and a group figure you can defend on the spot.

For the consolidated Business Central model, built, see the Power BI build for Dynamics 365, or talk to us about consolidating your Business Central companies.

On Business Central online you cannot query the SQL database directly, so reporting reaches Power BI through Business Central's own APIs and OData and a read-only replica, not raw SQL. That is a BC-specific data path a generic Power BI shop gets wrong, and it is the single clearest reason to use a builder who knows Business Central rather than one who knows only Power BI.

If a supplier talks about pointing Power BI straight at the SQL database, they are describing a system that is not Business Central online.

The Business Central data path. BC online exposes its data through API pages and queries, the recommended, modern route, or OData web services, not through direct SQL. There is no direct SQL Server access on BC SaaS by design: querying the database directly would bypass Business Central's service tier, losing calculated fields and the permission model, and Microsoft does not guarantee the schema stays stable between releases. Since early 2022, BC also serves reporting from a read-only replica, so your dashboards do not compete with people doing their day job in the system. A BC-literate build is designed around all of that; a generic one trips over it.

How Business Central differs from Finance & Operations. This is where "we do Power BI on Dynamics" quietly stops being enough. Finance & Operations reaches analytics through a different, Dataverse-based path and consolidates legal entities. Business Central is per-environment and per-company, is fed primarily through its own BC APIs, and consolidates companies into a consolidated-company container. A BC reporting build is not the F&O pattern scaled down; it is a different data model that has to be handled on its own terms.

The Fabric moment. For richer analytics, Microsoft points Business Central customers towards Microsoft Fabric and its OneLake data lake. That path is real and evolving, and the right way to think about it is simple: the modernisation moment is when to put a governed, reconciled model in place, not when to lift the same fragile month-end onto a newer pipe. We build the governed Business Central model so it is ready to modernise onto Fabric when that fits you, rather than promising a specific pipeline as a finished, turnkey thing.

To talk through the data path and the Fabric moment for your estate, get in touch.

No. It is right-sized for a smaller business through a three-step ladder: a fixed-scope health-check first, then a build of only what the evidence says you need, then a managed run-state so a lean team with no BI staff is never left owning it alone. You climb one rung at a time, on the evidence, and you never commit further than the value you have already seen.

Two fears stall this conversation for a Business Central buyer. The first is whether a Power BI project is enterprise-sized overkill for you. The second is who owns it after it is built, when you have no BI team. Both have the same answer: you do not buy a big-bang programme. You climb a ladder scaled to a lean organisation.

1. Diagnose.

   A fixed-scope reporting health-check for Dynamics 365 tells you exactly where and why your Business Central reporting stops reconciling, and what it would take to fix, before you spend anything on the fix itself.

2. Build.

   If the evidence says fix it, the Power BI build for Dynamics 365 puts the governed, consolidated Business Central model in place, so the numbers reconcile and consolidate and keep doing both, built only to the scope the diagnosis justifies.

3. Run.

   Managed BI for Dynamics 365 keeps it running, so a team with no in-house BI staff is not left owning a model alone. This is the direct answer to who owns it after.

It is right-sized, fixed scope, with the cost shown before you commit. You never pay for a rung the evidence has not justified, and where you enter the ladder depends on what the diagnosis finds.

This product sits inside the full Power BI for Dynamics 365 programme.