Number of maverick spend incidents KPI

Number of maverick spend incidents serves as a crucial performance indicator for organizations seeking to enhance operational efficiency and cost control.

High maverick spending can indicate poor compliance with procurement policies, leading to inflated costs and reduced ROI.

By tracking this metric, companies can identify areas for improvement in supplier management and purchasing processes.

A reduction in maverick spending directly contributes to better financial health and strategic alignment with budgetary goals.

Organizations that effectively manage this KPI can expect improved forecasting accuracy and enhanced data-driven decision-making capabilities.

Ultimately, this leads to more favorable business outcomes and a stronger bottom line.

How Number of maverick spend incidents Connects to Your Strategy

Number of maverick spend incidents sits in KPI Depot's Procurement KPI group, a large roster led by Supplier On-time Delivery Rate, Cost Savings per Purchase Order, and Total Cost of Ownership (TCO), followed by Procurement Policy Exception Rate, Contract Compliance Rate, Spend Under Management, Budget Adherence Rate, and Cost Reduction per Buyer. Within that priority order this KPI sits well down the list: a supporting compliance count rather than one of the group's headline cost or reliability metrics, and one that earns its place by explaining movements in the metrics above it.

Its balanced scorecard placement is internal process, which puts it in a leading role. It reports on the discipline of the buying process itself, and spend that bypasses procurement is spend nobody negotiated, so incidents here precede erosion in Cost Savings per Purchase Order and in Budget Adherence Rate rather than reporting on it. The group's own guidance treats the rate-form sibling in the same roster, Procurement Policy Exception Rate, as a leading indicator of compliance risk. The same reading applies to this count with one caveat that the rate does not share: it has no denominator, so it moves with transaction volume as well as with behaviour.

The tension worth watching first is with Spend Under Management. These two look like allies, and in intent they are, but they can move together for the wrong reason. Pulling tail spend into formal channels is what raises Spend Under Management, and it also drops previously invisible purchases in front of controls that can flag them. So the incident count can climb in the same quarter compliance genuinely improved, purely because coverage widened. Rising Spend Under Management alongside a rising incident count tells a very different story from a flat Spend Under Management alongside a rising count, and the pair has to be read together to tell them apart.

The second tension runs against Supplier On-time Delivery Rate, the group's top-priority metric. When the compliant route is slow, or a contracted supplier misses its dates, the operational pressure to buy around procurement is exactly what manufactures an incident here. A team measured hard on both will resolve the conflict in whichever direction is measured harder. Contract Compliance Rate is the metric in the group that separates the two cases: incidents concentrated in categories where a contract already exists point to indiscipline, while incidents in categories with no contracted supplier point to a sourcing gap procurement has not closed, which is a different problem with a different owner.

Measuring Number of maverick spend incidents in Practice

There is no table in any system called maverick spend. The count is assembled by running tests against transactions, and each test lives somewhere different: invoices in the payables file with no matching purchase order, purchase orders raised after the invoice date, spend with a supplier outside the contracted list in a category that has an active contract, card and expense transactions in categories that policy routes through procurement. That means the ERP purchase order and invoice tables, the contract or supplier master, and the card or expense platform all have to be joined, and the join needs a supplier identity that survives it. Duplicate supplier records are the usual failure point, because the same vendor set up a second time under a slightly different name turns off-contract spend into spend with a supplier that simply has no contract on file.

Settle the biggest fork before anything else: only spend a control can see is ever counted. If purchasing cards, expense claims, or a subsidiary running its own ERP sit outside the tests, purchases made there do not become incidents, they stay invisible. So this metric measures detection coverage at least as much as it measures buying behaviour. Write down which systems, entities, and categories are in scope, and treat any later change to that scope as a break in the series rather than as a change in performance. A control outage or a decommissioned integration will look like a compliance win.

Next decide the unit, because it changes the number by more than any behavioural improvement will. An incident can be a requisition, a purchase order, an invoice line, a payment, or a supplier relationship. One off-contract decision that produces a standing arrangement and a recurring monthly invoice is a single incident under a supplier-level definition and a long run of incidents under an invoice-level one. Neither is wrong, but a count that switches definitions between reporting periods, or between business units, is not a metric.

