Purchase Order Management: Why Your PO Compliance Rate Is Lower Than You Think

The Metric That Flatters Itself

A finance director reports 87% PO compliance. The number comes from the ERP: 87% of invoices processed last quarter carried a purchase order reference.

Then someone asks a different question — how many of those purchase orders were raised before the goods were ordered?

The answer, in most organisations that have never measured it, is uncomfortable. A large share of purchase orders are created after the fact: the requester bought something, the invoice arrived, AP could not match it, and someone raised a PO retrospectively so the invoice could be paid.

Those orders count as compliant in every standard report. They provide no spend control whatsoever.

This is the central problem with purchase order management as it is practised. The purpose of a purchase order is to move the approval decision to a point where it can still change the outcome. An order raised after the commitment exists has been reduced to paperwork that unblocks a payment.

What Is Purchase Order Management?

Purchase order management is the control of a purchase order across its entire life — from the internal requisition that triggers it, through approval, issue to the supplier, receipt of goods or services, matching against the supplier’s invoice, and formal closure.

The full lifecycle:

1. Requisition — an internal request to buy, capturing what is needed, why, and against which budget
2. Approval — authorisation by someone with delegated authority for that value and category
3. Purchase order issue — the external commercial document sent to the supplier, creating the commitment
4. Acknowledgement — supplier confirms acceptance, price and delivery
5. Receipt — goods or services recorded as received, in full or in part
6. Matching — invoice reconciled against the order and receipt
7. Closure — the order formally closed and any residual commitment released

Steps 1 to 3 are where control lives. Steps 5 to 7 are where most organisations lose data quality — and where the resulting problems surface months later.

Requisition versus purchase order

These are routinely conflated, and the distinction matters for control design. A requisition is internal: a request, routed for internal authorisation. A purchase order is external: a commercial document that commits the organisation to a supplier.

Confusing the two typically produces one of two failure modes — requisitions being sent to suppliers as though they were orders, or purchase orders being issued without any internal approval step preceding them.

Which Types of Purchase Order Should You Use?

Using a single order type for all spend is a common and costly simplification.

Blanket purchase orders are the most under-used instrument in most organisations. A great deal of the pressure that produces non-compliance comes from applying full standard-PO process to small, repetitive, entirely predictable purchases. Moving that spend onto blanket orders with controlled releases removes the administrative burden while preserving an overall spend ceiling — and typically improves compliance more than any policy reminder.

They do need their own discipline: monitored consumption against the ceiling, expiry alerting, and a clear rule about who may raise a release.

Why Does PO Compliance Break Down?

Almost never because people are careless. Non-compliance is usually a rational response to a process that costs more than it delivers.

The approval cycle is too slow. If a requisition takes a week to approve and the requester needs the item on Thursday, they will buy it and deal with the paperwork afterwards. Approval turnaround is the single strongest predictor of PO compliance.

The threshold is set irrationally low. Requiring a full purchase order for very small purchases costs more in process time than the purchase is worth. People notice, and route around it.

The category genuinely does not fit. Utilities, statutory charges, insurance, professional fees billed on time and emergency repairs do not fit a pre-approved fixed-quantity order. Forcing them into one produces fictional orders.

Nobody knows what to raise it against. If cost codes are unclear or budget structures unintuitive, requesters delay rather than guess wrong.

The system is unusable on a phone. Approvers who are on site, travelling or between meetings will not open a desktop ERP. Approval collapses to email, and the audit trail with it.

Urgency has no legitimate path. Where no fast route exists for genuine emergencies, the workaround becomes the emergency process — and then simply becomes the process.

The Two Failures That Cost Most

Open purchase orders that never close

Orders stay open for mundane reasons: partial delivery, over- or under-receipting, informal cancellation, or simply that closing them is nobody’s job.

The consequences compound. Committed spend is overstated, so budget holders see less available budget than they have and defer legitimate purchases. Period-end accrual calculation becomes guesswork, because genuine outstanding commitments cannot be distinguished from abandoned ones. And the open PO report becomes so noisy that nobody reads it — which is precisely when a real problem hides in it.

Ageing open orders needs an owner and a cadence. An order open past its expected delivery date with no receipt is either a supply problem or a data problem, and both need attention.

Amendments that escape re-approval

An order approved at one value, then edited upward in place with no version history and no return to an approver, is a control failure that auditors find quickly.

The rule should be explicit: amendments are versioned, the original approved state is retained, and any increase crossing an approval threshold triggers re-approval. Without this, the approval threshold is advisory — a requester who wants to avoid a higher approval tier can raise a compliant small order and grow it afterwards.

How Does Purchase Order Quality Affect Accounts Payable?

