Procurement dashboard in Power BI: what to show

Published 25 October 2026 · 6 min read

A good procurement dashboard answers three or four questions a manager actually asks, on one screen, with numbers that do not need explaining. Most fail for the same reason: they are built on data that was never categorised, so every chart is either a supplier list or a GL code summary. This guide covers what to put on one, how to model it in Power BI, and what has to be true of the data first.

Start with the data, not the visuals

One table is enough to start: one row per invoice or PO line, with supplier, description, amount, date, business unit, and a category at Level 1, 2 and 3. If the category columns are missing, stop — no amount of DAX will fix it. Our guide on exporting spend from your ERP covers the extract.

Five visuals worth having

Spend by category. A bar chart of Level 1, drillable to Level 2 and 3. This is the page people open first.
Suppliers per category. Count of distinct suppliers by Level 2. High counts on commodity items are consolidation candidates.
Top suppliers. The top twenty by spend, with their share of total.
Trend. Monthly spend by Level 1, so a sudden change is visible.
The tail. How many suppliers account for the last 20% of spend. Usually a surprisingly large number.

Add a business-unit slicer and a date slicer. Resist adding more pages until people use these.

Modelling it in Power BI

A date table. Mark it as a date table and relate it to the spend date, so time intelligence works.
A category hierarchy. Level 1 › Level 2 › Level 3 as a hierarchy enables drill-down on every visual.
Simple measures. Total spend, distinct supplier count and share of total cover most of the five visuals.
A supplier dimension. Once duplicate names are merged, a separate supplier table keeps counts honest. See cleaning supplier master data.

The same model works in Tableau or Looker; only the vocabulary changes.

Common mistakes

Charting GL codes. They describe budgets, not purchases.
KPIs without a decision. If nobody will act when a number moves, remove it. See procurement KPIs that matter.
Refreshing the visuals but not the categories. New suppliers and items arrive uncategorised and quietly pile up in “Other”.

Keeping it fresh

A dashboard is only as current as its newest categorised line. Plan for a monthly refresh where new lines are categorised the same way as the old ones, otherwise trends compare different taxonomies and mean nothing.

How Structera helps

Structera produces the table the dashboard needs: every line with its Level 1, 2 and 3, as an Excel file Power BI can load directly. Monthly updates are categorised into the same taxonomy at half the rate. See how it works.