Blog · Procurement and supply chain · Procurement
A procurement dashboard compares purchasing spend, contract coverage, and supplier exceptions on a reconciled basis. Build one from invoice lines and receipt records, with spreadsheet formulas, a worked layout, and checks that keep separate purchasing events from being counted twice.
A procurement dashboard brings reconciled spend, contract coverage, and supplier exceptions into one purchasing review. Start with the decisions category managers must make, then build separate invoice and receipt views that share site and supplier identifiers without multiplying their records.
For a US manufacturer, the opening questions might be: where did purchasing spend change, which purchases lack confirmed contract coverage, and which suppliers missed their delivery commitment? Those questions need different source records. One combined transaction total cannot answer all of them.
Write the reporting basis above the dashboard: posting period, included companies, USD amount definition, tax treatment, and extract date. For this example, use September 2026 posted purchasing amounts, including signed credits, under a finance-approved net-spend policy. Delivery performance uses purchase-order lines due during that month, assessed as of October 2, 2026.
Use the existing procurement KPI definitions to choose the measures. Dashboard construction is the next step: arranging those measures so an owner can find the underlying exception and act. Negotiated savings require a separate savings realized analysis; a falling spend total alone does not prove savings.
Keep document ID and line ID, supplier ID, category, site, posting date, signed amount, and the contract assessment. Match contracts by supplier, covered item or category, business unit, and applicable purchase date. A supplier's name appearing in a contract list is insufficient evidence that every purchase is covered.
Use three coverage values: Yes, No, and Unknown. Unknown means the assessment lacks evidence; it does not mean the purchase was approved or that the supplier breached an agreement. Preserve the relevant contract reference and review reason outside the compact example below.
Put these example invoice rows in a sheet named Spend, with headers in row 1 and columns A through E as shown. MRO means maintenance, repair, and operations supplies.
| Line ID | Site | Category | Net spend (USD) | Contract valid |
|---|---|---|---|---|
| I101-1 | Columbus | Packaging | 40,000 | Yes |
| I102-1 | Columbus | MRO | 15,000 | No |
| I103-1 | Dayton | Packaging | 25,000 | Yes |
| I104-1 | Dayton | MRO | 10,000 | Unknown |
| C104-1 | Dayton | MRO | -2,000 | Unknown |
| I105-1 | Columbus | Packaging | 12,000 | No |
Total net spend and confirmed contract-covered spend are:
=SUM(Spend!D2:D7)
=SUMIFS(Spend!D2:D7,Spend!E2:E7,"Yes")
Microsoft documents SUMIFS as adding values that meet multiple criteria. Add site or category criteria when building the corresponding dashboard view.
| Coverage assessment | Calculation from invoice rows | Net spend (USD) | Share of net spend |
|---|---|---|---|
| Confirmed covered | 40,000 + 25,000 | 65,000 | 65.0% |
| Confirmed not covered | 15,000 + 12,000 | 27,000 | 27.0% |
| Unknown | 10,000 - 2,000 | 8,000 | 8.0% |
| Total | 65,000 + 27,000 + 8,000 | 100,000 | 100.0% |
Divide each classification amount by SUM(Spend!D2:D7); display percentages to one decimal place. Keep this label as contract-covered spend, because a broader compliance assessment may also require approved buying channels and other conditions.
For the supplier-category-site arrangement behind the charts, use the procurement spend cube method. Retain the same amount basis in every view.
Do not join every receipt event directly to invoice amounts. A purchase-order line can have multiple receipts and invoices, which can repeat monetary values. Instead, assess each due order line once, using its receipt history and the approved on-time and in-full definitions.
For this example, the receipt export has been assessed into the following due-line table. On-time and in-full are independent pass flags from the source assessment; a combined pass requires both. Keep overdue open lines in the due population.
| PO line | Site | Supplier | On-time pass | In-full pass | Combined pass |
|---|---|---|---|---|---|
| P1 | Columbus | S1 | Yes | Yes | 1 |
| P2 | Columbus | S2 | No | Yes | 0 |
| P3 | Dayton | S1 | Yes | No | 0 |
| P4 | Dayton | S3 | No | No | 0 |
Place this table in Receipts, columns A through F. Enter the combined pass in F2 and fill down:
=IF(OR(D2="",E2=""),"Review",--AND(D2="Yes",E2="Yes"))
Once the missing-status review is clear, the combined pass rate is =SUM(F2:F5)/COUNTA(A2:A5): 1 / 4 = 25.0%. Exceptions are 4 - 1 = 3 lines. A line failing both conditions is still one exception.
The Dayton exception count is:
=COUNTIFS(Receipts!B2:B5,"Dayton",Receipts!F2:F5,0)
It returns 2. Microsoft's COUNTIFS documentation explains that all criteria must be met for a row to be counted. Validate the allowed status values before calculating; a blank or unexpected spelling needs review.
Covirage is not affiliated with Microsoft.
Use the top section for net spend, confirmed covered share, unknown spend, and delivery exceptions. Every headline needs its period and denominator. Avoid placing invoice spend and open commitments under an unlabeled total.
The middle section should compare category and site. Columbus spend is 40,000 + 15,000 + 12,000 = $67,000. Dayton spend is 25,000 + 10,000 - 2,000 = $33,000. Together they reproduce $100,000, making the site view a useful independent check.
Use the bottom section for records requiring action: document or order line, site, supplier, reason, accountable owner, and next review date. The Unknown Dayton purchases go to the contract administrator; the failed receipt lines go to supplier managers. A chart highlights the issue, but the source identifier makes follow-up possible.
The procurement dashboard template gives a neighboring layout reference. Keep this dashboard limited to the measures the current review actually uses.
Bring your purchasing export, contract assessment, and supplier receipt records with their control totals. Covirage maps the columns, its tools compute and check the comparisons, and the external AI model explains the result with every figure traced to its rows. Create a free Covirage account and bring a sample of your own export.
See Covirage for procurement teams for the purchasing context.
Match the update schedule to the purchasing review. A monthly spend review can use closed invoice periods, while supplier exceptions may need a more frequent file extract. Always display the extract date and distinguish incomplete periods from closed ones.
They can appear in separate views with clearly labeled measures. Purchase orders describe commitments, invoices describe recorded purchases, and receipts describe fulfillment. Adding their dollar amounts together counts different stages of the same transaction as additional spend.
A procurement operations lead can own the reporting process, with finance approving the spend basis and category managers owning actions. Contract administrators resolve coverage questions, while supplier managers investigate delivery exceptions. Assign responsibility for each unresolved row as well as each headline measure.