Cross-border loads, fuel surcharges that move with the fuel price and customers entering formal rescue make logistics credit control in South Africa demanding. Credit controllers need training to supervise agents that match payments and build dispute packs: depth, verdicts and provenance, with limits, holds and rescue claims kept with people. POPIA and the Information Regulator govern the data.
What does credit control look like at a South African logistics firm?
Road hauliers, freight forwarders, clearing agents and warehouse operators invoice customers for local and cross-border transport, clearing, storage and distribution. Fuel surcharges are recalculated as the fuel price changes, and cross-border loads attract detention charges when trucks wait at borders. Customers pay by EFT, and those in neighbouring countries pay through cross-border channels.
The controller matches remittances, chases arrears, agrees settlement of disputed surcharges and detention, and reviews credit limits, often with a credit insurer. Two risks stand out. Cargo theft and hijacking lead to claims that customers try to deduct from payments. And when a customer enters a formal rescue process for financially distressed companies, collection rules change overnight, and the controller must stop ordinary chasing and lodge a claim.
Where can agents help, and at what depth?
Cross-border loads behave differently from local ones, so certify on both before the agent earns depth, which runs from 1 (read) to 4 (moves money or is hard to undo). The role sets the ceiling either way.
- Remittance matching, depth 3 once certified. Exact matches clear; differences are held for a person.
- Fuel surcharge recalculation checks, depth 2. The agent recalculates each surcharge from the agreed formula and the published fuel price, and drafts the explanation for a disputing customer.
- Border detention evidence, depth 1 to 2. The agent assembles the truck's tracking timestamps and border records and drafts the detention claim.
- Reminders, depth 3 within approved wording. Sent only to the customer's finance contacts, at approved intervals.
- Credit notes, depth 4, held. A named approver releases above the firm's limit.
- Rescue and liquidation notices, depth 1. The agent detects them in correspondence or public notices and stops all automated chasing for that customer at once, by your own limits.
How do controllers review an agent's work?
How credit controllers review an agent's decisions sets out the method. It begins with the verdict: allowed, held, refused or withheld, and which of five bounds decided it, namely role scope, certificate, sources, the firm's limits or the platform guardrails.
Provenance comes next. Tracking data and the firm's ledger are sealed. A customer's statement that a truck arrived late is declared. A border agent's emailed record is external until matched to tracking. When a controller corrects the agent, for example because it used the wrong fuel price date for a contract, the correction must be banked in the agent's sources; teaching credit controllers to bank corrections explains how.
Controllers should also plan for the agent's certificate: it lapses after 90 days, and a run that clears no depth drops it to depth 1 the same day, which at month end means matching falls back to people.
What should never leave the controller's hands?
| Decision | Reason |
|---|---|
| Setting or raising credit limits | Commits the firm to a customer's risk |
| Accepting a cargo theft claim deduction | Needs investigation and insurer involvement |
| Lodging a claim in a rescue process | Legal process with strict requirements |
| Holding goods or stopping service | Contract and commercial consequences |
| Writing off balances | Management decision on the firm's money |
The full list is in what credit controllers should never let an agent do. For how these roles compare across the business, see AI agent skills by role.
Which South African rules apply?
POPIA governs personal information, enforced by the Information Regulator. It sets conditions for lawful processing: accountability, processing limitation, purpose specification, information quality, openness, security safeguards and data subject participation. Logistics firms hold drivers' details, consignees' names and addresses, and customer contacts, and a collections agent should read only the billing and contact data it needs. POPIA also restricts decisions with legal consequences based solely on automated processing that profiles a person. The guide to POPIA and training staff who use AI agents goes deeper.
Cross-border payments run under the South African Reserve Bank's exchange control rules, which affect how foreign receipts and refunds are processed. South Africa has no single AI law; the wider position is in how AI agents are regulated in South Africa. If the firm handles EU customers' data, GDPR may also apply.
This is an explanation of the rules, not legal advice; confirm how they apply to you with counsel.
A 90-day plan
- Weeks 1 to 4. Literacy for controllers, billing staff and operations managers: depth, verdicts, provenance, the record and POPIA handling. Write the firm's own limits, including the automatic stop on rescue notices.
- Weeks 5 to 8. Controllers review matching, surcharge checks and detention packs daily; weekly calibration on disputed detention claims.
- Weeks 9 to 12. Credit note release ties to a current certificate. Rehearse a certificate lapse at month end, and test the rescue stop with a dummy notice.
Where the Academy fits
Pryme Intelligence Academy's free readiness assessment, for teams of up to 25, has the credit team sit the Foundations test set in logistics and returns a report of scores by concept and the first agent to start with. Controllers who release credit notes then move to the Operator track: 32 of 40 on the written exam, then a two-week practicum signed off by a Pryme assessor.
Questions people ask
What should the agent do when a customer enters rescue?
Stop all automated reminders immediately and alert the controller. Claims and any further contact follow the rescue process and are handled by people.
Can the agent explain fuel surcharges to customers?
Yes, at depth 2, drafting from the agreed formula and the published price. A person sends anything going to a disputing customer.
Do drivers need training too?
Not as reviewers. They should know which records the agent relies on, such as delivery scans, and why accuracy matters.