If you're running HR across more than one African country, the software market doesn't fit you. Most products were built for one country, then bolted on a "country selector" and called multi-country. The seams show on day one of your evaluation — and on day thirty of your live cycle.

This is the framework we wish every multi-country buyer used. Twelve checks, in the order they matter. Each one comes with a test you can run during the demo — and a red flag that should pause your decision.

1. Real country isolation, not screen-level filtering

Ask the vendor: "Can my Kenya HR manager retrieve a single Nigeria payroll record — via the UI, the export, or the API?" The answer must be no. Isolation has to be enforced at the database query layer, not by hiding a tab in the navigation. Anything weaker is one curious user away from a compliance incident.

Test in the demo: log in as a country HR role, open the developer console, and try to fetch records for another country via the platform's API. If anything comes back, the isolation isn't real.

2. Per-country statutory engines, maintained centrally

Every country has its own tax authority, social security, public-holiday calendar, and statutory deduction rules. Kenya runs PAYE, SHIF, NSSF, and the Affordable Housing Levy. South Africa runs PAYE, UIF, SDL, and ETI. Nigeria runs PAYE per state, Pension Reform Act contributions, and NHF. The vendor either keeps these current or you do.

Ask: "When the Kenya Finance Act changes a PAYE band, what's your turnaround?" A real answer is measured in days from gazette publication, not weeks. Browse the country guides to see the depth a serious vendor maintains.

3. Multi-currency payroll, with a configurable FX policy

You will run payroll in local currencies and report consolidated in USD, EUR, or GBP. The system needs three FX modes: spot rate at run-time, locked monthly rate, or a custom rate you set. Most multi-country operations pick locked monthly for budget predictability and staff fairness.

If the vendor offers only one mode, ask why. If they have no policy at all and "just use today's rate," you'll be reconciling variance every cycle.

4. Cross-country transfers that don't break service

This is the hardest test, and the one most products fail silently. Transfer a programme officer from Kenya to Tanzania to Uganda inside the demo. Then check four things: original service date preserved, leave history continuous, pension restarted under new rules without losing accrued balances, gratuity entitlement bridged correctly.

If the system creates a new employee record at each transfer — walk away. The data model is wrong, and you will discover it during a real exit settlement when the staff member opens a case.

5. Consolidated HQ visibility with respect for country isolation

Your CFO needs to see group headcount, payroll cost in USD, leave liability, attrition, and salary benchmarking across markets — in real time. The country HR teams still need their data fully isolated from each other. These two requirements seem contradictory but aren't: a Global Admin role reads across; country roles read only their country.

If the vendor shows you a "consolidated dashboard" that's just a CSV export emailed monthly, you've found a country-level system pretending to be multi-country. See the multi-country solution overview for what a real implementation looks like.

6. Statutory deadline calendars per country

Kenya PAYE is due by the 9th. South Africa EMP201 is due by the 7th. Nigeria PAYE is due by the 10th. Ghana PAYE filing is due by the 15th. Multiply across your country count and your finance team is tracking 8-12 monthly deadlines. The system should surface them on a calendar with email and Slack reminders, not bury them in country-specific help articles.

7. Local salary disbursement options per country

In Kenya you need M-PESA and bank transfer. In Uganda MTN Mobile Money and Airtel Money matter more than bank. In Nigeria it's mostly bank. In Tanzania Tigo Pesa and Airtel Money cover most field staff. South Africa is bank-and-EFT. The system should generate the right disbursement format per country automatically — bank file for one, mobile-money batch for another — without your finance team learning each provider's spec.

8. Country-specific contract templates and leave types

Kenyan contracts reference the Employment Act 2007. South African contracts must comply with BCEA and reference the relevant Bargaining Council if any. Ghanaian contracts reference the Labour Act 651 of 2003. Annual leave entitlements differ — Kenya is 21 working days, South Africa is 21 consecutive days (which works out shorter), Ghana is 15 working days after 12 months of continuous service.

The vendor should ship country-specific templates and leave types out of the box. If your country HR team has to draft contracts from scratch, that's not a multi-country product.

9. Auditor-scoped access

Donor and internal auditors will ask for read-only access scoped to a single country, a single grant, and a specific date range. The vendor must support this without requiring you to provision a permanent user, change your firewall rules, or expose data outside the audit scope.

Ask: "Can I create a 7-day auditor login that expires automatically and is scoped to one country and one date range?" A serious answer is yes, with a one-click form. A vague answer is a no.

10. Data sovereignty options

If you operate in countries with data localisation requirements — Nigeria (NDPA), Kenya (Kenya Data Protection Act), South Africa (POPIA), Egypt (Data Protection Law) — you need a clear answer on where data is stored, how it's encrypted, and whether you can pin it to a region.

For most companies cloud hosting in a regional data centre (Cape Town, Johannesburg, Nairobi) is enough. For banks, insurers, government entities and some NGOs, on-premise or private-cloud deployment is non-negotiable — and only Enterprise-grade vendors offer it. See SmartHR Enterprise for the deployment model that satisfies risk teams.

11. Update cadence — not just feature releases, but statutory updates

Ask: "Show me the last 10 statutory rate updates you've shipped, when each gazette was published, and when your system went live with the new rate." A serious vendor will produce the log without hesitation. The gap between gazette and go-live should be under 7 days for high-impact changes. If it's measured in weeks, you'll be running last cycle's PAYE bands in the wrong month — which is a compliance issue, not just an inconvenience.

12. Pricing that scales fairly across countries

Per-employee-per-month pricing is the only model that scales fairly when you're in 5+ countries. Per-country flat fees punish growth into smaller markets. Per-module pricing creates an internal political battle every time a country wants a feature. Ask for USD pricing and a local-currency view per country — pinned monthly so finance can budget.

See the pricing page for SmartHR Africa's structure, or jump to /pricing/multi-country for a custom quote built around your country mix.

Red flags that should pause the deal

The country selector is in the user profile, not the URL — meaning the system has one database of all countries with a UI filter on top.
"Multi-currency" means the system stores a single currency code per company; conversion happens in reports only.
The vendor can't answer questions about cross-country transfers without escalating to "the engineering team."
Statutory updates are listed as "professional services" — meaning they bill you each time the law changes.
No public list of supported countries — just "we support all of Africa" in marketing copy.

Test the answer, not the demo

Demos are choreographed. The questions above are designed to break out of the choreography. Run them in your own test session, with your own data. If you operate in countries we haven't named here, swap them in — the questions hold for any multi-country setup in Africa.

If you want to see how SmartHR Africa handles each of these tests, book a 30-minute working session. Bring your country list, your headcount per country, and your hardest cross-country transfer case. We'll run through the framework with you, on real data.

How to Choose HR Software for a Multi-Country African Operation: a 12-Point Evaluation Framework