Requisition-to-PO conversion: the PO compliance problem

PO compliance is low in most organizations because requisition-to-PO conversion is slower and more error-prone than the workaround: a phone call to the supplier, an email order, a P-card swipe. Buyers who skip the PO process are making a rational trade, and they will keep making it until the compliant path wins on speed. Training campaigns and approval gates treat the symptom; the cure is a conversion step fast enough that nobody wants to route around it.

Buyers route around the PO process because it loses on speed

Watch a buyer convert an approved requisition. It arrives missing a cost center, the GL code has to be looked up, and the delivery date defaults to something wrong. The contract reference lives in another system, and the vendor record needs checking against master data in a third. Twenty minutes later there is a compliant PO. The alternative was a two-minute call to a supplier the buyer has known for years.

This gets worse exactly when leadership cares most: during a new ERP rollout, or a push toward a PO-first culture. The new process is unfamiliar and feels slower than the old way, so buyers quietly fall back on legacy habits, and compliance sags just as the program meant to raise it goes live.

One skipped PO seeds a chain of downstream exceptions

Each workaround costs more than the one purchase it covers. Goods arrive with nothing to receive against, then an invoice shows up with nothing to match, so AP builds a PO after the fact by copying whatever the invoice says, which defeats the point of matching at all. Cost centers and GL codes get guessed at month end. The purchase never touches the negotiated contract, so agreed pricing and volume tiers go unapplied. One skipped conversion can surface as exceptions in receiving, matching, coding, and payment, each landing on a different team weeks later.

The visibility cost is quieter. Spend that bypasses the PO process stays invisible until a quarterly review, too late to act. Ardent Partners' 2025 Metrics that Matter research puts average spend under management at about 71 percent, and finds each new dollar brought under management saves 6 to 12 percent in the first contract period. Low PO compliance is one of the main ways the other 29 percent leaks out.

More enforcement makes the compliant path slower

The standard response is a compliance program: mandate PO-first purchasing, add approval gates, report offenders by department. That misdiagnoses the behavior as a discipline problem. Every added gate makes the compliant path slower, which widens the speed advantage of the workaround it was meant to stamp out. Compliance ticks up while the mandate has attention, then slides back as buyers under delivery pressure rediscover the phone.

The fix is a conversion step that beats the workaround

Buyers will use the compliant path the day it is the fastest option. Most conversion work is mechanical judgment: fill the missing fields, reconcile them against master data, check the contract, validate pricing. That profile suits agent-based procurement automation. Fragment's agents pick up approved requisitions and generate compliant POs with cost centers, GL codes, delivery dates, and contract references populated and validated against master data and catalog pricing. Anomalies, say an unusual quantity or a price that disagrees with the contract, get flagged for a human decision. The buyer approves exceptions instead of keying fields, and the recovered hours go to sourcing decisions.

The agents work across the systems already in place (ERP, contract repository, supplier records, email), so nothing gets ripped out or replaced, no data standardization project comes first, and production is measured in weeks. Conversion is also a strong first candidate when weighing which procurement processes to automate first: high volume, well-defined inputs, and a compliance metric that moves within a quarter, the shape of a clean procurement automation business case.

Conversion is one link in the chain. Fragment's agents handle exception-heavy work across the full source-to-pay lifecycle, from requisition-to-PO conversion and change orders through supplier master data, invoice matching, credits and rebates, and tax holds. See the workflows Fragment covers, or book a demo and walk through your own conversion numbers.