Purchase Order Management: The Complete Guide

Issuing a purchase order is the easy part. The real work starts the moment it leaves your system: getting it acknowledged, chasing the deliveries that slip, deciding what to do when only half the order turns up, handling change requests, and making sure every line eventually closes rather than drifting into an ageing backlog. This guide covers purchase order management after issue, the controls that keep committed spend accurate, and the housekeeping that stops open orders piling up.

Life after issue: what PO management actually covers

Most explanations of the purchase order stop at the point of despatch. Requisition raised, approval granted, order sent to the supplier, job done. In practice that is roughly the midpoint. Between issue and closure sit acknowledgement, expediting, receipting, amendments, variance resolution, matching and closure, and each of those stages can go wrong in ways that cost money or distort your numbers.

The purpose of managing an order after issue is to keep three things true at once: the supplier knows exactly what is expected and when, the operational teams know what is actually coming, and finance knows what has been committed but not yet spent. A live purchase order is a promise on both sides, and an unmanaged one quietly stops being reliable within weeks.

The symptom of poor PO management is always the same: a long list of open orders nobody can explain. Some are genuinely awaiting delivery, some were delivered but never receipted, some were cancelled by phone and never closed in the system, and a few are duplicates. Once that list grows past a few hundred lines, commitment reporting becomes fiction and month end becomes guesswork.

Acknowledgements and order confirmations

A PO sent is not a PO accepted. Until the supplier acknowledges it, you have made an offer and nothing more. The order acknowledgement, sometimes called an order confirmation, is the supplier's formal reply stating that they accept the lines, prices and dates, or that they accept with changes.

That last case is where problems begin. A confirmation that quietly moves the delivery date out by three weeks, or prices a line differently from the order, is a counter-offer. If nobody reads it, the difference surfaces months later as an invoice mismatch, and by then the goods are consumed and the negotiating position is gone. Treat every acknowledgement as a document to be checked against the order, not a receipt to be filed.

• Full acceptance. The supplier confirms every line as ordered. Record the confirmation and use the confirmed date as your expediting baseline.
• Acceptance with a revised date. Common and often acceptable, but it must be reviewed by whoever needs the goods, then written back onto the PO so the system reflects reality.
• Acceptance with a price change. Never accept silently. Either reject and hold the supplier to the agreed price, or amend the PO deliberately so the invoice will match later.
• Partial acceptance. The supplier can supply some lines but not others. Decide early whether to split the order or source the balance elsewhere.
• No response at all. The most dangerous outcome, because it looks like agreement. Chase acknowledgements that are outstanding after a set number of days.

Setting an acknowledgement service level with your main suppliers, say two working days, gives you an early warning system. If a supplier will not confirm, that tells you something about the order long before the delivery date passes.

Expediting and chasing late deliveries

Expediting is the discipline of chasing orders before they become late rather than after. It works on a simple principle: contact the supplier ahead of the promised date on anything that matters, and confirm the delivery is on track.

Not every order deserves the same attention. Sort your open book by consequence, not by value alone. A small order for a part that stops a production line matters more than a large order for stationery. A practical approach is a short expediting list refreshed weekly: critical items due in the next fortnight, anything already past its confirmed date, and anything from a supplier whose recent performance has been poor.

Record the outcome of every chase against the PO itself, not in a personal inbox. When the person who made the call is on leave, the next person needs to see that the supplier promised a revised date last Tuesday. Systems such as ProcureWave keep that conversation attached to the order line, so the history travels with the document rather than with the buyer.

Partial, over and under deliveries

Deliveries rarely arrive exactly as ordered. Goods receipting has to handle the messy cases cleanly, because what gets recorded at the goods-in door drives everything that follows: stock, accruals, matching and payment.

Tolerances deserve a decision rather than a default. A quantity tolerance of a few per cent is sensible for bulk or cut-to-length materials where exact quantities are impractical, and pointless for serialised equipment. Set them per category, not globally, and make sure the tolerance used at receipting is the same one used at invoice matching. Mismatched tolerances between goods-in and accounts payable generate exceptions that nobody can resolve without a phone call.

Amendments, change orders and when a new PO is needed

Requirements change. The question is whether to amend the existing order or raise a fresh one, and the answer matters because amendments overwrite history while new orders preserve it.

A change order is an amendment issued formally to the supplier, versioned, and re-approved if it crosses a threshold. Any change to price, quantity or scope should follow that route rather than being agreed verbally. The test is simple: if the change would have altered who approved the original order, it needs approval again.

Raise a new PO when the supplier changes, when the item or service is materially different, when the contract or terms behind the order change, or when a different budget or cost centre should carry the spend. Amend when the substance is unchanged: a corrected delivery address, a revised date, a quantity adjustment on lines that have not yet moved.

Price and quantity variances at matching

Variances are where PO management meets the finance ledger. When the invoice arrives, three-way matching compares it against the order and the goods received note. Anything that does not agree becomes an exception that somebody has to clear.

Price variances usually trace back to one of four causes: an unnoticed price change on the acknowledgement, a contract price that was never loaded onto the order, an uplift the supplier applied without agreement, or a unit of measure mismatch where the order was per box and the invoice per item. Quantity variances trace back to receipting: goods delivered but not receipted, receipted twice, or receipted against the wrong line.

The fix for most variances is upstream, not in the exception queue. Accurate prices on the order, disciplined receipting on the day of delivery, and consistent units of measure remove the majority of them. For the remainder, agree a tolerance below which small differences are auto-approved rather than routed to a human; the cost of investigating a trivial variance usually exceeds the variance.

Blanket orders, standing orders and call-offs

Raising a separate PO for every small repeat purchase is a waste of everyone's time. Blanket and standing orders solve that by committing to a value or a schedule up front, then drawing against it.

Blanket orders need their own management routine. Watch the drawdown rate against the remaining term, review prices at renewal rather than rolling them forward by habit, and close orders that expire with value remaining so the commitment does not linger. Because a blanket order is often the mechanism behind a wider supply agreement, it should be reviewed alongside the contract, not separately from it.

Open PO reporting, ageing and period end

The open PO report is the single most useful document in purchase order management, and in most organisations it is the least read. It shows every order issued but not yet closed, and it is the source for both commitment reporting and accruals.

Age the report rather than just listing it. Orders under thirty days old are normal. Orders between thirty and ninety days need a reason. Anything over ninety days should be actively challenged: has it been delivered and not receipted, cancelled and not closed, or genuinely still awaited? Reviewing the tail monthly stops it becoming a permanent feature.

At period end the same data drives two different numbers. Goods received but not yet invoiced sit in a received-not-invoiced accrual so the cost lands in the right period. Ordered but not yet received value is a commitment against budget, not an accrual. Getting these right depends entirely on receipting being done promptly and on the open PO list being clean, which is why good procurement practice and good reporting are the same exercise.

Closing, short-closing and cancelling

A PO closes when every line has been fully received and invoiced. That is the clean path, and in a healthy system it accounts for most orders. The rest need a deliberate decision.

Short-closing applies when a line will not be fulfilled in full and the balance is no longer wanted. It closes the line at the received quantity and releases the remaining commitment. Cancellation applies before any receipt or invoice, and should be communicated to the supplier rather than performed silently in your own system. Both need a reason code, because the pattern of reasons over a year is one of the better sources of supplier performance data you will get for free.

Decide who owns closure. In most organisations it should be the buyer who raised the order, with a monthly prompt for anything older than a threshold. Leaving closure to finance at year end guarantees a rushed clean-up and a set of write-offs nobody can explain.

Housekeeping that stops the backlog building

Open PO backlogs are not caused by one big failure. They accumulate from small omissions repeated across thousands of lines, so the cure is routine rather than heroics.

Receipt on the day of delivery, not at month end. Chase acknowledgements that are missing after the agreed window. Review the ageing report every month and give each line over ninety days an owner and an action. Short-close deliberately rather than letting orders expire into the void. Keep units of measure and prices consistent between contract, order and invoice. None of that is difficult; all of it needs to happen every month rather than every year.

Automation helps because it makes the routine unavoidable. Acknowledgement chasers, ageing alerts, tolerance based matching and one-click short-closing all belong in the system rather than in someone's diary, and choosing the right purchase order management software is largely about how well it handles these unglamorous cases. If you would like to see how ProcureWave handles acknowledgements, expediting and open PO ageing on your own order book, get in touch and we will walk you through it.

Frequently asked questions

What is purchase order management?

Purchase order management is everything that happens to a PO after it is issued: getting it acknowledged, expediting late deliveries, handling partial and over deliveries, processing amendments, resolving price and quantity variances, and closing the order once it is fully received and invoiced.

When should I amend a PO instead of raising a new one?

Amend when the commercial substance stays the same, such as a revised delivery date or a small quantity change on an unreceipted line. Raise a new order when the supplier, the item, the contract terms or the budget code changes, or when the original PO has already been part-received and invoiced. The PO process guide walks through the stages in order.

What is an open purchase order?

An open PO is one that has been issued but not yet fully received, invoiced and closed. Open POs represent committed spend, so they should appear on your commitment reporting and be reviewed by age, with anything old enough to be stale chased or short-closed.

What is short-closing a purchase order?

Short-closing means closing a PO line for less than the ordered quantity, because the supplier will not deliver the balance or the balance is no longer needed. It releases the leftover commitment from your budget and stops the order sitting open forever.

How do open POs affect period-end accounting?

Goods received but not yet invoiced sit in a received-not-invoiced accrual, so finance can recognise the cost in the correct period. Ordered but not received values are commitments rather than accruals. Both come straight from open PO data, which is why accurate receipting matters at month end.