Heavily, and in a direction most organisations underestimate: most invoice exceptions are created at ordering time, not at invoicing time.

When an invoice fails to match, the cause is usually upstream — no purchase order exists, the quantity ordered does not reflect what was actually agreed, the price on the order is out of date, an amendment was never recorded, or goods receipt was never entered.

Accounts payable then absorbs the cost: investigating, contacting the requester, contacting the supplier, and holding the invoice while the supplier chases payment. The organisation pays twice, once in AP time and again in supplier goodwill.

This is why improving order accuracy is usually a better investment than improving exception handling. Our guide to three-way matching in accounts payable covers the matching mechanics in detail, and preventing invoice overpayments covers what happens when price and quantity variances go unchecked.

There is also a direct relationship with the non-PO problem. Every purchase that should have carried an order but did not becomes a non-PO invoice requiring manual coding and approver identification — the most expensive invoices in any AP function. See non-PO invoice processing challenges and, for the fragmented low-value spend where this concentrates most heavily, our analysis of tail spend management.

How Do You Design a PO Policy That People Actually Follow?

1. Define coverage by category and value, not universally. Decide deliberately which categories require an order, which are better handled by blanket orders, and which are legitimately exempt. A short list of well-justified exemptions beats a universal rule that is widely ignored.

2. Set thresholds proportionate to risk. The approval effort should reflect the value and risk at stake. Low-value, low-risk, well-understood purchases warrant light process.

3. Move recurring spend onto blanket orders. This is usually the highest-leverage single change available.

4. Make approval fast and mobile. Approval turnaround drives compliance more than policy does. See AP approval workflow automation for the routing patterns involved.

5. Provide a controlled urgent route. A documented emergency path with post-hoc review is far better than an undocumented workaround.

6. Enforce amendment versioning and re-approval.

7. Own open PO ageing. Assign responsibility and a review cadence.

8. Turn on commitment visibility. Budget holders should see committed spend at the point of decision — the gap our guide to budget control and visibility examines.

9. Measure honestly. Report genuine compliance, excluding retrospective orders.

How Does Peakflo Support Purchase Order Management?

Peakflo connects the ordering process to the payables process, so control established at the point of commitment carries through to payment.

Requisition and approval routing that works anywhere. Requests route by value, category, cost centre and entity, with mobile approval and automatic escalation when an approver is unresponsive — directly attacking the approval latency that causes most non-compliance. See approval workflow automation.

Procurement and purchase order handling. Peakflo’s procurement and purchase request, quote and order capabilities cover the flow from request through quotation to issued order, keeping internal authorisation and external commitment distinct.

Budget visibility at the point of request. Budget management surfaces budget position when the request is raised rather than at month end, so approvers decide with commitment data in front of them.

Automated matching with tolerance rules. Two-way and three-way matching reconciles invoice, order and receipt automatically, applying tolerances so only genuine variances reach a person.

Exception routing with full context. Where an invoice cannot match, Peakflo routes it with the order, receipt and history attached, rather than leaving AP to reconstruct the story.

Handling for the invoices that arrive without an order. Since no policy achieves total coverage, non-PO invoice processing applies AI-based coding and approver identification to the remainder, so exceptions do not become bottlenecks.

Open commitment visibility. Consolidated reporting on open orders, ageing and committed spend across entities — the basis for meaningful accrual and budget management. Related patterns are covered in our multi-entity AP automation guide.

ERP integration in both directions. Orders, receipts, commitments and invoice status synchronise with SAP, NetSuite, Xero and others, so the order lives in one authoritative place.

Our Verdict: When Is Purchase Order Management Worth Investing In?

Invest when:

• You cannot separate genuine PO compliance from retrospective order creation
• A significant share of invoices arrive with no purchase order at all
• Open purchase orders are stale and nobody owns the ageing
• Budget holders discover committed spend at month end rather than at approval
• Invoice exceptions are frequent and usually trace back to order data
• Requisition approval regularly takes more than a couple of days
• Purchase orders can be amended after approval with no re-approval

A lighter approach is defensible when:

• Purchasing is concentrated among a small number of people with strong budget discipline
• Spend is dominated by a few large contracted suppliers with negotiated terms
• Transaction volumes are low enough that every purchase is genuinely visible
• Your spend is overwhelmingly in categories that legitimately do not suit purchase orders

The judgement worth making is that purchase order management is a spend control, not an administrative requirement. If your process produces orders that document decisions already taken, you are paying the administrative cost without receiving the control benefit — which is the worst of both positions, and more common than most finance teams realise. The savings calculator offers a starting view of the processing-cost side.

Conclusion

