Procurement Process: 8 Steps From Purchase Request to Payment

By Kirill Stolbushkin

Short answer: The procurement process is the sequence a company follows from a purchase request to paying the supplier. It runs in eight steps: requisition, budget approval, sourcing, vendor onboarding, negotiation and contract, purchase order, goods receipt with three-way match, and payment with supplier review. Requesters, budget owners, procurement, suppliers, and accounts payable each own part of it.

Most delays come from the handoffs between those people, not from the steps themselves. Ask five people in a company how buying works and you will often get five answers. The requester thinks it ends when they get approval. Accounts payable thinks it starts when the bill arrives. Procurement sees the middle. This guide walks the whole chain in order, so everyone can see where their part sits.

You will also see the process described in 7 steps, or 13. The middle is the same; guides just start and stop in different places.

What is the procurement process? Procurement vs purchasing vs procure-to-pay vs source-to-pay

The terms overlap, and people use them loosely:

• Purchasing is the transaction: raising the order and buying the thing.

• Procurement is wider. It includes deciding what to buy, choosing and vetting suppliers, negotiating terms, and managing the relationship over time.

• Procure-to-pay (P2P) is the end-to-end cycle that finance cares about, from the request to the payment, with the controls around money. It is one of the core finance processes, alongside order-to-cash and the close.

• Source-to-pay (S2P) adds the sourcing front end: finding suppliers, running quotes, and negotiating, all the way through to payment. The sourcing half on its own is often called source-to-contract.

This guide uses "procurement process" for the full eight steps. If you only need the front end, see the purchase requisition approval process.

The 8 procurement process steps at a glance

A procurement flow chart usually has five swimlanes: requester, budget owner, procurement, supplier, and accounts payable. Each step lands in one or two of them and leaves a document behind:

Want those eight steps as an editable swimlane diagram? Type your version into the free AI process mapper and you will have one to work from, no account needed.

Not every purchase goes through every step. A repeat order from an existing supplier under an existing contract skips steps 3 to 5. A one-off software subscription might skip the PO if your policy allows card purchases under a limit. Write those shortcuts down as part of the process, so they are rules and not workarounds. For how purchasing fits next to every other department's processes, see our business process examples by department.

Step 1: Identify the need and raise a requisition

Someone needs something: materials, a contractor, a laptop, a software tool. They submit a request through one agreed channel with what they need, why, roughly what it costs, and which budget pays for it. One entry point matters more than the form itself. Requests that arrive by chat, email, and hallway conversation are the first thing that breaks a procurement process.

Step 2: Budget check and approval

Someone confirms the budget has room and the right person approves the spend. How many approvers, at what amounts, and in what order is a design choice in its own right. The requisition guide linked above covers spend limits and approval chains in detail, so I will not repeat the matrix here. The one rule to keep in mind at this step: the approval decides whether to spend, not who to buy from.

Step 3: Sourcing and supplier selection

For anything beyond a routine repeat purchase, procurement finds suppliers and compares them. Small purchases might need one quote or none. Larger ones usually need several quotes, and big or strategic purchases may go through a formal request for quotation (RFQ) or request for proposal (RFP) with scoring criteria agreed in advance.

Write down the amounts that trigger each level: when one quote is fine, when you need three, and when a formal RFQ is required. Also decide who scores the bids. Having the requester alone pick the winner is a common gap.

Step 4: Vendor onboarding and due diligence

Before a new supplier can be paid, someone has to set them up. That means collecting company and tax details, payment details, insurance certificates or other documents your policy requires, and a named contact. For higher-risk suppliers, such as those handling your data or working on your sites, add the extra checks your policy calls for: security questionnaires, references, financial checks.

The person who adds a vendor should not be the person who approves payments to that vendor. Vendor setup is also a frequent target for payment fraud, so payment details always get a second check. Our guide to finance processes covers how to verify a payment details change.

Step 5: Negotiate and sign the contract

Once a supplier is chosen, someone agrees the price, payment terms, delivery terms, and service levels. For small purchases that is a short email. For larger ones it is a real negotiation, and it is worth deciding in advance who can agree what: a discount, a longer term, a change to payment terms.

