Automate Employee Onboarding: the paperwork one new hire triggers, and where it stops being manual

A new hire in South Africa triggers at least four separate records: the written particulars required on day one, the employee record kept for three years, the monthly UIF declaration, and payroll registration. Most of them ask for the same handful of fields. Automating onboarding means capturing those fields once and letting every artefact draw from them.

That is the whole idea, and it is worth being precise about why it works, because the overlap between those records is larger and more literal than most owners realise.

What one new hire actually triggers

Before any of this is a software question, it is a list. Hiring one person in South Africa sets off a chain of obligations that do not arrive together and are not owned by the same person in most small businesses.

1. Written particulars of employment, on commencement. Section 29 of the Basic Conditions of Employment Act requires the employer to supply the employee with written particulars covering a specified list of matters when employment begins.
2. The employee record, from the first day worked. Section 31 requires a record of the employee's name and occupation, time worked, remuneration paid, and date of birth if the employee is under 18.
3. The UIF declaration, before the 7th of the month. New appointments and changes go onto the employer's UI-19 declaration monthly.
4. Payroll and tax registration. The person has to exist in payroll before the first pay run, with an identity number and banking details, or the first payment fails and the first submission is wrong.

None of these is difficult on its own. The cost is that each one is a separate act of typing, performed at a different moment, by somebody working from a different piece of paper.

Two sections of the same Act ask for the same field, in the same words

This is the part that makes onboarding a genuine automation candidate rather than a tidy-up job. Read the two record-keeping obligations side by side, in their own wording.

Section 29(1)(b) requires "the name and occupation of the employee, or a brief description of the work".

Section 31(1)(a) requires "the employee's name and occupation".

Same Act. Two sections apart. The same two facts, demanded in almost identical words, for two different artefacts kept on two different schedules: one handed over on day one, one maintained continuously and retained, in the Act's words, "for a period of three years from the date of the last entry in the record".

The start date behaves the same way. Section 29(1)(d) requires the date on which employment began. The same date is what the UI-19 declaration reports as the appointment. Nothing about the fact has changed between the two uses. Only the form it is being written onto has changed.

That is the shape of the problem in one sentence: the information is stable and the containers are not. A business that types the name, the occupation and the start date four times is not doing four pieces of work. It is doing one piece of work and three transcriptions, each of which can disagree with the others.

Why the search results are about Microsoft 365, and why that does not help you

Search for how to automate employee onboarding and the results are dominated by Power Automate flows, Active Directory provisioning and enterprise HRIS integrations. Those articles are not wrong. They assume a company with a directory service, licensed identity management and an IT function to own the flow.

A six-person business in South Africa has none of that, and does not need it. The provisioning half of enterprise onboarding, creating accounts and assigning licences, is the half a small business already handles in a few minutes. The half that actually costs it time is the statutory and payroll half above, which enterprise articles barely mention because a large employer has a payroll department absorbing it.

So the useful question is not which enterprise tool to buy. It is narrower: which of those four records can be generated from one capture instead of typed from scratch.

How to stop re-keying the same person

The mechanism matters more than the tool, so here it is concretely.

Capture once, at the offer stage. One form, completed by the new hire before day one, collects the fields every downstream record needs: full names as they appear on the identity document, identity number, address, banking details, tax reference number, start date, job title, ordinary hours, and rate of pay. That single submission is the only place a human types this person's details.

Generate the day-one document from that capture, not from a template somebody edits. The section 29 particulars are largely a merge: employer details are constant, the employee's details come from the form, and the leave, notice and hours clauses come from your standard terms. Editing last month's contract in a word processor is how a previous employee's job title survives into somebody else's document.

Open the employee record at the same moment, not later. Section 31 wants a running record from the start, and the cheapest running record is one that was created automatically when the person was captured, rather than reconstructed in March because somebody asked for it. If time worked is already being captured by a time tracking tool, that half of the record maintains itself.

Make the monthly declaration a report, not a memory task. The UI-19 asks who joined and who left. If joiners and leavers are dated events in one system, the monthly declaration is a filter over data that already exists. If they live in a WhatsApp thread and somebody's memory, it is a monthly investigation.

