A procurement SOP template is a ready-made standard operating procedure that sets out, step by step, how your organisation buys goods and services. It covers who requests, approves, sources, contracts and pays, so every purchase follows the same controlled route.
It is the written, numbered procedure your team follows for every purchase, from the moment someone needs something to the moment the supplier is paid. Where a procurement policy states the rules, the SOP explains how to carry them out: which form to use, who signs, what gets filed.
Procurement and finance teams write one when spend starts flowing through several departments, before an audit, or after a purchase slips through without approval. New starters use it to learn the process, and auditors use it to test whether the controls actually run.
The template gives you the sections, the process steps and the controls already in order. You replace the bracketed thresholds, names and systems with your own and have the CFO or head of procurement sign it off.
Why the SOP exists, which spend it covers and which it excludes, such as payroll or tax payments.
Requester, budget owner, procurement, legal, finance and AP, with a RACI for each step.
The numbered steps from intake request to payment, with owners and target times.
Who can approve what, by amount, and how many quotes each band needs.
Segregation of duties, PO before invoice, three-way matching and supplier verification.
What is kept, where, for how long, and when the SOP is next reviewed.
Ready to use in Word, Google Docs and PDF. Fill it in, save it, reuse it.
Write down how purchases happen today, including the shortcuts people take.
Fill the template with the target process, thresholds and owners.
Have the CFO or head of procurement sign it and set an effective date.
Walk requesters and approvers through it and publish it where they will find it.
Test it against real purchases each year and update the version number.
Start with three sections: Roles, Approval limits, Steps from request to payment. Add controls and records once the basics are followed.
Keep the numbering fixed so people can cite a step by number, such as 6.3. Put thresholds, system names and owners in brackets until you have confirmed them. Most finished SOPs run to four to eight pages.
One paragraph on why the SOP exists: controlled, compliant and value-for-money purchasing.
Which entities, departments and spend types it covers, and what is out of scope, such as payroll, tax and intercompany charges.
Requester, budget owner, PO, three-way match, preferred supplier and any other term a new starter might not know.
What each role does, with a RACI table for the main steps.
The procurement policy, approval matrix, supplier code of conduct and delegation of authority.
Numbered steps from intake request to payment, each with an owner, an input, an output and a target time.
Approval bands by value and the number of quotes or the sourcing route each band needs.
Segregation of duties, PO before invoice, matching tolerances and verification of new suppliers and bank changes.
How to handle urgent or single-source buys, who can approve them and how they are recorded afterwards.
What is filed and where, retention in line with your finance policy, the review date and the change log.
6. Procedure 6.1 Raise a request. The requester submits a purchase request in [intake tool or form] with the business need, supplier (if known), estimated cost, cost centre and required date. 6.2 Budget and approval. The request routes to the budget owner, then to approvers set by the approval matrix in section 7. No supplier may be engaged until all approvals are recorded. 6.3 Source. For spend over [5,000], procurement obtains [2] written quotes; over [25,000], [3] quotes; over [100,000], a formal competitive process. Single-source buys follow section 9. 6.4 Onboard the supplier. New suppliers complete [supplier form], provide tax and bank details on company letterhead, and pass [security / risk] review before a PO is issued.
Use this table as section 6 of the SOP or as a standalone procurement process template on a wall or intranet page. Target times are a starting point; set your own from how long steps take today. The output column is what auditors will ask to see.
| Step | Owner | Output | Target time |
|---|---|---|---|
| 1. Intake request | Requester | Purchase request with need, cost and cost centre | Same day |
| 2. Budget check and approval | Budget owner, approvers | Approved request | 2 working days |
| 3. Sourcing | Procurement | Quotes or selected supplier | 5-15 working days |
| 4. Supplier onboarding | Procurement, finance | Supplier record, verified bank details | 3 working days |
| 5. Contract and PO | Procurement, legal | Signed contract, issued PO | 2-10 working days |
| 6. Receipt | Requester | Goods receipt or service sign-off | On delivery |
| 7. Invoice and matching | AP | Invoice matched to PO and receipt | 3 working days |
| 8. Payment | Finance | Payment on the agreed terms | By due date |
| 9. File and review | Procurement | Complete purchase record | Monthly |
Illustrative target times. Read the full procure-to-pay process guide for more on each step.
Under [1,000] from a preferred supplier: request, budget owner approval, purchase on a PO or card, receipt.
All nine steps, with quotes as set by the approval band.
Start 90 days before the renewal date, review usage, then rejoin at step 2.
The RACI stops steps falling between teams, which is where most delays start. Approval bands should match your delegation of authority, so check both documents say the same thing. The figures below are placeholders to replace with your own.
| Step | Requester | Budget owner | Procurement | Finance / AP | Legal |
|---|---|---|---|---|---|
| Intake request | R, A | I | I | ||
| Approval | I | A | C | C | |
| Sourcing | C | I | R, A | ||
| Contract | C | I | R | A | |
| PO issue | I | R, A | I | ||
| Invoice and payment | C | I | R, A |
R = responsible, A = accountable, C = consulted, I = informed.
| Value band | Approvers | Quotes or route |
|---|---|---|
| Under [5,000] | Budget owner | 1 quote or preferred supplier |
| [5,000] to [25,000] | Budget owner, department head | 2 written quotes |
| [25,000] to [100,000] | Plus finance | 3 written quotes |
| Over [100,000] | Plus CFO | Formal competitive process |
Illustrative thresholds. Set yours in an approval workflow that matches your delegation of authority.
A control that leaves no record cannot be proved to have run. For each control below, the evidence column is what you file. Keep records for as long as your finance or tax policy requires.
| Control | How it runs | Evidence filed |
|---|---|---|
| Segregation of duties | Requester, approver and payer are different people | Approval log with names |
| Approval before commitment | No supplier engaged before approvals are complete | Dated approval record |
| PO before invoice | Invoices without a PO are returned to the requester | PO number on every invoice |
| Supplier verification | New suppliers checked for tax ID, bank details and risk | Completed supplier form |
| Three-way match | Invoice matched to PO and receipt within [2%] tolerance | Match result in AP system |
| Bank change call-back | Changes confirmed by phone on a number already held | Call log with date and caller |
| Exception log | Emergency and single-source buys recorded with reason | Exception register |
The checklist is the SOP in a form people will actually use on each purchase. Attach it to the purchase record, so the audit trail is in one place. The download adds an initials and date column to each check.
Steps 1 and 2 are where SOPs break. Spendflo runs intake and approvals so every request follows them.
See how it worksThe policy sets the rules; the SOP sets the steps that carry them out.
The first record of a need, raised before any supplier is contacted.
The buyer's formal commitment to a supplier, with price, quantity and terms.
Checking that the invoice agrees with the PO and the goods receipt before paying.
Purchases made outside the agreed process, contracts or suppliers.
The document that sets who may commit the organisation to spend, and up to what amount.
| P | Question it answers | Where the SOP checks it |
|---|---|---|
| Product | Is it the right quality and specification? | Intake request and sourcing |
| Price | Is it a fair price for the value? | Quotes and approval band |
| Place | Will it arrive where it is needed? | PO delivery details |
| Period | Will it arrive on time? | Required date on the request |
| Quantity | Is it the right amount, no more? | PO and goods receipt |
Lists vary between organisations; some swap place for people or process.
Map today's route, shortcuts included, before you write the target one.
Shared ownership is where requests stall and nobody notices.
Reference the approval matrix instead of repeating figures through the document.
Most readers are budget owners, not buyers, so keep steps short and plain.
Add a change log so auditors can see which version applied to each purchase.
Restating rules without steps leaves people unsure what to actually do.
Without one, urgent buys bypass the SOP entirely and are never recorded.
Approving an invoice for work already done is not an approval control.
Link the SOP from the intake form so requesters see it at the point of need.
Trace five recent purchases from request to payment and note every handover.
Complete sections 1 to 10, keeping brackets where decisions are still open.
Confirm approval bands and the RACI with finance, legal and department heads.
Get sign-off, link it from your intake form and brief every budget owner.
Lumen Retail's marketing team requested a 32,000.00 analytics tool. Under section 7 it needed department head and finance approval plus three quotes. Procurement onboarded Orbit Analytics, legal signed the contract and the PO went out on day 12. The invoice matched first time. Figures are illustrative.
Every part on this page, in Word, Google Docs and PDF, with the examples filled in.
Two approval bands, one quote threshold and a single finance approver. Keep the SOP to two pages and the checklist on one.
Four bands, a RACI, supplier risk review for data-handling vendors and a separate route for software renewals.
Add the tender rules and record-keeping your sector requires, and have compliance review each version before sign-off.
Best for formal sign-off and version control.
Best when several teams comment on the draft.
Checklist and process map, ready to print.
Spendflo routes every request through intake, approvals and supplier onboarding before anyone buys.
Book a demoA clear procurement SOP sets owners, limits and controls for every purchase from intake to payment. It works when requests enter through one front door, so the right approvals happen before anyone talks to a supplier.
Quick answers to what people ask most about the procurement sop template.
An SOP in procurement is a written, step-by-step procedure for buying goods and services, covering requests, approvals, sourcing, contracts, receipt and payment. It turns the procurement policy into actions people can follow. Download the template for a ten-section version ready to edit.
A common version is product, price, place, period and quantity: buying the right item at a fair price, delivered to the right place, on time and in the right amount. Lists vary between organisations. The download maps each one to a check in the SOP.
Yes, you can download this procurement SOP template in Word, as well as Google Docs and PDF. The Word version has numbered sections and bracketed fill-ins, so you only replace thresholds, names and systems.
It should include purpose, scope, definitions, roles, related documents, the procedure, approval limits, controls, exceptions and records. The procedure is the core, running from intake request to payment. Download the template to get all ten sections in order.
You can download a free procurement checklist template from this page, included with the SOP in Word, Google Docs and PDF. It has twelve checks across request, approval, supplier, receipt and payment.
Procurement
Purchase orders
Contracts
Vendor management
Sourcing and RFx
Budgets and business cases
Accounts payable
Purchasing
Software buying
Supply chain
Spendflo runs intake, approvals, supplier onboarding and contracts, so purchases follow your procedure by default. AP automation is coming soon.
Enter your work email and we'll unlock every format.
Didn't start, or need another format? Pick one below.
Google Docs: upload the file to Google Drive, then open it with Google Docs.
