Sick Leave in South Africa: The 36-Month Cycle, Medical Certificates and Employer Responsibilities

How much sick leave is available?

During every sick-leave cycle, the BCEA generally entitles an employee to paid sick leave equal to the number of days the employee would ordinarily work during six weeks.

For example:

• Five days per week × six weeks = 30 working days.
• Six days per week × six weeks = 36 working days.

This is a 36-month entitlement—not an annual allocation.

What happens during the first six months?

A new employee does not simply receive the entire three-year sick-leave entitlement for immediate use. During the first six months of employment, the employee is generally entitled to one day’s paid sick leave for every 26 days worked. Sick leave taken during this initial period may reduce what remains available during the balance of the first sick-leave cycle. The employee’s employment date therefore matters.

When can an employer require a medical certificate?

Section 23 of the BCEA addresses when an employer is not required to pay qualifying sick leave if the employee fails, when requested, to provide the required medical certificate.

The relevant circumstances include absence:

• for more than two consecutive days; or
• on more than two occasions during an eight-week period.

The precise statutory wording matters. A blanket rule stating that “two days off always requires a doctor’s note” does not accurately describe these thresholds.

What should a medical certificate establish?

For BCEA purposes, the certificate must meet the statutory requirements concerning the employee’s incapacity to work because of sickness or injury and the appropriately qualified professional providing the opinion. Employers should avoid unnecessarily demanding detailed diagnoses where those details are not required. Medical information should also be handled with appropriate confidentiality and privacy controls.

Sick leave needs a reliable record

A useful sick-leave record should connect:

• absence dates and the applicable cycle;
• leave used;
• supporting evidence, where required; and
• the resulting balance.

Compare that with a common manual process:

1. The employee messages the supervisor.
2. The supervisor forwards the message to HR.
3. The certificate arrives on WhatsApp.
4. HR plans to update Excel later, while payroll holds a different record.
5. Three months later, nobody can find the supporting document.

Without a single governed record, the organisation cannot reliably connect the absence, supporting document and payroll outcome.

What should HR track?

At minimum:

• current sick-leave cycle;
• cycle start and end dates;
• employee work pattern;
• entitlement;
• sick leave used;
• remaining entitlement;
• supporting documentation where required;
• adjustments and reasons; and
• transaction history.

Absence patterns require care

Structured data can help employers identify repeated operational problems. But an absence pattern does not automatically prove misconduct.

Employers should distinguish between:

• legitimate illness;
• disability or accommodation issues;
• occupational injury or disease;
• possible abuse requiring fair investigation; and
• operational pressure caused by absence.

The purpose of better data should be better management—not automatic suspicion.

How LeaveCtrl should handle sick leave

LeaveCtrl should calculate the cycle around the employee rather than requiring HR to remember when the three-year period starts and ends.

The system should know:

• which cycle applies;
• what has been used and what remains;
• whether supporting evidence may be required; and
• what changed the balance.

That is much safer than maintaining an unexplained “30 days” field in a spreadsheet.