RPA in South Africa: what a software robot can do for your business, and what it costs.
What robotic process automation is, which South African jobs it suits, what Power Automate and UiPath cost, and when a direct connection is the better choice.
AutomationUpdated 7 min read
Someone in your business spends the first hour of every day logging in to the bank, downloading statements and typing the totals into Sage Pastel. Someone else copies orders from email into the accounting package, one field at a time. The systems involved are old, or locked down, and none of them connect to anything.
That is the job robotic process automation, or RPA, was made for. This guide explains what a software robot is, which South African jobs it suits, what the main tools cost, and when you should skip the robot and connect your apps directly instead.
What RPA is, in plain words
A software robot uses a computer the way a person does. It opens a program, clicks buttons, types into fields, copies values and saves files. It follows the same steps every time, and it keeps a log of what it did.
The robot does not need the program to have an API or an export. If a person can do the job by looking at the screen, a robot usually can too. That makes RPA useful for older desktop software, government and bank portals, and industry systems that were never built to connect to other apps.
It is not artificial intelligence. A robot follows rules you give it. It can be paired with AI, for example to read an invoice PDF before the robot types the figures in, but the clicking and typing part is plain rule following.
RPA or a direct connection: which you need
Before you build a robot, check whether the systems can talk to each other directly. A direct connection between two apps, through their APIs or a tool such as Zapier, is faster, cheaper to run and far less likely to break. Shopify to Xero, a web form to Google Sheets and WhatsApp to a CRM all connect directly.
RPA is the right choice when:
- The only way into a system is its screen, such as a desktop accounting package with no import.
- A portal has no download or report you can schedule, so someone has to log in and click.
- The software is too old, or too expensive to change, for a proper integration.
A robot depends on screens staying the same. When a portal moves a button or a program updates, the robot can stop. That is why our rule is simple: connect directly where you can, and use a robot only where you must. Our guide on which business processes to automate first helps you pick the jobs worth doing at all.
Jobs a robot does well in South African businesses
These are the kinds of jobs that fill a morning and suit a robot.
- Capturing orders or invoices into Sage Pastel or another desktop package, from a spreadsheet, an email or a PDF.
- Downloading bank statements from online banking each morning and filing them in a shared folder.
- Collecting new prices from supplier portals and updating your price list.
- Pulling reports from industry or medical aid portals that have no way to schedule an export.
- Copying details between two systems that cannot connect, such as a booking system and an older invoicing program.
- Checking a list of reference numbers on a portal and noting the status of each one.
Good candidates share three traits. The steps are the same every time, the job happens often, and the data starts in a digital form, such as a file, an email or a screen. Jobs that need judgement on every item are better left to people, or split so the robot does the typing and a person makes the call.
The main RPA tools and what they cost
Power Automate for desktop
Microsoft's robot tool runs on Windows 10 and Windows 11. You can sign in with a free Microsoft account to build desktop flows and run them on your own computer while you start them by hand. It has a recorder and hundreds of ready-made actions for Excel, browsers, files and desktop programs.
The free version has limits. According to Microsoft's comparison, scheduling flows, triggering them from the cloud, sharing them with colleagues and running them unattended all need a paid organisation account. On Windows Home you also cannot trigger desktop flows from the cloud, so a robot that must run on a schedule needs Windows Pro or a server.
At the time of writing, Microsoft's pricing page lists Power Automate Premium at US$15 per user a month and the Process plan, which lets one robot run unattended, at US$150 a month, both paid yearly. Microsoft notes that local prices vary by country, so check the rand price before you commit.
UiPath
UiPath is one of the best known RPA platforms and is common in large companies. It has a free Community edition, but its licence limits who may use it for work and how robots can be scheduled. Read the current licence terms on UiPath's site before you rely on it for a business process. Paid plans are priced for teams and enterprises, and usually come through a quote.
Browser robots in code
When every step happens in a web browser, a robot can be written in code with a tool such as Playwright and run on a small server. There is no per-robot licence, so running costs are low. It takes a developer to build and fix, which makes it a good fit for a stable, high-volume job rather than something that changes every month.
What a robot needs to run
A desktop robot needs a Windows computer that is switched on when the job runs. That can be an office PC that stays on overnight, or a small cloud server. Plan for load-shedding: if the robot runs on an office computer, check that the computer restarts and signs in by itself after the power returns, or run it in the cloud.
The robot also needs its own login for each system wherever the system allows it. Keep those passwords in a secure vault, never in a spreadsheet or inside the robot's steps. A separate login also means every action in the system's own audit trail shows it was the robot.
Robots and POPIA
A robot that handles names, ID numbers, account details or medical aid numbers is processing personal information, so POPIA applies to it in the same way it applies to a person doing the job. In practice:
- Give the robot access only to the screens and data its job needs.
- Keep its logs, and keep them safe, because they can contain personal information.
- Make sure downloaded files go to a protected folder and are deleted when they are no longer needed.
- If the robot sends information to another system or provider, check that the transfer is covered in your privacy notice.
This is general information, not legal advice.
How to start without wasting money
- Pick one job. Choose the one that takes the most hours a week and follows the same steps every time.
- Record yourself doing it once, start to finish, including the logins and the odd cases.
- Check whether the systems connect directly. If they do, use that instead of a robot.
- Build the robot for the normal case first, and let it hand anything unusual to a person.
- Run it next to the person doing the job for a week or two, and compare results before you switch over.
- Decide who gets the alert when it stops, and who fixes it.
To see whether the job is worth automating at all, our free automation savings calculator shows the hours and money your manual work costs each month.
What to do next
Start with the job your team complains about most, and write down every step. If it lives in systems that connect, a direct link will serve you better. If the only way in is the screen, a robot can take it over.
We build both, and we tell you which one fits before we start. Our automation service covers direct connections, AI steps and robots, and a single automation has a fixed price on our pricing page. If you would like help, send us the job through our contact page.