How to Automate Purchase Requests and Approvals

Write out today’s real process. The steps run from noticing a need through requisition, budget check, approval, vendor selection, order, goods receipt and payment, including the ones nobody ever documented. Consider a restaurant group whose branches ask head office for kitchen supplies by WhatsApp message, an untracked step that automation should replace first.

Mapping reveals skipped steps. A budget check that some branches perform and others skip is a common find, and fixing it on paper must come before any software is configured. Maverick buying, where a manager orders on a personal card or a phone call, usually surfaces during mapping and belongs on the diagram even though nobody likes it. Otherwise you automate the inconsistency.

Structured fields make automatic checks possible. Each request needs the item or category, quantity, required vendor, estimated cost, department, cost centre and a business reason, because free text cannot be checked against a budget. Someone must interpret each one first. Add a field for the delivery address, since branches often receive stock at a site different from the billing office, and a wrong address costs a second delivery.

Attach evidence at the start. A vendor quote for anything above a routine amount removes the commonest cause of delay, an approver waiting on information the requester had not yet gathered. Above a higher limit, require a comparative set of quotes from two or three vendors so the approver can judge the price. Reject submissions without it.

Copy the rules you already use informally. A branch manager approves routine restocking up to a set limit, regional approval covers anything higher, and every new vendor passes a one-time vetting step whatever the amount. Watch for piecemeal ordering, where one large purchase is split into several small ones to slip under a limit, and flag a vendor receiving repeated orders just below it. Never let one person raise and approve the same order, because collusion and kickbacks hide where one person controls both ends of a purchase.

Check budgets automatically where possible. If your accounting or ERP system tracks budgets live, the workflow can block a request that would exceed the remaining balance before any approver spends time on it. Approvers stop checking by hand.

Some requests will not go smoothly. A rejected request should return to the requisitioner with a reason instead of vanishing from their screen, and a substitution should edit the request without restarting the approval. Substitutions are routine, not exceptional. Send the requester a status message at every step, so nobody has to phone head office or the finance desk to ask where an order stands.

Urgent purchases cause the most trouble. Either the process is too slow for a genuine emergency and people bypass it, or an urgent flag becomes a routine way to skip approval. Build a fast but logged urgent path with a lower approval limit and same-day escalation, then audit how often it gets used.

Measure time from submission to order. Look for where requests stall: at one approver, in one category or at one branch, because that points to the first fix better than an average does. Report the median and the slowest quarter of requests separately, because the slow tail is where urgent flags, phone calls and side orders begin.

Keep one record per purchase. It should hold the request, quotes, approval history and outcome, ready for a vendor dispute, an audit or a tax query asking who approved the purchase and why.