Leave management is rarely described as a strategic issue, yet it is one of the processes that create the most day-to-day friction: requests lost in an inbox, disputed balances, two critical absences discovered in the same week. None of this is inevitable. It can be fixed structurally, once and for all, provided you separate what comes from the country’s law, what comes from your internal rules and what comes from the tool. This guide covers all three, then points you to our country guides for the detail of the applicable law.
Why leave management creates so much friction
Three things are almost always missing: a channel where the request leaves a trace, a balance employees can check for themselves, and a team calendar that shows conflicts before they happen. The three causes are independent, and each one is enough to degrade the process.
- The channel. A request made by email, chat message or word of mouth has no trace and no status. Nobody knows whether it was received, read or approved, and the discussion starts again with every reminder.
- The balance. When only HR knows the exact balance, every question goes through HR. The team becomes a bottleneck, and the smallest calculation gap turns into a dispute.
- Visibility. Without a shared team calendar, conflicting absences are discovered too late, once the tickets are bought or the site is already short-staffed.
There is also a financial risk that is often overlooked: a poorly tracked balance becomes a liability. Days earned and not taken are paid out when the employee leaves, and an error accumulated over several years shows up in the final settlement, sometimes in front of the labour inspectorate.
The concepts to master before configuring anything
Sound leave management rests on four concepts that every labour code in the region addresses, each with its own figures. Understanding them lets you read any national text and ask the right questions of your adviser or software vendor.
Accrual
Employees earn leave days as they work, at a monthly rate set by the country’s law and sometimes improved by the collective agreement or the contract. Some absences count as actual work and keep accruing rights, others do not. Days are counted as working days, business days or calendar days depending on the text, and mixing the three is the most common spreadsheet error.
Additional days
Most codes grant extra days, for instance for seniority, family situation or certain distinctions. These are what make a manual calculation fragile: they depend on data that changes (hire date, dependent children) and must be recalculated every year.
Taking leave and planning
Leave that has been earned must be taken, under conditions set by law: reference period, departure schedule set by the employer, the option to split leave, limits on carrying days over. Special leave for family events and public holidays follow separate rules and must not be deducted from annual leave.
Leave pay
During leave, the employee receives an allowance calculated on a basis set by each code, which is not always the same as the monthly salary. When the contract ends, accrued days not taken give rise to a compensatory payment. This is where leave management connects directly with payroll.
Leave management: what changes from one country to another
The principles are shared, the figures are not. Days earned per month, additional days, carry-over limits, the basis for leave pay: each country has its own rules, and a group operating in several countries cannot apply a single grid. Rather than summarising rules that change over time, we cover them country by country.
| Country | What makes it specific | Detailed guide |
|---|---|---|
| Senegal | A new legal basis: Law No. 2026-18 of 3 September 2026 enacting the Labour Code (Code du travail), published in the Official Journal of 17 September 2026, replaces Law No. 97-17 of 1997. Balances should be reviewed against the new text. | Leave management in Senegal |
| Ivory Coast | Several types of additional days to track (seniority, children, distinctions) and specific rules on splitting leave. | Leave management in Ivory Coast |
| Cameroon | Additional days under the Code, splitting, carry-over and time limits on claims. | Leave management in Cameroon |
| Benin | Additional days for seniority and for mothers, in an economy of small businesses and NGOs with small teams. | Leave management in Benin |
| DRC | Leave as a matter of public policy, a duration that grows with seniority and limited accumulation, with teams often spread across several sites. | Leave management in the DRC |
| Morocco | Seniority increase, organisation of departures and precise rules on leave pay. | Leave management in Morocco |
| Multi-country group | Aligning a group policy without falling below the legal minimum of any country. | Leave management in Africa |
For Senegal, the official text of the new Code is available in Official Journal No. 7931 of 17 September 2026 (in French).
The internal rules to set once and for all
The law sets a floor. Everything else is a matter of organisation, and that is where the quality of the process is decided. Five rules are enough for the vast majority of companies.
- Notice period, adjusted to the type and length of leave: one day is not requested like three weeks.
- Maximum simultaneous absences per team or site, with an alert at the time of the request.
- The approval chain, with a named deputy when the approver is away: this is what blocks most often.
- Carry-over rules for days not taken, within the limits of the country’s law.
- A closed list of absence types (annual leave, special leave, sickness, maternity, unpaid leave), each with its own effect on the balance and on payroll.
Once configured, these rules apply automatically to every request, with no case-by-case arbitration. Managers still decide, but they decide with the balance, the calendar and the rule in front of them.
Rolling out leave management in five steps
For a company of 50 to 200 employees, allow four to six weeks between the decision and the first normal month. The schedule below is a realistic illustration, to adapt to your size.
- Week 1: agree opening balances. Take each employee’s balance, have it confirmed in writing and settle discrepancies before migrating. A tool that starts on disputed balances inherits the dispute.
- Week 2: write the policy. Put the five internal rules above into a short note, approved by management and, where relevant, presented to staff representatives.
- Week 3: configure. Country rules, additional days, public holidays, approval chains, deputies.
- Week 4: pilot with one team. Choose a representative team, including field staff who will submit requests from their phones.
- Weeks 5 and 6: roll out and close the old channel. As long as email is accepted, it will be used. Set a date after which only requests made through the tool are processed.
Spreadsheet, email or software: comparing approaches
| Criterion | Email and spreadsheet | Generic international software | HRIS configured for the country |
|---|---|---|---|
| Request trail | Scattered | Yes | Yes |
| Balance calculated under local law | Manual, fragile | To be rebuilt yourself | Built in per country |
| Local additional days and holidays | Manual | Often missing | Included |
| Link with payroll | Re-keying | Variable | Direct |
| Mobile use on weak networks | No | Variable | Check during the demo |
A spreadsheet remains defensible for a very small organisation. Beyond about twenty employees, or as soon as there are several sites, the hidden cost of re-keying and disputes generally exceeds the cost of a tool.
Indicators to track
- Average untaken balance per employee, and its trend: a growing balance is a growing liability.
- Average response time to a request, per manager.
- Share of requests outside the tool in the first months: it measures real adoption.
- Peaks of simultaneous absence per team, to anticipate around holidays and school breaks.
- Number of balance disputes: it should trend towards zero.
Leave management FAQ
Who sets leave dates, the employee or the employer?
Under most codes in the region, the employer organises the order of departures, taking into account business needs and employees’ circumstances. The employee proposes, the employer decides. Check the exact rules for your country in the relevant guide.
Can approved leave be refused afterwards?
Going back on an approval creates social and legal risk, especially if the employee has already incurred costs. Hence the value of a calendar visible at the time of the request: conflicts are settled before approval, not after.
How does leave management work in a group operating in several countries?
With a common base (channel, chain, indicators) and calculation rules specific to each country. The Africa guide listed in the table above sets out the alignment method.
Does a 30-person company need software?
Not necessarily, but it needs at least a single channel, a shared balance and a team calendar. If the spreadsheet does not let employees check their balance without going through HR, it does not solve the problem.
Leave management: key takeaways
- Friction comes from three gaps: a traceable channel, a visible balance, a shared calendar.
- The country’s law sets entitlements: accrual, additional days, carry-over, leave pay. Internal rules set how the process runs.
- Five rules to configure once: notice, simultaneous absences, chain with deputy, carry-over, absence types.
- Agree validated balances before any migration.
- A poorly tracked balance becomes a liability payable when the employee leaves.
Socium centralises requests from mobile, calculates balances under each country’s rules and lets managers approve in one click, with a consolidated team calendar and a direct link to payroll. Discover our time and absence module for leave management, or book a demo from that page.
Want to go further?
See how Socium transforms HR and payroll practices across 12 African countries.