For South Africa

You already own a system. The layer that failed is rarely the layer with vendors calling you.

Most South African buyers already own a system. This one is for the operations layer underneath it — stock counted across provinces, procurement that holds its approvals, assets with named custody, and evidence you can reconstruct on demand rather than assemble under pressure.

The subject: You already own a system, so the useful question is which layer of your stack actually failed — and the answer decides whether you need us, a different finance package, or nothing at all. Two of the four rows below send you elsewhere.
SARS: We do not file and we do not transmit to SARS. Our e-invoicing transmission is Kenya's eTIMS and it is Kenya-only.
Payroll: Kenya-only. PAYE, UIF and SDL are not calculated here, and the advice we would give unpaid is that a local bureau already filing monthly is cheaper than commissioning us and correct by default.
Two refusals: We will not calculate a B-BBEE score and we will not call the product POPIA compliant. Both are boundaries rather than backlog, and both are explained below rather than asserted.

Diagnose the layer Talk to us about South Africa

A diagnostic, before a pitch

Four layers. The one that failed is rarely the one being replaced.

This is the only page in this set written for a buyer who already owns a system. So the useful question is not what we do — it is which layer of your stack actually broke, because the answer decides whether you need us, a different finance package, or nothing at all. Read the last column before the others.

Statutory and the general ledger

Owned by — Your finance system, and your accountant

The books are wrong or cannot be closed.

This is not us Replace it — and this is not us. If your ledger is genuinely failing, buy a better ledger. We do not want this layer and we are not competing for it.

Reporting and consolidation

Owned by — Usually a spreadsheet, maintained by one person

Nobody can get a reliable number out without a week of work.

This is not us Almost never the real fault. A reporting layer is only as good as what feeds it, and rebuilding it on the same inputs buys you a faster route to the same wrong figure.

Operations — stock, procurement, assets, people

Owned by — Usually nobody, formally

The numbers reaching the ledger were assembled by hand from a warehouse, four sites and an inbox.

This is us This is the layer we are. It is also, in our experience of these conversations, where the failure almost always is.

Capture — what happens at the gate, the yard, the site

Owned by — Paper, memory and a messaging app

Everything above is downstream of a fact somebody wrote on a pad and typed up later.

This is us This is the root, and it is also us. A control that requires somebody to re-enter it later is not a control, it is a hope with a deadline.

If you read that and concluded your problem is layer one, we would rather you bought a finance package and did not call us. That is a genuine sentence and not a negotiating position: an operations layer installed underneath a broken ledger inherits the broken ledger, and the project fails in a way that gets blamed on us. If it is three or four, keep your finance system, keep your accountant, and put this underneath both — which is the whole shape of what we sell here.

Operations in South Africa

You almost certainly do not need another ledger. The layer that failed is underneath it.

This is the one market page in the corpus written for a replacement decision rather than a first purchase. Most South African buyers already run a competent finance system and the thing that broke is not the accounting. It is that the numbers arriving in the ledger were assembled by hand from a warehouse, four provincial sites and a procurement process living in email — so the books are tidy and the operation underneath them is not evidenced. Every card below sits below the general ledger rather than beside it.

Inventory

Provincial stock as positions the ledger can be fed from

Each site holds its own position, transfers confirm on arrival, counts are blind and variance is valued. Your finance system keeps receiving numbers; it stops receiving numbers somebody typed.

Procurement

A commitment recorded when it is made, not when it is invoiced

Requisition, refusing threshold, RFQ comparison with losing quotes retained, purchase order and three-way match. The gap between committing money and seeing it in the ledger is where most reporting surprises are born.

Document vault

Evidence reconstructable on demand rather than assembled under pressure

Supplier invoices against receipts, contracts against vendors, delivery notes against movements, supplier documents with expiry tracked — retrievable by the transaction. This is also the substrate a verification agency asks for when your own reporting process needs it.

Assets

Custody, which the fixed asset register does not hold

Your ledger knows what you own and what it is worth. It does not know who has it, where it went and what condition it came back in. Named custodian, movement history and condition at each hand-off are a different question from depreciation, and it is the one that gets asked.

Offline operations

Capture that keeps working when the power does not

Stock transfers, inventory check-out and check-in, and asset movements recorded on mobile with no connectivity and synced when it returns. Built for East African networks, and load-shedding is the same constraint arriving on a schedule.

Project cost

Cost coded to a place as it is entered

Site, cost centre, project and funder captured at entry rather than allocated at reporting time, so per-site profitability is a filter instead of a month-end excavation.

The sequencing advice we would give before you ask: do not replace the ledger. If your finance system works, keep it and put this underneath it. A replatform that touches the books as well as the operation doubles the risk to fix half the problem, and the half that is broken is almost never the accounting.

Recognisable, we hope

Four symptoms that all point below the ledger

A system that reports but does not govern

The finance package produces beautiful statements over operational records nobody enforced — approvals that warned, counts that drifted, receipts nobody matched.

Provinces that reconcile late

