What to Automate First: A Practical Guide to Business Process Automation in South Africa

Most South African businesses do not have an automation problem. They have a repetition problem. The same invoice captured by hand, the same approval chased over email, the same figures re-keyed into the same return every quarter. Business process automation is how you hand that repetitive work to a system and get your people back for the work only people can do.

What business process automation actually means

Business process automation (BPA) is software that runs a complete business process, not just a single task. A macro fills one spreadsheet cell. BPA takes the whole sequence, the trigger, the steps, the approvals, and the record-keeping, and runs it end to end.

It helps to separate three things people blur together. A task is one action, like sending a reminder. Robotic process automation (RPA) mimics a person clicking through screens, which is useful when two systems have no proper connection. Business process automation is the broadest: it models the real process and runs it, ideally by connecting systems directly rather than imitating a human at a keyboard.

The amount of work that can be automated is larger than most teams assume. McKinsey's analysis of work activities found that about 60% of occupations have at least 30% of their tasks that current technology could automate, while only around 5% of jobs could be fully automated.¹ The practical reading: you rarely automate a whole job. You automate the repetitive 30% inside it, and give the person back the other 70%.

Where business process automation pays off in a South African business

The best candidates look the same across most SA operations. Here is where the payback usually shows up first.

Finance and month-end

Reconciliation and the monthly close are the classic drain. APQC's benchmarking puts the median monthly close at about 6.4 calendar days, with a quarter of organisations taking more than ten.² A process that clears the easy matches automatically and surfaces only the exceptions turns most of that fortnight back into time. This is the job of an automated reconciliation engine.

Operations and the handoffs between systems

Most growing businesses run more tools than they realise. Okta found that large organisations run an average of 211 applications.³ Even a ten-person Johannesburg firm might run a point-of-sale, an accounting package, a CRM, a WhatsApp line, and a bank portal that do not talk to each other. The handoffs between them, re-keying one order into three places, are where time and accuracy leak. An event-driven orchestrator makes one event land cleanly in every downstream system.

Back-office documents

Invoices, IDs, proof of payment, delivery notes. Every one re-typed by a person is a chance for a wrong number. Manual data entry carries an error rate of roughly 1% for skilled operators, and up to 4% on average, per field.⁴ Reading documents automatically removes both the typing and the error. This is what document intelligence does.

Compliance and reporting

For regulated South African businesses, reporting is not optional and the penalties are real. Under POPIA, the Information Regulator can issue an administrative fine of up to R10 million.⁵ Automating the assembly and validation of POPIA, SARB, and tax submissions turns a quarter-end scramble into a controlled, evidenced process, with an audit trail that answers the auditor in seconds.

How to choose what to automate first

Do not start with the most interesting process. Start with the most expensive one. A simple test ranks any candidate on four questions:

• Volume: how often does it run? Daily beats quarterly.
• Repetition: are the steps the same each time, or does every case need judgement?
• Cost of error: what does one mistake cost, in rands, rework, or a regulator's attention?
• Effort to change: how tangled is the current process, and how many systems does it touch?

The first build should be high volume, highly repetitive, expensive when wrong, and not impossibly tangled. In most businesses that points to a finance or a document process, not the rare edge case that feels clever to solve.

"The process worth automating first is rarely the one people complain about loudest. It is the quiet one that runs fifty times a day and costs a little every time."

- Zabble engagement lead, automation builds

Three mistakes that sink automation projects

The failures are predictable. Automating a broken process just makes the mess run faster, so fix the process on paper before you automate it. Boiling the ocean, trying to automate everything at once, stalls under its own weight, so ship one process and prove it. Imitating people instead of connecting systems, the RPA trap, leaves you with a brittle robot that breaks every time a screen changes, when a direct connection would have been steadier.

Build versus buy: off-the-shelf tools or a system shaped to your process

Off-the-shelf automation tools are the right answer when your process is standard. If you need a generic approval flow and nothing about it is specific to your business, buy it. The trade-off arrives when your process is the thing that makes you competitive, when it spans several systems no single tool covers, or when it has to follow a South African rule (POPIA retention, SARB returns, FICA checks) that global software treats as an afterthought.

At that point a bought tool forces your business to bend to its template. A system shaped to how you already work does the opposite. The honest guidance: buy the commodity parts, and build only the parts that are genuinely yours. That is the line Zabble draws in a bespoke build.

How to start without betting the business

You do not need a transformation programme. You need one process and a clear before-and-after.

1. Pick one process using the test above. One, not five.
2. Measure it as it is today: hours spent, error rate, how long an answer takes. That is your baseline.
3. Automate that one process end to end and keep a person on the exceptions.
4. Compare to the baseline. If it paid back, move to the next process. If it did not, you have spent a small experiment, not a year.

Done this way, automation compounds. Each process you hand to a system frees the time to tackle the next, and the pieces start to connect into one operating picture of the business. For the wider approach, start at the automation pillar, then tell us which process costs you the most.