Purchase Request Approval Workflow: Ending the 'Can I Buy This?' Chat Thread

Purchase Request Approval Workflow: Ending the "Can I Buy This?" Chat Thread

"Boss, can I buy a replacement charger for the label printer? It's $45." A thumbs-up arrives four hours later, in a group chat with sixty other messages. The charger gets bought on someone's personal card. Three weeks later the finance person finds a $45 reimbursement claim with no approval attached, and has to scroll back through the chat to confirm it was real.

Multiply that by every small purchase in a month, in a company of ten to fifty people, and you have a spending process that works on trust and memory, with no record of who agreed to what.

The core pain point: spend finance can't see until it's gone

Procurement vendors have spent years measuring this, and their numbers come from larger organisations, so apply them to a small business with some caution. Still, the pattern is consistent. ProcureDesk reports that spending outside the approved process typically accounts for 15-25% of company expenditure. Fraxion puts the figure at up to a fifth of total spend, and says it shows up most in exactly the low-value, high-frequency purchases an SME makes every week: maintenance, repairs, office supplies and small services.

The reason is rarely bad intent. An article on fleet spending notes that the overwhelming majority of off-process buying happens because employees believe they are doing the right thing. Zone & Co describes the mechanism neatly: a formal request with multi-level routing can take two days, while a card purchase takes thirty seconds, so people take the thirty seconds. The cost shows up as a month-end surprise, because the purchase never passed through a request that would have shown its budget impact beforehand.

Where it breaks down

In a chat-based process, four things go wrong:

• Requests are vague. "Can I order more of the usual?" gives the approver nothing to approve.
• Approvals are informal. A thumbs-up is not a record, and two people can remember it differently.
• Budget is invisible. The approver has no idea whether this is the first purchase of the month in that category or the tenth.
• Receipts drift. The purchase happens, the paperwork follows weeks later, and sometimes never.

The workflow: request, route, approve, record

Here is what DVA Workflows builds.

1. A short request form. Item, cost, reason, supplier, urgency and which budget it belongs to. Five fields, mobile-friendly, so it is easier to fill in than to type a paragraph in a chat.

2. Routing by amount. Small purchases go to the team lead. Larger ones go to the owner or finance as well. The thresholds are yours to set; the point is that routing is automatic rather than depending on who the requester thinks to ask.

3. One-tap approval. The approver sees the request, the running spend in that category and the remaining budget, then approves, declines or asks a question, all from their phone. A decision takes seconds instead of sitting in a thread.

4. A spend log that updates itself. Approved requests land in a log tied to budget lines. At any point you can see what has been committed, not just what has been paid.

5. Receipt capture closes the loop. After purchase, the requester is prompted to attach the receipt. The request isn't closed until they do.

Keeping it light enough that people use it

The biggest design risk is making the compliant path slower than the shortcut. ProcureDesk's own advice is that the most effective way to prevent off-process buying is to make proper purchasing easier than improper purchasing, and it names too many approval levels as a classic mistake. For an SME that means one approver for most things, two for large ones, and a quick lane for genuine urgent buys that records the purchase after the fact instead of blocking it. If the process feels like paperwork, staff will go back to the group chat.

What changes for the business

Finance sees commitments before they become costs. Approvers see budget context instead of approving blind. Requesters get answers in minutes. And when a manager leaves or a supplier disputes an order, there is a record of who approved what and when. None of it needs a procurement department. It needs one form, one routing rule and one place where the answer lives.

The bigger picture

The goal is not to say no more often. It is to turn "I think someone said yes" into a record anyone can check, without adding a layer of bureaucracy a ten-person company can't afford.

Curious how much of your monthly spend never passes through an approval? Book a free automation audit with DVA Workflows and we'll map this workflow against how your team currently buys.