The short answer

Use Datplan to authorise and pull Xero data into local prepared tables, export the Basic BI package to a stable folder, and connect Power BI to those files. Create the first model manually using the supplied grain and relationship guidance. On later runs, Datplan updates the same files and Power BI refreshes from them.

Choose the Xero reporting grain before Power BI

The most important decision is not the chart colour or even the connector. It is what one row represents. A Financial Summary row represents an account at a reporting date; an Invoice Summary row represents an invoice or bill; an Invoice Line represents one item line; and a Payment row represents a settlement event.

Use Financial Summary for P&L and balance-sheet questions. Use Invoice Summary for invoice totals, due dates and outstanding balances. Use Invoice Lines for item and tracking analysis. Use Payments for cash-settlement timing. Treat Financial Activity as reconstructed activity rather than official journal parity.

Build the local Xero-to-Power BI workflow

  1. Authorise the correct Xero organisation. Complete the provider consent flow and confirm the tenant in Datplan.
  2. Run a standard sync. Check endpoint results, run notes and reconciliation output before exporting.
  3. Choose Basic first. A smaller curated table set is easier to model and audit than every transformed table.
  4. Export to a dedicated stable folder. Do not mix multiple clients or sources and do not rename files after connecting Power BI.
  5. Load files in Power BI. Follow the semantic description and only create relationships that preserve the intended one-to-many path.
  6. Build and verify measures. Compare the first headline figures with a detailed table and the source reporting period.

Refresh Datplan before Power BI

A file-based workflow has two separate refreshes. First Datplan must update the local reporting files successfully. Then Power BI must reread them. If the report is published to Power BI Service, there is a third stage: the service must reach the local or shared files through a separately configured Microsoft-supported route.

Use a schedule only after a manual end-to-end refresh has worked. Keep the PC, Windows session and export folder available, then review both the Datplan execution result and the Power BI refresh history.

Avoid four common Xero reporting mistakes

  • Do not treat invoice value as recognised revenue without checking the accounting basis and question.
  • Do not sum an invoice-header amount after joining it to multiple invoice lines.
  • Do not interpret reconstructed Financial Activity as complete official journals.
  • Do not combine files from separate Xero organisations in one refresh folder unless you have deliberately designed and validated a consolidation model.

When a local file workflow fits

It fits teams that use Windows, want source datasets stored locally, can manage a stable folder and accept a one-time Power BI modelling step. It is not a substitute for a native real-time connector, a fully managed shared cloud warehouse or automatic group consolidation.

Frequently asked questions

What is the simplest Datplan workflow from Xero to Power BI?

Authorise Xero, run and verify the Datplan sync, create a Basic BI package in a stable folder, connect Power BI to the prepared files, then build and validate the model once.

Which Xero table should I use for revenue?

Use Financial Summary and filter to the appropriate revenue section and reporting period. Invoice Summary represents invoice events and should not automatically be treated as accounting revenue.

Can Power BI Service read a file on my PC by itself?

Not by itself. A service refresh needs a Microsoft-supported path to the file, such as an appropriate gateway or accessible storage arrangement configured by the user.