The Procurement Process: Stages & Best Practices

Every purchase your organisation makes travels through a process, whether or not anyone has written it down. When that process is clear and connected, buying is fast, controlled and easy to audit. When it is not, requests stall, invoices go astray and money leaks through the gaps. This guide walks through the procurement process one stage at a time, from the first sign of a need to the final record, with a text flowchart of the flow, the best practices that matter at each step, who owns what, and how software ties the stages together.

What is the procurement process?

The procurement process is the structured sequence of steps an organisation follows to acquire the goods and services it needs. It begins the moment someone recognises a need and ends only once the supplier has been paid and the transaction has been recorded for the next audit. In between sit sourcing, evaluation, negotiation, ordering, receipt and reconciliation. Taken as a whole, this cycle is often called source to settle, and it is the operational heart of any procurement function.

It helps to separate the process from the wider discipline. Procurement as a subject covers strategy, categories, supplier relationships and measurement; our complete guide to procurement covers that ground in full. The process is the practical machinery underneath it, the actual route a purchase takes through your organisation. Getting that route right is what turns good intentions into controlled, repeatable buying. You can read the formal definition of procurement for the broader context, but the value lives in how well the stages connect in practice.

The procurement process flow at a glance

Before we examine each stage in detail, it helps to see the whole flow. Picture it as a text flowchart, reading left to right, with each box passing its output to the next:

Identify need -> Purchase requisition -> Requisition approval -> Supplier sourcing -> RFx (RFI, RFQ or RFP) -> Bid evaluation -> Negotiation -> Purchase order -> Order acknowledgement -> Goods or service receipt -> Three-way match -> Invoice approval -> Payment -> Record and close.

Two things stand out when you lay the flow out this way. The first is that approval gates sit between stages, not inside them: a requisition has to be approved before sourcing begins, and an invoice has to clear the match before payment is released. The second is that the flow is a loop rather than a straight line. The record created at the end feeds the spend analysis that shapes the next need, so a well-run process gets smarter each time round. Where the boxes are joined by a system rather than by email, the output of one stage becomes the input of the next automatically, which is the whole promise of e-procurement.

The stages, from need to record

Here is the full sequence in one place, with the purpose of each stage and the artefact it produces. Use it as a reference map for the sections that follow.

Smaller, low-value buys often collapse several of these stages: a routine reorder from an approved supplier may skip sourcing and RFx entirely. Larger or riskier purchases run the full sequence, sometimes twice, as an early RFI narrows the field before a formal RFP. The art is matching the depth of process to the value and risk of the buy, rather than forcing every purchase down the same long road.

Best practices at each stage

Each stage has a handful of habits that separate a smooth process from a painful one. These are the ones that repay the effort most reliably:

• Identify need. Define the requirement in outcome terms, not brand names, so sourcing stays competitive and you buy what solves the problem rather than what someone happened to remember.
• Requisition. Capture the budget code, quantity and delivery date up front, so approvers have everything they need and nothing bounces back for missing detail.
• Sourcing. Keep a maintained supplier list and check existing contracts first; the cheapest sourcing event is the one you do not have to run because an approved supplier already covers the need.
• RFx. Ask every supplier the same structured questions, so responses are genuinely comparable rather than a pile of differently shaped documents.
• Evaluation. Agree the scoring criteria and their weights before the bids arrive, which keeps the decision objective and defensible.
• Negotiation. Negotiate total value, not just headline price; payment terms, warranties and service levels often move the number more than a unit discount.
• Purchase order. Raise the PO only against an approved requisition and budget, so no commitment is made that has not been signed off.
• Receipt. Record what actually arrived, in full, at the point of delivery, because an accurate receipt is what makes the later match trustworthy.
• Payment. Pay to terms rather than early or late, protecting cash flow while keeping suppliers onside.

None of these are complicated. What makes them hard in practice is consistency: a best practice applied to some purchases and skipped on others creates the exact blind spots it was meant to close. The goal is to make the good habit the default path, so following it is easier than working around it.

The three-way match, explained

Of all the stages, the three-way match is the one most worth understanding, because it is the control that protects your organisation from paying for things it did not order or receive. The match compares three documents before any money moves: the purchase order (what you agreed to buy), the goods received note (what actually turned up) and the supplier invoice (what you are being asked to pay). When all three agree on quantity and price, the invoice clears automatically. When they do not, the mismatch is flagged as an exception and held for a human to review.

Done by hand, matching is slow and thankless, which is why so many teams wave invoices through and hope. Done by software, it is instant and exhaustive: every line is checked, only the genuine exceptions reach a person, and duplicate or inflated invoices are caught before they are paid. It is one of the clearest examples of a process control that pays for itself.

