Employee
The person doing the work, and the position they occupy — which are separate records that most reporting merges incorrectly.
01 Why it matters
What depends on getting this right
Every per-head metric divides by it, and the contingent workforce that sits outside the HR system is exactly the population that makes cost per output look better than it is.
02 Where it lives
Every system holds a different version
None of these is wrong. Each was built for a purpose and records the part of the entity that purpose needed, which is exactly why resolution is required rather than optional.
| System | What it holds of this entity |
|---|---|
| HRIS | establishment, position, contract and effective-dated history |
| Payroll | what was actually paid, by wage type and period |
| Time and attendance | hours worked, absence occurrences and premium time |
| Rostering or field service | availability, skills and what they were assigned to |
| Access and directory | the identity used by every system they touch |
03 Match keys
What actually matches, and what only looks like it does
| Key | How well it works |
|---|---|
| National insurance or tax identifier | Strong, sensitive, and access-controlled by law in most jurisdictions. |
| Employee number | Reliable within one system and rarely consistent across countries. |
| Corporate identity or email | Good for system access joins, absent for many frontline workers. |
| Name plus date of birth | A weak fallback that must not stand alone. |
04 Survivorship
When two records disagree, which value wins
Survivorship is a business decision, not a technical default. These rules should be agreed with the people who own the data and then applied consistently, because changing them later restates history.
HRIS is authoritative for the contractual record
Role, grade, manager and contract come from HR, not from a local roster.
Payroll is authoritative for what was paid
Retrospective corrections mean payroll history restates and must be versioned.
Rehires keep one person, many assignments
A returning employee is the same person; treating them as new destroys tenure and attrition analysis.
Contingent workers are flagged, not merged
They belong in the workforce view and must remain distinguishable from employees.
05 The cost of not doing it
What stays broken while it is unresolved
Headcount that nobody agrees on
FTE, headcount, positions, paid people and active workers are five numbers, and the dispute is definitional rather than technical.
Contingent labour invisible
Agency and contractor cost sits in procurement, so revenue per employee flatters.
Attrition understated by rehires
Treating a returning employee as a new person breaks both tenure curves and turnover cost.
Skills and certifications stranded
Whether someone may legally perform a task lives in a system the scheduler cannot see.
06 Metrics that divide by it
The numbers this entity carries
07 Questions
Frequently asked
Person or position — which should the golden record be?
Both, related. The person carries identity, tenure and skills; the position carries cost centre, grade and establishment. Metrics must state which one they count.
How do we handle the privacy constraints?
Resolve and govern the entity centrally, but enforce attribute-level access so that compensation, health and performance data are visible only to entitled roles. That is a policy applied at the data layer, not a reason to keep the record fragmented.
See the duplicates in your own data
We will resolve one entity on your systems, live, and show what the duplicates are costing.