ERP reporting disappoints for a structural reason, not a vendor one: an ERP's reports are transactional, because the ERP exists to process transactions. They show what happened to this order, this invoice, this works order, this stock item, and they show it accurately, with drill to the document. The questions a management team asks are analytical: how has margin by customer moved over three years, which product mix is shifting, what did the order book look like at each month end, how does throughput compare with plan, which customers are worth having. Those need history, joins and definitions, which is a model's job, not a report writer's. Sage 200, Business Central, NetSuite, SAP Business One, Epicor and SYSPRO all have this shape of gap, they all have a route to Power BI, and the fix is the same three steps in the same order for every one of them.
What every ERP gives you
| ERP | Built-in reporting tools | Analytical layer, if any | Power BI route |
|---|---|---|---|
| Sage 200 | Report Designer, Excel Integrated Reporting, workspaces | Older BI module on some versions | Sage 200 connector (Standard) or SQL (Professional); Sage 200 Reporting |
| Business Central | Standard reports, Financial Reports, analysis mode, Excel add-in | Nine free Microsoft Power BI apps, open-sourced Oct 2025 | Native connector; Business Central Reporting |
| NetSuite | Saved Searches, Report Builder, SuiteAnalytics Workbook | SuiteAnalytics Workbook; SuiteAnalytics Connect for external tools | SuiteAnalytics Connect (ODBC, separately licensed) or Saved Search web queries |
| SAP Business One | Crystal Reports, Query Manager, Report and Layout Manager | Dashboards and cockpit; SAP Analytics Cloud as an add-on | SQL Server or HANA direct, or SAP's connectors |
| Epicor Kinetic | Standard reports, BAQs, dashboards | Epicor Data Analytics | Database, data services or Epicor's BI |
| SYSPRO | Standard reports, SYSPRO Reporting Services | SYSPRO Analytics | SQL or the reporting API |
Source: each vendor's product documentation, read 21 September 2026. Business Central is the only one where the vendor's own analytical layer is free, native to Power BI and open source; the rest have an add-on or a licence step.
The right-hand column matters more than the middle one. Every ERP in the table can be read by Power BI; the difference is whether it's a native connector, a vendor connector, a database login or a separately licensed ODBC add-on (NetSuite's SuiteAnalytics Connect being the notable extra cost).
Why the built-in reports fall short
Three reasons, all structural:
No history. The ERP shows the current state. Aged debtors as at today; stock on hand now; open orders now. It can often run a report retrospectively (Sage 200 and Business Central can, for ageing), but a trend across thirty-six month-ends on one chart needs the snapshots stored, and the ERP doesn't store them for you.
One module at a time. The sales report knows about sales. The stock report knows about stock. "Margin by customer including the cost of the stock we sold them and the hours we booked to their jobs" crosses three modules and the report writer wasn't built to join them with a calendar and a customer dimension.
Definitions live in people. "Active customer", "on time", "gross margin" mean what the person running the report decides they mean that day. Six people, six reports, six numbers (Six Reports, Six Different Revenue Numbers). A semantic model writes the definition once and every report inherits it.
None of this is a criticism of the ERP. It's doing its job. The analytical job is a different job.
The three fixes, in order
1. Use what's already there. Financial Reports in Business Central, Excel Integrated Reporting in Sage 200, SuiteAnalytics Workbook in NetSuite, Crystal layouts in SAP B1. And for Business Central, install the free Power BI apps before doing anything else. A surprising share of "we need BI" is "nobody set up the reporting tool we already pay for". This step costs a few days of a partner's or an in-house person's time.
2. Build the semantic model on the ERP. One model, over the transaction tables (not the reports), with the definitions written once, a calendar, the dimensions (customer, item, department, site), and a reconciliation page that ties the model to the ERP's trial balance and its stock valuation on every refresh. Store the month-end snapshots from day one, even before anyone asks for a trend, because in six months they will. This is a single-source build, and it's the shape of the First Report: one system, one report answering one written question, the headline figure reconciled to the ERP to the penny, £1,950 fixed, ten working days. The first report is usually one of: aged debtors with owners and trend, margin by customer and product, the stock reorder and write-off list, or on-time-in-full and order book.
3. Join the second system. The CRM, the web shop, the service desk, the timesheets. Only after the ERP model reconciles, because a join between a trusted source and an untrusted one produces an untrusted result. Each join is a shared key, a second reconciliation and a Reporting Sprint.
Doing step three before step two is the most common way ERP reporting projects fail: a lot of money spent joining systems, none of whose numbers tie to anything.
Changing ERP? Plan the reporting before you choose
An ERP change is the one moment the reporting question can be settled cheaply, and it's usually left until after go-live, when the first month-end in the new system arrives and nobody can produce the board pack. Five things to settle before you sign:
- List the numbers leadership needs, then check the new ERP holds each one at the right level of detail. Margin by customer needs cost of sales on the invoice line. Project profitability needs costs coded to the job. If the new system can't hold it, no report on top will fix that.
- Ask how reporting gets out, and what it costs. A native Power BI connector, an API, direct database access, or a separately licensed analytics add-on. Get the answer and its licence cost in writing from the vendor or partner, because it changes the total cost of the project.
- Decide what happens to the history. Most migrations move open items and balances, not years of transactions. The old system then sits on a support contract so someone can look things up. An archive that keeps the history queryable, reconciled and read-only lets you switch the old system off (see Switch Off the Legacy ERP, Keep the History and the legacy system archive).
- Run two month-ends in parallel. Produce the headline figures from both systems and reconcile them before the old one goes read-only. Differences found in month one are cheap. Differences found at year end aren't.
- Don't rebuild every old report. Use the change to cut to the reports people actually open. The rest can wait until someone asks for them, which is often never.
Settle these five and the new ERP's first board pack comes out on time, with numbers the board already recognises.
What this month has covered
This post closes a month of write-ups on the same theme, system by system and document by document. If you came here from a search about your ERP or your report, the map:
By system: Xero (Xero Reporting), QuickBooks Online (QuickBooks Online Reporting After the Power BI Connector Was Retired), Sage 50 (Sage 50 Reporting), Sage 200 (Sage 200 Reporting), Sage Intacct (How to Connect Sage Intacct to Power BI, and What to Model Once You Have), Business Central (Business Central Reporting), HubSpot (HubSpot Reporting), and every accounting route side by side (How to Connect Your Accounting Software to Power BI).
By document: aged debtors (The Aged Debtors Report), budget vs actual (Budget vs Actual), month-end (Month-End Reporting Checklist), KPI report (KPI Report Template), cash (Cash Flow Dashboard), margin (Gross Margin by Customer and Product), group reporting (Group Reporting for Multi-Entity Businesses), stock (Stock Report), manufacturing KPIs (Manufacturing KPI Dashboard), and the CEO page (The CEO Dashboard).
And for the leadership questions around all of it: why you can't see all your numbers in one place, a one-page data strategy, ChatGPT, Claude or Copilot, whether Microsoft 365 Copilot is worth it and an AI policy for a small business.
Power BI Pro is £10.80 per user per month on Microsoft's UK page as of September 2026, for each viewer, whichever ERP you're on.
Common questions
Why is ERP reporting so bad?
It isn't bad; it's transactional. ERP reports show what happened to individual documents, accurately, because processing documents is the ERP's job. Analytical questions (trends, cross-module joins, definitions applied consistently) need a model on top, which is a different job.
What are the best ERP reporting tools?
Start with the ones inside your ERP: Financial Reports and the free Power BI apps for Business Central, Excel Integrated Reporting for Sage 200, SuiteAnalytics Workbook for NetSuite, Crystal Reports for SAP Business One. Then a semantic model in Power BI for the analytical layer, reading the ERP's transaction tables.
Can Power BI connect to my ERP?
Business Central natively; Sage 200 through Sage's connector or SQL; NetSuite through SuiteAnalytics Connect (separately licensed) or Saved Search web queries; SAP Business One through its SQL Server or HANA database; Epicor and SYSPRO through their databases or APIs. All of them work; the cost and effort differ.
What should the first ERP report in Power BI be?
One question, one page, reconciled to the ERP: usually aged debtors with owners and a trend, margin by customer and product, the stock reorder and write-off list, or on-time-in-full with the order book. Pick the one the MD asks about most.
Why do our ERP reports and our Power BI reports disagree?
Usually posting date versus document date, a document type the model missed (credit notes, adjustments), a costing method handled differently, or a definition applied differently. A reconciliation page comparing the model to the ERP's trial balance and stock valuation on every refresh finds it.
Should we buy the ERP vendor's own BI add-on instead?
For Business Central, yes, it's free and native: install the Power BI apps first. For the others, evaluate the add-on against a Power BI model on three questions: does it join to systems outside the ERP, can people without an ERP licence read it, and do you own the model afterwards. The add-ons usually answer no to at least two.
What should we plan for reporting when we change ERP?
Five things, before you sign: the numbers leadership needs and whether the new ERP holds each at the right level of detail; how reporting gets out of it and what that costs; what happens to the history; two month-ends run in parallel and reconciled; and which old reports genuinely need rebuilding. Settled early, they cost days. Discovered after go-live, they cost months.
What happens to our old data when we move to a new ERP?
Usually only open items and balances migrate, and the old system is kept on a support contract so people can look things up. A read-only archive that keeps the full history queryable and reconciled lets you switch the old system off and stop paying for it.
How much does ERP reporting in Power BI cost?
Power BI Pro is £10.80 per viewer per month (Microsoft UK, September 2026), plus any vendor connector licence (NetSuite's SuiteAnalytics Connect is the notable one). A single-source First Report is £1,950 fixed; a Sage 200 Reporting Audit is £1,500; a second system joined is a Reporting Sprint at £9,500.