Put the reminder on the calendar, not on a person. The 7th is a fixed date. Every recurring obligation with a fixed date should be generating its own reminder, with the list attached, before the person responsible has to remember it exists.

The test for whether this has worked is simple. After a new hire is captured, count how many times a human types that person's identity number. The target is one.

What to automate first, and what to leave alone

Not all of it is worth automating, and the honest answer to which parts are is the same as it is for any process.

The work	Automate it?	Why
Collecting the new hire's details	Yes, first	Every other record depends on it, and it happens once per hire with no judgement involved.
Producing the day-one particulars	Yes	Mostly a merge of captured fields into standard terms.
Opening and maintaining the employee record	Yes	It is a byproduct of systems you already run, if they are connected.
Monthly joiner and leaver declaration	Yes, as a report	The data exists; the work is retrieval, not decision.
Deciding the rate of pay, the job title, the probation terms	No	These are judgements. Automating the paperwork around a decision is not the same as automating the decision.
The first week of actually teaching somebody the job	No	A checklist helps. Nothing replaces it.

The same tiering applies to every process in the business, and it is worth applying deliberately rather than by enthusiasm. We set it out in workflow automation for small business.

One correction worth making about section 29

A common belief is that the day-one obligation is to get a signed contract back. It is not. Section 29 obliges the employer to supply the written particulars. It does not oblige the employer to obtain a signature on them.

That distinction matters operationally, because businesses routinely treat an unsigned document as an unmet obligation and chase it for weeks while the record sits incomplete. Supplying the particulars, and being able to show when and how they were supplied, is the thing the section asks for. A signature is good practice and useful evidence. It is not what makes the supply obligation met.

This is also a good argument for delivering the document through something that records delivery automatically, rather than through an attachment somebody may or may not have sent.

Frequently Asked Questions

What paperwork is legally required when you hire someone in South Africa?
The Basic Conditions of Employment Act requires written particulars of employment supplied on commencement under section 29, and an employee record under section 31 covering name and occupation, time worked and remuneration paid. Separately, the new appointment goes onto the employer's monthly UIF declaration.

How long must employee records be kept?
Section 31(3) of the Basic Conditions of Employment Act requires the record to be kept for three years from the date of the last entry in it. That runs from the last entry, not from the employee's start date or their last day.

Does an employment contract have to be signed to be valid in South Africa?
Section 29 requires the employer to supply written particulars of employment, not to obtain a signature on them. A signed document is strong evidence and remains good practice, but an unsigned one does not by itself mean the section 29 obligation was missed.

What part of employee onboarding is worth automating first?
The initial capture of the employee's details. Every later record, the particulars, the employee record, the UIF declaration and payroll, draws on the same fields, so capturing them once removes the transcription step from all of them at the same time.

Is automating onboarding different for a small business than for a large one?
Yes. Most published guidance assumes directory services and enterprise identity management, which is the part a small business handles quickly anyway. The statutory and payroll half is where a small employer's time actually goes, and that half is rarely covered.

Where to start

Onboarding is usually not the only place the same details get typed twice. Client intake has the identical shape, which is why we wrote automating the client onboarding process separately, and the wider pattern is set out in the real cost of manual admin.

If you want the whole picture before changing anything, a business autopsy maps where information gets re-entered across the business, not just at hiring. Or start with a discovery call.

Related reading: employment contracts in South Africa and UIF registration for employers.

Sources

• Basic Conditions of Employment Act 75 of 1997, section 29 (written particulars of employment), read 27 August 2026. Source of the quoted wording of section 29(1)(b) and of the commencement timing and the list of required particulars.
• Basic Conditions of Employment Act 75 of 1997, section 31 (record of employees), read 27 August 2026. Source of the quoted wording of section 31(1)(a) and of the three-year retention requirement in section 31(3), "for a period of three years from the date of the last entry in the record".
• Google autosuggest, gl=za, probed 27 August 2026, for the observation that published guidance on this keyword is dominated by Microsoft 365, Power Automate and Active Directory provisioning.