The PO-first culture problem: why buyers work around the process
Buyers bypass the PO process when the compliant path is slower than the workaround, and no amount of messaging about PO-first culture changes that. If an approved purchase order takes five days and a phone call to the supplier takes five minutes, a buyer who is measured on delivery dates will make the call, take the maverick-spend lecture later, and do the same thing next month. PO compliance is a speed problem wearing a compliance costume.
The workaround is a rational decision, and your best buyers make it most often
A verbal order, an email commitment, or a P-card swipe before a PO exists is a buyer solving the problem they are actually paid to solve. Plant managers are measured on uptime, buyers on delivery, and when the source-to-pay process asks them to trade a week of lead time for a document, the trade fails on its own terms. The Hackett Group found in 2025 that top-performing procurement organizations run 58% shorter requisition-to-PO cycle times than their peers. Buyers at the slow companies can feel that spread even if nobody has measured it.
Low compliance clusters exactly where the process is slowest
Aggregate PO compliance tells you very little. The diagnostic number is compliance by category and by buyer, and the pattern is remarkably consistent: urgent purchases, small-dollar purchases, and one-off specialized suppliers sit at the bottom, because those are the cases where the PO process is slowest relative to the alternative. A new supplier needs master data setup before a PO can even be cut. A small buy routes through an approval chain designed for six-figure spend, and an emergency part cannot sit in a buyer desk queue. An attitude problem would spread evenly across the org chart. A speed problem clusters, and yours is probably clustering right now.
Enforcement raises the price of the workaround and leaves the slow path slow
The standard response is to tighten the screws: block invoices without a PO number, escalate violations, publish compliance league tables by business unit. What that mostly produces is retroactive POs, created after the goods have shipped so the invoice will clear. A retroactive PO carries the full administrative cost of a real one and none of the control value. Buyers get better at hiding, suppliers get caught between a buyer who ordered and an AP team that will not pay, and the program stalls the way most procurement transformation programs stall: quietly, with the policy still officially in force. You cannot punish your way across a speed gap.
Close the speed gap and compliance largely takes care of itself
The fix is to make the compliant path fast enough that the workaround stops being worth the trouble. The mechanics of requisition-to-PO conversion get their own article; the short version is that most of the delay is exception handling: incomplete requisitions, supplier master data gaps, unclear approval routing, and requests sitting in a buyer's queue behind forty others. This is the work agentic automation handles well. Fragment's agents work those exceptions across your ERP, supplier portals, email, and spreadsheets the way an analyst would, with a human approving the judgment calls, nothing ripped out or replaced, and production typically within weeks. Req-to-PO is also a strong candidate when you are deciding which procurement processes to automate first, because the payoff shows up as adoption rather than as another dashboard.
Stalled PO adoption is usually the loudest symptom of exception-heavy work running across the whole source-to-pay lifecycle: change orders, supplier master data, invoice exceptions, credits and deductions, GL coding. If the clustering pattern above looks familiar, see how Fragment handles these workflows or book a demo.