Most companies do not decide to have a purchase approval process. It just happens: someone sends a message asking "can I buy this?", a manager answers "sure", and three weeks later finance finds an invoice nobody can explain.
That works until it doesn't. The team grows, purchases get bigger, the person who said "sure" is on vacation, and the answer to "who approved this?" becomes a search through email threads.
Key takeaways
- A purchase approval workflow answers four questions: what is being bought, who may say yes, who orders it, and whether it arrived.
- Standardize the request with a short form, and calculate the total instead of asking for it.
- Choose approvers by amount, so small purchases move fast and large ones get more eyes.
- Approval has to happen before the order, and every decision should be recorded automatically.
This guide shows how to set up a purchase approval workflow that a team of 10 or 200 can actually follow. You do not need an ERP to do it. You need a clear request, the right approvers, and a record of what happened.
What a purchase approval workflow is
A purchase approval workflow is the path a purchase request follows from "I need this" to "it was paid and received". At minimum it answers four questions:
- What is being bought, and why? The request.
- Who is allowed to say yes? The approval.
- Who actually places the order? Purchasing.
- Did we get what we paid for? Receiving.
When those four answers live in one place, you get the two things finance and auditors care about: spend that was authorized before it happened, and a trail that shows it.
Step 1: Standardize the request
The single biggest improvement is a request form that asks the same questions every time. Free-text emails produce free-text answers.
A good purchase request collects:
| Field | Why it matters |
|---|---|
| Description of the item or service | So the approver knows what they are saying yes to |
| Quantity and unit price | Lets the total be calculated, not typed |
| Total amount | Drives who needs to approve (more on this below) |
| Supplier, if known | Purchasing can reuse existing vendors |
| Cost center or budget line | Finance can match spend to the budget |
| Business reason | The question every approver asks anyway |
| Needed by date | Separates urgent from "whenever" |
| Quotes or attachments | Supports the price, especially above a threshold |
Two practical tips:
- Calculate the total, never ask for it. If the form multiplies quantity by unit price and sums the lines, nobody types $1,200 when the lines add up to $12,000.
- Keep it short. Every extra field is a reason to go back to email. Start with the list above and only add what someone actually uses.
Step 2: Decide who approves what
This is where most processes either get stuck or get skipped. If every purchase goes to the CEO, the CEO becomes a bottleneck. If nothing does, there is no control.
The usual answer is approval limits by amount: the bigger the purchase, the more senior (or the more numerous) the approvers. A simple example for a small company:
| Total amount | Approvers |
|---|---|
| Up to $1,000 | Requester's manager |
| $1,000 to $10,000 | Manager, then department head |
| Above $10,000 | Manager, department head and CFO |
These numbers are only an example. Pick thresholds that match your size and risk, write them down, and apply them every time. We go deeper into tiers, delegation and edge cases in our guide to building an approval matrix.
A few rules that prevent the classic problems:
- Nobody approves their own request. If the requester is also the approver for that tier, the request goes one level up.
- Watch for split purchases. A $12,000 order split into three $4,000 requests to stay under a limit is the oldest trick in the book. Reviewing requests per supplier per month catches most of it.
- Plan for absence. Decide who approves when the approver is out of office, before it happens.
Step 3: Separate approving, ordering and receiving
Segregation of duties sounds like an audit term, but the idea is simple: the person who asks for a purchase should not be the only person who approves it, orders it and confirms it arrived. Splitting those steps between at least two people makes mistakes and fraud much harder.
A lean version for small teams:
- Request: anyone on the team.
- Approval: manager (plus more approvers by amount).
- Order: purchasing or an office manager places the order and records the purchase order number.
- Receipt: the requester confirms the item or service was delivered as expected.
Finance then pays the invoice against an approved, received request. Many accounting teams call this a three-way match: the purchase order, the receiving record and the supplier invoice agree on what was bought, how much, and at what price.
Step 4: Make approvals fast
A process that takes a week to approve a $200 purchase will be bypassed. Speed is part of compliance.
What helps the most:
- Approve from the email. Approvers should not need to log in to a system they use twice a month. An email with the request summary and Approve / Reject buttons removes most of the delay.
- Ask for a reason on rejection. "Rejected" with no explanation produces the same request again tomorrow. Requiring a short reason teaches the team what is acceptable.
- Set a due time. If an approval sits for two business days, remind the approver, then escalate to their manager.
- Send back instead of rejecting when something small is missing, like a second quote. The requester fixes it and the request continues.
One security detail worth knowing: email security scanners often open every link in a message to check it. If clicking "Approve" in an email approves immediately, a scanner can approve your purchases. Approval links should open a confirmation page first.
Step 5: Keep the audit trail automatically
At the end of the year, or during an audit, you want to answer questions like "who approved this $8,400 laptop order, and when?" in seconds.
That means every request should keep:
- The original request, exactly as submitted
- Every approval and rejection, with who, when and the comment
- Changes to the request after submission
- Attachments: quotes, the purchase order, the invoice
- The final status: received, cancelled or rejected
If your process lives in email and spreadsheets, this trail is scattered across inboxes. If it lives in a workflow tool, it should be the timeline of each request, exportable to CSV or PDF.
A purchase approval workflow you can copy
Putting it together, here is a complete, linear workflow that fits most small and mid-sized teams:
- Request (requester): items table with quantity and unit price, calculated total, supplier, cost center, reason, needed by date, quotes.
- Approval (by amount): manager up to $1,000; manager and department head up to $10,000; add the CFO above that. Rejections require a reason.
- Place the order (purchasing): supplier confirmed, purchase order number, expected delivery date.
- Confirm delivery (requester): received in full, partially or with issues, with a photo or the delivery slip.
- Done: finance pays the invoice against the approved, received request.
Notice what is not in it: branches, loops, or a dozen special cases. Most purchase processes are a straight line with an approval that depends on the amount. Keep it that way, and handle the rare exception with a comment instead of a new branch.
Common mistakes
- Approving after the fact. If the order is already placed, it is a notification, not an approval. Make "approved before ordering" the rule.
- One approver for everything. It creates a bottleneck and a single point of failure.
- Thresholds nobody remembers. If the limits live in a PDF policy, people will guess. Put them in the workflow so the right approvers are picked automatically.
- No receiving step. Without it, you pay for things that never arrived.
Frequently asked questions
What is the difference between a purchase request and a purchase order?
A purchase request (or purchase requisition) is internal: someone asks for permission to buy. A purchase order is external: the company's commitment to a supplier, with the items, prices and terms. The approval happens on the request, and the purchase order is created only after it is approved.
Do small businesses need a purchase approval process?
Yes, but a light one. With 5 or 10 people, a single approval by the owner above a small threshold is enough. What matters is that the rule is written, applied every time and leaves a record, so it can grow with the company instead of being invented later.
How long should a purchase approval take?
For routine amounts, the same or the next business day. If approvals regularly take longer, people start buying first and asking later. Due times with reminders, and approvals that can be done from email, keep most requests within a day.
What is a three-way match?
It is a check before paying a supplier invoice: the purchase order, the receiving record and the invoice must agree on the items, quantities and prices. If one of them does not match, the invoice is held until someone explains the difference.
Running it in Easyflow
Easyflow was built for exactly this kind of routine. The Purchase request process in the gallery already has the items table with a calculated total, the approval step and the order and delivery steps, and the Purchase order with approval limits process picks approvers by amount automatically. Approvers can decide from the email (with a confirmation page), each step can have a due time with reminders and escalation, and every request keeps its full timeline, exportable to CSV and PDF.
If you are also formalizing onboarding, our employee onboarding checklist follows the same approach.