Last updated: November 10, 2026
By ZapAI Team
Business Central Power BI reporting works best as one layer in a stack, not the whole stack. Microsoft Dynamics 365 Business Central ships with built-in reports, Word and Excel layouts, analysis mode, financial reporting and nine Microsoft Power BI apps. Power BI earns its license when you need trends over several years, views across more than one company, or data from systems outside the ERP like CRM, payroll or e-commerce. Native mirroring to Microsoft Fabric is a production-ready preview as of November 2026.
Business Central connects to Power BI through Microsoft’s connector, API pages and nine free template apps for finance, sales, purchasing, inventory, projects and manufacturing. Each app needs Power BI Pro or capacity, works per company, and refreshes from a read-only database replica.
Most guides on this topic list features. Fine. But the questions controllers actually ask us are narrower. Which report belongs where? Who needs Pro? Why did last night’s refresh fail? And when is Power BI simply too much tool for a 12-person finance team that just wants a clean income statement on the fifth working day of every month?
That’s what this guide answers. Every product fact below, from app names and license prices to refresh limits and preview labels, was checked against Microsoft Learn or microsoft.com during the first ten days of November 2026. We won’t repeat the general case for dashboards, which our post on how Power BI helps businesses make better decisions already makes. Business Central specifics only.
What Reporting Options Does Business Central Have?
Six, roughly. Built-in reports with Word, Excel or RDLC layouts, analysis mode on list pages, Open in Excel, financial reporting, embedded Power BI reports from Microsoft’s apps, and your own Power BI models. Microsoft’s analytics and reporting overview also lists Fabric mirroring and API extraction for data warehouses.
| Tool | Best for | Who builds it | Extra license |
|---|---|---|---|
| Built-in reports and layouts | Invoices, statements, aging, printed or PDF output | Power users, partners for RDLC | None |
| Analysis mode | Quick pivots on ledger entries and lists | Any user with permission | None |
| Open in Excel | One-off checks, what-if work | Anyone | None |
| Financial reporting | Income statement, balance sheet, budget vs actual | Controller or accountant | None |
| Microsoft Power BI apps | KPIs and trends by functional area | Admin installs, Microsoft maintains | Power BI Pro or capacity |
| Custom Power BI models | Cross-company, cross-system, custom KPIs | Analyst or partner | Power BI Pro, PPU or capacity |
Notice the last column. Four of six tools cost nothing beyond the Business Central license you already pay for, which our Business Central pricing guide breaks down. Start there.
When Are Built-In Reports, Layouts and Analysis Mode Enough?
Usually, for operational reports, documents and quick questions. Business Central has more than 300 built-in reports, layouts you can change without a developer, and analysis mode for pivoting list data on screen without exporting a single row to Excel first. A bookkeeper rarely needs more.
Reports and layouts
Every report runs through a layout. Microsoft’s report and document layouts overview lists four types. Word, Excel, RDLC and External. Each fits a different job.
- Word layouts suit customer-facing documents and email bodies. Email layouts must be Word.
- Composite Word layouts split a report into a body, a reusable theme and a reusable header and footer.
- Excel layouts use formulas, PivotTables and PivotCharts.
- RDLC layouts need SQL Server Report Builder or Visual Studio.
- External layouts come from partners.
One catch. You can’t edit a layout that ships inside an extension, so you copy it into a user-defined layout and change the copy, which also means your changes survive when Microsoft or an app publisher updates the original.
Analysis mode
Analysis mode is the most underused tool in Business Central. Open almost any list, like Customer Ledger Entries, switch it on, then group, filter and pivot. Microsoft’s data analysis documentation covers the details. A few matter to finance.
- Users need the DATA ANALYSIS – EXEC permission set.
- Views are private. Share links instead.
- Bookmarks to views arrived in 2026 release wave 2.
- Dates follow the calendar year.
- The Chart of Accounts can’t use it.
- Above 100,000 rows, calculated fields don’t display, and an export to Excel needs filters first.
That calendar point trips people up. If your fiscal year starts in July, a quarterly pivot in analysis mode shows calendar quarters, the totals won’t match the board pack, and somebody in finance will spend an afternoon proving the data isn’t wrong. Use financial reporting or Power BI for fiscal periods.
What Does Financial Reporting Do That Power BI Doesn’t?
It produces statements straight from the general ledger, inside Business Central, with no extra license. Row definitions say what to calculate. Column definitions say which data to use. Controllers own it.
Longtime NAV users still call this feature account schedules. Microsoft’s guide to building financial reports explains the model, where each report pairs one row definition with one column definition and every cell applies the row’s formula to the column’s data. A column definition holds up to 15 columns. Enough for twelve months, a total and two comparisons.
Some details matter before month-end.
- Sample reports need adjusting to your accounts, categories and dimensions.
- Definitions aren’t versioned. Export first.
- Draft and Retired statuses keep half-finished reports out of circulation.
- Reports can feed an Excel workbook template you design once and refresh monthly.
- Statistical accounts add headcount or square footage.
- Additional reporting currency works too.
Our view is simple. If the output is a financial statement your auditor reads, build it in financial reporting first. Power BI is better at trends, drill-down and blending other data. It’s worse at being the one signed-off P&L.
What Are the Business Central Power BI Apps?
They’re nine Microsoft-built Power BI template apps, one per functional area, each with a semantic model, reports and KPIs. The connector side comes preinstalled in Business Central. You install the Power BI side from Microsoft Marketplace, for version 27.0 and later.
Microsoft’s Power BI apps by functional area page, updated November 3, 2026, lists the current set.
| App | Examples of included reports |
|---|---|
| Finance | Financial Overview, Income Statement, Balance Sheet, Budget Comparison, EBITDA, aged receivables and payables with back dating |
| Sales | Sales Overview, Sales by Customer, Actual vs. Budget, Sales Forecasting, Customer Retention |
| Purchasing | Purchases Overview, Purchases by Vendor, Vendor Quality Analysis, Purchase Forecasting |
| Inventory | Inventory Overview, Item Availability, Inventory by Lot, Bin Contents |
| Inventory Valuation | Valuation Overview, by item and by location |
| Projects | Project Profitability, Performance to Budget, Project Timeline |
| Manufacturing | Work Center Load, Consumption Variance, Production Scrap, Production Order WIP |
| Subscription Billing | Revenue Analysis, Churn Analysis, Customer and Vendor Deferrals |
| Sustainability | CO2e Analysis, Emissions by Category and Scope |
Older Dynamics 365 Business Central Finance, Sales and CRM apps on Marketplace are obsolete. So is Intelligent Cloud Insights. Replace them.
How installation works
Two parts, both required. Per Microsoft’s install guide for the Power BI apps, the connector app holds the APIs, setup pages and embed pages, the template app holds the semantic model and reports, and the Connect to Power BI assisted setup then walks you through calendar type, UTC offset, date range, work days and report mapping.
Three settings bite later. Reports default to fiscal calendar measures. The date table ends at your last accounting period, so if your budgets already run into next year you have to set the ending date by hand or the extra months won’t reach the date table. And dimensions only appear after the Update Dim. Set Entries job queue entry runs, which Microsoft suggests scheduling weekly or nightly.
Customization needs care too. Microsoft recommends keeping the template app workspace locked down and putting copies of reports in a separate workspace per company for embedding, so that a template update never overwrites the changes your analyst spent a week making. The .pbix source files are downloadable from version 26.2 or 27.0, depending on the app. Useful. You can study Microsoft’s star schemas and measures before building your own.
How Should Power BI Connect to Business Central Data?
Through API pages or queries, using the Dynamics 365 Business Central connector in Power BI. Microsoft recommends APIs over OData web services because they load faster and don’t break when someone changes a page. Reports read from a read-only replica.
OData gets blunt treatment on Microsoft’s page about enabling Power BI integration, which labels OData web services not recommended. Fields on UI pages change between updates, through Microsoft releases or extensions, and Business Central has no idea your report depends on them. An API page is a contract. A UI page isn’t.
Since February 2022, Power BI reports for Business Central online read from a secondary, read-only database replica. Good for performance. But custom API pages that write data while loading records can fail or slow a refresh, so developers should keep triggers like OnAfterGetRecord free of database writes and test each custom endpoint in a sandbox first.
Throughput has limits. Microsoft’s data extraction methods page cites around 2 MB per second per API call and a parallelism of five calls in Business Central online, which is plenty for a nightly refresh of yesterday’s changes but tight for a 100 GB initial load that Microsoft estimates can take up to a day.
Need a field the standard v2.0 APIs don’t expose? Have a developer build a custom API page or query. Don’t publish a UI page as OData because it’s quicker today.
Why Do Business Central Semantic Models Refresh Slowly or Fail?
Usually because the model loads more data than it needs, or a query runs past the server’s web service limit. Filter rows. Drop unused columns. Keep query folding intact. Then check your refresh limits.
Load performance is covered in Microsoft’s Power BI dataset guidance for Business Central. The connector translates Power Query steps into OData parameters, so a row filter becomes $filter and removing columns becomes $select. Joins can break that folding and pull everything client side. The familiar error about a connection being forcibly closed by the remote host means either a transient failure or a query that hit the server limit, and Microsoft’s advice is to retry the first and tune the second with filters, fewer columns or partitioning.
Then the Power BI side. Per Microsoft’s data refresh documentation, shared capacity, meaning ordinary Pro workspaces, allows up to eight scheduled refreshes a day, each finishing within two hours. Premium and Fabric capacities allow 48. And five hours.
Practical fixes we apply, in order.
- Set start and end date filters on the Power BI Connector Setup page for each Microsoft app.
- Remove unused columns. Ledger tables are wide.
- Filter on posting date in Power Query so the filter folds into the API call.
- Use incremental refresh for big ledgers.
- Send web service telemetry to Application Insights and filter on the Power BI user agent.
- Move heavy history to Fabric.
What Power BI Licenses Does a Business Central Team Need?
Power BI Pro for whoever installs, refreshes and views the Microsoft apps, or a Power BI Premium or Fabric capacity. A free Power BI license doesn’t work with the apps. Every viewer also needs a paid Business Central license.
Pricing comes from Microsoft’s Power BI pricing page, which lists Pro at $14 and Premium Per User at $24 per user per month, paid yearly, in November 2026. Those prices rose from $10 and $20 in April 2025. Microsoft 365 E5 and Office 365 E5 include Pro.
| Who | What they need for the Microsoft apps |
|---|---|
| Person installing the template app | Power BI Pro |
| Account that refreshes the model | Power BI Pro, plus Read permission on the source tables in Business Central |
| Report viewer, in Power BI or embedded in Business Central | Power BI Pro, or content on Premium or Fabric capacity |
| Every viewer | A paid Business Central license such as Essentials, Premium or Team Member |
Read that last row twice. A warehouse supervisor without a Business Central license can’t view these reports, even with Pro, so check the license list before anyone promises dashboards to the whole shop floor at the kickoff meeting.
Why free fails is answered in the Power BI apps FAQ. Template apps install from Marketplace into shared workspaces, and anything built under a free license has to live in the user’s personal workspace, which is why the free route works for your own embedded reports but not for the Microsoft apps. On capacity, free viewers only work on F64 and above. Smaller F SKUs still need Pro for every viewer. Our Fabric vs Power BI Premium comparison runs the break-even math, so we won’t repeat it.
How Do You Report Across Multiple Companies?
Not with the Microsoft apps alone. They work per company. You either consolidate inside Business Central, build a custom Power BI model that appends companies, or mirror several companies into Fabric.
Each app reports on one company, so a business with four companies installs four copies of each app, each in its own workspace, configured with its own environment and company parameters. Fine for local managers. Useless for a group CFO.
Three routes, then.
- Consolidation in Business Central. Microsoft’s company consolidation guide covers different charts of accounts, currencies, fiscal years and even separate environments through a free API. Eliminations stay manual.
- A custom Power BI model that pulls the same API from each company and appends them, with a company column and a mapped chart of accounts.
- Fabric mirroring, which supports several companies in one setup.
Our rule of thumb is that statutory consolidated statements belong in the consolidation company, where eliminations are posted and auditable, while management views across entities, like margin by product line across three subsidiaries, belong in Power BI. Don’t make Power BI do eliminations. It can. It shouldn’t.
Where Do Fabric and OneLake Fit for Business Central?
Once you outgrow API refreshes or need Business Central data next to other systems. Microsoft now offers native data mirroring from Business Central to Fabric, a production-ready preview in November 2026. The older bc2adls code sample is unsupported.
Setup is laid out in Microsoft’s Business Central data mirroring overview, updated October 29, 2026. You install the Microsoft Fabric Mirroring (Preview) extension, create an open mirrored database in a Fabric workspace, grant a Microsoft-provided service principal access, and pick companies and tables, after which Business Central sends an initial snapshot and then ongoing changes into OneLake as Delta Parquet.
- Up to 1,000 selected tables, standard and extension, if they pass export validation
- Several companies per environment
- Deletes sync too.
- Whole tables, not fields
- Same Entra tenant required
- Active Fabric capacity required
Cost is mostly capacity. Fabric’s mirroring documentation says replication compute is free and each capacity unit includes a terabyte of mirroring storage, while queries from SQL, Power BI or Spark bill as usual. So an F2 you already own can host it. Sources conflict on timing, though. Learn labels the feature a production-ready preview with supplemental terms, while a partner blog covering the FabCon announcement tied it to version 29.1 and reported a roadmap entry still marked in development. We’d pilot it. Not bet a board pack on it.
And bc2adls? Microsoft archived its GitHub repository in September 2023, and the extraction page above calls it unsupported. Community forks continue. Existing pipelines can keep running, but we wouldn’t start a new one there.
New to Fabric? Start with what Microsoft Fabric is, then decide where modeled tables live with our Fabric lakehouse vs warehouse guide.
Does Copilot in Power BI Help With Business Central Reports?
Somewhat, if your semantic model is clean and sits on paid Fabric F2 or Premium P1 capacity or higher. Pro or PPU alone doesn’t turn it on. Copilot reads a model. It won’t fix one.
Raw Business Central API tables add a wrinkle, because they carry cryptic field names, eight shortcut dimensions and posting logic that Copilot simply can’t guess from column headers. The Microsoft apps give it a head start, because their star schemas, documented KPIs and named measures already describe the business in terms a language model can map to a question from a sales manager. A homegrown model built straight off ledger entries doesn’t. Our guide to Copilot in Power BI covers setup, capacity cost and model preparation.
Which Tool Should You Use for Which Report?
Match the tool to the audience and the output. Documents and statements stay in Business Central. Quick questions go to analysis mode. Trends and cross-system views go to Power BI. Volume goes to Fabric.
| Report need | Best tool | Why |
|---|---|---|
| Invoices, statements, remittances | Word layout | Prints and emails cleanly |
| Monthly P&L and balance sheet | Financial reporting | GL-native, no license, auditable |
| Board pack in a fixed format | Financial reporting with Excel template | Same workbook every month |
| Who owes us what, by month | Analysis mode pivot | Two minutes, no build |
| Margin trends by customer and item | Power BI Sales app | Built, maintained, free to install |
| Inventory and WIP tracking | Inventory or Manufacturing app | Ready-made KPIs |
| Group view across companies | Custom Power BI model | Apps are per company |
| ERP plus CRM, payroll or e-commerce | Custom model, Fabric if large | Needs a shared data layer |
When Power BI is overkill
Sometimes it is. Say a single-company distributor with eight finance and ops users wants a monthly P&L, an AR aging and a sales-by-customer list. That’s an example, not a client. Financial reporting, built-in aging and one analysis view cover all three, and nobody needs Pro. In our experience Power BI starts paying for itself when someone asks why the numbers moved rather than what they are, or when the answer needs data from more than one system.
What Mistakes Do Teams Make With Business Central and Power BI?
Building on OData UI pages, loading every ledger row ever posted, ignoring dimension setup, and treating Power BI as the system of record for statements. Licensing surprises come close behind.
- Publishing UI pages as OData. It breaks later.
- No date filters. Refresh times out.
- Forgetting the Update Dim. Set Entries job, then wondering why dimension slicers are empty.
- Assuming everyone can view embedded reports.
- Customizing reports inside the template app workspace, then losing them on update.
- Comparing a fiscal-year Power BI report against a calendar-year analysis view and calling the data wrong.
- Rebuilding every legacy NAV report as a dashboard.
- Skipping G/L account categories and dimension design.
That last one starts during implementation, and our Business Central implementation guide covers where reporting fits in the plan. Coming from NAV? The NAV to Business Central migration guide explains which old reports to convert and which to retire.
What Does a Staged Reporting Plan Look Like by Company Size?
Start inside Business Central, add Microsoft’s Power BI apps once people ask for trends, and build custom models or Fabric only when several companies or systems demand it. Each stage should prove its value first.
This is ZapAI practice, not a Microsoft framework. Sizes are rough.
Stage 1, small single-company teams
- Map G/L account categories and dimensions.
- Build the P&L, balance sheet and budget comparison in financial reporting.
- Save analysis views for AR, AP and sales checks.
- Fix document layouts in Word.
- Skip Power BI for now.
Companies moving off QuickBooks usually land here first, and our QuickBooks to Business Central migration guide covers how much history to bring for year-over-year reports.
Stage 2, growing mid-market teams
- Install the Finance and Sales apps first.
- Add Inventory, Projects or Manufacturing when asked.
- License Pro for real viewers.
- Set date filters and the dimension job before the first refresh.
- Copy reports before customizing.
Stage 3, multi-company or multi-system groups
- Build a custom semantic model on API pages, or on mirrored data in Fabric.
- Keep statutory consolidation in Business Central.
- Add CRM, payroll or e-commerce data.
- Consider capacity as viewers grow.
Some groups at stage three are really asking a bigger question about their ERP, usually after the third subsidiary or the first overseas entity, and if that sounds familiar our Business Central vs Dynamics 365 Finance comparison is the honest next read.
What Could Change After Ignite 2026?
Possibly the Fabric mirroring status. Ignite runs November 17 to 20, 2026, in San Francisco. Treat this post’s preview labels and prices as a snapshot. Expect a refresh by late November.
We’ll check four things first. Whether mirroring reaches general availability, whether Power BI or Fabric prices move, whether the Microsoft apps gain cross-company support, and whether Copilot in Power BI changes its capacity floor for smaller tenants.
Wrapping Up
Most day-to-day reporting needs no Power BI at all. Financial reporting handles statements, analysis mode handles quick questions, and layouts handle documents. Microsoft’s nine Power BI apps add trends and KPIs for the price of Pro licenses. Custom models and Fabric mirroring are for groups with several companies, several systems, or a lot of history that the API route can no longer refresh inside a two-hour window.
ZapAI is a Microsoft Dynamics 365, Power Platform, Fabric and AI consulting firm in Irving, Texas, working with businesses across Dallas-Fort Worth and nationwide. Our Business Central consultants set up financial reports and dimensions, and our Power BI consulting team installs the apps, builds cross-company models and plans Fabric when it’s warranted. Not sure which stage you’re at? Talk to us about your Business Central reporting, and we’ll tell you honestly whether you need Power BI yet.
Questions Teams Ask About Business Central Reporting
Are the Business Central Power BI apps free?
Installing them costs nothing. Using them doesn’t. Installers, refresh accounts and viewers need Power BI Pro, or the reports must sit on Premium or Fabric capacity, and viewers also need a paid Business Central license.
Can I use a free Power BI license with Business Central?
Yes, for your own reports in a personal workspace. Not for the Microsoft Power BI apps. They install into shared workspaces, which the free license doesn’t support.
Should Power BI connect through API pages or OData?
API pages. Microsoft recommends them because they load faster and don’t break when a UI page changes. Use custom API pages or queries for fields the standard v2.0 APIs don’t expose.
Can one Power BI app report across several companies?
No. Each app works per company, so you install a copy per company. Cross-company views need consolidation in Business Central, a custom model, or Fabric mirroring.
Is Business Central mirroring to Fabric generally available?
Not as of November 10, 2026. Microsoft Learn labels it a production-ready preview under supplemental terms. It needs the Microsoft Fabric Mirroring (Preview) extension and an active Fabric capacity.
Do the Power BI apps work with Business Central on premises?
Microsoft says the apps are only available for online environments. On-premises customers can still build their own Power BI reports on Business Central data.
What replaced account schedules in Business Central?
Financial reporting, built from row definitions and column definitions. It still produces the Income Statement, Balance Sheet, Cash Flow and Retained Earnings reports, and it needs no extra license.