Can an Employer Refuse Annual Leave in South Africa?

What does the BCEA say?

Section 20 provides that annual leave should be taken in accordance with an agreement between employer and employee. Where there is no agreement, the employer determines the timing. At the same time, the BCEA requires the employer to grant the statutory annual leave no later than six months after the end of the relevant annual-leave cycle. The question is whether the employer can decline these particular dates while still ensuring that the employee receives the leave to which they are entitled.

Why might particular dates be difficult?

Consider a customer-support team of six. Two employees already have approved leave. Another request is pending. A fourth employee now requests the same week. That employee has enough leave.

• Entitlement: the employee has a sufficient balance.
• Operations: overlapping absence may create a staffing problem.

A sensible leave process needs both pieces of information.

What should the manager see?

An approval screen should show more than “Thandi requested five days.” The manager needs context:

• Requested dates: 14–18 December.
• Leave balance: sufficient.
• Already approved away: 2 employees.
• Separate pending requests: 1 employee.
• Projected availability after this new approval: 50%.
• Critical-role coverage: at risk.

Now the manager can make an informed decision. Illustrative scenario: with six team members and two already away, approving this new request would leave three available (50%). If the separate pending request is also approved, only two would remain available (33.3%). Pending requests are shown separately, not treated as approved absence.

Operational discretion should not become arbitrary decision-making

A good policy should explain:

• how leave is requested;
• normal notice expectations;
• who determines timing;
• how overlapping requests are handled;
• whether particular periods require additional planning;
• what minimum staffing or skills are required;
• how employees are informed of decisions; and
• how alternative dates are considered.

Consistency matters.

Is “first come, first served” enough?

It can be useful because it is simple and transparent. But it is not necessarily sufficient for every organisation. The first person to request leave may be the only person available with a critical capability. Another employee may have repeatedly accommodated colleagues during previous peak periods. A sound system therefore combines transparent policy with documented managerial judgment.

What if the employee is repeatedly prevented from taking leave?

The BCEA places an obligation on the employer to grant statutory annual leave. “Operational requirements” should therefore not become a permanent explanation for why one employee can never take meaningful leave. If the organisation genuinely cannot function whenever a particular employee is absent, that may indicate a succession, cross-training or workforce-resilience problem.

Better approval workflow

A strong process looks like this:

1. The employee submits a request.
2. Entitlement, availability and policy are checked.
3. The manager makes a decision.
4. The balance is updated.
5. The decision and its impact are recorded in the audit history.

The system should support managerial judgment rather than replace it.

LeaveCtrl’s role

LeaveCtrl should help managers answer two connected questions:

• Does the employee have enough days, and does the request meet the applicable rules?
• What happens to the team if these dates are approved?

That is the difference between leave administration and workforce availability.