Business Central Power BI: Reports, Dashboards & Apps, Explained

What 'Business Central Power BI' actually means

Business Central online ships with built-in Power BI integration. BC maintains a read-only database replica (used since February 2022) that powers embedded reports, and it exposes operational data primarily through OData v4 API pages and queries consumed by the Microsoft Power BI connector. The two products are designed to work as a pair, not bolted together.

It helps to frame BC plus Power BI as a layered system rather than a single feature. Layer one is the embedded reports that appear inside BC as Role Center parts and list-page FactBoxes. Layer two is the Power BI service, where full interactive dashboards live and are shared. Layer three is Power BI Desktop, where you build custom semantic models and reports on top of the same OData feeds.

One vocabulary note: the keyword phrase 'Business Central content pack' is legacy. Microsoft replaced the old content packs with Power BI template apps (now just called 'Power BI apps'). The two terms refer to the same intent — a pre-built bundle of semantic model plus reports — so this guide uses 'Power BI apps' throughout.

How to connect Business Central to Power BI

For Business Central online, the fastest path is the assisted setup inside BC. Search for 'Set Up Power BI reports' or 'Connect to Power BI'. This guided flow verifies your licensing and deploys the default embedded reports. It is a one-time setup per environment.

To install a Power BI app, go to Microsoft AppSource, find the BC app for your functional area (Finance, Sales, Purchasing, Inventory, and so on), and install it. Authentication is OAuth2, and you should set the privacy level to Organizational so Power BI treats your BC tenant as an internal data source.

After install, you must configure two parameters on each semantic model in the Power BI service: Environment and Company. Company is case-sensitive — a mismatch silently returns no data. The assisted setup also asks for Calendar Type (Fiscal is the default; Standard and Weekly 445/454/544 are available), UTC offset (tied to your BC time zone), Date Table Range, and Work Days.

In Power BI Desktop, the manual path is Get Data, then Online Services, then 'Dynamics 365 Business Central'. The Navigator exposes Environments, then Companies, then the available endpoints — API V2.0 (recommended), custom APIs, or legacy OData web services. Pick API V2.0 unless you have a specific reason not to. Apply date-based data filters early to limit the volume you pull — OData queries that scan years of history are the most common cause of slow refreshes.

1. 01
   Run assisted setup in Business Central

   In BC, search 'Set Up Power BI reports' or 'Connect to Power BI'. The guided flow verifies licensing and deploys default embedded reports. One-time per environment.

2. 02
   Install a Power BI app from AppSource

   Go to Microsoft AppSource, pick the BC app for your functional area, install it, authenticate with OAuth2, and set the privacy level to Organizational.

3. 03
   Set Environment and Company parameters

   After install, open the semantic model parameters in the Power BI service and set Environment and Company. Company is case-sensitive — a mismatch silently returns no data.

4. 04
   Configure calendar, UTC offset, and refresh

   Set Calendar Type (Fiscal default), UTC offset, Date Table Range, and Work Days in the assisted setup or on the Power BI Connector Setup page. Use 'Refresh now' to validate, then configure a scheduled refresh. For dimension data, ensure the BC job queue entry 'Update Dimension Set Entries' runs.

5. 05
   Connect manually in Power BI Desktop (optional)

   Get Data, Online Services, Dynamics 365 Business Central. In Navigator choose API V2.0 under the right Environment and Company.

Default Business Central Power BI reports by functional area

Microsoft publishes a dedicated BC Power BI app for each functional area. Each app bundles a semantic model, multiple reports, and embeddable pages. Knowing what ships out of the box stops you rebuilding reports that already exist.

The Finance app covers financial statements and operational finance: Financial Overview, Income Statement by Month, Balance Sheet by Month, Budget Comparison, Liquidity KPIs (current, quick, and cash ratios), Profitability, EBITDA, Average Collection Period, Aged Receivables and Aged Payables, and Late Payments. If your finance team asks for a cash-ratio trend, the report already exists.

The Sales app covers revenue analytics: Sales Overview, Daily Sales heatmaps, Moving Average and Moving Annual Total, Period-over-Period and Year-over-Year growth, Sales by Item, Customer, Salesperson, and Location, Actual vs Budget, Customer Retention, and Sales Forecasting.

