Loading…
ES/EN
In most mid-sized companies across Latin America, purchase approvals do not have a process — they have a habit. That habit usually involves WhatsApp, emails without follow-through, and a manager who approves or ignores depending on availability. The result is blocked operations, no audit trail, and no way to know what was bought or who authorized it. Digitizing this flow does not require an ERP — it requires clear rules and a simple system to execute them.
Before talking about solutions, it helps to describe the purchase approval process as it exists in many companies of 20 to 100 people across the region — because the description alone makes the problem obvious.
An employee needs to buy something: office supplies, a third-party service, a spare part. They message the manager on WhatsApp: "Hey, can you approve buying X for Y amount?" The manager reads it when they can — sometimes in minutes, sometimes hours later, sometimes the next day when they return from a meeting or a trip.
If the manager approves, the employee makes the purchase, keeps the receipt in their pocket, and hands it to accounting a week later or whenever someone asks. If the manager does not respond, the employee follows up again — or, if the purchase is urgent, just goes ahead and apologizes later.
At month-end, the finance manager cannot answer "what did we buy this month and who authorized it?" without reviewing WhatsApp threads and scattered emails. The external auditor — if there is one — cannot answer it either.
The most visible cost is the bottleneck. A technician who cannot buy the supplies they need loses half a workday waiting. A project that depends on an external service gets delayed because the contract cannot be signed without approval, and the approval is not coming.
This cost rarely appears in any report. It gets logged as "project delay" or "coordination issue," but the root cause is a purchase authorization process that was not designed to be fast.
An informal approval gives the feeling of control because the manager says yes or no. But it provides no information about purchasing patterns: what is being bought, how often, from which vendors, at what price margins. Without that information, it is impossible to negotiate better vendor terms or identify where spending is running high.
When urgency outpaces the manager's availability, purchases happen without formal authorization. After it happens several times without consequences, it becomes the norm. The informal system stops being a control mechanism and becomes a formality that gets bypassed when convenient.
A purchase approval process that actually works is not complicated. It requires four elements:
1. A single request channel
Every purchase request enters through the same channel: requester name, description of the good or service, estimated amount, suggested vendor, and urgency level. This can be a Google Form, a Typeform, a Notion form, or a screen in a purpose-built system. What matters is that it is the only channel — not WhatsApp, not email, not verbal.
2. Approval rules by amount
Not every purchase needs to go to the general manager. The rules can be simple: purchases under $100 are approved by the department head, purchases between $100 and $500 require the operations manager, purchases over $500 require the general manager. These rules eliminate the bottleneck for 70-80% of purchases without sacrificing control on the ones that matter.
3. Automatic notifications to the approver
When a request comes in, the approver receives a notification — by email, WhatsApp Business, Slack, or whatever channel they use — with the request details and a link to approve or reject. The approver does not need to open any special system. The approval takes 30 seconds.
4. Automatic record-keeping and traceability
Every request, with its status (pending, approved, rejected), the name of who approved it, and the date, is logged automatically. This gives finance and management access to a complete history without having to ask anyone for it.
If the company already has an accounting system (QuickBooks, Alegra, Siigo, SAP B1, or similar), the natural next step is connecting the approval flow to that system: when a purchase is approved, a purchase order or expense record is automatically created in the accounting system. This step adds technical complexity but also closes the control loop completely.
For many mid-sized companies, this can wait. The primary value — visibility, speed, traceability — is achieved with the basic flow. The accounting integration can be a second phase.
A 60-employee logistics company with operations in two cities had a general manager receiving 15 to 25 WhatsApp messages a day related to purchase approvals. Some were urgent, others could wait. There was no way to prioritize them without reading each one, and when he traveled, everything piled up.
Redesigning the process took three weeks: a Google Forms request form, an approval-by-amount table documented and communicated to the team, email notifications to approvers with "approve" and "reject" buttons, and automatic logging in a Google Sheet that finance could query in real time.
The outcome was that the manager went from receiving 20 approval WhatsApp messages a day to receiving only those that genuinely required his judgment — higher-amount purchases or special cases. The total time he spent on approvals dropped proportionally. Finance, for the first time, could generate a month's purchasing report in minutes instead of days.
No system works without a clear process behind it. Before building or buying any tool, the team needs to agree on:
With those definitions in place, the system — whether simple or sophisticated — can execute the rules. Without them, the system will reproduce the informality in digital form.
Is your team getting blocked by purchase approvals that do not come through on time? Schedule a diagnostic session and we will review your current process and design a flow that fits your approval structure and the tools you already use. Let's talk.
MORE IN THIS CATEGORY
What an Internal Ticketing System Is and When You Need One
What an internal ticketing system is, what problems it solves, and when it makes sense to implement one at a mid-size company. For operations leaders in LATAM.
How to Build a Weekly Operations Report That Generates Itself
How to eliminate the manual operations report with a system that collects, structures, and distributes data without human intervention. For companies in LATAM.
What to Automate First When Your Company Has 20 to 50 People
A framework for identifying the first automation target at mid-sized companies: frequency, time, and error cost. Common first candidates and why starting small works