Automation Consultant, South Africa

Choosing what to automate in a South African back office

Good automation candidates are frequent, rule-based and costly when done late. In South African finance, credit and procurement teams, the list typically includes:

• Unpaid debit orders: each returned item needs a customer contact, a note on the account and sometimes a hold, and doing it by hand means some are missed.
• Supplier compliance documents: certificates and affidavits expire, and renewals are chased manually or not at all.
• Supplier invoice entry: PDFs are typed into Sage, Xero, Zoho Books, Odoo or another system, with VAT details checked by eye.
• Approvals: requisitions and payment batches wait for directors who are travelling or in meetings.
• Statements and reports: age analysis and customer statements are exported and emailed one by one each month.

None of these gets built until the rule behind it has been agreed. If nobody has decided how many times an unpaid item is re-presented, or who may place an account on hold, automation would simply move the disagreement into software. In that case, business process consulting in South Africa comes first.

Candidates are ranked in a shared backlog by frequency, effort removed, risk when late and build complexity, which lets anyone in the business see, and challenge, why one item is ahead of another.

Designing workflows that survive outages

An automation that fails silently when the power drops is worse than no automation, because people assume it ran. South African conditions make resilience a design requirement rather than a refinement.

For each workflow, the design covers:

• Where it runs. A cloud-hosted workflow keeps running when your office is dark, but the systems it reads from may not be reachable. An on-premises server stops entirely unless it has backup power.
• What happens when a step fails. Failed steps are retried after a pause, then parked with a notification to whoever owns the flow, rather than dropped.
• How it catches up. After an interruption, the workflow processes what it missed in order, without creating duplicates, such as sending a customer the same reminder twice.
• What people do meanwhile. The fallback procedure tells staff which steps to perform manually and how to mark them so the automation does not repeat them.

Testing includes these cases deliberately: a connection lost halfway through, a system unavailable during a scheduled run, a batch processed twice. Integration between systems is a related but separate design question, covered on my South Africa system integration page; the focus here is on the workflows that remove manual steps.

VAT documents, supplier records and payment fraud controls

Supplier invoices are a natural target for document capture. An extraction step can pick out the supplier name, VAT number, invoice number, date and amounts, then check them before anyone types anything:

• is the supplier on the approved list, with a VAT number on file?
• does a purchase order or goods received note match?
• has this invoice number been captured before?
• do the VAT and total add up?

Failures and uncertain readings go to a review queue, and a person confirms every invoice before it posts. Your accountant decides whether a document supports an input VAT claim and how long it must be retained; the workflow follows their answers and keeps the source document attached.

Supplier records benefit from the same discipline. Expiry dates for B-BBEE certificates and other documents trigger reminders to suppliers and a task for procurement. Scorecard strategy stays with your B-BBEE specialist; the automation keeps the underlying data current.

The most important control is the simplest. Requests to change a supplier's bank details, often the first step in payment fraud, should never be processed automatically. The workflow instead opens a verification task, requires a call to a known contact, records who verified it and holds payments to the new account until a second person confirms. Here automation strengthens a manual check rather than replacing it.

POPIA, AI tools and steps that stay with people

Automations often process personal information: customer contacts for reminders, employee names on claims, identity numbers on credit applications. So the first question for any new AI feature or hosted automation service is simple: which pieces of personal information would it see, and where would they go?

For each workflow I document the fields it reads, the external services that receive them, where those services process data according to the vendor, who can see logs and how long logs are kept. That gives your information officer or legal advisor the facts to assess the design against POPIA. I do not give legal opinions; they decide, and the workflow is adjusted accordingly. Many useful AI steps, such as classifying emails or drafting reminders, can run without identity numbers at all.

Some decisions should stay with people regardless of how easy they are to automate:

• granting or increasing customer credit
• approving supplier bank detail changes
• reviewing VAT return figures before submission
• writing off debts or settling disputes
• sending AI-drafted messages about disputes or legal matters

To judge results, the process owner looks at concrete changes rather than invented figures: whether unpaid items are followed up the same day, whether supplier files are current when reports are prepared, whether directors still receive calls about pending approvals and whether the review queue is cleared regularly. Run histories make those questions answerable.

Who builds, who owns and how the engagement runs

The split of work follows my AI and business automation service. My side covers finding and prioritizing opportunities, writing rules and exceptions with each owner and configuring workflows that need no bespoke code. Bespoke code, a specialist capture product or substantial ERP changes fall to your developers or implementer, who work from a brief I write; I then help test what they deliver.

Many South African businesses already have scattered automations: a macro in the debtors spreadsheet, a rule in the accounting package, a flow set up by a former employee under a personal login. Each one is listed, and together we sort them into keep-and-document, rebuild or switch off.

Every workflow is handed over with an accountable owner in your business, brief operating notes, failure alerts to someone who will act, and credentials belonging to the company. When a workflow generates more corrections than it prevents, it is stopped until the rule behind it has been rethought.

The work is remote, conducted in English and scheduled in South African hours. Customer-facing templates in Afrikaans, isiZulu or other languages are written by your staff. No tool vendor pays me referral money or commission. For related support, see the South Africa overview or my ERP consulting for South African firms.