Purchase order management fails quietly. It rarely produces a crisis; it produces a compliance number that looks respectable, an open PO report nobody trusts, budget holders who learn about commitments after the fact, and an AP team resolving exceptions created weeks earlier by someone else.

The correction is not stricter policy. In most organisations non-compliance is a sensible reaction to a process that is slower than the alternative, and tightening enforcement without addressing speed simply drives the workaround further underground.

What works is making the compliant path the easy path: thresholds proportionate to actual risk, blanket orders carrying predictable recurring spend, approvals that happen in hours on a phone rather than days at a desk, amendments that are versioned and re-approved, open orders someone is responsible for closing, and commitment visibility that reaches the budget holder while the decision is still open.

Then measure it honestly. The share of invoices with a PO number will tell you what you want to hear. The share of purchase orders raised before the commitment will tell you what is actually happening.

Request a demo to see how Peakflo connects purchase order management to invoice matching and payment in one workflow.

Frequently Asked Questions

What is purchase order management?

Purchase order management is the discipline of controlling the full life of a purchase order, from requisition and approval through issue to the supplier, receipt of goods or services, matching against the invoice, and formal closure. Its purpose is to commit spend before it is incurred, so that budget holders approve expenditure at the point of decision rather than discovering it when the invoice arrives.

What is PO compliance rate and how is it calculated?

PO compliance rate is the proportion of eligible purchases covered by a valid purchase order raised before the commitment was made. The important qualifier is before. Many organisations calculate it as the share of invoices carrying a PO number, which counts retrospective purchase orders as compliant and can overstate genuine compliance considerably.

What is a retrospective purchase order?

A retrospective or after-the-fact purchase order is one raised after the goods or services have already been ordered or received, usually created so an invoice can be matched and paid. It satisfies the system requirement but delivers none of the control benefit, because the spend was committed before anyone approved it. The approver can only ratify a decision already made.

What is a blanket purchase order?

A blanket or standing purchase order covers repeated purchases from one supplier over a period, up to an agreed value or quantity, with individual deliveries drawn down as releases against it. It suits predictable recurring spend such as consumables or ongoing services, and removes the need to raise a separate order for every transaction while retaining an overall spend ceiling.

Should every purchase require a purchase order?

No. Requiring a purchase order for every transaction regardless of value or category adds administrative cost to purchases too small to justify it, and reliably produces workarounds. A better approach defines which categories and value bands genuinely require a purchase order, uses blanket orders for predictable recurring spend, and provides a controlled non-PO route for legitimate exceptions such as utilities and statutory charges.

What is commitment accounting?

Commitment accounting records committed spend against a budget at the moment a purchase order is issued, rather than waiting until the invoice is posted. It gives budget holders a view of remaining uncommitted budget rather than only remaining unspent budget, which is the difference between managing a budget and reporting on it after the fact.

Why do open purchase orders accumulate and why does it matter?

Purchase orders stay open when goods are partially delivered, quantities are over or under received, orders are cancelled informally, or nobody is responsible for closing them. Stale open orders overstate committed spend, distort budget availability, complicate accrual calculation at period end, and make genuine outstanding commitments impossible to distinguish from abandoned ones.

How should purchase order amendments be controlled?

Amendments should be versioned and re-approved where the change is material, particularly any increase in value that crosses an approval threshold. The common control failure is allowing a purchase order to be edited in place with no version history, which lets an order approved at one value grow substantially without returning to an approver and leaves auditors unable to see what was originally authorised.

What is the difference between a purchase requisition and a purchase order?

A purchase requisition is an internal request to buy something, raised by the person who needs it and routed for internal approval. A purchase order is the external commercial document issued to the supplier, creating a contractual commitment. The requisition captures internal intent and authorisation, the purchase order communicates the commitment externally.

How does purchase order management reduce invoice exceptions?

Most invoice exceptions originate in poor order data rather than in the invoice itself. Missing purchase orders, incorrect quantities, outdated prices and unrecorded amendments all surface as mismatches at matching time. Improving accuracy at the point of ordering removes exceptions at source, which is far cheaper than resolving them later with the supplier.

What metrics indicate healthy purchase order management?

Useful measures include genuine PO compliance excluding retrospective orders, requisition to purchase order cycle time, purchase order approval turnaround, share of orders amended after approval, ageing of open purchase orders, first-pass match rate, and the proportion of spend covered by blanket orders. Tracking only the share of invoices with a PO number gives a misleadingly positive picture.

How do you improve PO compliance without creating workarounds?

Make the compliant route faster than the workaround. Most non-compliance is a rational response to a slow or cumbersome process rather than deliberate circumvention. Reducing approval turnaround, using blanket orders for recurring spend, applying thresholds proportionate to risk, and enabling mobile approval usually improve compliance more than policy enforcement does.