How do you calculate the true hourly cost of an employee in South Africa?

Add employer UIF, the skills development levy, COIDA, provisions for leave and sick leave and any 13th cheque to gross salary, add an overhead allocation of around 25 percent for workstation, IT, software and management time, then divide by genuinely productive hours rather than contracted ones.

How many productive hours does a full-time employee actually have per month?

About 122, against 176 contracted. Leave and public holidays take roughly 18 hours, sick leave 4, meetings, training and admin 16, and interruptions and context switching another 16. Nobody performs six hours of concentrated data work a day, every day, for a month.

What is a realistic loaded hourly rate for a South African admin role?

Roughly 2 to 2.5 times gross monthly salary divided by 176. For someone on R15 000 a month that works out at about R187 an hour, against the naive figure of R85.

← All guides

The cost of manual product data

The real hourly rate of your product data administrator

The Smart Station team21 July 20267 min read

Key takeaways

Gross salary divided by contracted hours understates the true hourly cost of an employee by 40 to 60 percent.
For a product data administrator on R15 000 a month, the total monthly cost is about R22 758 once UIF, the skills development levy, COIDA, leave and sick-leave provisions, a 13th cheque and a 25 percent overhead allocation are added.
A full-time employee is contracted for about 176 hours a month but is available for roughly 122 hours of concentrated work, after leave, sick leave, meetings, training and interruptions.
R22 758 divided by 122 productive hours is R187 an hour — 2.2 times the naive figure of R85.
A useful rule of thumb for South African office roles: true hourly cost is roughly 2 to 2.5 times gross monthly salary divided by 176.
At R85 an hour almost no intervention pays for itself. At R187, most do. Same business, same work — the decision turns entirely on a number most people never calculate.

Any decision about whether to hire, outsource or automate catalogue work depends on one number: what an hour of that work actually costs. Almost everybody uses gross salary divided by contracted hours, and almost everybody is therefore wrong by 40 to 60 percent.

Why gross salary is the wrong number

Gross salary is what the employee receives. It is not what the employment costs, and it is not spread across the hours you think it is.

Two adjustments are needed: add the costs of employment beyond salary, and divide by hours that are genuinely available for the work rather than hours contracted.

The build-up

Working through it for a product data administrator on R15 000 a month:

Component	Monthly	Note
Gross salary	R15 000	The starting point
UIF (employer)	R148	1% capped
Skills development levy	R150	1% of payroll
COIDA	R60	Varies by industry classification
Leave provision	R1 250	~8.3% for 21 days
Sick leave provision	R400	Statutory entitlement, provisioned
13th cheque, if paid	R1 250	Omit if not applicable
Employment cost	R18 258
Overhead allocation	R4 500	Desk, IT, software, management, ~25%
Total monthly cost	R22 758

Overhead allocation is the contested line. It covers the workstation, the laptop, the software licences, the proportion of premises and the management time this person consumes. Twenty-five percent is a common working figure for an office role; use your own if you have it. Excluding it entirely is the more serious error, because those costs are real and somebody is paying them.

Then divide by productive hours

A full-time employee is contracted for roughly 176 hours a month. They are not available for 176 hours of catalogue work.

	Hours
Contracted	176
Less leave and public holidays	−18
Less sick leave provision	−4
Less meetings, training, admin	−16
Less interruptions and context switching	−16
Productive hours	122

The last line is the one people resist, and it is well supported by any honest time study. Nobody performs six hours of concentrated data work a day, every day, for a month.

The answer

R22 758 ÷ 122 hours = R187 an hour.

Against the naive calculation — R15 000 ÷ 176 = R85 — the real figure is 2.2 times higher. Every build-or-buy decision made on R85 is being made on a number that is wrong by more than half.

A useful rule of thumb for South African office roles: the true hourly cost is roughly 2 to 2.5 times gross monthly salary divided by 176.

The decision it changes

Return to a catalogue onboarding 2 000 SKUs a year at 25 minutes each — 833 hours.

At	Annual cost
R85/hr (naive)	R70 805
R150/hr (conservative)	R124 950
R187/hr (calculated)	R155 771

At R85, almost no intervention pays for itself and the correct answer is to carry on. At R187, most interventions do. Same business, same work — the entire decision turns on a number most people never calculate.

Two cautions. Do not use this number to justify a decision you have already made; calculate it before you look at any pricing. And note that automation does not remove the hour, it changes what happens in it — the review time that replaces data entry is real, and any honest model includes it.

Common questions

How do you calculate the true hourly cost of an employee in South Africa?: Add employer UIF, the skills development levy, COIDA, provisions for leave and sick leave and any 13th cheque to gross salary, add an overhead allocation of around 25 percent for workstation, IT, software and management time, then divide by genuinely productive hours rather than contracted ones.
How many productive hours does a full-time employee actually have per month?: About 122, against 176 contracted. Leave and public holidays take roughly 18 hours, sick leave 4, meetings, training and admin 16, and interruptions and context switching another 16. Nobody performs six hours of concentrated data work a day, every day, for a month.
What is a realistic loaded hourly rate for a South African admin role?: Roughly 2 to 2.5 times gross monthly salary divided by 176. For someone on R15 000 a month that works out at about R187 an hour, against the naive figure of R85.

Where to next

Who wrote this

The Smart Station team

Written by the engineering and delivery team at Smart Station (Pty) Ltd, the South African software company that builds GetShopSync. The material here comes from building catalogue systems for distributors — it is what we have measured and what we have got wrong, not a survey of the literature.