Purchase Order Process: The 9 Steps From Requisition to Payment

The purchase order process is the sequence a business follows to formally buy goods or services. Someone raises a purchase order request, the request is approved as a requisition, a purchase order is created and issued to the supplier, the supplier confirms and delivers, the goods are received and recorded on a goods received note, the invoice is matched three ways against the PO and the GRN, payment is released, and the PO is closed.

TL;DR / Key Takeaways:

• The purchase order process runs in nine steps: requisition, RFQ, vendor selection, PO issue, delivery and goods receipt, invoice check, payment, record keeping, and closure.
• The PO, not the requisition, is the legally binding commitment. Issuing one before approval is the most common control breach in the whole cycle.
• Every PO needs a unique number, line-item detail, agreed price, delivery date, and payment terms. Vague POs are what invoice disputes are made of.
• Partial deliveries need a partial GRN and an open PO balance. Close the PO early and you lose the outstanding quantity.
• Three-way matching (PO + GRN + invoice) is the step that stops overpayment and duplicate payment.
• Amendments have to be versioned and re-approved. A PO changed over email breaks the audit trail.
• Automation compresses the cycle from weeks to days and gives finance the open-PO commitment data it needs for cash forecasting.

Purchase orders do not get much attention outside procurement. But if you manage spend for a living, you already know a PO is more than paperwork. Done properly, it is the one document that tells you what was bought, who approved it, at what price, and on what terms, months after everyone involved has forgotten the conversation.

The problem is that plenty of companies still run purchases on scattered emails, a shared spreadsheet, and a verbal nod in the corridor. That produces untracked spend, approvals nobody can find, and suppliers working from terms that expired two quarters ago. A 2023 Ivalua survey found that 53% of procurement and supplier management processes are still not digitized, and that teams lose 22% of their working time chasing paper trails and correcting manual errors.

This guide is the blueprint for fixing that. It covers what a purchase order is, how the purchase order process flow actually runs, the nine steps in order, what changes when you automate, and the metrics that tell you whether the process is working. If you are new to the wider discipline, start with our guide to what procurement is and then come back here.

What Is a Purchase Order?

A purchase order is a legally binding document sent from a buyer to a supplier that confirms what is being bought, how much of it, at what price, and under what terms, before anything changes hands. Once the supplier accepts it, both sides are bound to it.

That is what separates a PO from an email saying “go ahead”. The PO is enforceable, it is numbered, and it sits in the middle of the wider procurement process as the point where intent becomes commitment. Every PO number you issue becomes the thread that ties the requisition, the delivery, the invoice, and the payment together.

What Goes Into a Well-Structured Purchase Order

The best POs leave nothing to interpretation. At minimum, include:

• A unique PO number so the order can be traced end to end
• Item descriptions and quantities specific enough to prevent scope creep
• Pricing and payment terms that match the contract and the budget line
• Delivery dates and locations so supply planning and receiving both work off the same date
• Shipping and packing instructions for accurate fulfilment
• Quality specs or SLAs where the deliverable is a service or a made-to-order item
• Dispute resolution clauses so exceptions are handled by a rule, not a phone call

Get those fields right and the PO stops being an ordering document. It becomes the reference your finance team uses at audit, the record that settles a purchase order vs invoice argument, and the evidence that a purchase followed policy. If you are still deciding whether a request should even become a PO, our comparison of purchase requisition vs purchase order draws the line clearly.

Quote to retain on page: “POs are not paperwork, they are legally binding commitments. Treat them with the respect they deserve.” – Tim Cummins, IACCM President.

What Is the Purchase Order Process?

The purchase order process, sometimes called the purchase order cycle, is the workflow procurement teams use to request, approve, issue, track, receive, match, pay, and close purchase orders. It exists to make sure every purchase is budget-checked, vendor-approved, and contractually aligned before money is committed.

Think of the PO as the GPS for a purchase. It sets the route, records where the order is, and leaves a log you can replay later. The surrounding procurement workflow is what keeps that route consistent across departments so a marketing laptop order and a factory raw-material order follow the same rules.