Thresholds and exemptions need to be explicit for the same reason. Most policies exempt purchases below a value threshold, and many carve out categories that cannot practically be routed through procurement: utilities, legal fees, regulated services, some travel. An unwritten exemption is where the metric quietly stops being comparable across units that interpret it differently. Split purchases deserve their own rule: several transactions each sitting under the approval threshold are individually compliant and collectively the violation, and a test that reads transactions one at a time will never see it. Look for repeat same-supplier, same-requester activity clustered just below a threshold.

Retrospective approval is the fork that decides whether the metric is honest. When a confirming purchase order is raised after the purchase, does the incident close? If it does, the metric ends up measuring whether paperwork was completed rather than whether the process was followed, and the quickest way to improve it becomes raising more retrospective orders. Keep retrospective approvals as their own category and report them beside the count. The same goes for cases closed as approved exceptions: an exception granted after the money was committed is not the same thing as an approval obtained before it, and folding the two together removes the only evidence that the control was bypassed.

Because this is a count with no denominator, it cannot be compared across periods or business units on its own. A unit that buys often in small amounts will produce more incidents than a unit that buys rarely in large amounts, even at a much better violation rate, and a growing business will show a rising count while behaviour holds steady. Normalize by transaction count or by spend value before any comparison, and expect seasonality, since budget cycle ends and unplanned demand both push off-process buying up with no change in policy or training.

Segment by category first, separating categories where a contracted alternative existed from those where none did, then by business unit, by value band, and by requester. If a handful of repeat requesters account for most of the count, that is an access, training, or system usability problem with a specific owner rather than a cultural one. The remaining traps are mundane and consistent: incidents that are effectively self-reported by the team measured on them, backdated purchase order creation dates that convert a violation into a clean record, and duplicate counting where one requisition spawns several orders.

Common Pitfalls

Many organizations struggle with maverick spending due to a lack of visibility into procurement processes and poor communication among teams.

• Failing to enforce procurement policies can lead to unchecked spending. Without clear guidelines, employees may resort to off-contract purchases, undermining cost control efforts.
• Neglecting to provide training on procurement systems results in confusion. Employees may not fully understand how to utilize approved vendors, leading to unnecessary maverick spend.
• Overcomplicating the purchasing process can frustrate employees. Lengthy approval workflows may drive them to bypass established protocols in favor of quicker, albeit unauthorized, solutions.
• Ignoring data analytics prevents organizations from identifying spending patterns. Without quantitative analysis, it becomes challenging to pinpoint root causes of maverick spending.

Improvement Levers

Addressing maverick spending requires a multifaceted approach that enhances compliance and streamlines procurement processes.

• Implement a user-friendly procurement platform to simplify purchasing. A centralized system can guide employees toward approved vendors and streamline the approval process.
• Regularly train staff on procurement policies and best practices. Ongoing education ensures that employees understand the importance of compliance and the impact of maverick spending on financial health.
• Establish clear communication channels between procurement and other departments. Regular updates on policy changes and vendor performance can foster collaboration and adherence to guidelines.
• Utilize data analytics to monitor spending patterns and identify maverick incidents. Regular variance analysis can help pinpoint areas needing attention and drive continuous improvement.

KPI Depot is trusted by consulting, strategy, finance, and analytics teams at leading organizations worldwide, including those listed below.

OKRs That Use Number of maverick spend incidents

No key result in the Procurement KPI group's OKR examples names this KPI. The closest genuine objective is the group's first, to optimize cost efficiency across the purchasing process to maximize savings and spend control, which already carries Spend Under Management as a key result alongside Cost Savings per Purchase Order and Cost Reduction per Buyer. Maverick spend is that same quantity viewed from the other side, since every purchase that bypasses procurement is spend Spend Under Management does not cover. A team could add a directional key result under that objective to reduce off-process purchasing incidents in the categories where a contract already exists, which keeps the target pointed at indiscipline rather than at sourcing gaps the buying teams cannot fix themselves.

The group's best-practice guidance points the same way. It treats Procurement Policy Exception Rate as a leading indicator of compliance risk and reads exceptions as evidence of weak controls or training gaps rather than of intent. On that logic this count belongs in an OKR as a diagnostic key result rather than a headline one: useful for showing whether control coverage and buyer training are working, best expressed as a direction of travel, and always reported with its denominator next to it. The guidance's own reasoning collapses if the count falls because fewer transactions were tested.

See OKR Examples for Procurement

Free Whitepaper

Want to achieve performance excellence in Procurement? Download our in-depth whitepaper: Definitive Guide to Procurement KPIs.

Download the Free Guide

KPI Categories

This KPI is associated with the following categories and industries in our KPI database: