What is purchase order management, and how do you run it?
Short answer
Purchase order management is running each purchase order from creation to closure: approve, send, confirm, change under control, receive, match and close, with an owner for every step.
Key takeaways
- Purchase order management is the control of every purchase order (PO) over its whole life, not only its creation. A PO is managed well when it is approved before the supplier works, confirmed by the supplier, changed only through a new revision, received, matched and closed.
- Each step needs one owner: the requester for the need and the receipt, the buyer for the order and its changes, the supplier for the confirmation, accounts payable for the match. The person who creates an order should not also approve it or record its receipt.
- Changes are a frequent source of errors. A change agreed by phone and never put on the PO surfaces weeks later as an invoice that does not match.
- Open orders need a regular review. An order that will receive nothing more should be closed, so that the budget it reserves is released and no late invoice can be matched to it.
- Measure a few things: orders raised after the invoice, orders not confirmed by the supplier, changes after sending, and old open orders. Each one points to a fix upstream.
What is purchase order management?
Purchase order management is the process of controlling each purchase order from creation to closure. It covers approval, sending the order to the supplier, getting it confirmed, handling changes and cancellations, tracking delivery, matching the invoice and closing the order, with a named owner and a check at each step.
The purchase order is the document: the numbered order a buyer sends to one supplier, with items, quantities, prices, dates and terms. That page also gives the short sequence from requisition to payment. This page is about running that sequence day after day: who does what, which status the order is in, how it is changed, and what goes wrong. The tools that support it are compared in purchase order software.
A simple case shows the difference. A maintenance team orders 40 pumps for delivery in March. The order is created and sent: that is ordering. Then the supplier confirms only 30 pumps for March and 10 for May, the project asks to add 5 pumps, and the last delivery never comes. Someone has to record the split delivery, change the order, chase the missing pumps and close the line. That ongoing work is purchase order management.
What are the stages of the purchase order lifecycle?
The purchase order lifecycle has eight stages. Guides and systems name and count them differently, but the work is the same. The table gives each stage, its usual owner and the control that keeps it honest.
| Stage | What happens | Usual owner | Control |
|---|---|---|---|
| 1. Create | An approved requisition, a catalogue item or a contract call-off becomes a draft order | Buyer, or the system for catalogue and contract items | Supplier is active and approved; price comes from the contract or catalogue |
| 2. Approve | The order is approved under the delegation of authority | Budget holder, then higher levels by amount | Approval limits by amount and category; the creator cannot approve |
| 3. Send | The order goes to the supplier by email, portal or electronic message | Buyer or the system | One channel per supplier; the order number is fixed |
| 4. Acknowledge | The supplier accepts, accepts with changes, or rejects | Supplier, checked by the buyer | Unconfirmed orders chased after a set number of days |
| 5. Change or cancel | Quantity, price, date or account changes; or the order is cancelled | Buyer, with re-approval when the value rises | New revision number; supplier accepts the revision |
| 6. Receive | Goods receipt, or confirmation that the service was done | Requester or warehouse | Receipt recorded on delivery, by someone other than the buyer |
| 7. Match | The invoice is checked against the order and the receipt | Accounts payable | Tolerances set by policy; differences go back to the owner |
| 8. Close | No more receipts or invoices are expected; remaining budget is released | Buyer or the system | Periodic review of open orders; closed orders cannot take new invoices |
If a stage has no owner in your organisation, that is the stage where orders get stuck; name one before choosing any tool.
Systems record these stages as statuses. Oracle’s procurement documentation, for example, lists statuses such as Pending Approval, Pending Acknowledgment, Open, On Hold, Pending Change Approval, Closed for Receiving, Closed for Invoicing, Closed, Finally Closed and Canceled. Lines carry their own status, so one line of an order can be closed while another is still open. The names differ in other systems, but the idea is the same: the status tells everyone what may still happen to the order.
Disclosure: the author works as an Ivalua consultant. The other vendors named on this page are described from their public documentation only, to show how the step works; this is not a comparison.
Who owns each step of purchase order management?
Purchase order management works when each step has one owner and no person controls a whole purchase alone. Four roles carry most of the work.
- Requester
- States the need, checks what the supplier delivered and records or confirms the receipt. Answers the question “did we get what we ordered?”.
- Buyer
- Owns the order once it is created: sends it, gets it confirmed, makes every change, chases late deliveries and closes it. When a buyer leaves, their open orders are reassigned to someone, not left without an owner.
- Approver
- Approves the spend within their limit. A change that raises the value above what they approved goes back to them, or to the next level.
- Accounts payable
- Matches invoices to orders and receipts and sends differences back to the buyer or the requester. It does not change the order to make an invoice fit.
The supplier is the fifth actor. It confirms the order, ships against it and quotes its number on every delivery note and invoice. Suppliers can only do this well if they receive orders in one predictable way, with one contact for questions.
Separation of duties is the main control. The buyer who creates an order should not approve it or record its receipt, and nobody involved in ordering should be able to change the supplier’s bank details. Otherwise one person can order, confirm a delivery that never happened and have the invoice paid.
How do you get the supplier to confirm the order?
Ask for an order acknowledgement and check it against the order. Legally, a purchase order is usually an offer to buy; under the US Uniform Commercial Code, it can be accepted by a prompt promise to ship or by shipping. A confirmation removes the doubt about what the supplier agreed to.
Electronic standards build this step in. In the Peppol ordering standard, the supplier answers with an order response: accepted, conditionally accepted with changes on some lines, or rejected. Only quantity, delivery period, a replacement item and price may be changed, and an order accepted this way has the status of a contract. In EDI, the X12 standard pairs the purchase order (850) with the purchase order acknowledgement (855). Supplier portals do the same with a “confirm” button.
Read the acknowledgement; do not just file it. Suppose a supplier confirms an order for office chairs with a delivery date three weeks later than requested and its own terms of sale attached. Under UCC § 2-207, a confirmation with additional terms can still be an acceptance, and between merchants those terms can become part of the contract unless the order limited acceptance to its own terms, they materially alter it, or the buyer objects in time. The buyer should accept the new date or reject it, and answer the terms, before the goods ship.
Many orders still go out as PDF attachments that nobody confirms. Set a rule: if no acknowledgement arrives within a fixed number of working days, the buyer calls the supplier. An order with no confirmation is an order whose delivery date nobody can rely on.
How do you change or cancel a purchase order?
Change the order itself, through a new revision that the supplier accepts, before the supplier acts on the change. A change made only by phone or email leaves the order and the delivery out of step, and the difference surfaces at the invoice.
- The requester or the supplier asks for the change: a new quantity, date, price, delivery address or account code.
- The buyer checks it against the contract. A price change outside the contract terms is a commercial decision, not an order correction.
- The buyer edits the order. The system keeps the old version and gives the new one a revision number.
- If the change raises the value above what was approved, it goes back for approval. Lower quantities, dates and addresses usually do not.
- The revision is sent to the supplier, which accepts or rejects it.
- Receipts and invoices are matched against the latest accepted revision.
Peppol’s Advanced Ordering standard shows the same logic in electronic form. The buyer sends an order change, which must carry a sequence number so changes are applied in the right order, and changes must be made before the order is prepared for delivery. The buyer can cancel an order with an order cancellation; the supplier can propose changes in its response, which the buyer then accepts or rejects.
A common failure: a project manager phones the supplier and asks for 10 extra units. The supplier ships 110 units against an order for 100 and invoices 110. The receipt shows 110, the order shows 100, and the invoice fails the match. Accounts payable cannot pay it, and the buyer learns about the change a month late. The fix is a rule that only the buyer changes orders, and that suppliers are told to ship only what the order says.
Public buyers have the strictest version of this rule. In US federal contracts, only contracting officers acting within their authority may sign contract modifications, and other staff must not direct or encourage a contractor to do work that should be covered by a modification. Orders placed under a framework agreement or a blanket order follow the agreement’s terms; how their call-offs are controlled is explained in blanket purchase orders.
How do you track open orders and deliveries?
Track open orders by due date and by what is still missing: quantity not yet received, or receipts not yet invoiced. A weekly list of overdue lines lets the buyer chase suppliers before the requester complains.
- Overdue deliveries. Lines past their confirmed date with no receipt. The buyer asks the supplier for a new date and records it on the order.
- Partial deliveries. Thirty pumps of forty arrived. The line stays open for the rest, or the buyer closes the balance if it is no longer needed.
- Received, not invoiced. In many ERP systems this appears as an open balance on the goods receipt / invoice receipt (GR/IR) clearing account. Old items there are either missing invoices or receipts posted in error.
- Invoiced, not received. Invoices held because nobody recorded the receipt, often for services. The requester confirms the work or disputes it.
- Orders on hold. Orders where receiving and invoicing are suspended, for example while a quality problem is resolved. Each hold needs an end date and an owner.
Open orders also hold budget. Where budget control is used, confirming a purchase order records an encumbrance, a reservation of funds, which is relieved as invoices arrive. An order that will never be fully invoiced keeps money reserved that the budget holder could use elsewhere.
When and how do you close a purchase order?
Close a purchase order when nothing more will be received or invoiced against it. Many systems close orders by themselves when every line is fully received and invoiced; the rest need a person to decide.
Closing often happens in two steps. An order can be closed for receiving when the delivery is complete, but stay open for invoicing until the last invoice arrives. In Oracle’s terms, a finally closed order has completed all receiving and invoicing and can be archived and purged, so treat final closing as permanent. The useful rule is to close for receiving early, close for invoicing once the supplier’s statement shows nothing more due, and finally close only when you are sure.
Run a review of open orders at least before each period end. Look at orders with no activity for several months, orders with a small remaining balance, and orders whose requester has left. For each one, the buyer either chases the delivery, closes the balance, or records why it stays open. Public bodies set time limits for this kind of closure: US federal rules ask that files for firm-fixed-price contracts be closed within six months after the contracting officer receives evidence of physical completion.
What goes wrong in purchase order management?
Many failures come from steps done out of order or by the wrong person. The table lists the common ones, as they appear in day-to-day work.
| Situation | What it causes | Fix |
|---|---|---|
| The order is raised after the invoice arrives (an “after-the-fact” PO) | The approval comes after the money is committed; prices were never checked | Track these orders by requester; return invoices with no prior order; require a written reason |
| The order is sent as a PDF and never confirmed | Delivery dates and prices are unknown until the goods or the invoice arrive | Ask for an acknowledgement; chase unconfirmed orders after a set number of days |
| Changes agreed by phone, not on the order | Receipt or invoice does not match; the payment is held | Only the buyer changes orders; every change is a new revision |
| One purchase split into several orders | Each order stays under an approval limit | Report several orders to one supplier on the same day for the same need |
| No receipt recorded for services | Three-way match becomes two-way in practice; work is paid unchecked | Service confirmation as a step of the order, done by the requester |
| Order price differs from the contract price | Overpayment, or invoices blocked for a price difference | Prices taken from the contract or catalogue, not typed |
| Open orders never closed | Budget stays reserved; old orders can take late or duplicate invoices | Periodic review; automatic closing when fully received and invoiced |
Count each failure by requester, buyer and supplier every month; a few people or suppliers usually account for most of them, and that is where training or a talk pays off.
Some organisations treat after-the-fact orders as a serious breach. The University of Colorado’s procedure, for example, defines one as a unit making a commitment over $10,000 before its Procurement Service Center issues a purchase order. The supplier’s invoice is not processed until the after-the-fact purchase is approved, and an unapproved one is the personal obligation of the person who placed it.
Matching tolerances, and what happens when an invoice does not match, are explained in three-way match.
How do you measure purchase order management?
Pick a few measures that show where orders break, and set your own targets from your starting point. The measures below can be counted from most purchasing systems.
- After-the-fact orders: the number and value of orders created after the invoice date.
- Acknowledgement rate: the share of orders confirmed by the supplier within the set number of days.
- Orders changed after sending: the share of orders with at least one revision, and the most common reason.
- Requisition-to-order time: working days from an approved requisition to an order sent.
- Late deliveries: the share of order lines received after the confirmed date.
- First-time match rate: the share of PO invoices that match without a person.
- Old open orders: the number and value of orders with no activity for several months.
How to choose and define procurement indicators in general, and build a dashboard from them, is covered in procurement KPIs.
Do you need software to manage purchase orders?
Not at the start, but soon. A small team can run purchase orders from an accounting package or even a numbered spreadsheet, if every step above has an owner. Volume is what breaks this: once dozens of orders a week need confirmations, changes and receipts, statuses and revisions have to be tracked by a system.
What purchase order systems do, the types available and how to test them in a demo are explained in purchase order software. Systems that cover the whole chain, from requisition to payment, are compared in procure-to-pay software.
Questions
What is the difference between purchase order management and the purchase order process?
The purchase order process is the sequence of steps from an approved requisition to a paid and closed order. Purchase order management is the ongoing control of that sequence: who owns each step, which status each order is in, how changes and cancellations are handled, and how open orders are reviewed and closed.
Who is responsible for purchase order management?
The buyer owns each order once it is created: sending it, getting it confirmed, changing it, chasing late deliveries and closing it. The requester owns the need and the receipt, approvers own the spend within their limits, and accounts payable owns the match between invoice, order and receipt.
What is a purchase order change order?
A change order is a new revision of an existing purchase order. It changes quantity, price, date, address or account, keeps the same order number with a new revision number, goes back for approval if the value rises, and is sent to the supplier to accept. Invoices are matched against the latest accepted revision.
When should a purchase order be closed?
When nothing more will be received or invoiced against it. Many systems close fully received and invoiced orders automatically. Orders with a balance that will never be delivered, or with no activity for months, should be reviewed and closed by the buyer, so the budget they reserve is released.
What is an after-the-fact purchase order?
An after-the-fact purchase order is raised after the goods or services were ordered, often after the invoice arrived, so the supplier can be paid. The approval comes too late to change anything. Many organisations track these orders, require a written reason and may refuse to pay them.
New guides on the procure‑to‑pay line
One short email when a guide on this line is added or revised. Nothing else.
Coming soon: sign-up opens with the first email.