One employee record, and why it beats any single module

Companies rarely buy HR software because they lack features. They buy it because a number does not match. Headcount in the board deck disagrees with headcount in payroll, and both disagree with the number of people who badged in this morning.

That disagreement is almost always the same underlying fact: the same human being exists as several records, created by several tools, at several times, and no one of them is authoritative.

Integration is not the same as agreement

A stack of best-of-breed tools wired together with connectors can move data between systems without ever agreeing on it. Each system keeps its own identity, its own joining date and its own idea of a department. Synchronisation makes the copies converge most of the time, which is precisely the problem: most of the time is indistinguishable from always right up until an audit.

What one record buys you

• An offer that is accepted becomes an employee without re-entry, so payroll and recruitment cannot disagree about a salary.
• A department change is made once and is immediately true for approvals, reporting and the org chart.
• An exit closes access, final settlement and reporting lines from the same action, rather than three that can be done partially.

None of these are features anyone shortlists on. They are the reason the features you did shortlist on stay correct in the second year.

The unglamorous test

When you evaluate a platform, do not start with the module you care most about. Start by correcting something mundane, a surname or a reporting manager, and then go and look at every other screen that mentions it. Whatever you find is what you are actually buying.