HR for South African employers

One place for a whole working life.

The modern HR system made for South Africa. Hiring, onboarding, pay, leave, reviews and learning on one employee record, with payroll connected and POPIA built in. The AI drafts the paperwork around each moment, and people make every decision.

Book a demoFollow Lindiwe's 31 years

13 moments, 2026 to 2057

In use at

One person, start to finish

Lindiwe Dube, Logistics Coordinator

Meridian Logistics is a fictional South African company. Follow Lindiwe from the night she finds the job to the day she retires, and see who did what at each step.

A person decidedandteam's rules worked it outAI helped

01 · Careers site

Sun 15 Feb 2026, 21:40 · Lindiwe, candidate

She finds a job she wants at 21:40 on a Sunday.

Meridian's careers site is hosted by andteam. Its assistant answers from the job ad and Meridian's own pages, and shows where each answer comes from.

AI (AI helped)
Answered her question from Meridian's depot page.
Lindiwe (a person decided)
Decided to apply.

02 · Applying

21:52, the same night · Lindiwe, candidate

Her CV fills in the form. She checks every field.

Each field read from her CV is marked, and nothing is sent until she has looked at it. She gives her POPIA consent as she applies, and can download or delete her profile at any time.

AI (AI helped)
Read her CV into 11 fields.
Lindiwe (a person decided)
Fixed one, added her licence and sent it.

03 · Shortlisted

Tue 17 Feb 2026 · Sipho, recruiter

The recruiter sees why she matches, line by line.

Match scoring explains itself against the role's criteria and is advisory only. It never rejects or moves a candidate. Names, photos and protected attributes are never used.

AI (AI helped)
Scored her against five criteria and gave a reason for each.
Sipho (a person decided)
Read the reasons and moved her to Screen.

04 · Offer signed

Thu 5 Mar 2026, 19:12 · Lindiwe, new starter

The offer arrives signed by Meridian, waiting only for her.

Each approver saw the letter beside the package. By default the employee signs last, inside andteam, with no separate signing account.

