Digitising multi-country payroll often drags on for lack of method, not lack of goodwill. This guide sets out an eight-week calendar plan for moving several entities in French-speaking Africa onto a single tool, with no double entry and no lost payroll month: prerequisites, week-by-week steps, cut-over checks and pitfalls to avoid.
Eight weeks is an order of magnitude for a scope of a few entities whose data is accessible. A group of ten subsidiaries, or a badly degraded employee master file, will take longer: the method stays the same, applied in waves.
Why multi-country payroll is a project of its own
Multi-country payroll is not national payroll repeated several times. Each country has its own bodies (IPRES and CSS in Senegal, CNPS in Ivory Coast and Cameroon, CNSS and AMO in Morocco, CNSS, INPP and ONEM in the DRC), its own payroll taxes, its own filing calendar and sometimes its own currency: the XOF CFA franc in the WAEMU zone, the XAF in the CEMAC zone, the dirham in Morocco, the Congolese franc and the US dollar in the DRC. Rates are detailed in our guide to social security contributions in Africa.
The project must therefore reconcile two requirements that pull in opposite directions: a common master file so the group can steer its payroll costs, and strict local rules so every payslip is compliant. Most delays come from getting that balance wrong.
What should be common, what stays local
- Common to the group: the structure of the employee master file, the reporting codes, approval workflows, indicators and access rights.
- Specific to each country: rates, ceilings and bases, collective agreements, public holidays, filing formats and salary payment methods.
Prerequisites before you start
Three decisions must be made before week one, or the schedule slips from the outset.
- A sponsor and a group project lead. The sponsor settles trade-offs; the project lead owns the plan and coordinates country leads.
- A payroll lead in each country. They know the local specifics and sign off the tests. Without them, the parameters stay theoretical.
- A cut-over month chosen in advance. Avoid year-end closing and adjustment months. The start of a quarter is often a good compromise.
The 8-week method for digitising multi-country payroll
| Week | Step | Deliverable |
|---|---|---|
| 1 | Scoping and inventory | Map of entities, agreements and variables |
| 2–3 | Configuration and tests | Test payroll on the last closed month, gaps explained |
| 4 | Employee master file cut-over | Import validated field by field |
| 5–6 | Parallel run | Two cycles reconciled line by line |
| 7 | Training | Payroll staff, managers and employees trained |
| 8 | Go-live | First live cycle, old system read-only |
Week 1: scoping and inventory
One workshop per entity is enough to list the applicable collective agreements, local specifics (bonuses, sector allowances, specific leave) and the source of truth for each payroll variable. A simple rule: if a piece of data lives in several Excel files at once, treat it as a risk before migration, not after. Also record, for each country, how salaries are paid (bank transfer, cash, mobile money) and the filing deadlines.
Weeks 2 and 3: configuration and tests
While payroll parameters are configured (rates, ceilings, tax scales, agreements), each country lead prepares a test payroll on the last closed month. It is compared line by line with the old system: every significant gap is explained before moving on. The most frequent gaps concern ceilings by branch, managers' tiers and flat-rate contributions. No cut-over without a clean reconciliation.
Week 4: employee master file cut-over
This is the most sensitive step of multi-country payroll: bulk import of employees, with field-by-field validation of critical data (employee number, social security registration numbers, bank or mobile money details, family status, seniority). Also bring over the current year's cumulative totals and leave balances: without them, year-end filings will be wrong. The old system stays accessible: access is never cut overnight.
Weeks 5 and 6: parallel run
Both payrolls run side by side, country by country. Gaps are analysed and parameters adjusted. This phase reassures every stakeholder (finance, HR, statutory auditors) before the old system is switched off. Set the exit criterion in advance: for example, no unexplained gap on net pay or on the totals declared to each body.
Week 7: training
- Dedicated sessions for payroll staff in each country.
- A short session for managers, focused on approving variables and absences.
- Simple communication for employees: app access, reading the new payslip.
- Local documentation, adapted to each country's specifics.
Week 8: go-live
Payroll runs live on the new tool. The old one stays read-only for as long as archiving and any audits require. Reinforced support is kept for the first weeks to absorb questions from the field.
Compliance and data: points to lock down country by country
Digitising multi-country payroll also means moving sensitive personal data. Several countries regulate this processing: in Senegal, law no. 2008-12 on personal data, overseen by the CDP; in Morocco, law 09-08, overseen by the CNDP; in Cameroon, law no. 2024/017 of 23 December 2024, whose compliance period expired on 23 June 2026. Check where the data is hosted, who can access it and what the contract says about transfers outside the country.
Paperless payslips are also gaining ground. In Senegal, the new Labour Code (law no. 2026-18 of 3 September 2026, in force since 18 September 2026) provides for a paper or electronic payslip, whose electronic storage must guarantee availability, integrity and confidentiality (official page on the reform). In other countries, check local conditions before dropping paper.
Resources to commit during the project
The schedule holds if the workload is planned. On the group side, the project lead spends a large share of their time steering over the eight weeks, with a short weekly check-in and a tracker of gaps by country. On the country side, the payroll lead is mostly needed in weeks 2, 3, 5 and 6: tests, reconciliations and the parallel run. Plan to lighten their load in those periods, as they keep running current payroll at the same time.
Finance steps in twice: to approve the reporting codes at scoping, and to sign off the exit from the parallel run. Statutory auditors appreciate being told about the calendar and planned checks in advance. Finally, IT checks access, authentication and file exchanges with banks or mobile money operators. In multi-country payroll, this last point is often discovered late, although it determines the first live payment.
Mistakes that derail multi-country payroll
- Switching everything at once. Move in waves, country by country or entity by entity. The first wave becomes the template for the next.
- Underestimating master data quality. It is the most frequent cause of delay: duplicates, inconsistent employee numbers, missing registrations.
- Standardising what must stay local. A "group" pay code does not replace a national calculation rule.
- Switching off the old system too early. Keep read access throughout stabilisation.
- Forgetting managers. If absences and variables are not approved in the tool, data entry falls back on HR and the gain disappears.
Indicators to track after go-live
Once multi-country payroll is live, four indicators are enough to tell whether the project delivers: post-closing corrections per country, time between variable cut-off and payment, the share of filings submitted on time, and employee payslip queries. Track them month by month and compare countries: a country that falls behind often points to a local parameter or process to review. For the monthly cycle itself, see our guide to payroll management in Africa.
Frequently asked questions
Are eight weeks enough for multi-country payroll?
For a few entities with clean data, it is a realistic order of magnitude. Beyond that, run several eight-week waves rather than one longer project.
Do you need a single tool for multi-country payroll?
It is preferable for reporting and access rights, provided the tool genuinely applies each country's rules. Our guide to payroll software in Africa details the selection criteria.
Which country should come first?
The entity with the cleanest data and the most available lead. A successful first wave makes the next ones easier to win over.
What about payroll history?
At a minimum, bring over the current year's cumulative totals and leave balances. Earlier years can stay viewable in the old system, read-only.
Key takeaways
- Multi-country payroll combines a common master file with strict local rules: settle the balance at scoping.
- The eight-week plan rests on a test on a closed month, a validated master file cut-over and two parallel-run cycles.
- Move in waves and keep the old system read-only.
- Check each country's rules on personal data and electronic payslips.
Preparing to digitise multi-country payroll? Discover our multi-country payroll software for French-speaking Africa or book a demo on your own entities.
Want to go further?
See how Socium transforms HR and payroll practices across 12 African countries.