POs are not paperwork—they’re legally binding commitments. Treat them with the respect they deserve.

– Tim Cummins

[IACCM President]

The Purchase Order Process Flow, Stage by Stage

Here is the purchase order process flow in table form. Every stage produces a record, and that record is what the next stage depends on.

That flow sits inside the broader procure-to-pay process. The PO process covers the ordering half. Procure-to-pay carries it all the way to settlement and reconciliation.

Manual Purchase Order Process vs. an Automated PO Process

Most teams do not fail at the purchase order process because they do not know the steps. They fail because the steps live in different tools. Here is what actually changes when the same process runs in a system:

If you want the technical side of that shift, our guide to an automated purchase order system covers what to configure first, and the procurement automation guide widens the lens to the rest of the function.

What a Strong Purchase Order Procedure Actually Buys You

A well-run PO procedure does more than keep procurement tidy. It changes what leadership can see and how fast the business can move. Six things happen once the procedure holds:

1. It Stops Unapproved Spending Before It Starts

Maverick and off-contract buying is still the biggest leak in most procurement functions. A PO procedure that requires approval before the commitment is your first line of defence. It catches budget overruns while they are still requests, and it makes policy deviations visible in real time rather than at quarter end.

Zapro insight: connect your PO data to spend analytics so price jumps and duplicate requests get flagged the moment they appear.

2. It Makes Approvals Faster and More Predictable

Unclear ownership is what stalls approvals, not the number of approvers. A defined purchase order procedure names who signs off at each threshold, so nothing sits in an inbox waiting for someone to decide whether it is theirs. Pre-approved vendor catalogs and PO templates cut the cycle further, which is where catalog management in procurement earns its keep.

3. It Keeps You Audit-Ready All Year

Every PO logs who asked for what, when it was approved, and on what terms. That history is the difference between a two-day procurement audit and a two-week one. Digital signatures and automatic time stamps make each record defensible on its own, without anyone reconstructing the story from memory.

4. It Gives Your Team Its Week Back

Chasing orders and matching invoices by hand is a full-time job nobody was hired to do. Automating it frees the team for supplier development and cost work. The Hackett Group puts the gap at 21% lower operating cost for procurement teams that automate and standardise, which shows up directly in procurement savings.

5. It Reduces Supplier and Delivery Risk

A PO that states quantity, date, spec, and price removes the ambiguity that disputes grow in. Attach the relevant contract terms and product specs to the order itself, and both sides are working from one document. Live purchase order tracking then tells you about a late delivery before the requester does.

6. It Improves Forecasting and Financial Control

Every open PO is committed spend that has not been invoiced yet. Finance needs that number to forecast cash properly, and most manual processes cannot produce it. Sync PO data with your ERP and you get a rolling commitment view. Our guide to integrating procurement with ERP and financial systems covers how that connection is usually built, and procurement and finance covers who owns what once it is live.

The 9 Steps of the Purchase Order Process

These are the purchase order process steps in the order they run. Each one has a failure point, so I have called those out as we go.

Step 1: Raise the Purchase Order Request and Turn It Into a Requisition

Everything starts with a purchase order request. A department submits what it needs with item specs, a business justification, quantity, and a required-by date. Good purchase requisition software validates that request against approved vendors, budget thresholds, and historical pricing before it ever reaches an approver, so the purchase order creation process starts from clean data.

Failure point: free-text requests. “Two laptops, the usual spec” becomes a dispute three weeks later. Use structured fields. If your requests still arrive by email, our template for a purchase request email will at least make them consistent, and automating the requisition to order process shows what replacing them looks like.

Step 2: Run the Budget Check and Send Out RFQs

Before sourcing starts, the request is checked against the budget and the policy for that category. Once it clears, non-catalog purchases go out to several suppliers as requests for quotation so you can compare price, lead time, and terms side by side rather than accepting the first number you are given.

