Skip to main content

HRIS

HRIS: human resource information management in one record

An HRIS is where an organisation’s employee data lives and is governed. HR & OMS keeps one record per person — identity, employment, documents, schedule, credentials — and every other module reads from it rather than keeping a copy.

What an HRIS is

A human resource information system is the authoritative store for employee data: who works here, under what terms, in which unit, reporting to whom, with which documents on file and which credentials issued. Everything else an HR department does — a leave balance, a payslip, a performance review, a door that opens — is downstream of that record being right.

Human resource information management is the practice around it: keeping the record current, controlling who may read or change each part of it, retaining what has to be retained, and being able to show afterwards who changed what. An HRIS that only stores data, without governing it, moves the filing cabinet online and leaves every other problem where it was.

What the record holds

Identity and contact

Legal name, photo, contact details, emergency contacts, and the issued work email the person signs in with.

Employment

Position, employment type, org unit, reporting line, hire date, regularisation, and movement history kept as history rather than overwritten.

Compensation

Pay rate and pay basis, allowances, statutory numbers, and the bank details a payroll export needs.

Work schedule

The shift pattern, rest days and holiday calendar the timesheet computes against.

Documents

Contracts, IDs and clearances in a document library with per-tenant retention rules.

Credentials and devices

RFID cards, biometric enrolments, digital ID cards and issued equipment, each tied back to the person.

HRIS, HRMS and HCM

The three terms overlap and are used loosely, but the usual distinction is scope. An HRIS is the data layer. An HRMS is an HRIS plus the operational processes that run on it — time and attendance, leave, payroll, performance. HCM usually means an HRMS plus talent strategy: recruiting, succession, workforce planning.

HR & OMS is an HRIS and an HRMS in one system. What it deliberately adds beyond either is the operational side of the building — doors, readers, assets and devices — because the same tap that opens a door is the cleanest attendance record you can get. See the HRMS page for the process half, and HR and operations management system for why the two sit together.

Governing the data, not just storing it

Role-based access decides who may read or change each part of a record, and scope narrows it further so a supervisor sees their own unit rather than the organisation. Every tenant-scoped table carries row-level security in PostgreSQL, so one customer’s records are unreachable from another’s session even if application code forgets to filter.

Fields that should not sit in the clear — government identifiers, bank details — can be tokenized: the row holds a token, the readable value lives in a vault, and reading it is a permissioned action that is logged. Changes are recorded in an audit trail. More detail on platform security.

Common questions

Human Resource Information System — the system of record for employee data. It is also written HRIS software, and the discipline it supports is called human resource information management.

An HRIS holds and governs the data. An HRMS adds the processes that run on it — time and attendance, leave, payroll, performance. HR & OMS is both, so the distinction matters when comparing vendors rather than when using it.

Yes. Employee records import from a spreadsheet, and the import is checked against the same validation the on-screen form uses, so a duplicate employee number or a malformed date is reported rather than silently stored.

Whatever your roles say. Access is by role and by scope, so a department head sees their own unit, HR sees the organisation, and sensitive fields can be restricted further or tokenized so that even a database row does not carry the readable value.

Yes. Employment changes are stored as history rather than overwriting the record, and an audit trail records who changed what and when.

See it running on your own data

A live walkthrough of the modules above, using a sample of your own headcount, shifts and pay rules — not a canned deck.