Onboarding is the bridge between two systems and two states: a hired candidate in the recruiting tool, and an employee on the record in the HRMS. It runs from the moment an offer is accepted, through a productive day-one, and across the first 90 days. The key seam is the offer-accepted handoff — where the ATS lets go and the employee record begins. In South Africa it's also where the statutory clock starts: written particulars, registrations, and a tax record all become due the day someone walks in.
Recruiting ends with a decision: this person, this role, at this offer. Onboarding begins the moment they say yes. Its job is to turn an accepted offer into a real employee — provisioned, paid, paperwork done, and ramping toward useful work — without dropping anything in the gap between the two systems that hold the data.
That gap is the load-bearing detail. The candidate's record lives in an ATS (the applicant-tracking system used to recruit them). The employee's record lives in the HRMS. The offer-accepted handoff is the seam where one hands to the other — and it's where things go wrong: data re-keyed by hand, a contract that never matched the offer, a start date nobody told IT about. Get the seam right and the rest of onboarding is a checklist. Get it wrong and you spend the first 90 days firefighting.
This leaf treats onboarding as that handoff plus the sequence that follows — and, because this is South Africa, the statutory starting line that fires the day someone begins. It sits between recruitment (the prior stage) and performance (the next), over the compliance backbone.
Onboarding is a sequence, not an event. Each phase has a job; each one is where a different thing gets dropped if nobody owns it. The phases below are the spine — provisioning, paperwork, policy sign-off, and role ramp threaded through all three.
The handoff lands. Create the employee record, kick off provisioning (laptop, accounts, access), collect the documents the contract and payroll need, and send a welcome pack so day-one isn't a cold start.
Written particulars and the signed contract in hand, accounts working, a desk and a person to find. Policy sign-off begins. The statutory record must exist by now — not "soon".
Role ramp: context, goals, the people and systems the job touches. Probation review cadence. The handoff to performance happens here — onboarding ends when the person is simply an employee.
| Thread | What it covers | Owned by |
|---|---|---|
| Provisioning | Hardware, accounts, system and building access — scoped to the role | IT + manager |
| Paperwork | Contract, written particulars, banking, tax and statutory-registration data | HR + payroll |
| Policy sign-off | Acknowledgement of policies — code of conduct, IT/acceptable use, POPIA notice | HR |
| Role ramp | Context, first goals, introductions, probation review cadence | Manager |
In South Africa, onboarding isn't just culture and kit — it's the point where a stack of statutory duties becomes live. These fire on day-one, not at month-end. Miss them and you're non-compliant before the new hire has finished their first coffee.
The Acts, figures and thresholds above are orientation, current as at mid-2026, and application is fact-specific. Validate every contract, written-particulars pack, registration and payroll set-up with a qualified SA labour-law practitioner or registered payroll specialist before you rely on it. The deeper statutory map lives on the compliance leaf — onboarding is where it first bites.
No stage collects more personal data faster than onboarding. In one sitting you take an ID number, banking details, a tax number, next-of-kin, and sometimes health or biometric information. POPIA governs all of it — and the Information Regulator enforces.
Apply POPIA (Protection of Personal Information Act 4 of 2013) from the first form. The two conditions that bite hardest here are minimality — collect only what the purpose actually needs, not everything the form template happens to ask — and purpose limitation — onboarding data is gathered to employ and pay the person, not to be silently repurposed later.
The lawful basis for most onboarding data is the employment contract itself — the processing is necessary to perform it — not a blanket consent tick-box. Reaching for consent where the contract already grounds the processing is a common mistake; consent can be withdrawn, the contractual basis is sturdier. Secure what you collect under section 19 (appropriate technical and organisational safeguards) and keep it in-country on an SA-resident store.
Health data and biometrics (a fingerprint clock-in) are special personal information with extra protection — don't collect them as a default, and justify each one against a specific purpose.
Before a field goes on the new-hire form, ask: which statutory or contractual purpose needs it? UIF and PAYE need an ID and tax number; payroll needs banking; emergency contact is a safety purpose. A field that fails the test shouldn't be there. Same discipline the Frappe HR leaf sets for the employee record — minimality, then security, then in-country.
Onboarding is where the employee record comes into existence and where the recruiting tool finally lets go. The agent threads through the busywork — but stays well clear of anything binding.
The HRMS employee record is created here. In this tree that's Frappe HR's Employee DocType — the canonical store of who someone is, what they're paid, and the statutory data the registrations need. The recruiting side hands over: Huly carries the hired candidate to the seam, and onboarding picks them up. The whole game at the handoff is to move the data once, cleanly, rather than re-key it by hand.
The agent assists with the repeatable scaffolding: generating onboarding checklists from the role, assembling document packs and welcome material, building provisioning task lists, and firing reminders before deadlines slip. What it does not touch: the contract terms and the right-to-work verification. Those are human decisions with legal weight — the agent drafts around them and chases the admin, but a person owns what's binding.
The offer-accepted handoff is the one place to get integration right. Map the candidate fields the ATS holds to the Employee record the HRMS needs, and carry them across in one operation rather than typing them twice. Re-keying is where errors enter the statutory record — the wrong ID on a UIF registration, a banking typo on the first payslip. Treat the handoff as a build item, scoped tightly, with the agent assisting and a human confirming.