One employee, three versions of the record: fixing employee information management

An HR executive was asked how many people the company employed. She gave a number. Payroll gave a different number. The finance head, working from the cost centre report, gave a third. All three were defensible and all three were produced in good faith from a different copy of the same information. It took two days to reconcile, and the answer was that two people had left without payroll being told and one contractor had been entered as staff.

Nothing dramatic had gone wrong. The business simply had no single place where the employee record lived, so every function kept its own, and every copy drifted at its own pace.

The employee record is rarely wrong at joining. It goes wrong afterwards, in the gap between an event and the copies that never hear about it. A promotion updated in payroll but not in the org chart. A change of address told to the manager. A transfer the site knows about and head office does not. Each is small, and together they mean that no report from any single source can be trusted without checking another.

• No system of record. Three systems each hold the field, and nobody has said which one wins when they disagree.
• Events without a route. A change happens and there is no defined path by which every copy learns of it.
• Access to edit without a trail. Anyone who can see a record can change it, and nobody can see who changed what.
• Reconciliation only at crisis. The copies are compared when an audit or a dispute forces it, by which time the drift is months deep.

The instinct is to pick one system and declare it the master. It rarely works, because payroll genuinely is the best source for pay and bank details, the HR system for reporting lines, and the site for attendance. The workable version is to decide the system of record per field, write it down, and route every change to that system first.

FIELD                   SYSTEM OF RECORD   COPIES
Name, ID, DOB           HRMS               payroll
Joining date            HRMS               payroll, finance
Reporting line          HRMS               org chart
Designation, grade      HRMS               payroll
Salary and bank         payroll            HRMS (view only)
Location, cost centre   HRMS               payroll, finance
Attendance              attendance system  payroll (monthly)

A change is made in the system of record and
flows outward. Never the other way.

Once the map exists, most of the drift stops on its own, because the argument about which copy is right has an answer. The rest stops with change control.

A clean record stays clean only if changes go through a route that updates every copy. That does not require software; it requires that a change of any mapped field is made once, in its system of record, by someone with the right to make it, with a record of who and when.

1. 1

   One change form, or one screen

   Whatever the route, there is one of it. A change told to a manager verbally is not a change until it reaches the system of record.

2. 2

   Named editors

   Who may change each category of field. Personal details, reporting lines and pay are three different permissions, and the last is the narrowest.

3. 3

   A trail

   Who changed what, from what, to what, when. Without this the record cannot be defended, and a dispute about a date becomes an argument about memory.

4. 4

   Downstream notification

   The systems that hold copies are told. Where that is manual, a weekly list of changes does it; where it is integrated, it should still be checked.

The narrowest permission — who may see and change salary — is the one most businesses get wrong first, and it is worth settling deliberately. That question is covered in who should see salary data in more depth than belongs here.

Payroll is the copy that has to be right every month, because money moves on it. That makes it the ideal reconciliation partner: once a month, compare the HR record's headcount, joiners, leavers and reporting lines against what payroll paid, and resolve every difference before the next run. The first reconciliation is slow and unpleasant. By the third it is an hour, because the change-control route has stopped the drift at source.

One habit makes the monthly reconciliation almost free: run it from a list of changes rather than from the whole record. If the change-control route produces a log of what moved this month — joiners, leavers, transfers, pay revisions — then reconciliation is a check that each of those reached payroll and nothing reached payroll that is not on the list. Two lists of a dozen lines, compared in ten minutes. Businesses that reconcile the whole record every month are doing so because they have no change log, and the effort is what makes them stop after two attempts. The log is the shortcut, and it only exists where the change-control route does.

This is the same discipline that closes a payroll month cleanly, and it is why payroll process management work almost always starts by asking where the employee record lives.

Every record map has orphan fields — the emergency contact that was collected at joining and never updated, the qualification nobody verified, the shift pattern that changed twice since it was entered. They cause no monthly pain because nothing reconciles against them, so they drift for years and are discovered at the worst moment: an accident, an audit, a dispute about eligibility.

The map should name an owner and a review trigger for these too. Emergency contacts are re-confirmed annually and at any change of address. Qualifications are verified once at joining and re-checked when the role changes. Shift patterns are owned by whoever runs the roster and updated when the roster does. None of this is onerous; it is a line in the map and a date on a calendar, and it is what separates a record that is merely tidy from one that can be relied on when it matters.

Getting those ownership lines written is most of what an employee information management engagement produces. The software, if there is any, comes after the map — and works only as well as the map allows.

Where the record has already drifted, the order matters. Reconcile headcount first — who is actually employed — because every other field hangs off the answer. Then reporting lines, confirmed by each manager for their own team, which is faster than any central exercise. Then dates, designations and locations. Salary and bank details last, and only through payroll, because those are the fields where a well-meant correction can cause real harm.

Expect the reconciliation to surface people nobody can account for, contractors entered as staff and leavers still on a list. That is normal, and it is the reason the exercise is worth doing before an HRMS migration rather than after — loading a drifted record into a new system produces a confidently wrong system. The record map, the change-control route and the monthly reconciliation are what employee information management work establishes, and they are the foundation everything in HR reporting and analytics depends on. A report is only as good as the record it counts.