Some purchases come with terms that matter: auto-renewals, liability caps, data handling, exclusivity, notice periods. Procurement should know which contracts go to legal and which can be signed under standard terms. A simple rule set works for most companies: anything over a set value, anything multi-year, and anything involving personal data gets legal review. Our post on legal and compliance workflows covers the contract side in more depth.

Step 6: Purchase order

The purchase order is the formal document that tells the supplier what you are buying, at what price, on what terms, and where to deliver. Once the supplier accepts it, you have a commitment. Issue the PO from the approved requisition, not from scratch, so the details match. If the final price has moved beyond the tolerance your policy allows, send it back for re-approval instead of quietly going ahead.

Many companies run a "no PO, no pay" rule: suppliers know an invoice without a PO number will not get paid. It only works if it is applied every time.

Step 7: Goods receipt and three-way match

This step runs in a fixed order:

1. The goods or services arrive, and the requester or the warehouse confirms what was received.

2. The supplier invoice comes in, quoting the PO number.

3. Accounts payable matches three documents: the purchase order (what you ordered), the goods receipt (what arrived), and the supplier invoice (what you are being charged).

4. If they agree within tolerance, the bill moves to payment.

5. If they do not, the bill goes on hold until the difference is resolved with the supplier or the requester.

For services, "receipt" is usually the requester confirming the work was done. Make that confirmation a defined step, or bills for services will sit waiting for someone to say yes. The approval routing for supplier bills, including bills without a PO, is covered in our invoice approval workflow guide.

Step 8: Payment and supplier review

AP schedules the payment according to the agreed terms and your payment run calendar. Procurement's work does not end there. For suppliers you use often or spend a lot with, run a periodic review: delivery on time, quality, pricing against the contract, and any issues raised. That review feeds back into sourcing decisions the next time around, which is what turns purchasing into procurement.

Procurement approval workflow: thresholds and segregation of duties

Procurement is a control as much as a workflow. As good practice, keep these duties with different people wherever you can:

• Requesting a purchase and approving it.

• Approving a purchase and choosing the supplier on your own.

• Setting up a vendor and approving payments to that vendor.

• Confirming receipt and approving the matching bill alone.

In a small company one person may hold two of these roles. When that happens, have someone else review their transactions monthly. Keep a record of who approved what, in whatever tool you use, so you can answer the question later. If you need to document these controls formally, our guide to SOX internal controls documentation explains what reviewers look for.

Where procurement stalls

The same few spots slow down procurement in most companies:

• Requests with missing information, which bounce back and forth.

• Approvers who are away, with no backup named.

• Vendor setup, waiting on documents from the supplier.

• Legal review queues, especially for low-risk contracts that did not need review.

• Services receipts, where nobody confirms the work was done.

• Mismatched bills, where PO, receipt, and invoice disagree and nobody owns fixing it.

Each of these is a handoff. A timer and a named backup fix most of them on paper before you automate anything.

How to measure the procurement process

A handful of measures tells you whether the process is working:

• Requisition-to-PO cycle time

• Approval time at each step

• Share of spend covered by a PO

• First-time three-way match rate

• Invoices on hold and how long they have waited

• Supplier on-time delivery

Procurement process by company size

1 to 49 employees

There is usually no procurement team. A founder or office manager buys, and finance pays. The steps that matter are a single request channel, a spend limit above which a founder approves, and a second person checking any new vendor before its first payment. Skip formal RFQs except for big purchases.

50 to 249 employees

Spend is spread across many people, so steps 1, 2, and 6 need real rules: one request form, approval by amount, and POs above a set value. Vendor onboarding becomes a defined process. Someone, often in finance or operations, becomes the de facto procurement owner. Name them.

250 employees and up

A dedicated procurement team is common. Sourcing rules, preferred supplier lists, contract review rules, and supplier reviews all become formal. The work is keeping the process consistent across departments and sites. Manufacturers will find more in our post on standardizing procurement workflows across sites.

How to make a procurement process flow chart: a worked example

Vevos is an AI-powered Playbook platform for operations leaders, team managers, and business analysts: describe a process in plain language or upload a document, and it generates a BPMN 2.0 process map and process documentation you can review, version, and export.

