Finance Index
What procurement KPIs should a finance-led function track, and what goes on the CFO dashboard?
Reference guide to procurement kpis reporting, including request intake, purchasing controls, approval routing, vendor coordination, and finance visibility.
Track a small set that maps to control and efficiency: cycle time (request -> approval -> PO -> receipt), PO coverage (% of spend that's PO-backed where it should be), approval bottlenecks, match exception rate, requisition-to-PO conversion, spend under management, and committed-vs-budget-vs-actual by department. The CFO doesn't need twenty metrics - they need to see whether spend is controlled, where it's slowing, and whether commitments are tracking to budget.
At a Glance
| Aspect | Short Answer | Why It Matters |
|---|---|---|
| What procurement KPIs should | Track a small set that maps to control and efficiency: cycle time (request -> approval -> PO -> receipt), PO coverage (% of spend that's PO-backed where it should be), approval bottlenecks, match exception rate, requisition-to-PO conversion, spend under management, and committed-vs-budget-vs-actual. | Keeps evidence clear and reduces control risk. |
| Approval path | Break the lifecycle into its segments and measure each, because the aggregate hides where the delay actually is. | Reduces payment errors, timing issues, and reconciliation cleanup. |
| Spend control | Five things, each answering a question the CFO actually asks. | Reduces payment errors, timing issues, and reconciliation cleanup. |
| What KPIs should | Cycle time by stage, PO coverage, match exception rate, requisition-to-PO conversion and rejection rate, spend under management, committed-vs-budget-vs-actual, and approval bottleneck metrics. | Keeps spend tied to policy, ownership, and review. |
| Measure | PO-backed spend ÷ total spend (ideally limited to spend that *should* be PO-backed). | Keeps spend tied to policy, ownership, and review. |
How do I measure procurement cycle time - request to approval, approval to PO, PO to receipt?
Break the lifecycle into its segments and measure each, because the aggregate hides where the delay actually is. Request-to-approval exposes slow or bottlenecked approvers; approval-to-PO exposes a procurement processing backlog; PO-to-receipt exposes vendor lead times or receiving lag. Timestamp each stage transition (which happens automatically when the lifecycle runs in one system) and report median and outliers per segment. Targeting the worst segment beats chasing a blended number - a fast approval stage won't save you if approved requests sit unconverted for a week.
How do I build a monthly procurement dashboard for the CFO - what goes on it?
Five things, each answering a question the CFO actually asks. Committed-vs-budget-vs-actual by department (are we tracking to plan?). PO coverage and non-PO spend (is spend controlled?). Cycle time by stage (where are we slow?). Open commitments and aging POs (what's outstanding that affects close?). Exception and savings indicators (is the process clean and delivering value?). Keep it to one view, drillable to the underlying documents, sourced from live data rather than a monthly spreadsheet build - a dashboard that takes three days to assemble is stale before it's read.
What KPIs should a finance-led procurement function track?
Cycle time by stage, PO coverage, match exception rate, requisition-to-PO conversion and rejection rate, spend under management, committed-vs-budget-vs-actual, and approval bottleneck metrics. Track the few that map to control and efficiency, not a vanity dashboard.
How do I measure and report PO coverage / what percentage of spend is PO-backed?
PO-backed spend ÷ total spend (ideally limited to spend that *should* be PO-backed). Report it by category, since appropriate coverage differs sharply between goods and services - a blended number can mislead.
How do I report procurement's impact on the P&L - savings, avoidance, and working capital?
Tie negotiated savings and avoidance to budget lines that actually decline, and report terms/DPO improvements as working-capital impact. Procurement value is credible only when it shows up in the P&L or the budget, not just a claimed-savings tally.
How do I track approval cycle times and find bottleneck approvers?
Measure time-in-queue per approver and per stage; the approver consistently holding items longest is the bottleneck. A dashboard that shows who's sitting on what, with aging, turns this from anecdote into a managed metric.
How do I measure requisition-to-PO conversion and rejected request rates?
Track what share of approved requests convert to POs (and how fast) and what share are rejected and why. High rejection or slow conversion points to intake quality or a processing backlog - both fixable once visible.
How do I report spend by category, department, and vendor when data lives across systems?
Easiest when procurement and AP share one platform so the cut is a report, not an integration project; otherwise consolidate via the ERP or a BI layer with consistent coding. Fragmented data makes category reporting a recurring manual exercise.
What is a good purchase requisition approval time benchmark?
Mature teams target a small number of business days end to end (same-day for low-dollar); multi-week approvals are the signal that drives bypass. Anchor on your own trend and the point at which slowness causes maverick spend.
How do I track contract utilization and on-contract spend percentage?
Compare actual spend per contracted vendor against the contract's commitment/minimum, and report on-contract spend as a share of the category's total. Low on-contract percentage is contract leakage made visible.
How do I report committed vs budget vs actual in one view for budget owners?
Show four columns per budget line - budget, committed, actual (spent), and remaining (net of both) - sourced from one system that sees both commitments and invoices. The single-view requirement is why commitments and actuals need to live together.
What procurement metrics should go in the board deck?
A tight set: spend under management trend, PO coverage, maverick-spend reduction, realized savings/working-capital impact, and cycle-time improvement. The board wants direction and control, not operational detail.
Stampli perspective
Stampli surfaces procurement visibility from the same workflow data it already runs - no separate BI build. Procurement Dashboards give a real-time view of where requests and outcomes are stuck (by owner, type, and age) for bottleneck identification, and Procurement Reports provide exportable, audit-ready views of open POs (with remaining quantity/amount), requests pending routing, and lifecycle status, drillable to the source document. Budget Management tracks committed, spent, and remaining against budget lines in real time. Because requests, POs, receiving, budgets, and invoices share one platform, cycle time, coverage, and commitment metrics come from the operating data rather than reconciled exports.