A purchase should not become a surprise invoice. Automation is most useful before anyone commits company money.
Short answer
Create one request record, route it by amount and category, require evidence for exceptions, and lock the approved version before ordering. Keep a substitute approver and never let the requester approve their own exception.
Minimum request contract
{
"request_id": "immutable",
"requester": "known identity",
"supplier": "proposed supplier",
"items": "description and quantity",
"total": "amount and currency",
"cost_center": "approved destination",
"business_reason": "why now",
"status": "draft|review|approved|rejected|ordered|received"
}
Microsoft documents approval users, substitutes, amount limits, and notifications. NetSuite’s basic template locks a submitted purchase order and allows rejected requests to be resubmitted. Amazon Business describes routing before the order becomes a commitment. These are product patterns, not a universal purchasing policy.
Routing matrix
| Condition | Route | Human gate |
|---|---|---|
| within budget and preferred category | manager | confirms need and coding |
| above threshold | manager → finance | confirms budget and authority |
| new supplier or unusual terms | procurement/owner | validates supplier and terms |
| requester is approver | alternate | preserves separation of duties |
| approved request changes | reopen review | compares old and new versions |
Approval is not ordering. Store the approved snapshot, approver, timestamp, reason, and later order reference as separate evidence.
State flow
draft → submitted → review → approved → ordered → received
↘ returned/rejected
Any change to supplier, items, quantity, currency, or total after approval returns the request to review. A timeout escalates visibility; it must not auto-approve.
Reversible pilot
Run synthetic cases for a routine purchase, threshold boundary, absent approver, self-approval, changed total, duplicate request, new supplier, and missing budget. Pass only when no synthetic request creates a real order, each exception reaches the expected person, and the audit record can reconstruct the decision.
Measure decision time, returns for missing fields, changes after approval, expired requests, duplicate candidates, and orders without an approved request. Connect the design to human approval boundaries and expense reimbursement without mixing pre-purchase authorization with post-purchase repayment.