How your accounting software connects to Power BI depends entirely on which one it is, and the differences are large. Business Central has a native connector and nine free Microsoft Power BI apps. Sage 50 Accounts ships an ODBC driver and connects through the on-premises data gateway. Sage 200 connects through the Sage 200 Power BI connector on the Standard edition or straight to SQL Server on Professional. Sage Intacct connects through its web services API via a third-party connector or a staged extract. Xero has had no native Microsoft connector since 2019, and QuickBooks Online lost its native connector in August 2025, so both connect through third-party connectors, an export pipeline, or their APIs. Whichever route you take, the thing to check isn't the connection, it's whether the model's totals reconcile to the ledger's trial balance on every refresh, because a connected report that doesn't tie is worse than no report.
This is the hub post. Each system has its own longer write-up, linked from its row.
Every route, side by side
| System | Native Microsoft route? | How it connects | Cost shape | Refresh | The gotcha | Longer write-up |
|---|---|---|---|---|---|---|
| Business Central | Yes: native connector + 9 free Power BI apps (open-sourced Oct 2025) | Cloud to cloud, sign in with a BC user | No connector cost; Pro licences for installers, refreshers and viewers | 8/day Pro, 48/day capacity | Apps are module-shaped; your definitions may differ from Microsoft's | Business Central Reporting |
| Sage 50 Accounts | Via ODBC | Sage's ODBC driver + on-premises data gateway on a machine that sees the data | No connector cost; gateway is free | 8/day Pro | Driver bitness (often 32-bit), slow on big tables, gateway must stay on | Sage 50 Reporting |
| Sage 200 Standard | Via Sage's connector | Sage 200 Power BI connector reading the Sage 200 Web API | Included with Sage 200 Standard | 8/day Pro | Only what the API exposes; no direct SQL | Sage 200 Reporting |
| Sage 200 Professional | Via SQL | Direct read-only connection to the Sage 200 SQL database + gateway | No connector cost | 8/day Pro | IT has to allow a read-only login; model from transactions not reports | Sage 200 Reporting |
| Sage Intacct | No | Third-party connector (CData etc.) or staged extract via the web services API | Connector licence, or a small database | 8/day Pro; staging can keep snapshots | Credit notes join differently; measures must let the engine skip empty rows | How to Connect Sage Intacct to Power BI, and What to Model Once You Have |
| Xero | No (content pack deprecated 2019) | Third-party connector (CData, Dataddo, Connectorly, Windsor.ai, Coupler.io, Acterys), Power Query on the API, or a staged database | Subscription, or developer time | 8/day Pro plus the connector's schedule | OAuth token handling on the API route; no history unless you store it | Xero Reporting |
| QuickBooks Online | No (native connector retired Aug 2025) | Third-party connector, Power Automate export to SharePoint/OneDrive, or the API | Subscription, M365 flow, or developer time | 8/day Pro plus the route's schedule | Reports built on the old connector stopped refreshing; rebuild on a new route | QuickBooks Online Reporting After the Power BI Connector Was Retired |
| NetSuite | No | SuiteAnalytics Connect (ODBC/JDBC, separately licensed) or Saved Search web queries (no extra cost) | SuiteAnalytics Connect licence, or none | 8/day Pro | Connect licence is an add-on; Saved Searches need designing for Power BI | ERP Reporting |
Sources: Microsoft Learn (Business Central Power BI apps; Power Query connector list and the QuickBooks Online deprecation notice), Sage product documentation for Sage 50 ODBC and the Sage 200 connector, Sage Intacct and Xero developer documentation, NetSuite documentation, and the connector vendors' pages. All read 21 September 2026. Power BI Pro is £10.80 per user per month on Microsoft's UK page, paid yearly, excluding VAT, as of September 2026.
Three routes, in general
Across all of those, there are only three shapes of connection:
Direct. Power BI reads the system's database or API through a connector Microsoft or the vendor supplies. Business Central, Sage 200, Sage 50 via ODBC. Simplest, no subscription, but Power BI only sees the current state of the system.
Through a connector service. A third party handles authentication, paging and rate limits, and either presents the API as tables or copies the data somewhere Power BI reads. Xero, QuickBooks Online, Intacct, HubSpot. Fastest to get working without a developer, at a monthly cost, and a dependency.
Staged. Something (a flow, a script, an integration platform, a Fabric pipeline) copies the system's tables into a database or files on a schedule, and Power BI reads that. Works for every system. More moving parts, but the model reads a stable source, the refresh is a normal database refresh, and you can store the month-end snapshots the source system doesn't keep. This is the route I take for anything that has to survive the person who built it.
The right one depends on who maintains it afterwards. A connector service is maintained by the vendor. A direct connection is maintained by whoever owns the gateway or the login. A staged route is maintained by whoever owns the staging job. Name that person before choosing.
The one thing to check regardless of route
Whether the numbers tie.
Every route above will give you data that looks right. None of them will tell you whether it is. The check is a reconciliation page in the report: the model's totals (P&L by account, or trial balance by account, or the aged receivables total) next to the same figures read directly from the accounting system, for the same period, with the difference shown. Zero or it doesn't go to anyone.
The things that page catches, from experience: a document type the query missed (credit notes, adjustments, manual journals), a posting-date versus document-date mismatch, an entity or book filter, a currency, a dimension keyed on a name that changed, an API that pages and dropped the last page. Every one of those produces a report that's confidently wrong, and without the page nobody knows until the FD does.
It's also why every model I publish has that page, and why the First Report's second payment is only invoiced once the reconciliation ties: the check is the deliverable, not a nicety.
What should you do first?
- Find your system in the table and read its write-up. The route is usually obvious once you know the edition you're on.
- Decide who maintains the connection. Vendor, IT, or a named person. If the answer is nobody, choose the vendor route.
- Write down the one question the first report should answer. Not "a finance dashboard". "Which customers are overdue and who's chasing them." "Are we on budget by department." One question keeps the first build small enough to be reconciled properly.
- Build that one report with a reconciliation page. On one system, that's a First Report: £1,950 fixed, ten working days, published to your workspace, the headline figure reconciled to the ledger to the penny (see the First Report). Xero, Sage 50, Sage 200, QuickBooks Online and Business Central are all named on the page.
- Then add the second system, if there is one: the CRM, the job system, the timesheets. That's a Reporting Sprint, because a second source means a shared key, a second reconciliation and a real model.
If you're not sure which route or which question, the Setup Hour is an hour with your data for £195, and it usually settles both.
Common questions
Which accounting software connects to Power BI natively?
Business Central, with a native connector and nine free Microsoft Power BI apps. Sage 50 connects through its ODBC driver and Sage 200 through Sage's own connector or SQL, which are vendor routes rather than Microsoft ones. Xero, QuickBooks Online, Sage Intacct and NetSuite have no native Microsoft connector as of September 2026.
Can Xero connect to Power BI?
Yes, but not natively. Microsoft's Xero content pack was deprecated in 2019. Use a third-party connector (CData, Dataddo, Connectorly, Windsor.ai, Coupler.io, Acterys), Power Query against the Xero API, or a staged database.
Can QuickBooks Online connect to Power BI?
Yes, via a third-party connector, a Power Automate export to SharePoint or OneDrive, or the QuickBooks API. Microsoft's native connector was retired in August 2025 and reports built on it stopped refreshing.
Does Sage connect to Power BI?
Sage 50 Accounts through its ODBC driver and the on-premises data gateway. Sage 200 Standard through the Sage 200 Power BI connector (API); Sage 200 Professional usually directly to its SQL database. Sage Intacct through a third-party connector or a staged extract via its web services API.
How often can Power BI refresh from my accounting system?
Up to eight scheduled refreshes a day in a Pro workspace, forty-eight on Fabric or Premium capacity. Connector services and staging jobs add their own schedule, so the effective latency is the slower of the two.
What's the cheapest way to connect accounting software to Power BI?
The direct routes (Business Central connector, Sage ODBC or SQL) cost nothing beyond Power BI licences. For Xero and QuickBooks, an export pipeline in Power Automate is included with Microsoft 365 and needs no subscription, at the cost of working from exports rather than the full API.
How do I know the Power BI numbers are right?
A reconciliation page: the model's totals next to the accounting system's, for the same period, every refresh, difference shown. If it isn't zero, the model is wrong and gets fixed. Every report I build has that page and the First Report's final payment depends on it.