Why purchase approvals slow down in growing businesses
In many South African SMEs, buying is still handled through our contact form, WhatsApp, or a paper form that moves from one manager to the next. That works for a small team, but once you have branches in Centurion, Pretoria, Johannesburg, Durban or Cape Town, the process starts to drag. A request sits waiting for a signature, somebody is on site, and nobody is sure who last approved it.
The result is usually the same. Operations wait for spares, finance gets rushed at month end, and procurement staff end up chasing people instead of managing suppliers. During load-shedding or a breakdown on the factory floor, those delays can cost far more than the item itself. Good approval workflows keep the control, but remove the waiting around.
What a practical approval workflow should do
A useful approval process does not need to be complicated. It should match how the business actually works, with rules that are easy to follow and hard to bypass. For example, a branch manager might approve day-to-day purchases up to a set Rand value, while anything above that goes to a finance lead or managing director.
In an ERP environment, the system can check supplier details, budget limits and category rules before the request moves forward. That means a request for office consumables does not follow the same path as a request for a capital item or a critical machine part. The workflow should also show where the request is stuck, so users do not keep asking the same question over and over.
- Set approval limits by role, department and amount
- Route urgent items differently from routine purchases
- Keep an audit trail for every decision
- Flag exceptions before the order is released
- Make it easy to see who still needs to act
Keeping procurement control without slowing the business
There is a common belief that tighter controls automatically mean slower buying. In practice, the opposite can be true if the process is designed properly. Clear approvals reduce rework, because staff know exactly what information must be on the request before it is sent. That cuts out incomplete forms and the back-and-forth that wastes half a day.
Strong workflow design also helps with compliance. Many businesses need to show who approved what, when it was approved and whether the purchase stayed within policy. This matters for internal controls, supplier disputes and year-end reviews. It also helps when teams work across different branches, where one office may have a different spending pattern from another. A small typo in a supplier code can also cause avoidable hold-ups, so validation rules matter more than people think.
- Match approval steps to your spend policy
- Use validation to catch missing order numbers or cost centres
- Allow budget checks before approval, not after
- Store every decision with a date and user name
- Review high-value approvals monthly
A local example from a multi-branch SME
Consider a Centurion-based services company with teams in Gauteng and the coast. The Durban branch needs parts for a critical installation, while the Johannesburg office is waiting on a stock replenishment order. Before workflow automation, requests were sent to different managers and approval times varied from one hour to three days. The purchasing team had no clear view of what was pending, and the branches kept phoning head office for updates.
After the approval rules were mapped properly, routine items moved through a standard path, while urgent maintenance orders followed a faster route with tighter thresholds. Finance could see the spend before the order was released, and branch managers only approved what sat within their limit. Turnaround times improved, and the team stopped keeping backup stock just in case a request got stuck. It was not fancy, just practical and it worked.
The biggest improvement was visibility. Once managers could see where each request sat, they stopped using side messages to push things through. That reduced confusion and made the process fairer across all branches.
How to design approvals that staff will actually use
People ignore systems that are too hard to use. If a purchase request takes ten fields, three attachments and a separate follow-up call, users will find a shortcut. A better design keeps the form short, uses sensible defaults and gives staff a clear reason when an item is blocked. Training is part of the fix too, because even a well-set process fails if people do not understand why it exists.
For SMEs, adoption usually improves when the workflow reflects real working habits. For example, a project manager may need to approve site consumables quickly, but finance may still want to review supplier terms above a certain threshold. The right balance keeps the business moving without opening the door to overspend. It also helps to standardise role names and approval paths across branches, especially where teams in Pretoria, the East Rand and Gqeberha use slightly different routines.
- Keep forms short and relevant to the item type
- Use clear approval reasons and rejection notes
- Train approvers on limits, exceptions and escalations
- Set mobile-friendly review steps for managers who travel
- Update the workflow when roles or budgets change
What Bizmatics looks at when setting up approval controls
When Bizmatics helps an SME improve procurement approvals, the first step is to map the actual process, not the ideal one on paper. That includes who raises the request, who checks the budget, who approves the spend and where delays usually happen. From there, approval rules can be built into the ERP and connected to other business systems so information only needs to be entered once.
We also look at reporting, because approval data is useful beyond the buying team. Management can see where delays are happening, which departments overspend and where supplier issues keep repeating. That information supports better decisions at month end and during planning. If the business needs support retainer services, go-live help, or upgrade planning later, the approval structure should still be easy to maintain and adapt.
For growing SMEs, the aim is simple: fast enough to keep operations moving, controlled enough to protect the Rand. With the right workflow, purchase approvals become part of the business rhythm instead of a daily bottleneck.