Gauteng knows Gauteng. The Cape, KZN and the outlying branches report on their own rhythm, and the national stock position is always a few days behind the trucks.

Capture that stops when the power does

A scheduled interruption should cost you two hours of electricity, not two hours of records. Work that was not captured during the outage is rarely captured afterwards.

Evidence assembled under audit pressure

The quotes, the approval, the delivery note and the invoice all exist — in four places, held by three people, and reconstructable only by the person who happens to remember.

Scope in South Africa, and the two refusals we would rather state early

Running in the product today

Stock held per provincial site, transfers confirmed on arrival, blind counts with valued variance and adjustments carrying a reason and a person.
Procurement with refusing thresholds, RFQ comparison, purchase orders and three-way matching, with the commitment recorded when it is made.
Supplier records with documents attached and expiry dates tracked, which is the procurement evidence a verification process asks for.
Asset registers with named custody, movement history and condition on every hand-off — a different record from your fixed asset register and complementary to it.
Cost coded to site, cost centre, project and funder at entry, so per-site profitability is a filter.
Offline capture for four field operations — stock transfers, inventory check-out and check-in, and asset movements — which keeps running through load-shedding and syncs when power and network return. Selling is not one of them, so a till still stops.
ZAR as your base currency, with foreign-currency transactions held at the rate actually applied and never silently converted in reporting.

More we can add — on the roadmap, and commissionable now

South African statutory payroll. The maintained statutory engine covers Kenya only. Employee records, attendance, leave and payroll cost allocation are real; PAYE, UIF and SDL calculation is not. Earnings and deductions can be configured to your practitioner's specification, but nothing is calculated, filed or remitted on your behalf.
A SARS submission. Filing returns and transmitting to SARS are both part of it. Our e-invoicing transmission is Kenya's eTIMS and it is Kenya-only.
Bank statement reconciliation, for any market, in any form. This is the limit most likely to matter to a South African buyer replacing a system, and it is the one least likely to come up in a demo.
A local payment rail integration. M-Pesa exists and is Kenya-only; South African payments are recorded rather than initiated or matched.

What we would decline, and would rather say now

We will not calculate a B-BBEE score. Scoring turns on verification by an accredited agency against codes that change, and a vendor computing a number no verification professional will stand behind is selling you a false comfort. We hold the supplier and procurement detail an agency asks for; the score is theirs to certify. This one does not change with a commissioned build, and it is a boundary you should want.
We will not call the product POPIA compliant. We will tell you in writing which region your data sits in, who can access it, how long backups are kept and what happens to your data if you leave — and your own advisers assess that against your obligations as the responsible party. Treat any vendor claiming unqualified POPIA compliance as having answered a different question.

The middle column is work rather than positions, and each is commissionable now on a written specification, a timeline and a price agreed before any money moves. A South African payroll engine with PAYE, UIF and SDL on live employee records, producing schedules in the layout your filing body expects, is the same kind of build the Kenyan engine was. The advice we would give first, unpaid: a local bureau already filing every month is cheaper than commissioning us and correct by default. We will take the build if you want it; we would rather you did not need it.

Read the right-hand column as the reason to believe the left one. Both entries are refusals of things buyers actively ask for, and both are positions we would hold with a signed contract on the table — which is exactly what makes them worth something to you. A vendor with an empty right-hand column has simply not been asked a hard enough question yet.

How this starts

Three moves, none of which touch your ledger

Name the failure before the module

Stock accuracy, approval discipline, asset custody or evidence reconstruction — the first module goes where the last bad afternoon came from.

Run a real month alongside what you have

Your branches, your suppliers, your approval chains, on your data — with training for the people who key transactions rather than the people who read reports.

Extend, and decide what the old system keeps

Many South African operations keep their finance package and put governed operations underneath it. That is a legitimate end state, not a half-migration.

Read before you shortlist

Guides for this market

Africa Business Guides

ERP Software in South Africa: A Practical Buyer's Guide (2026)

South African buyers are usually replacing something, not starting from nothing — which makes this a harder purchase, not an easier one. How to tell a system problem from a process problem, what to ask a polished vendor, and the straight answer on SARS, POPIA and payroll.

Aug 29, 2025 · 13 min Read

Africa Business Guides

SARS, VAT & Rand Operations: What Your Business System Should Handle

A VAT vendor is judged on the evidence behind the return, not the return itself. What "SARS-compliant software" should mean, what it usually means, and the reconstruction test that separates the two.

Aug 30, 2025 · 10 min Read

Africa Business Guides

Inventory Management for South African Distributors & Retail

Gauteng, the Cape and KZN on one stock position, long inland legs from the port, and capture that survives a scheduled power cut. What national distribution actually demands of a system.

Aug 31, 2025 · 11 min Read

HR & Payroll

Three Classifications the Report Wants

South Africa's employment equity regime sets numerical targets by sector and occupational level, and a certificate for government work turns on them. The report asks your HR record for three classifications, and a conventional employee record carries none of them as fields.

