Accounts receivable automation in South Africa: a practical guide

What accounts receivable automation actually means

Accounts receivable automation is not simply sending the same message to every customer. It is a system for moving an unpaid invoice through a clear process.

A practical workflow usually does six things:

1. identifies which invoices are overdue;
2. decides which reminder is appropriate for the account and age of debt;
3. sends that reminder through an approved channel;
4. records delivery, replies, disputes, promises, and payments;
5. pauses or changes the workflow when the customer responds; and
6. gives staff a focused queue for cases that need human judgement.

The goal is consistency. An invoice should not receive three messages in one week because different staff members worked from different spreadsheets. A customer who has raised a valid dispute should not keep receiving a generic demand.

What to automate first

Start with work that is frequent, rules-based, and easy to check.

The aging view

Create one view of open accounts grouped by how long they have been overdue. The exact buckets can match your business, but common stages are current, 1 to 30 days overdue, 31 to 60 days, 61 to 90 days, and older.

The age alone should not decide every action. Also track whether the account is disputed, on a payment plan, promised for a future date, opted out of a channel, or already escalated.

Reminder timing

Define a small cadence rather than allowing ad hoc chasing. An early reminder can assume oversight. Later reminders can become firmer while staying factual.

Each step should have:

• a trigger;
• an approved message;
• a preferred channel and fallback;
• contact-hour rules;
• a stop condition; and
• an owner when automation cannot continue.

Read the overdue invoice collection guide for a usable sequence.

Replies and promises

Automation creates value only when it listens as well as sends. A reply such as “I paid yesterday”, “the invoice is wrong”, or “I can pay on Friday” should change the next action.

Record promise dates and follow up only if the promise is missed. Route disputes to a person. Pause normal reminders while a material dispute is being checked.

Payment routes

Make the next step easy. A reminder should contain the correct reference, amount, contact route, and payment option. If you use a payment link, the customer should be able to identify the business receiving the money.

Zeroed is designed so the customer pays the business directly. The software does not hold the debtor payment.

South African checks that belong in the workflow

Automation does not remove the business's legal responsibilities.

Personal information and communication preferences

POPIA applies when a business processes identifiable customer information. Keep only what the workflow needs, control access, secure exports, and document why the information is being used.

Do not assume every electronic message is “direct marketing”. A payment reminder about an existing account has a different purpose from promoting a new product. Even so, the Information Regulator's direct-marketing guidance is useful when a message also contains promotional content. Keep collection and marketing purposes separate.

WhatsApp opt-in

Meta requires a business to obtain opt-in before messaging a person on WhatsApp. Its guidance says the person must have supplied a mobile number and agreed to receive messages from the named business. The business must also comply with local law.

Store evidence of the opt-in and make communication preferences visible to staff. See the WhatsApp payment reminder guide for the channel-specific steps.

Prescription and credit agreements

Older debt needs careful review. The Prescription Act sets different prescription periods and includes rules that affect when prescription begins, is delayed, or is interrupted. Do not use a generic automated message to make legal conclusions about an old account.

If an account arises from a credit agreement, National Credit Act procedures may apply before enforcement. Flag these accounts for an appropriate compliance workflow.

How to choose an automation system

Ask a vendor to show the workflow, not only the dashboard.

Question	What a useful answer should show
Where does customer money go?	Directly to your business account
Can a reply stop reminders?	Clear pause and routing rules
Can staff see every contact?	A time-stamped communication history
Are opt-outs enforced?	Channel preferences applied before sending
Can we limit spend?	Usage meters, alerts, and caps
Can we export our data?	A usable export without vendor lock-in
How are disputes handled?	A human queue, not continued generic messages

Also check how the system counts active accounts, how messaging usage is billed, and what happens when you cancel.

A sensible implementation plan

Week 1: clean the inputs

Choose one overdue-account export. Remove duplicates, confirm balances and references, and identify obvious disputes or payments already received.

Week 2: approve a small cadence

Write the first three messages. Define stop conditions and owners. Test links, reply routes, opt-outs, and contact hours.

Week 3: start with a controlled group

Use a limited set of recent overdue accounts. Review every reply and correction. Do not begin with the oldest, most legally complex debt.

Week 4: measure the process

Track delivery, replies, disputes, promises kept, payments recorded, opt-outs, and staff time. The useful question is not “how many messages did we send?” It is “did the process produce clear next actions without creating avoidable customer friction?”

Where Zeroed fits

Zeroed is first-party accounts receivable software for South African businesses. It works overdue accounts in the business's own name through WhatsApp and supporting channels, tracks promises and payment plans, and keeps customer payments flowing directly to the business.

It is not a debt collection agency and does not guarantee that an account will be recovered.