HR & Payroll Software in Africa: One Platform, Many Countries
The most over-claimed category in African business software, examined honestly. Why the HR layer genuinely travels across borders and the payroll calculation genuinely does not, what "configurable tax tables" actually means when a budget changes, and our own coverage stated as one country rather than a continent.
Of all the claims made in African business software, "one HR and payroll platform for the whole continent" is the one that survives contact with reality least often. Not because the vendors are dishonest — most are describing something real — but because the phrase compresses two very different products into one promise, and buyers reasonably hear the stronger half.
This post separates them. The HR layer travels almost perfectly. The payroll calculation does not travel at all. Everything that goes wrong in a multi-country HR implementation goes wrong at the seam between those two, and the seam is easy to find if you know the question to ask.
One question that separates the products
Ask this, and listen to the whole answer
"When the budget changes the income tax bands in this country, who updates them, how quickly, and what happens to my payroll run in the month between the announcement and your update?" A vendor operating a genuinely maintained engine has a rehearsed, specific answer because they have lived through it, repeatedly, and it is unglamorous. A vendor with configurable tables changes the subject to flexibility. Neither answer is disqualifying — but they are two different products at two different prices, and this question is what tells you which is on the table.
Everything below is a longer version of that question.
What travels, and what does not
A multi-country HR stack, layer by layer
Employee records and organizational structure
Who works here, in what role, reporting to whom, in which entity and location. Identical requirement in every country.
Compensation records and statutory identifiers
What each person is paid, and their national tax and social security numbers held as fields. The identifiers differ; holding them does not.
Leave, with configurable types and balances
Entitlements, requests, approvals, balances. Types and entitlements are configured per country and that is the correct design.
Attendance and regularization
Recorded time, corrections with an approval trail. Travels without modification.
Payroll cost allocation to projects and cost centres
The half of payroll that donors, funders and management actually ask about, and the half that is genuinely country-neutral.
Public holidays
Tenant-configurable, which is exactly right — no two countries share a calendar, and several change theirs annually.
The working week
Which days count as non-working is set per organization, so a Sunday-to-Thursday week is configured rather than worked around. This was hardcoded to Saturday and Sunday until recently and we said so here; it is now a setting, and the honest note is that it was a market telling us, not foresight.
Statutory payroll calculation
Income tax bands, social security contributions, levies and statutory return formats are maintained for Kenya only. Nowhere else.
Filing and remittance
Nothing is submitted to any revenue authority or social security fund in any country, including Kenya. Filing remains your process everywhere.
Read the shape of that rather than the individual rows. Six layers travel, one is correctly configurable, and three do not travel at all — and the three that do not are the ones the phrase "HR and payroll software for Africa" is usually selling.
Why maintained payroll cannot be continental
It is worth understanding why this is hard rather than treating it as vendor laziness, because the reasoning tells you what to demand instead.
- Bands and rates change on a national schedule, often at short notice. Someone has to be watching each country's budget process, and be able to ship a change before the next payroll run.
- The change is rarely a single number. A band shift usually arrives with relief adjustments, a new levy, a threshold change or a transitional rule, and the interaction between them is where errors hide.
- Effective dates matter more than values. A rule that applied from the fifteenth of a month has to be applied to that month, not to the whole of it, and retrospectively to runs already processed.
- Getting it wrong is not a bug report. It is an underpayment to an employee or an underremittance to an authority, both of which have consequences beyond software.
- Multiply by fifty-four. A vendor claiming maintained coverage across Africa is claiming a standing regulatory function in every one of those jurisdictions, permanently staffed. Very few organizations do that, and the ones that do charge accordingly and will name their countries without being pressed.
A maintained payroll engine is a standing regulatory function, not a feature. Ask how many countries it is staffed for, and expect a short list.
The arrangement that actually works
Given all that, the sensible structure for a group operating in several African countries is not one product. It is a written boundary with both sides staffed.
Multi-country HR, divided honestly
The HR platform, everywhere
One system, one set of records, comparable across the group.
- Employee records, roles, structure and entity.
- Compensation records and statutory identifiers.
- Leave types, entitlements, requests, approvals and balances.
- Attendance, regularization and the approval trail behind corrections.
- Payroll cost allocated to projects, funders and cost centres.
- Documents against the employee record, with expiry where relevant.
- Access revoked automatically when someone is terminated or archived.
A local payroll specialist, per country
Where the national regulatory work stays.
- Income tax band calculation and reliefs.
- Social security, pension and levy contributions.
- Statutory schedules in each authority's required format.
- Filing and remittance to authorities and funds.
- Interpretation of national employment and tax rules.
What crosses the boundary
- A monthly payroll input file from live records — starters, leavers, changes, absence — instead of a spreadsheet rebuilt by hand.
- Payroll cost by employee, project, funder and cost centre, returned into management reporting.
- Leavers, so access is revoked in the system on the same day the bureau is told.
The first crossing item is where most of the value sits and it is routinely overlooked. The recurring monthly pain in multi-country payroll is not the calculation — the bureau does that competently. It is the manual assembly of starters, leavers and changes, from four countries, into four spreadsheets, by the fifth of the month. Automate that and you have solved the part that was actually costing you.
The straight answer
What AWRA OpsHub does today
- Employee records, roles, structure, compensation and statutory identifier fields, which work in any country.
- Leave — configurable types, entitlements, requests, approvals and balances, with public holidays and the working week both configurable per organization.
- A configurable working week. Non-working days are chosen per organization, so leave-day arithmetic and the attendance present-rate average follow a Friday–Saturday or six-day week rather than an assumed Saturday–Sunday one.
- Attendance and regularization, with an approval trail on corrections.
- Payroll runs and payslips, with rule versions held against runs so a processed payslip stays reproducible.
- Date-effective statutory rule resolution and band calculation for Kenya — PAYE, NSSF, SHIF and the housing levy — plus P9 certificate generation.
- Payroll cost allocation to projects, funders and cost centres.
- Access lifecycle tied to employment — terminating or archiving an employee disables the linked login and clears sessions, with a reconciliation view for administrators.
- Employee documents with expiry tracking, and configurable custom fields on the employee record.
What it does not do
- Statutory payroll outside Kenya is not turnkey. No other country's income tax bands, social security contributions, levies or statutory return formats are maintained.
- No filing or remittance anywhere, including Kenya. There is no iTax, NSSF or SHA portal submission and no equivalent elsewhere. Filing remains your process.
- The working week is set in two places, not one. HR leave and attendance read the HR working-week setting; workflow due dates and escalation read a separate business calendar. Both are configurable, but an organization that changes one and not the other gets two different answers to the same question.
- The interface is English only. No French, Arabic or Portuguese, and no right-to-left layout.
- No employment law interpretation. We do not advise on contracts, notice, redundancy or dispute processes in any jurisdiction.
- No recruitment, applicant tracking or performance management module.
- No direct bank or mobile money disbursement outside Kenya. M-Pesa is our only payment rail integration, and it is Kenya-only.
The Kenya asymmetry is not a claim about which market matters. It exists because Kenyan clients needed a maintained engine enough to commission one, and it has been maintained since — which is precisely the reason we will not describe the same thing as existing anywhere else. If you want it for your country, that is a build with a written spec and price, not a checkbox.
What is not built for your market today can still be built for you
Anything described above as not built is a statement about what ships in the standard product today — not a limit on what AWRA OpsHub can do in your market. Kenya's eTIMS integration and its maintained payroll engine exist because Kenyan clients needed them and commissioned them; neither appeared by itself. The same door is open here. If a revenue authority pipeline, a bank or mobile money feed, a statutory return format or a link to a system you already run is what stands between you and a decision, tell us and we will scope it as a build — written spec, timeline and price — before you commit to anything.
Tax and e-invoicing pipelines
Electronic invoicing against your revenue authority's published interface, with the parts vendors gloss over — retries, a failure queue and a daily report of sales carrying no fiscal reference.
Banks, payments and mobile money
Statement feeds, payment gateways, bulk-payment files and collection accounts wired into the Payments Register so money in and out reconciles without re-keying.
Payroll and statutory returns
Payroll and social security schedules produced in the layout your filing body expects, generated from live payroll records rather than rebuilt each month.
Systems you already run
The accounting package, CRM, online store or custom database you intend to keep — connected through our API so a fact is entered once and appears everywhere it is needed.
How it works: you describe the requirement, we return a written scope, timeline and cost, and once agreed it is built into your environment and maintained as part of the product. No roadmap slide, and no pretending in a demo that something exists when it does not.
Tell us what you need integratedQuestions worth asking every vendor
Including us
- Name the countries where payroll bands are maintained by you, not configured by me.
- When the budget changes them, who updates, how fast, and what happens in the gap month?
- Is anything submitted to a revenue authority or social security fund on my behalf? By which mechanism?
- Are rule versions held against processed payroll runs, so an old payslip can still be reproduced?
- Which days does the system treat as non-working, can I change them, and is it one setting or several?
- What happens to a leaver's system access on the day they are terminated?
- Can payroll cost be allocated to a project or funder without a manual journal?
- What is the monthly payroll input handoff to a bureau, and is it a file or a person retyping?
Where to go next
The continental framework is in the best ERP software for African businesses. By market, the payroll boundary in local detail: Nigeria, Ghana, South Africa, Senegal and Côte d'Ivoire, Uganda and Tanzania. The regional variance question is worked through in regional HR and payroll variance.
For the one market where we do claim turnkey statutory payroll, PAYE, NSSF and SHIF payroll in Kenya sets out what that actually covers.
Our take
Buy one HR platform for the whole group and local payroll specialists per country, and write the boundary down before implementation. The HR layer — records, leave, attendance, cost allocation, access lifecycle — travels perfectly and gives you comparability you cannot otherwise get. The statutory calculation does not travel and no honest vendor should imply it does across fifty-four jurisdictions. Then spend your effort on the monthly input handoff, because that is where the recurring pain actually lives, and it is the part almost nobody automates.
See the HR layer that travels
Employee records, leave, attendance and payroll cost allocation across every country you operate in — with a written, specific answer on statutory payroll for each one before you commit.
Explore HR and payrollFrequently asked questions
Can one platform run payroll across several African countries?
The HR half can, and should. The statutory calculation half cannot, from anyone, without a standing regulatory function staffed in each country — which is why vendors who genuinely do it name a short list of countries and charge accordingly. Our own maintained engine covers Kenya only. Everywhere else we hold employee records, compensation, leave, attendance and payroll cost allocation, and a local bureau or specialist does the national calculation and filing. That arrangement works well when the boundary is written down and both sides are staffed.
What does "configurable tax tables" actually mean?
It means you or your consultant maintain the bands and rates, and that when a budget changes them you will most likely hear from your accountant rather than from your software vendor. That is a legitimate and often sensible product — it is simply a completely different promise from a maintained engine, and the price should reflect which one you are buying. The question that separates them is what happens in the month between an announcement and an update: a maintained vendor has a specific, rehearsed answer.
Do you submit anything to the revenue authority or social security fund?
No, in any country, including Kenya. There is no iTax, NSSF or SHA portal submission and no equivalent anywhere else, so filing and remittance remain your process everywhere. What we produce in Kenya is the calculation on date-effective statutory rules, payslips, P9 certificates and the underlying records; what we produce elsewhere is the employee, leave, attendance and cost data your bureau needs. Any vendor claiming submission should be asked which authority, by which mechanism, for which production customer.
Can the system handle a Sunday-to-Thursday working week?
Yes. Non-working days are configured per organization, so an organization on a Friday–Saturday weekend ticks those two days and leave-day arithmetic and the attendance present-rate average follow suit. Public holidays are separately configurable, as they should be, since no two countries share a calendar. Two caveats worth knowing before you rely on it. First, workflow due dates and escalation read their own business calendar, configured separately from the HR one — set both or they will disagree. Second, ticket SLA clocks and ageing reports run on elapsed calendar time, not working days, so a ticket raised on Thursday afternoon in a Friday–Saturday weekend country is still ageing over the weekend. That is a deliberate choice for support response, but you should know it is the behaviour.
What happens to a leaver's access?
It is revoked as part of employment lifecycle rather than left to a separate IT process: terminating or archiving an employee disables the linked login and clears active sessions, and administrators have a reconciliation view to catch mismatches. The residual risk this does not cover is logins with no employee record behind them — contractors, service accounts, someone set up directly as a user — so a periodic review of accounts against employees is still worth doing.
Can payroll cost be split across projects and donors?
Yes, and for donor-funded organizations it is usually the strongest single reason to hold HR in the same system as operations. Payroll cost can be allocated to projects, funders and cost centres, so staff cost against a grant is a report rather than a monthly reconstruction in a spreadsheet, and it reconciles to the same records the rest of the project spend comes from. This part is entirely country-neutral and works everywhere, regardless of who performs the statutory calculation.
Can old payslips still be reproduced after rules change?
Yes. Payroll runs hold the rule version they were processed under, so a payslip from two years ago reproduces on the rules that applied then rather than on today's. This matters more than it sounds: statutory rules are date-effective and change mid-year, and a system that recalculates history against current rules will quietly disagree with every certificate and return you have already filed. Ask any payroll vendor about this specifically — it is a good proxy for how seriously they take the domain.