Roles: who owns each stage

A process only runs smoothly when it is clear who is responsible at each point. The exact titles vary with the size of the organisation, but the responsibilities are consistent.

In a small business one person may wear every hat, and the process still works as long as the stages are kept distinct in their head. In a larger organisation the value of naming roles is that handoffs become explicit: everyone knows what they receive, what they are expected to do with it and who they pass it to next. Where those handoffs are vague, work stalls in the gaps between people, which is where most delay in a manual process actually hides.

How software connects the stages

The single biggest determinant of how well a procurement process runs is whether the stages are connected. In a manual setup, each stage lives in its own tool: requisitions in email, sourcing in spreadsheets, orders in an accounting package, receipts on paper and invoices in a filing tray. Information is re-keyed at every boundary, which is slow and error-prone, and no one can see the whole flow at once.

A procurement platform closes those gaps by making each stage feed the next. An approved requisition becomes a sourcing event with one click. A winning bid becomes a draft purchase order with the agreed prices already populated. A recorded receipt lines up automatically for the match, and a cleared invoice schedules itself for payment on terms. Because everything lives in one connected record, the audit trail builds itself as work happens rather than being reconstructed afterwards. This is the practical difference a system such as ProcureWave makes: not a new process, but the same process with the friction and the blind spots removed.

Connection also changes what the process can tell you. When every stage writes to one place, you can see where requests are stuck, how long each stage takes, and where spend is going, in real time rather than in a quarterly report assembled by hand. That visibility is what lets a process improve rather than merely repeat, and it draws on decades of thinking about strategic sourcing and electronic procurement to turn a sequence of tasks into a source of insight.

Where the process breaks, and how to fix it

Even a well-designed process develops predictable weak points. Knowing where they appear makes them far easier to prevent. Approval bottlenecks are the most common: a requisition sits in someone's inbox for days because approval depends on one person being at their desk. The fix is clear routing rules and delegated approvers, so work never waits on a single individual. Maverick spend is the next: purchases made outside the process, off-contract and unseen, which undermine every downstream control. The cure is convenience, making the compliant path the fastest one, so no one is tempted to go around it.

Weak receiving is a quieter problem but a costly one, because a sloppy goods receipt breaks the three-way match and lets invoice errors through. Poor data is the last: duplicate suppliers, inconsistent categories and missing contract dates make the closing record untrustworthy and the next spend analysis unreliable. All four share a root cause, which is stages that are disconnected and unmonitored. Bodies such as the Chartered Institute of Procurement and Supply publish standards that codify good process for exactly this reason: consistency, visibility and clear ownership are what keep the weak points from opening up in the first place.

Getting the process working for you

A good procurement process does not have to be elaborate to be effective. It needs to be clear, consistent and connected, with each stage owned by someone, each handoff explicit, and each control actually applied. Start by mapping your current flow against the eleven stages above and marking where purchases genuinely stall or leak. Fix the worst gap first, prove the improvement on one high-volume category, then extend the same discipline outward. Most organisations find that connecting the stages, so information flows once and stays visible, delivers more value than any single negotiation.

If your process today runs on email threads and spreadsheets, the fastest gain is usually to bring the stages onto one platform so they hand off cleanly. See how ProcureWave connects the whole flow from requisition to payment, or talk to our team to walk through your own process and find where the friction is hiding. The process rewards the organisations that treat it as a discipline: map it, connect it, measure it, and let each cycle make the next one better.

Frequently asked questions

What are the main stages of the procurement process?

Most organisations follow a recognisable flow: identify a need, raise a requisition, source and approach suppliers, run an RFx, evaluate bids, negotiate, issue a purchase order, receive the goods, run a three-way match, pay the invoice and keep the record. The labels vary between companies, but the sequence stays broadly the same.

What is the difference between the procurement process and a purchase order?

The purchase order is a single stage inside the wider process. Procurement covers everything around it, from spotting the need through sourcing and negotiation to receipt and payment. The order is simply the formal commitment to buy once the earlier stages are complete. For a step by step walkthrough, see our procurement steps guide.

What is a three-way match?

A three-way match compares the purchase order, the goods received note and the supplier invoice before payment is released. If all three agree on quantity and price, the invoice is cleared. If they do not, the exception is flagged for review, which stops overbilling and duplicate payments.

How does software improve the procurement process?

Software connects the stages so information passes from one to the next without re-keying. A requisition becomes a sourcing event, an approved bid becomes an order, and a receipt feeds the match automatically. The result is faster cycles, fewer errors and a complete audit trail across the whole flow.