The Purchase Order Cycle, End to End (Procure-to-Pay)
The purchase order cycle runs from the moment someone identifies a need to the moment the order is paid and closed — requisition, approval, PO raised, sent to supplier, goods received, three-way match, invoice, payment, close. This guide walks every stage end to end, explains what each one is for and who owns it, shows exactly where each stage breaks when it lives in email and spreadsheets — missed approvals, wrong quantities, unmatched invoices — and how an owned system controls the whole cycle from one view instead of nine disconnected steps.
The purchase order cycle is the full sequence a business runs to buy goods or services on credit: a need is identified, a requisition is raised and approved, a purchase order is sent and confirmed, the goods are received, the invoice is matched and paid, and the order is closed. Each stage answers one control question before money leaves the business.
The practical problem is rarely the list of stages. It is the time and the gaps between them. A request waits in an inbox, a delivery is booked in on paper, an invoice sits unmatched because nobody can find the receipt, and the order stays “open” long after it was paid. Measuring the cycle stage by stage shows where that time and risk actually sit. For the approval and matching stages, an invoice approval workflow routes each match and exception to a named approver instead of leaving it in an inbox.
Goods receipt is the point where the cycle stops dealing with intentions and starts dealing with what arrived. Illustrative photograph, not an OpsMavix project.
Image credit: Arum Visuals, Unsplash License. No edits.
Key Takeaways
- The purchase order cycle runs from need to closure, not just from order to delivery.
- Each stage needs a named owner, a clear output and an exit rule.
- Cycle time should be measured per stage, using timestamps the system records itself.
- Supplier lead time and agreed payment terms are not internal delay, so report them separately.
- A three-way match only works when the goods receipt is recorded against the order.
- Closing orders keeps the open-commitment list trustworthy for the next reorder decision.
In this guide:
- 1. Understand What the Purchase Order Cycle Is
- 2. Map the Nine Stages and Their Owners
- 3. Control the Commitment Stages
- 4. Verify Receipt and Invoice Before Payment
- 5. Measure Purchase Order Cycle Time
- 6. Work Through a Hypothetical Cycle Time Example
- 7. Choose the Right System Approach
- 8. Tighten the Cycle With a Practical Pilot
- Frequently Asked Questions
- How OpsMavix Can Help
1. Understand What the Purchase Order Cycle Is
A definition you can use
The purchase order cycle is the controlled chain of steps between deciding to buy something and closing the record of that purchase. Many finance teams call the same chain procure-to-pay, because it begins with procurement and ends with payment. Some versions stop at payment; a complete version also closes the order, so it no longer counts as an open commitment.
If you are new to the document at the centre of the cycle, start with what a purchase order is. That guide explains the fields on a PO and how it differs from an invoice. This guide looks at the cycle as a whole: who owns each stage, what each stage must produce, and how to measure how long it takes.
Two halves with different risks
The cycle has two halves. The first half commits the business to spend: need, requisition, approval, order and supplier confirmation. The second half verifies and settles that commitment: receipt, invoice matching, payment and closure.
| Half | Stages | Main risk | Main control |
|---|---|---|---|
| Commit | Need to supplier confirmation | Buying the wrong thing or buying without authority | Requisition and approval before the order is sent |
| Verify and settle | Receipt to closure | Paying for goods that did not arrive or at the wrong price | Receipt against the order and matching before payment |
The seam between those halves is where errors are hardest to see. What was ordered, what arrived and what was billed are often recorded by three different people in three different places.
What the cycle is not
The cycle is not the same as supplier lead time, which is only the stretch from placing an order to having the goods available. It is also not the same as the payment run, which is one step near the end. Treating either as “the cycle” hides the internal delays before the order and after the delivery.
2. Map the Nine Stages and Their Owners
The stages at a glance
Most businesses run some version of the nine stages below. Small teams may combine stages, and some add supplier selection or quotation, but the logic stays the same.
| # | Stage | Typical owner | Output | Exit rule |
|---|---|---|---|---|
| 1 | Need identified | Requester or stock rule | Stated requirement | Need checked against stock and open orders |
| 2 | Requisition | Requester | Purchase requisition | Item, quantity, reason and estimated cost recorded |
| 3 | Approval | Budget holder | Approved requisition | Approver has authority for the value and budget |
| 4 | PO raised | Buyer | Numbered purchase order | Linked to the approved requisition |
| 5 | PO sent and confirmed | Buyer | Supplier acknowledgement | Price, quantity and date confirmed or queried |
| 6 | Goods received | Receiving team | Goods received note | Counted and checked against the PO lines |
| 7 | Invoice matched | Accounts payable | Matched or exception invoice | Order, receipt and invoice agree within tolerance |
| 8 | Payment | Finance | Payment record | Paid on agreed terms after a passed match |
| 9 | Closure | Buyer or finance | Closed PO | Nothing outstanding to receive, bill or credit |
Give every stage an exit rule
An exit rule is the condition that must be true before the next stage can start. It is more useful than a description of the stage, because it can be checked. “Approval” is vague; “approved by a named person whose limit covers the value” can be tested.
Write the exit rules down before choosing software. They become the requirements for any system you use, whether that is a configured accounting module, a packaged tool or a focused application.
Owners and handoffs
Each handoff between owners is a place where the cycle can stall. A requester hands to an approver, an approver hands to a buyer, a buyer hands to receiving, and receiving hands to accounts payable. The table makes those handoffs visible, which is the first step to measuring them.
3. Control the Commitment Stages
Need and requisition
The need stage looks simple, but it is where duplicate orders begin. If nobody can see stock on hand and orders already on the way, a second order is easy to raise. A reorder point that checks open orders reduces that risk.
The requisition turns an informal need into an internal request. It is not a commitment to a supplier. The difference matters, and it is explained in purchase requisition vs purchase order. For a step-by-step view of the request stage, see the purchase requisition process.
Approval
Approval is the first hard control. It should be routed by value and budget, recorded against the specific request and impossible to bypass when the PO is raised. An approval given as a one-word email reply is hard to link to a specific order later. Routing rules, thresholds and audit trails are covered in the purchase requisition approval workflow guide, and the cost of slow purchase approvals breakdown shows how waiting time can be priced.
Raising, sending and confirming the PO
The PO is the reference every later stage is checked against, so errors on it travel downstream. A wrong quantity on the order becomes a wrong delivery and then an invoice that appears to “match” the mistake.
Sending is not the same as confirmation. Record whether the supplier has acknowledged the price, quantity and delivery date. Without that, the first sign of a problem is often a delivery that does not arrive. A purchase order tracking system keeps each open order and its status visible, and supplier order management software covers the wider inbound side.
Commitment stage checklist
- Check stock and open orders before raising a request.
- Record item, quantity, reason and estimated cost on the requisition.
- Route approval by value and budget, with a named approver.
- Prevent a PO being issued without a linked approval.
- Use one unique, sequential PO number per order.
- Record the supplier acknowledgement or query against the PO.
4. Verify Receipt and Invoice Before Payment
Goods received
Receiving is the cycle’s reality check. The team counts what arrived, checks condition and records shortages or damage against the PO lines. That record is usually a goods received note. Our guides to the goods received note and the goods receiving process cover the detail.
Timing matters. A receipt recorded days later from memory or a delivery note is a reconstruction, not a check.
Invoice matching
Before payment, accounts payable compares the purchase order, the goods receipt and the supplier invoice. When all three agree within an agreed tolerance, the invoice can be approved. When they do not, the difference becomes an exception with an owner. The mechanics are explained in three-way matching, and 2-way vs 3-way matching explains when the receipt check is worth adding.
| Match result | Typical cause | Action |
|---|---|---|
| All three agree | Correct order, delivery and invoice | Approve for payment on the agreed terms |
| Invoice quantity above receipt | Short delivery billed in full | Hold and request a credit or the missing goods |
| Invoice price above PO | Price change not agreed on the order | Hold and confirm with the buyer |
| No receipt recorded | Goods not arrived or not booked in | Check with receiving before any payment |
| Duplicate invoice reference | Same invoice submitted twice | Reject the duplicate |
Payment terms
Payment should follow a passed match, on the agreed terms. In the UK, GOV.UK guidance on late commercial payments says an agreed payment date must usually be within 60 days for business transactions, or 30 days for public authorities, although a longer business period can be agreed if it is fair to both businesses. Where no date is agreed, payment is late 30 days after the customer receives the invoice or the goods or services are delivered, whichever is later. Statutory interest for business to business transactions is 8% plus the Bank of England base rate, unless the contract sets a different rate.
That is why a slow match is not just an administrative delay. If exceptions are not resolved in time, a business can end up choosing between paying an unverified invoice and paying late.
Closure
Close each PO once everything is received, billed, credited and paid, or once any remaining balance has been formally cancelled. Unclosed orders make the open-order list unreliable, which feeds straight back into stage 1 of the next cycle.
Paper records make it hard to see when each stage started and finished. Illustrative photograph, not an OpsMavix project.
Image credit: Wesley Tingey, Unsplash License. No edits.
5. Measure Purchase Order Cycle Time
Decide which clock you mean
“Cycle time” means different things to different teams. Agree the start and end events before reporting a number.
| Measure | Starts | Ends | What it tells you |
|---|---|---|---|
| Request to PO | Requisition submitted | PO issued | Speed of internal approval and buying |
| PO to receipt | PO issued | Goods received note recorded | Supplier lead time plus booking-in delay |
| Receipt to match | Goods received note recorded | Match passed | Invoice arrival, accounts payable and exception handling speed |
| Match to payment | Match passed | Payment made | Mostly agreed payment terms and payment runs |
| Payment to closure | Payment made | PO closed | Housekeeping discipline |
| Need to closure | Need recorded | PO closed | The whole cycle end to end |
Separate internal delay from agreed time
Not all elapsed time is a problem. Supplier lead time depends on the supplier and the goods, and is covered in supplier lead time management. Waiting until the agreed payment date is normal practice, not a delay. Report those stretches separately so they do not hide the internal waits you can actually reduce: approval queues, unbooked deliveries and unresolved exceptions.
Use median and spread, not only the average
A few stuck orders can pull an average a long way. Report the median as well as the mean, and show the share of orders that met a target you have set. Use timestamps the system records when a status changes. Times typed in later from memory are not reliable enough to manage against.
Useful supporting measures
- First-time match rate: share of invoices that pass the match without an exception.
- Open orders past their expected delivery date.
- Orders received and paid but not closed.
- Exceptions older than an agreed number of days, by owner.
Counting the effort per order is a separate exercise, covered in what it costs to process a purchase order.
6. Work Through a Hypothetical Cycle Time Example
One order from need to closure
This example is hypothetical. All dates, quantities and prices are illustrative and exclude VAT. A wholesaler needs 400 units of a packaging item at £3.20 each, so the PO value is 400 × £3.20 = £1,280.00. The supplier’s agreed terms are 30 days from invoice. Days are calendar days counted from day 0, when the requisition is submitted.
| Event | Day | Stage elapsed |
|---|---|---|
| Requisition submitted | 0 | - |
| Approved | 3 | 3 days |
| PO issued | 4 | 1 day |
| Supplier acknowledgement | 6 | 2 days |
| Goods received: 380 of 400 units | 15 | 9 days |
| Invoice received for 400 units | 17 | 2 days |
| Credit note received, match passed | 24 | 7 days |
| Payment made | 47 | 23 days |
| PO closed | 50 | 3 days |
The receiving team recorded 380 units. The invoice billed 400, so the match flagged a 20 unit difference: 20 × £3.20 = £64.00. After the credit note, the amount payable was £1,280.00 - £64.00 = £1,216.00, which equals 380 × £3.20.
Read the result by stage
| Measure | Calculation | Days |
|---|---|---|
| Request to PO | 4 - 0 | 4 |
| PO to receipt | 15 - 4 | 11 |
| Receipt to match | 24 - 15 | 9 |
| Match to payment | 47 - 24 | 23 |
| Payment to closure | 50 - 47 | 3 |
| Need to closure | 4 + 11 + 9 + 23 + 3 | 50 |
The 9 days from receipt to a passed match include 2 days waiting for the invoice and 7 days resolving the short delivery. Payment on day 47 is exactly 30 days after the invoice on day 17, so it is on the agreed terms rather than a delay.
Of the 50 days, 11 are mainly supplier lead time and 23 are agreed payment terms. That leaves 50 - 11 - 23 = 16 days of internal handling: 4 to raise the order, 9 from receipt to a passed match and 3 to close. Those 16 days are what the business can influence directly.
Compare a small batch
Now take six hypothetical orders with request to PO times of 1, 2, 2, 3, 4 and 12 days. The mean is (1 + 2 + 2 + 3 + 4 + 12) ÷ 6 = 24 ÷ 6 = 4.0 days. The median is the average of the two middle values, (2 + 3) ÷ 2 = 2.5 days. Against a 3 day target, 4 of the 6 orders met it, which is 66.7%.
The one 12 day order raises the mean well above the median. That is the order to investigate first: was the approver absent, was the budget unclear, or was the request incomplete?
7. Choose the Right System Approach
Match the tool to the gap
The right approach depends on which stage fails, the volume of orders and how many systems the cycle touches.
| Approach | Where it can fit | Limitations to check |
|---|---|---|
| Email and spreadsheets | Low volume with one or two people buying | No enforced sequence, weak audit trail, manual timestamps |
| Configure current accounting software | Its purchasing features already cover approval and matching | Edition limits, receiving on site, approval routing depth |
| Packaged PO or procurement software | Standard approval and ordering workflows fit well | Fit with stock and receiving, integration effort, subscription cost |
| Focused custom application | A specific gap, such as receipt to match, has clear boundaries | Build, support and maintenance responsibility |
| Full ERP, packaged or custom | Purchasing, stock, production and finance need one data model | Implementation scope, data migration, change management |
Packaged tools can be a good fit when your process matches their workflow. Ask each supplier to demonstrate your own hypothetical order, including a short delivery and a price difference, rather than a clean example.
For buying guides, see purchase order software, purchase order management software and a purchase order system for small business. Manufacturers who need orders linked to works orders can read about manufacturing PO tracking.
Questions to ask any option
- Can a PO be issued without a linked approval?
- Is the goods receipt recorded against PO lines, including part deliveries?
- Does the match use the receipt, not just the order and invoice?
- Are status changes timestamped automatically?
- Can exceptions be assigned, aged and reported by owner?
- Are orders closed automatically or flagged when complete?
8. Tighten the Cycle With a Practical Pilot
Start with evidence
Pick 20 to 30 recent orders and record the timestamps you can find for each stage. Gaps in that evidence are themselves a finding. Identify the stage with the longest internal wait and the stage with the most exceptions.
Pilot one supplier group
Choose one supplier group or one site. Agree the exit rules, set targets for the internal stages and run the new process for a fixed period. Compare the median and spread with the baseline, not just the average.
Pilot checklist
- Exit rules written for all nine stages.
- Named owner for each stage and each exception type.
- Approval linked to every PO.
- Receipts recorded against PO lines on the day of delivery.
- Match tolerances agreed by finance.
- Exceptions aged and reviewed weekly.
- Received and paid orders closed within an agreed number of days.
- Cycle time reported by stage with median, mean and share within target.
Expand only when the pilot shows the controls work on partial deliveries, price differences and credits, not just on clean orders.
Frequently Asked Questions
What is the purchase order cycle?
It is the sequence of steps from identifying a need to closing the purchase order: requisition, approval, order, supplier confirmation, receipt, invoice matching, payment and closure. Each step controls a specific risk before money leaves the business.
Is the purchase order cycle the same as procure-to-pay?
They describe the same chain. Procure-to-pay is the name often used by finance teams. Some definitions end at payment, while a complete purchase order cycle also includes closing the order.
How do you measure purchase order cycle time?
Agree start and end events for each stage, capture timestamps when statuses change and report each stage separately. Show the median and the share of orders within target, as well as the average.
What is a good purchase order cycle time?
There is no universal figure. It depends on the goods, supplier lead times and agreed payment terms. Set targets for the internal stages you control, such as request to PO and receipt to match, and track improvement against your own baseline.
Why should supplier lead time be reported separately?
Supplier lead time is largely driven by the supplier and the goods. Mixing it with internal waits hides approval queues and matching delays that your own team can reduce.
What happens if the invoice does not match the order or receipt?
The invoice should be held as an exception with an owner. Depending on the cause, the business requests a credit, confirms a price change or checks whether goods were received before approving payment.
Do small businesses need the full cycle?
The stages still happen at small scale, but one person may own several of them. The important point is that approval happens before the order and the invoice is checked against the order and the delivery before payment.
Can OpsMavix build a purchase order system?
Yes. OpsMavix can build focused applications or a full custom ERP, and can configure or integrate suitable existing tools where those approaches fit the requirements.
How OpsMavix Can Help
OpsMavix can map your purchase order cycle stage by stage, measure where internal time goes and define the controls each handoff needs.
That may involve configuring the tools you already use, adding invoice approval workflow automation, connecting purchasing to a wholesale order management system or an inventory automation system, or linking materials to works orders with manufacturing production tracking.
Contact OpsMavix with one recent purchase order, the records behind it and the handoff that creates the most rework. We can use that evidence to define requirements and a practical pilot.
Keep reading
Getting value from OpsMavix? Add us as a preferred source on Google — you'll see more of our operations content in your AI Overviews, AI Mode and Search.