An approval process should do one job: make sure someone with the authority to say no has seen a purchase before you’re committed to it. Most problems with purchase approvals come from losing sight of that job, either by approving too late to matter, or by adding so many approvals that people find ways around them.
Step 1: Decide where the approval sits
The cheapest place to stop a purchase is before the vendor has the order. That means the approval belongs on the purchase request, or on the purchase order before it’s sent if you don’t use requests.
A common mistake is to approve only the vendor’s bill. By then the goods have arrived and been used, so the “approval” is really just a check on the paperwork. Checking bills is worth doing, but it’s a different job (see step 5).
If you’re not sure whether you need requests at all, purchase request vs purchase order explains when they earn their keep.
Step 2: Approve by role, not by person
Write the rule as “the Plant Head approves requests for this plant”, not “Ramesh approves requests”. Then:
- When the person changes jobs, you change who holds the role, not the process.
- More than one person can hold the role, so approvals don’t stop when one of them is on leave.
- New starters can see who approves what without being told.
Typical roles in a factory are the Plant Head or department head for requests, a Purchase Approver or purchase head for orders, and Accounts for bills.
Step 3: Keep the number of approvals low
Each approval adds a wait, often a day or more. On a production line, a day’s wait for consumables can cost more than the purchase. So:
- One approval on the request is enough for most day-to-day buying.
- Two approvals make sense where two people really both need to agree: capital items, a new vendor, or anything outside budget.
- No approval is fine for small routine re-orders that someone already agreed to as a standing need.
If your approvers are rubber-stamping, you have too many approvals, not too few.
Step 4: Handle large purchases separately
Most companies want large purchases to go to someone more senior. If your system can route approvals by amount, set one or two thresholds and no more. If it can’t, use a separate request type or workflow for capital or large purchases, with the senior approver on it. People raising the request pick the right type, and the senior approver only sees what they need to.
Step 5: Check the bill against the order
Separately from approving the purchase, someone should check the vendor’s bill before it’s paid: does it match the order’s prices and the quantity that actually arrived? This is the “three-way match” between order, delivery and bill. It catches overcharging and short deliveries, which approving the request can’t.
The check is quick when each bill is linked to its order and delivery, and slow when someone has to find the paperwork. Checking deliveries against purchase orders covers the delivery side.
Step 6: Make what’s waiting visible
Approvals get stuck when nobody can see them. Whatever system you use, two things matter:
- The approver sees everything waiting for them in one place, without hunting through email or chat.
- Everyone else sees who it’s waiting for, so the person who raised the request can chase the right person instead of asking around.
Approving from a phone helps too: plant heads are rarely at a desk.
A simple starting setup
For a factory with one or two plants, this is enough to start:
- Purchase requests approved by the Plant Head of the plant that needs the goods.
- Purchase orders raised by the purchase team from approved requests, with no second approval.
- A separate workflow for capital purchases, approved by the Plant Head and a Director.
- Bills approved by Accounts after checking them against the order and delivery.
Run it for a month, then look at where things waited longest and change only that.
Questions
How many approvals should a purchase order need?
For most factories, one approval on the request and none on the order, or one on the order if you don't use requests. Add a second approver only for purchases that really need two people to agree, like capital items.
Should approval depend on the order amount?
Many companies want large purchases to go higher. If your system can't route by amount, a simple workaround is a separate request type or workflow for large or capital purchases, with the senior approver on it.
Who should approve purchase requests in a factory?
Usually the head of the plant or department that will use the goods, because they know whether the need is real. Finance or a purchase head can approve the order or the bill.
What if the approver is away?
Approve by role, and make sure more than one person holds the role. Then any of them can approve, and nothing waits for one person's holiday.