Data Studio procurement dashboards for supply chain teams

What does our procurement dashboard show leadership?

A one-page view of spend, savings and supplier health, with detail a click away. The procurement dashboard we built in Data Studio opens with total procurement spend, savings realized, active suppliers and average supplier lead time as headline figures.

Beneath them sit top suppliers by spend, spend by category and by country, a list of suppliers at risk, compliance incidents and approval status for open requisitions and purchase orders. Every chart shares the same date, category and business unit filters. Category managers can open the report already filtered to their categories, and finance can switch between committed spend from purchase orders and actual spend from invoices with a single control.

Which ERP and P2P exports does a spend report need?

Three core extracts, plus whatever risk data you hold. Purchase order lines give committed spend, category, buyer and requested dates. Invoice lines give actual spend and payment terms. The supplier master gives names, countries, status and parent company. These usually come from the ERP and from a procure-to-pay or sourcing suite such as SAP Ariba or Coupa, exported on a schedule.

The cleanup matters more than the charts. Supplier names are duplicated with small spelling differences, categories are coded inconsistently, and some spend arrives without a PO at all. We normalize suppliers to a parent, map spend to your category taxonomy and keep a non-PO spend flag, then load the result into BigQuery. Data Studio blends cannot do this; they join at most five sources on exact matches.

How is savings realized calculated?

As the difference between a baseline price and the price actually paid, multiplied by the volume bought at the new price. The argument is always about the baseline: last price paid, average of the last year, the first quote, or the budget.

We agree the method with procurement and finance, store negotiated savings separately from realized savings, and show the method on the page. Realized savings then come from invoice lines, not from the negotiation tracker, so the number is something the CFO can trace. Cost avoidance, such as a price increase that was refused, is tracked separately and never added to realized savings.

How do lead time and supplier risk show up?

Lead time is the gap between PO date and goods receipt, averaged per supplier and category. We show the average and the spread, because a supplier with a good average and wild variation still forces you to hold safety stock.

Suppliers at risk are flagged by rules you choose, for example single-source categories, lead time drift, open compliance incidents, a high share of spend with one supplier, or an external risk score if you subscribe to one. Each flag is a calculated field, so the list explains why a supplier is on it.

• Average and spread of lead time by supplier and category.
• Concentration: share of category spend with the top supplier.
• Open compliance incidents and their age.
• Suppliers flagged at risk, with the rule that triggered each flag.

Where do compliance incidents and approvals fit in a procurement dashboard?

They show whether the process is being followed, which is half of what procurement is accountable for. Compliance incidents, such as purchases outside contract, missing documentation or supplier audit findings, are logged with date, supplier and severity and shown as a trend.

Approval status lists requisitions and POs by stage, pending, approved or rejected, with how long each has waited. Long approval queues often explain lead time problems that look like supplier issues. Splitting lead time into internal approval days and supplier days shows which side of the gap needs attention, and approvers can be ranked by average wait so bottlenecks are named, not guessed.

How do you handle multiple currencies and countries?

With one reporting currency and a dated exchange rate table. Spend by country only makes sense if a euro invoice and a rupee invoice are converted at a known rate for the right month. We keep the rate table in BigQuery or a Google Sheet, show which rate applied, and let viewers switch between local and reporting currency with a parameter.

As a data studio agency with offices in India and the USA, we are used to spend that crosses borders. Scheduled delivery sends the monthly spend pack to leadership, and reports built in the Looker Studio years carry over unchanged, so you can extend what exists.