Xero
Microsoft deprecated the old Xero Power BI content pack on 28 May 2019. In 2026 a Xero reporting model needs a current third-party, custom or file-based route.
Xero to Power BI in 2026 →Power BI connector alternatives in 2026
Xero, QuickBooks and HubSpot can reach Power BI through local files, hosted connectors or warehouses, or custom API pipelines. Datplan is the local-file route: source data is prepared on Windows, then Power BI reads stable reporting files.
Reviewed and updated 5 September 2026
There is no best connector in isolation. Choose by refresh requirement, data location, source complexity and who will maintain the model. Use a live/hosted route for continuously available query access, a warehouse for central multi-source governance, custom API code for engineering control, or a file-based route when scheduled local reporting is sufficient.
Four practical architectures
| Architecture | Strength | Important trade-off |
|---|---|---|
| Manual exports | Lowest setup for one-off work | Repeated download, cleanup and version control. |
| Hosted/live connector | Continuously available endpoint and, for some products, DirectQuery | Another service processes or stores data and becomes part of the reporting dependency. |
| Cloud warehouse | Central governance, many sources and shared transformation | Additional infrastructure, data copies and administration. |
| Datplan local files | Visible scheduled source preparation with the source dataset retained locally | Power BI's first model and any Power BI Service bridge remain organisation-controlled tasks. |
| Custom API pipeline | Maximum engineering control | Your team owns authentication, pagination, rate limits, schema changes, monitoring and reconciliation. |
Current connector context
Microsoft deprecated the old Xero Power BI content pack on 28 May 2019. In 2026 a Xero reporting model needs a current third-party, custom or file-based route.
Xero to Power BI in 2026 →Microsoft states that the QuickBooks Online Power BI connector is not supported after March 2026. Existing models should be treated as migration projects, not redirected blindly.
QuickBooks migration route →Microsoft Power Query connector catalogue → Microsoft QuickBooks Online notice →
The part connectors do not solve
Moving data is only one stage. The model must still distinguish financial summaries, documents, lines, payments, CRM deals and activities.
Keep Financial Summary, Financial Activity, invoice headers, invoice lines and payments distinct so one-to-many joins do not inflate totals.
Reconciliation guide →Use provider-report financial summaries for statement KPIs and separate document, payment, ageing and inventory facts for drill-down.
Migration guide →Keep Deals and Activities at separate grains so activity rows do not repeat pipeline value.
Deal-value modelling guide →Datplan workflow
A visible handoff makes it easier to find the failing stage when a report is stale.
Accounting modelling
Fact and dimension tables are useful only when their grain and relationships are understood. The Datplan BI package includes semantic metadata and relationship guidance, while the final Power BI model remains under your control.
Accounting star-schema export →TallyPrime
TallyPrime support is in development and is not part of the current public Datplan release. The development page explains the planned data-pull and reporting-schema direction without presenting it as available today.
TallyPrime development page →Decision checklist
These questions make vendor comparisons more useful than a feature-count table.
If users need queries against a continuously available source, scheduled files may be the wrong architecture. If daily or periodic snapshots are sufficient, a file workflow can be simpler and easier to inspect.
Decide whether another vendor-hosted database is acceptable or whether the reporting copy should remain on organisation-controlled Windows storage until you deliberately publish it elsewhere.
A useful design makes the provider pull, transformed files and Power BI refresh separately observable. A single green dashboard is not enough if nobody can tell which upstream stage is stale.
Ask this before choosing visuals. Invoice headers, invoice lines, payments, statement balances, CRM deals and activities should not be treated as one universal fact table.
Choose a source report, period and reconciliation method before deployment. A faster connector does not compensate for a model that cannot explain why its headline value differs from the accounting source.
Keep enough documentation to rebuild source inputs, relationships and measures. The Xero and QuickBooks connector history is a practical reminder that reporting dependencies can change.
The Windows app is free to download and includes Datplan Demo data, so you can test sync, dashboards, reporting grains and exports first.