Typing Employee Details Into Four Systems: The Duplicate Admin Cost in HR

One new starter, four keyboards

A new hire accepts an offer on Monday. By Friday, her name, ID number, bank details, address and emergency contact have been typed into the HR spreadsheet, the payroll package, the access request form for IT and the benefits administrator's portal. Each entry was done carefully by a capable person. Each was also a chance for a digit to slip, and each took a few minutes that nobody has ever measured. When she changes her bank account six months later, the same cycle begins again.

This is duplicate administration inside HR. The data itself is not complicated. The cost comes from the fact that every system holding it is updated by hand, one at a time, by whoever remembers.

How the duplication builds up

Systems are added for separate purposes. Payroll, leave, attendance, benefits, training records and IT access each arrived with their own employee list.
No one system is the official record. The HR file, the payroll master and the staff list all claim to be correct, so none is trusted enough to feed the others.
Integration was never funded. It is easier to ask an administrator to type than to scope an integration project.
Change events are scattered. A resignation, promotion or address change touches several systems, but the checklist for updating them lives in someone's memory.
Third parties have their own forms. Medical aid, provident fund and training providers each request the same details in their own format.

The general mechanics of how duplicate records slip into business systems are described in how duplicate data gets into business systems, and the broader employee-side picture appears in employees duplicating data entry.

Symptoms

an HR administrator who spends the first week of every month reconciling the staff list with payroll;
employees receiving payslips with an old surname, address or job title;
leavers who remain on the payroll or in one system for an extra cycle;
different headcount numbers in the HR report and the finance report;
new starters waiting for access because the request form was typed from an incomplete record;
a long list of "change of details" emails sitting in a shared inbox;
tax certificate corrections at year-end because an ID number or reference number was captured wrongly.

The yearly collection of the same information from everyone is a related burden covered in collecting employee information every pay period.

How the pain turns into money

Administrator payroll. The most direct cost is the HR and payroll hours spent entering and re-entering the same facts.
Error correction. A wrong bank account or tax number means an investigation, a re-run or a manual payment, and an unhappy employee. Corrections often take far longer than the original entry.
Statutory exposure. Employer tax reconciliations rely on accurate employee data. In its September 2026 notice for the employer interim reconciliation, SARS urged employers to ensure payroll and employee information is accurate and up to date, and to confirm all employees have valid income tax reference numbers, adding that accurate declarations help avoid penalties, interest and unnecessary administrative work. The detail is on the Pay As You Earn page.
Delayed access and onboarding. If the access request depends on a manually typed record, the new starter waits. See why new employees wait for system access and new employees without equipment.
Leaver risk. A termination typed into HR but not into every connected system leaves live accounts behind. The result is covered in former employees still active in systems.
Personal data spread. Every copy of an employee's identity and bank information is another place to protect under POPIA.

An illustrative cost model

The figures below are illustrative assumptions for a hypothetical business of 150 employees in Pretoria with a two-person HR and payroll function.

Assumption	Value
New starters a year	60
Systems each starter is typed into	4, at 25 minutes each
Changes of details a year (bank, address, status)	300
Systems each change is typed into	3, at 10 minutes each
Loaded HR administrator cost	R300 an hour
Data errors a month needing correction	10, at 1.5 hours each, at R350 an hour
IT time rekeying access requests from HR data	60 starters × 45 minutes at R350

Starter entry: 60 × 4 × 25 minutes = 100 hours
Change entry: 300 × 3 × 10 minutes = 150 hours
Entry cost: 250 hours × R300 = R75,000
Error correction: 10 × 1.5 × R350 × 12 = R63,000
IT rekeying: 60 × 0.75 × R350 = R15,750
Illustrative total: about R154,000 a year

The figure is modest for a business this size, and that is part of why it persists. It also leaves out the effect of a missed deadline or a payroll error that reaches an employee's bank account, which is harder to put a number on but far more disruptive.

Why it is tolerated

HR administrators are conscientious, so the work gets done, and the errors are usually caught eventually. The hours are spread across the month in small bursts. Each system owner assumes that integration is someone else's budget. Employee data feels sensitive, so there is a reluctance to connect systems. And when the team is small, the person doing the typing is also the person who would have to lead any change.

When it becomes urgent

headcount is about to grow quickly through a new contract or acquisition;
a payroll error reaches an employee, or a tax certificate must be reissued;
an audit finds mismatches between HR and payroll records;
a leaver keeps access to a system for weeks;
a key HR administrator resigns and the routine goes with them.

What better looks like

The principle is that each employee fact is entered once, in one system, and flows to the others.

Name the system of record. For most small businesses, either the HR system or the payroll system should be the source for core personal and employment details. Everything else reads from it.
List every place employee data is typed. Include spreadsheets, forms, benefit portals and IT request forms.
Connect the highest-volume path first. For many businesses it is HR to payroll, or HR to IT access. Microsoft's guidance on HR-driven provisioning describes the HR system as the source of authority for new digital identities, so that creating an employee triggers the creation of accounts without a second round of typing. The documentation on how application provisioning works adds that automatic provisioning covers maintaining and removing identities as status or roles change, which addresses leavers as well as starters.
Let employees update their own details. Self-service for address and bank changes, with HR approval, removes a large share of the inbox.
Build a change checklist. For events that cannot be automated, one checklist per event, with an owner, is far better than memory.
Validate on entry. ID number, bank account and tax number checks catch errors before they reach payroll.

Practical next actions

Pick the last three new starters and trace where each one's details were typed.
Count the number of times each fact (bank, address, ID) is entered.
Agree which system is the source of truth for each fact.
Connect one path, such as HR to payroll or HR to IT access, before anything more ambitious.
Introduce a self-service change-of-details form with approval.
Reconcile HR and payroll lists monthly until the duplication is gone.

Bottom line

Duplicate employee data entry is a quiet cost in hours, errors and exposure. It is not caused by careless people, but by systems that cannot talk to each other. A single source of truth, one connected path at a time, removes most of the retyping and makes payroll, tax submissions and onboarding more reliable.

Sources and further reading

Pay As You Earn - South African Revenue Service (last verified 10 October 2026)
What is HR-driven provisioning with Microsoft Entra ID? - Microsoft Entra ID (last verified 10 October 2026)
Understand how Application Provisioning in Microsoft Entra ID - Microsoft Entra ID (last verified 10 October 2026)