A purchase order approval workflow is the path a material request takes from the person who needs it to the person authorized to spend that amount, ending in an order number the supplier will honor. On most small contractor jobs that path is a phone call and a will-call pickup on account. A workflow system puts a spend ceiling, a cost code, and a budget check in front of that call, and records the commitment the moment the order is released.
Where material buying gets away from the office
Buying on account with no order number
A lead walks into the supply house, gives the company name, and walks out with material. The invoice arrives three weeks later with no job on it and no way to tell which of four active jobs consumed it. Someone in the office makes a guess.
The budget check happens after the money is spent
The person ordering has no view of what is left on that cost code. They order what the work needs, which is the right instinct, and nobody discovers the line was already overrun until the monthly job cost review.
Approval is a text message that scrolls away
The superintendent approves a two thousand dollar order by replying to a text. Two months later, during a backcharge dispute, nobody can produce what was approved, by whom, or against what scope.
The same material is bought twice
The subcontract already includes the fasteners and the sealant. Field orders them anyway because checking takes longer. You pay once in the subcontract and once at the counter, and the double buy surfaces at buyout reconciliation.
There is nothing to match the invoice against
Without an order record and a receiving record, accounts payable cannot do a three-way match. Every invoice becomes a judgment call about whether price, quantity, and job are right, and most get paid because arguing takes longer.
Spend ceilings and who clears each one
The dollar amounts are a starting point, not a recommendation. What matters is the shape: every ceiling has a named approver, a document that must exist first, and a specific behavior when a request hits it.
| Order amount | Who can release it | Required before release | What happens at the ceiling | Turnaround |
|---|---|---|---|---|
| Up to $500 | Foreman or crew lead | Job and cost code selected | Releases at once, issues an order number, posts the commitment | Immediate |
| $500 to $2,500 | Superintendent or project manager | Job, cost code, and remaining balance on that code | Routes to the project manager; flags anything exceeding what is left | Same day |
| $2,500 to $10,000 | Project manager plus purchasing | Two quotes, or a written sole-source note | Holds the order number until the second quote or the note is attached | One business day |
| $10,000 to $50,000 | Owner or operations manager | Signed vendor quote and a confirmed delivery date | Escalates, and flags overlap with a subcontract scope already covering it | Two business days |
| Over $50,000 | Owner, as a written buyout decision | Bid tab from three suppliers, or a documented reason there are not three | Creates a buyout record rather than a plain order, with the reasoning attached | Scheduled, not ad hoc |
| Any amount against change order scope | Project manager plus the change order owner | An approved change order number, or a named person accepting the risk | Blocks release until a number exists or someone signs for the at-risk buy | Follows the change order |
| Emergency or after hours | Superintendent, with retroactive review | Photo of the condition and why it could not wait | Issues a provisional number, then tops the next morning’s queue | Immediate, reviewed next day |
The path a requisition takes
The request starts where the need is
A phone form takes job, cost code, vendor, description, quantity, and needed-by date. It shows the remaining balance on that cost code before submission, so the person asking sees the number the approver will see.
Routing by amount and by scope
The amount picks the approver from the matrix. A second rule checks whether the material already sits inside a subcontract scope and warns before routing, which is the check that stops the double buy.
Release issues a real order number
Approval generates a sequential purchase order number and sends the order to the vendor with the job name, delivery address, and required-by date. The supply house has something to write on the ticket, which is what makes the invoice matchable.
Receiving is a separate event
Whoever takes delivery photographs the packing slip against the order. Partial deliveries stay open with the balance visible. An order with no receiving record cannot pass to payment without an override recorded by name.
Three-way match, then commitment relief
The invoice is matched to the order and the receiving record on quantity and price. Clean matches queue for payment and exceptions go to a short review list. When the invoice posts, the committed amount on the cost code drops by the same figure.
What a purchase order touches
- workflow automation and approval routing — Amount, cost code, and scope conflicts decide the route without anyone forwarding an email.
- QuickBooks automation for accounts payable — Orders become commitments, receipts become accruals, and matched invoices post to the job and cost code.
- electronic signature for larger commitments — Buyout awards and supplier agreements above the top ceiling get signed and filed against the job.
Is this a fit for your business?
A good fit when
- Field crews buy on account at more than one supply house
- You carry self-performed scope and subcontracts on the same jobs
- Accounts payable regularly cannot tell which job an invoice belongs to
- A backcharge dispute has cost you because there was no approval trail
Probably not a fit when
- One person places every order and already runs a numbered order book
- You need full inventory management across multiple warehouses
- Your vendors will not put an order number on the ticket, which is worth fixing first
What to have ready
- Your active vendor list and which crews buy from which suppliers
- The approval limits you actually want, even if they are informal today
- A month of material invoices, including the ones nobody could code
Questions we get asked
Will the crew use a form while standing at the counter?
Only if it finishes in under a minute and gives them something back. The order number is the payoff: with it, the counter transaction goes on the job instead of into a pile someone chases later. If the form asks for more than the crew can reasonably know, they route around it, and that is a design problem rather than a discipline problem.
Can requests be approved from a phone?
Yes, and for the lower ceilings that is the only realistic path. The approver gets the amount, the job, the cost code, and the remaining budget on that code, and approves or rejects without opening a laptop. Larger amounts deliberately require the full request with quotes attached.
How do blanket orders and standing accounts fit in?
A blanket order carries a total value and a date range, and individual pickups are recorded as releases against it. The commitment posts once at the blanket level and each release draws it down. It suits recurring buys like fuel, aggregate, or fasteners where an order per pickup would be noise.
What happens when the vendor invoice does not match?
It stops in an exception queue with the difference shown: price variance, quantity variance, or an order never received. Someone with authority resolves it and their decision is recorded. The point is that exceptions are a short visible list rather than being absorbed silently into the payment run.
Related
- change order approval workflow
- bid invitations and subcontractor bid tracking
- workflow automation services
- workflow automation for construction companies
Tell us what the process looks like now and we will map what a system would need to do. No obligation, and you keep the map either way.