Jul 8, 2026 · 13 min Read

Helpdesk & Support

Two Promises, and Why One Marker Was a Bug

A support contract makes two promises — we will answer by then, we will fix it by then — and they need two alarms. Giving them one shared "already notified" flag would have meant the first breach permanently silenced the second.

Jun 21, 2026 · 12 min Read

Reports & BI

Threshold Alerts: Letting a Dashboard Number Raise Its Hand

This product pushes a great deal at people — idle stock, expiring batches, lapsing documents, breached tickets. Threshold alerts on a dashboard number crossing a line are the natural next signal, and we can wire them into your workspace.

Jun 7, 2026 · 12 min Read

Questions we are asked in Johannesburg

Straight answers, and which of these we would build for you

Does AWRA submit VAT returns to SARS?

No. We are not a filing tool and we do not connect to SARS eFiling — our only fiscal e-invoicing integration is Kenya's eTIMS, and it is Kenya-only. What AWRA does is hold the records the return is built from: net, tax and gross separated on every sales and purchase line, with the source documents attached to the transaction. Your accountant or bookkeeper continues to file, and the reconciliation between the two is a routine check rather than a reconstruction. Confirm all VAT treatment and current rules with SARS or your tax practitioner. That is on the roadmap rather than a boundary, and it is commissionable now. Return output in the shape SARS expects, generated from transaction detail we already hold, is buildable work. Kenya's eTIMS transmission and its maintained statutory payroll engine both exist because Kenyan clients needed them and commissioned them — neither arrived on a roadmap by itself. If this is the thing standing between you and a decision, say so and we will come back with a written specification, a timeline and a price before you commit to anything. What we will not do is print a date nobody has paid for.

Do we have to replace our existing finance system?

Usually not, and we will tell you when replacing is the wrong call. South Africa has a mature accounting software market and many organizations here have a finance package that works perfectly well. The common failure is not in the ledger — it is in the operational layer beneath it, where stock, procurement and asset records are informal. Running governed operations underneath your existing finance system is a legitimate and often cheaper end state than a full replacement.

Where is our data hosted, and what about POPIA?

AWRA OpsHub is a hosted cloud service and you should ask us directly, in writing, which region your data sits in, who can access it, how long backups are retained and what happens to your data if you leave — then have your own advisers assess that against your POPIA obligations as the responsible party. We can supply those answers and support your compliance, but we do not certify it for you and no vendor honestly can. Treat any vendor who calls their product "POPIA compliant" without qualification as having answered a different question than the one you asked.

Does it handle South African payroll — PAYE, UIF and SDL?

No, not as turnkey statutory payroll. Our maintained statutory payroll engine covers Kenya only. South African payroll is a submission regime as much as a calculation one, and we recommend a South African payroll specialist for that layer, with AWRA holding employee records, attendance, leave and payroll cost allocation to projects, funders and cost centres. Earnings and deductions can be configured manually to your practitioner's specification, but the statutory rules are yours and nothing is calculated, filed or remitted on your behalf. That is on the roadmap rather than a boundary, and it is commissionable now. A South African engine with PAYE, UIF and SDL on live employee records, producing schedules in the layout your filing body expects, is the same kind of build the Kenyan engine was. Kenya's eTIMS transmission and its maintained statutory payroll engine both exist because Kenyan clients needed them and commissioned them — neither arrived on a roadmap by itself. The advice we would give before you ask: a local bureau already filing every month is cheaper than commissioning us and correct by default. We will take the build if you want it; we would rather you did not need it.

Does it do B-BBEE reporting?

No. We do not calculate B-BBEE scores, verify certificates, or produce scorecard reporting, and you should not buy any operations system on that basis. What AWRA does is hold supplier records with their documents attached and expiry dates tracked, so that when your verification agency or your own reporting process needs the underlying procurement evidence, it exists and is current. The scoring, the interpretation and the verification stay with the professionals who do that work. This one is a boundary rather than a backlog — it does not change with a commissioned build, and it is one you should want. B-BBEE scoring turns on verification by an accredited agency against codes that change, and a vendor computing a score in software is offering a number no verification professional will stand behind. We hold the procurement and supplier detail an agency asks for; the score is theirs to certify.

Will it keep working during load-shedding?

Part of it will, on a charged phone or tablet, and the part matters less than people hope — so be precise when you plan for it. Four operations continue with no connection and sync when power and signal return: stock transfers, inventory check-out and check-in, and asset movements. Selling, counting and receiving against a purchase order all need a connection, so a till still stops. What no software can do is run your equipment. This protects the record of stock movement during an outage; it does not keep the shop trading.

Where does support come from?

Nairobi, with remote onboarding and live training. South Africa is one hour behind us, so your working day overlaps ours almost entirely — you are not filing tickets into a timezone that closed before you started.

Bring your South African operation to a demo

One branch, one purchase order, one asset register — see them run governed, with straight answers about SARS, POPIA, B-BBEE and payroll before you sign anything.

Talk to us about South Africa See plans & pricing