Procurement KPIs the board actually reads
Boards read three numbers from procurement: how much of total enterprise spend is under procurement's management, how much of the savings identified in sourcing actually reached the P&L as cash, and what procurement did to working capital through payment terms and early payment capture. Everything else a procurement team tracks – cycle times, PO counts, first-pass match rates, supplier scorecards – belongs in an operating review, and putting it in a board deck buries the three numbers the board came for.
Operational metrics don't survive the trip upstairs
A board allocates capital and judges management. A first-pass match rate says something real about an AP team's workload, but a director has no way to price it: is it good, what does it cost, what would improving it release? The metric asks the board to understand procurement's process before it can understand procurement's contribution, and no agenda gives you that much time.
The frustrating part is that most procurement functions already hold the data for all three board numbers. Spend under management is a query against the spend cube. Realized savings is a reconciliation between the savings tracker and the general ledger. Days payable outstanding and discount capture sit in the AP system. The failure is translation more than measurement: the same data gets reported as process health when the board is listening for financial outcomes.
Spend under management is the first number the board checks
Spend under management is the share of total enterprise spend that flows through procurement's sourcing, contracting, and controls. To a board it is a control question: how much of the company's cost base does management actually govern, and how much gets negotiated ad hoc by whoever raised the requisition. For a benchmark, Ardent Partners' 2025 "Metrics that Matter" research found that procurement teams now manage about 71% of total enterprise spend on average, the first time the figure has passed 70% in two decades of the firm's research. State your own percentage against that number, with the plan to close whatever distance remains.
At the operating level this metric usually gets reported in pieces: catalog adoption, PO compliance, maverick spend by category. Those are the levers. The board number is the sum – one percentage, benchmarked, trending in a direction you can explain.
Realized savings is the only savings number the board believes
Every procurement function reports savings, and boards have learned to discount the figure, because identified savings routinely fail to appear in the P&L: negotiated prices leak through off-contract purchases, volumes drift to non-preferred suppliers, and budget owners spend the difference before finance can harvest it. The board metric is the realization rate: of the savings procurement claimed, how much did finance actually find in the ledger or remove from a budget.
Reporting realized savings means reconciling with finance before the meeting, which is exactly why it earns credibility. A CPO who shows what was identified, what was realized, and where the remainder leaked will be trusted with the next sourcing mandate. The same standard applies when procurement asks for technology budget – how to measure automation ROI honestly covers that discipline.
Working capital impact puts procurement on the CFO's agenda
The third number is cash. The payment terms procurement negotiates, and AP's ability to execute them, show up directly in days payable outstanding and in early payment discounts captured or forfeited. A board watching interest rates and free cash flow reads DPO movement the way it reads margin movement.
Operationally, this metric hides inside invoice processing. An invoice stuck in a three-way-match exception queue misses its discount window no matter what terms were negotiated, and a supplier who gets paid erratically stops offering favorable terms at renewal. Exception volume also sets the ceiling on any terms strategy.
When one of the three numbers is weaker than you want, the constraint is usually the same layer of work: requisitions that stall before becoming POs, supplier master data errors, invoices that fail the match, off-contract spend nobody catches until quarter close. That exception-heavy layer, across the full source-to-pay cycle, is what Fragment automates – agents that reason across your existing ERP, portals, email, and spreadsheets the way an analyst would, with nothing ripped out or replaced and a human approving the calls. Before the next board cycle, it is worth mapping which of your three numbers is gated by exceptions; the business case for procurement automation shows how to frame that internally, and Fragment's workflow catalog or a short demo can show how the same team covers more of that ground.