Purchasing adds spend analytics (Purchases Overview, Period-over-Period and YoY, by Item, Vendor, Purchaser, and Location, Actual vs Budget, Vendor Quality, and Forecasting). Inventory adds availability and replenishment views (Overview, by Item and Location, Item Availability, Gross Requirement and Scheduled Receipt, and Bin Contents). Together these round out the supply-chain view.

Additional apps cover Inventory Valuation, Projects, Manufacturing, Subscription Billing, and Sustainability — each with its own model and report set. Before building anything custom, audit the app for your area.

Power BI licensing traps that catch SMEs

This is where SMEs lose money and time. Power BI Free (sometimes included with BC) only works in a personal workspace and cannot install or share BC template apps. If you want to install a BC app, share a report, or be a recipient of shared content, Power BI Pro is required.

The alternative to per-user Pro is Microsoft Fabric capacity (F-SKUs). Microsoft retired the old Power BI Premium per capacity P-SKUs in July 2024 for new purchases, with existing customers transitioned to Fabric capacities. Fabric makes sense only at scale — most SMEs are better off licensing Pro per user who needs to view or author.

Apps are per-company. Each company in your BC tenant that you want to report on needs its own semantic model configuration, and cross-company consolidation requires either a custom model or a multi-company template. Plan the company parameter up front, not after the first refresh fails.

Refresh frequency also bites. Free datasets refresh up to 8 times per day; Pro and Fabric-backed datasets up to 48 times per day. If your finance team wants near-real-time cash position, schedule design matters more than the license tier — but the tier sets the ceiling.

Finally, remember BC itself does not include Power BI Pro for everyone. BC Essentials and Premium grant BC entitlements, not Power BI Pro. Budget Power BI Pro as a separate line item for every user who will open, share, or author a report.

The KPIs every SME should track in Business Central Power BI

Most SMEs install the apps, then stare at the Overview page and move on. The value is in the KPIs behind the reports. The five that move the needle for an SME finance and operations team are: cash ratio and current ratio (liquidity), DSO and DPO (cycle time), and inventory turnover (working capital).

Liquidity: the Finance app ships current, quick, and cash ratios out of the box. Trend these monthly against your operating expense run-rate, not against an industry benchmark you found online.

Cycle time: Average Collection Period (DSO) and the equivalent on the payables side (DPO) come from the Aged Receivables and Aged Payables reports. A 5-day improvement in DSO on a mid-sized SME is real cash.

Working capital: inventory turnover and days-of-supply come from the Inventory app. Pair them with the Gross Requirement vs Scheduled Receipt view so purchasing decisions are made against actual demand, not gut feel.

The trap is defining too many KPIs. Pick the three to five that map to this quarter's operating priorities, pin them to a Role Center, and review them weekly. Power BI metrics lets you track these against targets without building a new report.

Building custom Business Central Power BI dashboards

When the default apps do not answer a specific question, build a custom report in Power BI Desktop on top of the same API V2.0 feeds. The discipline that separates a maintainable dashboard from a slow, brittle one is data-volume hygiene: filter at the source, not in the visual.

Start in Power BI Desktop with Get Data > Online Services > Dynamics 365 Business Central. Select only the API pages you need — pulling every endpoint 'just in case' is the most common cause of refresh timeouts. Apply date filters using the RangeStart and RangeEnd parameters (case-sensitive reserved names) so incremental refresh can partition history from the rolling window.

Model with star schema discipline. BC API pages give you flat transactional tables; resist the urge to report off them directly. Build a date table aligned to your fiscal calendar, a customer dimension, an item dimension, and a single fact table per process (sales, purchases, ledger). This keeps DAX measures simple and refreshes fast.

Publish to a workspace backed by the right capacity (Pro per user for small teams, Fabric F-SKU at scale). Pin the key visuals to a Role Center in BC so the dashboard lives where the users already work, not in a separate browser tab they forget to open.

Test in a sandbox environment first. BC sandbox tenants mirror production data and let you validate refresh timing, parameter behaviour, and report performance without risking the live semantic model.