Failure point: skipping the RFQ for anything urgent. Urgency is exactly when single-sourcing costs the most. Set a value threshold that makes competitive quoting mandatory and template the RFQ so it takes minutes, not hours.

Step 3: Analyse the Quotes and Select a Vendor

Score the quotes on total cost rather than unit price: lead time, payment terms, freight, warranty, and past performance all belong in the comparison. For new suppliers, run due diligence before the award, not after. Supplier scorecards kept inside your PO system make this an objective decision you can defend later, and they feed straight into procurement analytics.

Failure point: awarding on price alone. A supplier who is 4% cheaper and two weeks slower is not cheaper.

Step 4: Negotiate the Terms and Issue the Purchase Order

With the vendor chosen, settle final terms, especially on high-value or strategic buys, then create and issue the PO. This is the purchase order creation process proper: the approved requisition becomes a numbered, versioned order carrying delivery dates, pricing, payment conditions, and any special clauses. Where a master agreement already exists, the PO should inherit its terms rather than restate them, which is why the procurement contract guide is worth reading alongside this step.

Failure point: issuing the PO before approval is complete because the supplier needs it today. That single habit undoes the entire control. If your approvals are too slow to survive real urgency, fix the routing, not the rule.

Step 5: Receive the Goods or Services and Log the Acknowledgement

The supplier confirms receipt of the PO and agrees the delivery date. On arrival, quantity and condition are checked against the order and a goods received note is recorded. For services, the equivalent is a signed-off milestone or timesheet. Where stock is involved, the receipt should also update your purchase order inventory management system so on-hand quantities stay true.

Failure point: partial deliveries. Book the quantity actually received, leave the balance open on the PO, and never close the order to tidy the list. Closing early is how the outstanding balance disappears from everyone’s view.

Step 6: Receive and Check the Invoice (Three-Way Match)

When the invoice arrives, match it against the PO and the GRN. Quantities, prices, and line items all have to agree. This three-way match is what stops overbilling, duplicate payment, and paying for goods that never arrived. Discrepancies should route to an exception queue with a named owner and a deadline, not sit in an inbox. If you also handle spend that arrives without an order, our breakdown of PO invoice vs non-PO invoice explains how to treat both without weakening the control.

Failure point: tolerance limits nobody agreed on. Decide in advance what variance passes automatically, at what value, and who approves the rest.

Step 7: Authorise the Invoice and Pay the Vendor

Once the match clears, the invoice goes for payment approval. Keep the approval role-based and automated so it does not depend on one person being at their desk. Payment is then scheduled to the agreed terms. Paying early costs you working capital; paying late costs you the relationship and sometimes the discount. Teams that want to shorten this end of the cycle usually start with procure-to-pay automation or a dedicated purchase order invoice software.

Step 8: Keep the Records for Compliance and Audit

Archive everything the order produced: the requisition, the RFQs and quotes, the PO and its amendments, the GRN, the invoice, and the payment record. Keep them together against the PO number, tagged so retrieval takes seconds. That archive is what makes procurement compliance provable rather than assumed.

Failure point: amendments handled informally. If a price or quantity changes, version the PO and re-approve it. A PO amended over email cannot be audited, because the document no longer matches what was agreed.

Step 9: Close the Purchase Order and Improve the Process

Once delivery, matching, and payment are all complete, formally close the PO. Then use the data: cycle time by stage, first-time match rate, on-time delivery by supplier, and the value of the open PO book. Feed it into your dashboards and review it monthly. This is the step most teams skip, and it is the one that turns a purchase orders process into a system that gets better rather than one that just repeats. Our list of procurement KPIs and the guide to procurement reporting will tell you which numbers are worth putting in front of leadership.

Sales and Purchase Order Processing: The Same Transaction From Both Sides

Your purchase order is your supplier’s sales order. Same transaction, two systems, two sets of paperwork. Understanding both sides is what people usually mean by sales and purchase order processing, and it explains most of the friction in the middle.

• On your side: the PO commits budget, creates an obligation, and sets the expectation for what arrives and when.
• On their side: your PO becomes a sales order that triggers production or picking, allocates stock, and eventually generates the invoice you will match.

