Why it happens
Requesters buy off-contract when catalogs are stale, preferred suppliers are slow, or they do not know a deal exists. Urgent maintenance and clinic supplies are common maverick categories. Sometimes maverick is intentional to avoid scrutiny—policy and culture both matter.
Decentralized buying without feedback loops looks like savings locally but fragments volume and weakens leverage at renewal.
How to measure
Analytics map spend to contracted suppliers and SKUs. Lines with no contract ID, wrong UNSPSC, or supplier not on the roster count as maverick. Segment by department and category to prioritize enablement over punishment.
Compare maverick unit price to contracted price on the same item—$40,000 on Amazon Business for laptops priced at $2,380 on contract is both maverick and measurable leakage.
Reduction tactics
Fix the easy path: punch-out catalogs, guided buying in the ERP, and intake agents that suggest contracted items from free text. Pair with approval rules for off-contract buys above thresholds.
Quarterly business reviews with high-maverick departments beat blanket policy memos.
Governance balance
Zero maverick is unrealistic in emergencies. Define expedite paths with after-action review rather than forcing shadow purchases. Track maverick rate and dollars redirected, not only violations.
Operational checklist for maverick spend
Segment maverick by department and commodity before blaming suppliers; fix catalog gaps first. Show requesters side-by-side contracted vs off-contract unit price in intake screens.
Set approval requirements for non-contract buys that rise with dollar and risk tier. Celebrate redirected spend with evidence, not only policy violations.
Review metrics quarterly with procurement, finance, and business owners who feel process pain—adjust rules when data shows a control is cosmetic or a bottleneck is upstream.
Metrics, audits, and rollout for maverick spend
Internal audit samples maverick spend by tracing transactions from requisition or contract through payment, looking for missing evidence and override patterns. Findings are usually systemic—stale catalogs, receivers not trained, or tolerances set too wide—rather than one rogue approver. Remediation plans should name a process owner outside AP when the root cause is upstream.
Leading indicators for maverick spend include open exceptions, unposted receipts, contracts past notice windows, and classification backlog; lagging indicators include paid-after-due volume, duplicate hits, and price variance dollars. Review the same dashboard weekly with procurement during a transformation, not only at quarter close, so fixes land before suppliers escalate.
Pilot changes to maverick spend on one company code or region with documented before-and-after samples on the same supplier mix. Parallel-run old and new rules until match or classification variances fall below an agreed threshold, then cut over with a rollback plan. Executive sponsors should see cycle time and touch-per-document, not only license go-live dates.
Technology helps maverick spend only when master data, contracts, and receiving discipline keep pace. Budget for content stewardship—catalog updates, clause playbooks, screening lists—alongside software. Tie savings claims to redirected spend, captured discounts, and avoided overbill with line-level examples auditors can reproduce.
Stakeholder alignment matters: publish a one-page RACI for maverick spend that names who sets policy, who operates the process, and who approves exceptions. Exception approvals should expire automatically after 90 days unless renewed with business justification, preventing "temporary" tolerances from becoming permanent holes in control.
Training should use live examples from your ERP, not generic slides—walk receivers and buyers through one held document and show which fields they can change to clear maverick spend issues. Reinforce that fixing upstream data beats overriding match or approval rules downstream, because overrides rarely scale across thousands of transactions per month.