andteam (andteam's rules)
Sent the offer to the right approvers in order.
Thabo, Naledi (a person decided)
Approved it and signed for Meridian.
Lindiwe (a person decided)
Signed last, on her phone.

05 · Onboarding

Wed 1 Apr 2026 · Lindiwe, Logistics Coordinator, day 1

By her first morning, the paperwork is done.

Her journey opened the moment she signed: details, documents, policies, medical aid and right to work, page by page on her phone. Her health answers chose a medical aid shortlist, then were discarded. They were never stored and never sent to the AI.

AI (AI helped)
Drafted plain-language points for six policies. HR approved each one.
andteam (andteam's rules)
Filled her medical aid and fund forms from her record.
Lindiwe (a person decided)
Signed four documents in one sitting.

06 · First payslip

Fri 24 Apr 2026 · Lindiwe, Logistics Coordinator

Her first payslip is exactly the one payroll issued.

Payroll runs on Deel Local Payroll, powered by PaySpace, fed from andteam. Payslips and IRP5s come back to her Pay page as PaySpace produced them, never redrawn.

andteam (andteam's rules)
Sent her start date and pay to PaySpace in April's signed-off changes.
Payroll team (a person decided)
Ran the April payroll in PaySpace.
AI (AI helped)
Not involved. Pay figures never go to the AI.

07 · Leave

Sun 6 Dec 2026, 07:42 · on WhatsApp

She books leave on WhatsApp. Christmas Day counts itself.

The AI understands the request; andteam counts the working days, the public holiday and her balance from its own rules. Only Confirm on the card books it.

AI (AI helped)
Understood "21 to 25 Dec".
andteam (andteam's rules)
Counted 4 working days and found Christmas Day.
Lindiwe (a person decided)
Checked the card and confirmed.
Thabo (a person decided)
Approved it from his phone.

08 · Review

Tue 16 Feb 2027 · Thabo, her manager

Her manager's review gets more specific, not more automated.

As Thabo writes, Check my review flags only clear problems, such as a vague comment or one that doesn't match the rating, and suggests one rewrite. It never rates and never submits.

AI (AI helped)
Flagged one vague sentence.
Thabo (a person decided)
Rewrote it in his own words and gave the rating.
Lindiwe (a person decided)
Read the review and acknowledged it.

09 · Learning

Mon 22 Feb 2027 · Naledi, HR

A 14-page policy becomes a five-page course. HR checks every page.

Naledi uploads Meridian's road safety policy. andteam drafts the course and its check, with page references. She edits and publishes, Lindiwe completes it on her phone, and it comes round again in 12 months.

AI (AI helped)
Drafted five pages and six questions from the policy.
Naledi (a person decided)
Rewrote page 2 and published it.
Lindiwe (a person decided)
Passed on her first attempt.

10 · Increase

Mon 1 Mar 2027 · release day

Her increase arrives on the day, with the letter already signed.

The salary review calculates every increase from Meridian's rules. Managers change only what they must, with a reason, the approval chain decides, and every letter goes out on release day under one standing authorisation.

andteam (andteam's rules)
Calculated 6.5% from her rating and the guideline.
Thabo (a person decided)
Kept the proposal.
RemCom, CEO (a person decided)
Approved the review.
Lindiwe (a person decided)
Read her letter and acknowledged it.

11 · Internal move

Jun 2028 · year 3

andteam shows her a role before she goes looking.

"A role for you" puts open roles that fit her record and interests on her Home page, with the reasons. She applies in one tap, already filled in, and her manager is told only if she reaches interview.

AI (AI helped)
Matched her record to the role and said why.
Lindiwe (a person decided)
Applied, and was promoted from 1 August.

12 · Referral

Mar 2031 · year 5

She brings in someone she trusts.

Employees refer people from the portal. Lindiwe sees only that Kagiso applied and was hired. The interview notes stay with the hiring team.

Lindiwe (a person decided)
Referred Kagiso for a junior planning role.
Hiring team (a person decided)
Interviewed him and made the offer.
andteam (andteam's rules)
Kept the notes private and told Lindiwe the outcome.

13 · Retirement

30 Jun 2057 · year 31

Thirty-one years later, she leaves well.

Retirement starts the leaver journey: a prefilled UI-19, a certificate of service, and her leave balance for final pay. Access ends on her last day, and she keeps her payslips and tax certificates for 18 months.

andteam (andteam's rules)
Prepared her UI-19 and certificate of service from the record.
Zanele, HR (a person decided)
Checked and signed them.
Lindiwe (a person decided)
Chose to keep in touch with Meridian.

One record, 31 years

Every step happened in one place. Nobody typed anything twice.

What changes, and for whom

Less admin for HR. Fewer steps for everyone.

For the CEO

The whole workforce in one place, and decisions made on live data.

  • One record for every company in the group. Headcount, vacancies and pay come from the same data HR works in every day, not a month-end export.
  • Pay reviews you can steer while they run. Budget against spend by company and department, while managers are still proposing.
  • Less admin cost. Leave, letters, onboarding and approvals run without anyone retyping them into another system.
  • Risk handled in the product. POPIA retention and requests, BCEA leave rules, and EE reports per company.

For HR

Hours back every week. The AI drafts, and you decide.

  • People serve themselves. Balances, payslips, letters and policy questions are answered in the portal or on WhatsApp, with the page cited.
  • Onboarding, offers and reviews keep moving. Reminders slow down over time, then escalate to the right person instead of repeating.
  • Drafts, never decisions. Policy summaries, courses, help-desk replies and review checks are drafted by AI and approved by you.
  • Leave approves in one tap, from WhatsApp or the portal.

For IT

Single sign-on, accounts that open and close themselves, and nothing to host.

  • Microsoft Entra ID or Google Workspace. Accounts are created before the start date and closed at 23:59 on the last day, from andteam's own dates.
  • An API with granular access. Company-scoped keys or OAuth, read and write switches per group of fields, and every call logged.
  • Hosted in South Africa, with tenant isolation and an audit trail on every change, approval and signature.
  • Cloud only. No servers to run and nothing to install on-premises.

Why andteam

Modern, and made for South Africa.

Local HR systems were built for desktops and payroll clerks. Modern ones were built for another country. andteam is both modern and South African.

Modern

  • Built for phones first. Employees and managers do everything from the portal on their phone, or from WhatsApp.
  • One record, not modules bolted together. Every fact has one owner, so nothing is kept twice.
  • AI that drafts and explains. andteam's rules calculate, and a person confirms every action. Pay, ID, bank and health details never go to the AI.
  • Signed where people work. Offers, forms, policies and letters are signed without leaving andteam.

Made for South Africa

  • Data hosted in Johannesburg. The AI is named and disclosed under POPIA section 72, and stays off until you accept it.
  • Payroll connected to Deel Local Payroll, powered by PaySpace.
  • EE reports and WSP/ATR prepared from live data, per company, ready for your SDF.
  • POPIA workflows for your Information Officer, from retention approvals to access and correction requests.
  • Priced in rand, with implementation and support in South African hours.

The modules

Everything Lindiwe touched is one record.

People is always included. Add the other modules when you need them; each brings its own screens, concierge skills and setup steps.

Concierge

Answers the questions people used to email HR, and does what they could do themselves, once they confirm.

People

One record and one org chart across every company in the group.

Payroll

Changes signed off once per period and sent to PaySpace. Payslips come back.

Recruitment

Matches that give their reasons.

Performance

Every goal traces to the top.

Journeys

Paperwork done before day one.

Time off

Public holidays counted for you.

Learning

Courses drafted from your policies.

Engagement

Anonymous by default.

Signing

Built in, through Vumasign.

Switching from your current HR system

Switching is a plan, not a leap.

  1. Step 1

    We bring your people across.

    Import people, positions, pay history and leave balances from your current system's files, with a row-by-row preview and 30 days to undo. Where your current HR system stays in place for part of the group, andteam syncs from it, or connects through the API.

  2. Step 2

    Keep running your current payroll while you switch.

    Your payroll keeps running where it runs today, untouched. When you are ready, move to Deel Local Payroll, powered by PaySpace, after parallel runs that your payroll team signs off.

  3. Step 3

    Live in about 12 weeks, run with you.

    Kick-off, people data, setup, documents and signing, testing and training, then go-live and hypercare. Real dates are set from your go-live date.

  4. Step 4

    Everyone is on their phone from day one.

    At go-live every employee signs in to the portal at your own andteam address. No app to install.

See your switch plan

Security and POPIA

POPIA is the law here. It's built into the product.

Your data stays in South Africa

Stored and processed in Google Cloud's Johannesburg region. Each organisation is its own tenant on its own address, and every request is checked against it.

People see only what their role allows

One role per administrator, scoped by company. Pay, bank, ID, employment equity and medical documents are granted separately, and every view of a medical certificate is logged.

Your Information Officer has the tools

Retention set per category, with nothing deleted until the Information Officer approves the batch. Access and correction requests run on a 30-day clock.

AI is disclosed, and off until you accept

The concierge, policy summaries, course drafting, matching and the review coach use Claude through Google Vertex AI, which processes outside South Africa. Each stays off until you accept the POPIA section 72 position. Nothing is used for training.

Information security aligned to ISO/IEC 27001:2022, on Google Cloud's certified infrastructure. Certification is in progress.

Read Security and POPIA

Integrations

Connects to what you already run.

People are captured once in andteam, and their details reach every system around it. andteam connects to your current HR and payroll systems through import, scheduled sync and the API.

Third-party names belong to their owners.

API and developers

Build on the same record.

A REST API documented in OpenAPI, with reads and writes, company-scoped keys or OAuth client credentials, and signed webhooks for joiners, movers and leavers. Every write goes through the same approvals and audit trail as the console.

Read the docs at docs.andteam.com
Create a hirePOST /v1/hires
# A hire arrives as a prefilled draft offer.
# HR still approves it and sends it.
POST /v1/hires
Authorization: Bearer atk_live_••••
Content-Type: application/json

{
  "candidate": {
    "firstName": "Kagiso",
    "lastName": "Mahlangu",
    "email": "kagiso@example.com"
  },
  "position": "pos_junior_fleet_planner",
  "startDate": "2031-05-01"
}

201 Created
{ "offer": { "id": "ofr_8f2k…", "status": "draft" } }

Bring your hardest month. We'll show it running in andteam.

Book a demo See your switch plan