When the two do not line up, it is almost always because the buyer’s PO and the seller’s order acknowledgement disagree on a date, a quantity, or a part number. Insist on an acknowledgement that quotes your PO number back to you, and reconcile any difference before the goods ship rather than after the invoice lands.

The stretch from raising a need to placing the order is sometimes described as procure to order, with procure to pay covering the rest through to settlement. If you are mapping where one ends and the other begins, our comparison of procure-to-pay vs source-to-pay and the guide to optimizing requisition-to-pay cycles put the boundaries in one place.

Learn more about What is a PO and a Non-PO invoice?

The Financial Impact of Purchase Order Processing

Every purchase order carries more than the cost of the goods. It carries the cost of processing it. Manual purchase order processing is slow, error-prone, and expensive: paper approvals, email threads, and re-keyed data quietly drain margin without ever appearing as a line item.

According to APQC, manual processing can cost up to $506 per PO, while top performers bring it under $35 through automation and digital procurement tools. Multiply the gap by your annual PO volume and you have the business case in one line. Here is where that saving actually comes from:

1. Lower Processing Costs

Removing manual entry, printing, scanning, and physical storage takes the labour out of every order. Automated systems capture the data once and reuse it, so the marginal cost of the hundredth PO in a month is close to zero. Moving to a touchless PO-to-invoice flow with OCR and AI-based data capture is usually the largest single saving available.

2. Faster Cycle Times

Approval delay is the friction that everything else queues behind. With tiered approval logic, mobile sign-off, and automatic reminders, orders move from request to issued PO in hours instead of days. Shorter cycles mean shorter lead times, fewer rush shipments, and fewer late fees.

3. Fewer Errors, Better Data

Manual processes produce typos, mismatched line items, and blank fields that only surface at invoice stage. A digital PO system validates entries as they are typed and checks them against pre-approved contracts and price lists. The result is less rework, fewer invoice disputes, and suppliers who stop calling to ask what you meant.

4. Real Spend Visibility

Every PO raised through a system becomes searchable, analysable spend data. You can see committed versus actual spend by department, spot the categories drifting over budget, and find the same item being bought at three prices. That is the raw material for spend analysis in procurement and for any serious procurement strategy.

5. Stronger Compliance and Audit Readiness

Automation enforces policy by design. Approval routing, mandatory fields, vendor eligibility, and document retention all happen because the system requires them, not because someone remembered. That cuts audit preparation time and reduces the risk of a control failure being discovered by an auditor rather than by you.

Learn about Purchase Order Management Tools.

Pro Tips for a Tighter PO Procedure

Small habits separate a PO process that holds under pressure from one that quietly gets bypassed:

• Standardise the template. One PO format, mandatory fields enforced, so nothing ships with a missing delivery date.
• Set clear approval thresholds. Publish who approves what value, and make the thresholds match reality so people do not route around them.
• Keep a pre-approved vendor list. Most of your spend should be repeatable, and repeatable spend should not need a fresh sourcing exercise.
• Integrate with your ERP. Procurement and finance working from two versions of the same PO is where reconciliation time goes.
• Automate the alerts. Overdue deliveries, unmatched invoices, and POs open past their delivery date should find you rather than wait to be discovered.
• Review open POs monthly. An ageing open-PO report is the fastest way to find orders that were received but never closed.

For the longer version of this list, including approval design and exception handling, see our purchase order management best practices. Small teams working out where to start will get more from our roundup of the best purchase order software for small business, and if cash timing is the constraint rather than process, purchase order financing explains the options.

Zapro: Where Purchase Orders Become Strategic Tools, Not Paperwork

Most PO tools automate the paperwork and stop there. Zapro keeps the context: why a purchase was requested, what was said during approval, how the supplier has performed on the last ten orders, and what that means for the next one. Every PO sits inside the wider procurement software workflow rather than in a module of its own.

What that looks like day to day:

• End-to-end PO lifecycle: request, approval, issue, receipt, match, payment, and closure in one place
• Context-rich POs: emails, notes, attachments, and approval history attached to the order itself
• Smart approvals: routing that adapts to value, category, risk, and urgency instead of one fixed chain
• Automated three-way matching: AI reads the invoice, matches it to the PO and GRN, and flags only the exceptions
• Supplier catalog integration: buy from agreed catalogs at agreed prices, so the PO is right before it is raised
• Live spend and commitment data: open PO value, committed versus actual, and category trends without a report request
• Risk signals: alerts on unreliable or non-compliant vendors before a PO is issued, not after

The result is less time chasing signatures and clarifications, and more time on the work that changes numbers. If you want to see how AI handles the matching and exception steps specifically, read about AI in procurement, or compare platforms in our roundup of the best procurement software. Teams that want the ordering side only can start with cloud purchase order software.

The nine steps above compress from days to hours once approvals are automated. See the PO process in a demo, from request to payment, with approvals routed automatically, then check what that costs on our pricing plans.

Purchase Order Process FAQs

What is the purchase order process in simple terms?

It is the workflow a business uses to buy something formally: request, approve, order, receive, match the invoice, pay, and close. Nine steps in a full purchase order procedure, though smaller teams often combine sourcing steps for low-value, repeat purchases.

What are the steps in the purchase order process?

Create the purchase order request from a structured requisition, send RFQs, analyse quotes and select a vendor, negotiate and issue the PO, receive the goods and log the GRN, check the invoice with a three-way match, authorise and pay, keep the records, and close the PO with a performance review.

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

A requisition is an internal request to buy, routed for approval inside your organisation. A purchase order is the approved, formal document issued to the supplier, and it is the one that is legally binding.

What is the purchase order creation process?

It is the part of the cycle where an approved requisition becomes a numbered order: pull the vendor, pricing, and terms from the contract, add line items with quantity and delivery date, assign the PO number and cost centre, get final approval, and send it to the supplier with an acknowledgement request.

Why is a manual purchase order process a problem?

Manual processes scatter the record across inboxes and spreadsheets, so there is no single source of truth for what was ordered or approved. That produces duplicate orders, missed approvals, slow matching, and an audit trail that has to be rebuilt from scratch. It also costs up to $506 per PO against under $35 for automated top performers.

How does purchase order automation save time and money?

It removes re-keying, routes approvals automatically, prevents duplicate orders, matches invoices without line-by-line checking, and enforces policy at the point of entry. Teams typically cut PO cycle times by 30 to 50% and free up the hours previously spent chasing paperwork.

Can I track an order once the PO is issued?

Yes. A modern PO system gives real-time status on every open order, including acknowledgement, dispatch, partial receipts, and outstanding balance, so you can act on a delay before it becomes a shortage.

Is purchase order software worth it for small businesses?

For most small teams, yes. Once you have more than a handful of buyers or suppliers, the cost of untracked spend and duplicate orders overtakes the cost of the software. Look for per-user pricing, a simple approval builder, and accounting integration rather than enterprise sourcing features you will not use.

How do purchase orders help with compliance?

Every PO records who requested the purchase, who approved it, at what value, and under which terms, with a time stamp on each action. That gives auditors a complete, unbroken chain from request to payment and makes policy exceptions visible rather than buried.

What happens if a purchase order needs to change?

Amend the PO formally, version it, and route it back through approval at the level the new value requires. Send the amended version to the supplier and get a fresh acknowledgement. Never change an agreed PO by email alone, because the document and the agreement then no longer match.

Final Thoughts

A purchase order is not just a buying document. It is a control mechanism, a compliance record, and a clarity tool, and it works only when the process around it is consistent enough that people follow it under pressure.

If your team is still collecting approvals over email and tracking orders in a spreadsheet, the fix is not more discipline. It is a process where the discipline is built in. Zapro digitises and automates the full purchase order process in one platform, from the first request to a closed, archived PO. Start with a demo and see what your own PO cycle looks like when every step is connected.