Key Takeaways
- An HRIS is the system of record for people data: contracts, pay history, absence, right-to-work, training, appraisals and documents.
- HCM adds the talent layer — recruitment, onboarding, performance, succession. HRMS usually means HRIS plus payroll. In practice vendors use all three interchangeably.
- For UK employers the non-negotiables are right-to-work evidence, GDPR-compliant retention and access, holiday for irregular-hours workers, and a clean handover to payroll and pensions.
- Under about fifteen people a well-kept spreadsheet plus a document folder is genuinely fine. The trigger is when absence, holiday and starters stop fitting in one person’s head.
An HRIS — human resources information system — is the system of record for people data: who works here, on what contract, at what rate, who has taken what leave, what training and right-to-work evidence you hold, and which documents belong to whom. That is all it is. The related acronyms mark out roughly where the product stops: HCM adds recruitment, onboarding and performance; HRMS usually means the same thing with payroll included. The useful question is not which acronym you are buying, but where the authoritative record of a person lives and what reads from it.
What an HRIS Actually Holds
| Record | Why it has to be in one place |
|---|---|
| Person and contract | Start date, role, hours, contract type, rate, notice. Everything else is calculated from these |
| Right to work | Evidence and expiry dates, with a reminder before they lapse. A compliance duty, not admin |
| Absence and holiday | Entitlement, taken, remaining, carry-over — and sickness, separately |
| Pay history | Changes with effective dates, so you can answer what someone was on in March |
| Training and certification | Tickets, licences, competencies and expiry. In regulated trades this decides who can be sent where |
| Documents | Contracts, variations, opt-outs, disciplinary records, all attached to the person |
| Appraisals and notes | What was agreed and when, in a place that survives a manager leaving |
| Leavers | Final pay, access removal, and retention until the retention period expires |
Notice what is not in that list: payroll filing, and time capture against jobs. Those belong to payroll software and to your operational system. An HRIS should feed both, not replace either.
HRIS, HCM, HRMS — the Honest Version
| Term | What it usually means | Buy it when |
|---|---|---|
| HRIS | The people record: contracts, absence, documents, compliance | Almost always the first thing you need |
| HCM | HRIS plus the talent layer: recruitment, onboarding, performance, succession, learning | You are hiring steadily enough that a pipeline needs managing |
| HRMS | HRIS plus payroll in one product | You want one supplier and are happy for payroll to move |
| Core HR | A vendor’s name for the HRIS part of their suite | Not a distinct category, just a module name |
In real sales conversations the terms are used interchangeably, so ignore the label and ask which of the eight records above it holds, and what it does with the other two systems in your business. That single question sorts the shortlist faster than any comparison grid.
The UK Parts That Are Not Optional
- Right-to-work evidence. Held, dated and monitored for expiry. This is a legal duty with penalties attached, and a folder on a shared drive is a poor way to discharge it.
- UK GDPR. People data is some of the most sensitive you hold. That means a lawful basis, defined retention periods with actual deletion at the end of them, access limited by role, and an audit trail of who looked at what. “Everyone in the office can open the HR folder” is a finding waiting to happen.
- Holiday for irregular-hours and part-year workers. The calculation is not the same as for salaried staff, and the rules have moved in recent years. Get it computed by the system, and confirm the current method with ACAS or your accountant rather than with an article.
- Statutory absence. Sick pay, family leave and the records behind them, kept in a form you can produce.
- A clean handover to payroll and pensions. One starter record should create the payroll entry and trigger the auto-enrolment assessment — see payroll and workplace pensions.
When a Spreadsheet Is Still the Right Answer
Under roughly fifteen people, with salaried staff on regular hours and one person who genuinely knows everybody, a well-kept spreadsheet and an organised document folder work. They are free, everyone can read them, and there is nothing to learn.
They stop working at recognisable moments:
- Somebody’s holiday balance is disputed and you cannot settle it from the record.
- A right-to-work document expired and nobody was warned.
- You cannot say, quickly, who holds a current certificate for a particular job.
- Managers ask HR for figures HR has to assemble by hand.
- The HR folder is open to more people than it should be, and everyone knows it.
Two or more of those and the spreadsheet has become a risk rather than a saving.
Buy, or Build It Into What You Already Have?
Off-the-shelf HR software is a mature market and for most businesses it is the right answer: buy an HRIS, connect it to payroll, and get on with your actual work. It is cheaper and faster than building, and the compliance features are maintained by someone else.
Building the people layer into an existing operational system is worth considering in two cases. First, when certification and competency drive operational decisions — if who can be sent to which job depends on tickets and expiry dates, having that live next to scheduling and job costing is genuinely better than syncing it between two products. Second, when per-seat pricing on a second product is hard to justify for people who need to be in it twice a month.
Either way the boundary should be the same one: the HRIS or HR module owns the person, payroll owns HMRC, and the operational system owns jobs and hours. Our UK ERP page covers how we draw that line in a build, and the call ends with an honest answer — including “buy an HR product, you do not need us for this”.
Frequently Asked Questions
What is an HRIS?
A human resources information system: the system of record for people data. Contracts and rates, absence and holiday, right-to-work evidence and expiry, training and certification, documents, appraisals and leavers. It should feed payroll and your operational system rather than replace either.
What is the difference between HRIS, HCM and HRMS?
HRIS is the people record. HCM adds the talent layer: recruitment, onboarding, performance, succession, learning. HRMS usually means HRIS plus payroll in one product. Vendors use all three loosely, so ask which records it holds and how it talks to your payroll instead of comparing labels.
Is HR software the same as payroll software?
No. HR software holds the person; payroll software calculates pay and files RTI to HMRC under its own recognition. Some products do both, but the filing should always sit in software licensed and updated for it, with a person approving the run.
How many employees before we need an HRIS?
There is no threshold, only symptoms. Under about fifteen salaried people with one person who knows everybody, a good spreadsheet is fine. Move when a holiday balance cannot be settled from the record, a right-to-work document expires unnoticed, or you cannot say who holds a current certificate.
What should a UK HR system definitely handle?
Right-to-work evidence with expiry monitoring, UK GDPR retention and role-based access with an audit trail, holiday for irregular-hours and part-year workers, statutory absence records, and a clean starter handover to payroll and auto-enrolment. Ask to see the expiry report and the deletion settings in the demo.
Want this looked at properly, with your own numbers?
Book a free strategy call. We walk one real process through your business and tell you honestly whether custom, cloud or off-the-shelf fits — including when the answer is to change nothing yet.
Book a Free Strategy Call