Going from the table above to a procurement flow chart your team has actually checked takes four moves. The company in this example is hypothetical.

Describe your version

Write your process in plain sentences. For example:

"An employee submits a purchase request with a budget line. The budget owner approves. Requests above the finance limit also go to the controller. Purchases above the quote limit need three quotes, collected by procurement. If the supplier is new, procurement collects their details and a second person calls them to confirm where payments should go. Contracts that auto-renew or exceed one year go to legal. Procurement issues the PO. The requester confirms delivery. AP matches the PO, receipt, and invoice. Mismatches go back to procurement. Matched invoices are paid on the next payment run."

Draw it automatically

Enter it in the free AI process mapper and Vevos builds a BPMN 2.0 diagram with lanes, gateways, and loops, and writes the process documentation to go with it. To start from your purchasing policy instead, upload the PDF or Word file in a free Intro account. The result should have the five lanes from the table above, gateways for amount, new supplier, and contract type, and a loop for mismatched bills.

The model is standard BPMN 2.0, so you can export it as XML for another BPMN tool, or as SVG, PNG, or PDF for the policy manual.

Check it against reality

Take five recent purchases: a routine reorder, a new supplier, a software contract, a rush order, and one that went wrong. Trace each one through the map. Every purchase should have a path. If the rush order does not, you need an emergency route with approval after the fact. Our guide to reviewing an AI-generated process model has a fuller checklist.

Decide what is next

Once the model is reviewed, it works as your documented procurement process. When you are ready for software, Conductor Agents on the Tempo plan take that reviewed model and build and deploy a purchase approval app from it. While Conductor Agents build the app, every agent tool call is logged, and destructive changes pause until a person reviews them. For an example of what that can look like, our procure-to-pay use case shows an example app covering requests, conditional approvals, the PO, delivery, and reconciliation.

Start free on Intro (250 Beats, one time). Pulse is $9/month, Rhythm is $29/month for up to 4 users, and Tempo, where Conductor Agents build the approval app, is $199/month. Compare plans on the pricing page.

FAQ

What are the steps in the procurement process?

The eight common steps in the procurement process are: identify the need and raise a requisition, check the budget and approve, source and select a supplier, onboard the vendor, negotiate and sign the contract, issue a purchase order, receive the goods and match the invoice, then pay the supplier and review their performance.

What are the 7 stages of procurement?

The 7 stages of procurement usually cover the same ground as the 8 steps here, with two steps merged. Most 7-stage versions combine vendor onboarding with supplier selection, or fold the supplier review into payment. Other frameworks list up to 13 steps by splitting sourcing and contract management further. The order of the work stays the same.

What is the difference between procurement and purchasing?

Purchasing is the transaction itself: raising the order and buying the goods or services. Procurement is the wider process around it, including deciding what to buy, choosing and vetting suppliers, negotiating terms, managing contracts, and reviewing supplier performance over time. Purchasing is one part of procurement, usually covering the purchase order and receipt steps.

What is the procure-to-pay process?

Procure-to-pay is the end-to-end cycle from a purchase request to paying the supplier. It covers the requisition and its approval, the purchase order, receiving the goods or services, matching the invoice, and payment. Finance teams use the term because it follows the money and its controls, while procurement also covers choosing suppliers.

What is a three-way match in procurement?

A three-way match compares three documents before a supplier invoice is paid: the purchase order (what you ordered), the goods receipt (what arrived), and the invoice (what you are being charged). If all three agree within your allowed tolerance, the invoice can be paid. If not, someone resolves the difference with the supplier first.

Who should fix a three-way match exception?

A three-way match exception should go to whoever can fix its cause. A price difference usually goes to procurement, because they agreed the price. A quantity or receipt difference goes to the requester who confirmed delivery. Accounts payable owns tracking the exception and chasing it, but should not quietly adjust the invoice or the order to make them match.

How do you make a procurement process flow chart?

Draw one swimlane per role, usually requester, budget owner, procurement, supplier, and accounts payable. Place each step in the lane of whoever does it. Add a decision point wherever the path changes, such as amount, new supplier, or contract type, and show what happens when a request is rejected or a bill does not match.