In short
A purchase order approval workflow takes a purchase request, checks it against budget and supplier rules, gets the right people to approve it, and only then turns it into a purchase order that can be sent to the supplier. The steps are: a requisition with the item, the cost and the budget code; automatic checks (budget available, approved supplier, required fields); approval by limit, so small amounts need one approver and larger amounts need more; the purchase order itself; and the later match of order, receipt and invoice. Each step should leave a record of who did what. Approval limits are the design choice that matters most.
The steps, in order
Companies differ in detail, but a purchase order approval almost always follows this order. The point of writing it down as a workflow is that each step has an owner and a record.
- Requisition
- The requester states what is needed, how much it costs, the supplier if known, and the budget code. This is a request, not yet an order.
- Automatic checks
- Required fields are filled, the supplier is on the approved list, and the budget has room. Failing a check returns the request to the requester with the reason.
- Approval by limit
- The approver depends on the amount. A line manager may approve small purchases, a department head larger ones, and finance the largest. Some purchases need a second approver from another department.
- Purchase order
- Once approved, the requisition becomes a purchase order with a number, and it is sent to the supplier.
- Goods receipt
- Someone confirms what actually arrived against what was ordered.
- Invoice match
- The supplier’s invoice is compared with the purchase order and the receipt. If all three agree, the invoice can be paid; if not, the difference goes to a person.
From requisition to a matched invoice
Setting approval limits
Approval limits decide how much friction a purchase has. Too low, and managers approve all day. Too high, and large spending passes with one signature.
A common structure is a ladder of amounts, each tied to a role, not a person, so the rule survives holidays and job changes. The table shows the shape. The amounts are examples for illustration only; your own limits depend on your size and risk.
| Level | Example amount | Who approves | Rule type |
|---|---|---|---|
| Small | Up to a low limit | The requester’s line manager | One role |
| Medium | Above the low limit | The head of the department | One role |
| Large | Above the department limit | Finance, plus the department head | All of a group |
| Capital or unusual | Any amount outside the budget | A committee | A quorum of a pool |
The old way and the new way
The table compares a purchase approved by email and signature with one that runs as a workflow.
- Requesting
- The old way: A form or email with details that vary by requester
- The new way: A requisition record with required fields
- Checking budget and supplier
- The old way: Finance checks by hand when the request reaches them
- The new way: A step checks the budget and the approved supplier first
- Choosing the approver
- The old way: Whoever the requester remembers to ask
- The new way: A rule by amount, tied to a role
- Tracking
- The old way: Ask around to find where a request is
- The new way: The record shows the current step and the history
- Evidence for an audit
- The old way: Search inboxes for the approval
- The new way: A run history with who decided at each step
Controls that auditors look for
- The requester does not approve their own purchase
- This is segregation of duties. A role-based rule makes it easy to keep: the approver role excludes the requester.
- The order is created only after approval
- A purchase order that exists before approval lets a supplier be committed to spending nobody agreed to.
- Three-way match before payment
- Order, receipt and invoice should agree. A difference is reviewed by a person, not paid by default.
- A record of every decision
- Who approved, when, and on what amount. Later changes to the amount should send the request back for approval.
How we decided
We have not built a purchase order example in SynaptaGrid, so this guide describes the design, not a product demonstration. What we have built and run is a supplier onboarding approval in our own workspace, which has the same structure: a request arrives as a record, a check runs, a manager decides, and the outcome is saved on the record.
That example shaped three choices that apply here. An approval is asked of a rule, not of an address: one person, a role, a quorum or all of a group. A failed check does not approve the item and shows which step failed. And the record, not an inbox, holds the outcome.
The cost we accepted is that a workflow with limits by amount needs those limits to be written down as rules before it can run. The benefit is that the limits live in one place and every request is tested against the same ones.
Standards and accepted practice behind this
These are the practices the steps rest on. We align with them. This page does not claim a certification.
- Segregation of duties
- The person who requests a purchase does not approve or pay for it.
- Source: NIST glossary: separation of duty (opens in a new tab)
- Three-way match
- The long-standing accounts-payable practice of matching order, receipt and invoice before payment.
- Delegation of authority
- Written approval limits by role and amount, owned by finance.
- Audit trail
- Each approval records who decided, when and on what information.
- Source: NIST glossary: audit trail (opens in a new tab)
Where SynaptaGrid fits
SynaptaGrid Automation can run the approval part of this process: the requisition arrives as a record, steps run the checks, a person or a group decides by one of the approver rules, and the outcome is saved on the record with a run history.
The receipt and invoice match are not part of what this guide claims for the product. If your process needs them, plan them as separate steps or in the system that holds your invoices.
Frequently asked questions
- What is a purchase order approval workflow?
- It is the path a purchase request follows from requisition to an approved purchase order: checks on budget and supplier, approval by amount, and the creation of the order.
- What is the difference between a purchase requisition and a purchase order?
- A requisition is an internal request to buy something. A purchase order is the approved commitment sent to the supplier. Approval sits between them.
- Who should approve a purchase order?
- It depends on the amount and the budget. A common ladder is the line manager for small amounts, the department head for larger ones, and finance for the largest, with the approver tied to a role.
- What is a three-way match?
- It is the check that the purchase order, the goods receipt and the supplier’s invoice agree before the invoice is paid. A difference goes to a person for review.
SynaptaGrid
Design your approval ladder with us
Bring your approval limits and walk through one purchase from request to decision.