P.A.Y.
Skip to content
P.A.Y.Payroll All Year

HR systems terms, explained plainly

HRIS glossary: HR systems terms A to Z

Short definitions of the words HRIS, HR, payroll and IT teams use every day, from effective date to worker type. Legal and regulatory terms link to their official source.

Written by Robert Hartigos, 20+ years in payroll, HRIS and benefits · Last reviewed November 9, 2026

Browse the termsVisit the HRIS Desk

100 HRIS terms, A to Z

A

ACA measurement period
Under the Affordable Care Act look-back measurement method, the months an employer uses to count an employee's hours of service. The result sets full-time status for a later stability period. IRS: identifying full-time employees.
Access review
A scheduled check that each person's system access still fits their job. Managers or data owners confirm or remove each role, and the HRIS team keeps the evidence. Also called access recertification.
API
Application programming interface: a defined way for one system to request data from another or send data to it. HR and payroll systems use APIs for faster integrations. Integration methods.
Applicable large employer (ALE)
Under the Affordable Care Act, an employer with at least 50 full-time employees, including full-time equivalent employees, on average during the prior year. Related employers are generally combined. IRS: ALE status.
Audit trail
The system's record of who changed what and when, from which value to which value, with the effective date. Review it for pay, tax and bank changes every payroll. What it should show.
Authentication
Proving who a user is, usually with a password plus a second factor. Single sign-on and multi-factor authentication strengthen it.
Authorization
Deciding what a signed-in user may see and do. In an HRIS, security roles and groups control authorization.

B

Back-dated change
A change entered with an effective date in the past. If payroll already paid those periods, it usually creates a retro adjustment. Retro pay calculator.
Batch integration
An integration that moves data on a schedule, such as nightly or before each payroll, instead of as each change happens. Most file-based integrations work this way.
Benefit plan year
The 12-month period that a benefit plan's elections, rates and limits apply to. It may not match the calendar year, so check it before you load deductions.

C

Change control
The process for requesting, reviewing, testing, approving and releasing system changes. It keeps untested changes away from payroll. How it works.
COBRA
A federal law that lets employees and families keep group health coverage for a limited time after qualifying events, such as job loss. It generally applies to employers with 20 or more employees, and coverage generally lasts up to 18 or 36 months. DOL employer guide.
Compensation grade
A pay range with a minimum, midpoint and maximum that jobs are assigned to. The HRIS can flag pay rates outside the range.
Configuration
Settings an administrator changes without writing code, such as fields, rules and workflows. Configuration changes still need testing and approval.
Connector
A prebuilt integration between two systems, often from a vendor or partner. It still needs field mapping, testing and monitoring.
Core HR
The central employee record and the basic transactions on it: hires, job and pay changes, leaves and terminations. Payroll, benefits and time systems depend on it.
Correction
Fixing an entry that was wrong when it was made, instead of entering a new change. Corrections rewrite history, so limit who can make them. Correct or change?
Cost center
A code that tells Finance where to charge a worker's pay and benefits. The cost center on the HRIS record drives payroll's general ledger entries.
Cutover
The planned switch from an old system or process to a new one. A cutover plan lists each step, owner and time, and how to roll back.

D

Data dictionary
A list of every field with its meaning, format, allowed values, owner and the systems that use it. It settles arguments about what a field means.
Data governance
The rules and roles for how an organization defines, owns, protects and fixes its data. Good governance names an owner for every field.
Data mapping
Matching each field and code in one system to its partner in another, such as an HR job code to a payroll rule. Many integration errors start with a missing or outdated mapping.
Data migration
Moving data from an old system into a new one. Plan the extract, cleanup, load and validation, and reconcile counts and totals after each load.
Data owner
The person or team accountable for a field's accuracy and for deciding who may change it. For example, HR may own job data and benefits may own elections.
Data steward
The person who looks after day-to-day data quality for the owner. Stewards run audits, fix errors and update the data dictionary.
Delta file
A file that sends only the records that changed since the last run. It is smaller than a full file, but a failed run can drop changes. Also called a changes-only file.
Dependent
A family member, such as a spouse or child, recorded for benefits coverage or tax purposes. Dependent data feeds benefits carriers and some tax forms.

E

E-Verify
A federal online system that compares information from an employee's Form I-9 with government records. Employers that use it create a case no later than the third business day after the employee starts work for pay. E-Verify.
EEO-1 report
An annual workforce demographic report filed with the EEOC. Private employers with 100 or more employees file it, as do federal contractors with 50 or more that meet certain criteria. In July 2026 the EEOC proposed removing it, and that is not final. EEOC.
Effective date
The date a change takes effect, which can differ from the date someone entered it. Payroll uses it to decide which pay periods a change touches. Effective dating, explained.
Employee ID
A unique number the HRIS gives each person. Use it, not the Social Security number, to identify people in tickets, files and reports.
Employee self-service (ESS)
Screens where employees update their own data, such as address, tax forms, bank details and benefit elections. Self-service changes need the same controls as HR entries.
Employment status
Whether a worker is active, on leave, terminated or retired, and since when. Payroll pays based on status, so a late status change can cause an overpayment.
EOI (evidence of insurability)
Health information an insurance carrier may require before approving some coverage, often life or disability amounts above a set level. Hold the extra deduction until the carrier approves.
External ID
The identifier another system uses for the same person or record. Integrations store both IDs so records match across systems.

F

Field-level security
Security that controls who can see or change a single field, such as a Social Security number, bank account or pay rate.
Forms 1094-C and 1095-C
Affordable Care Act forms for applicable large employers. Form 1095-C reports offers of health coverage for full-time employees, and Form 1094-C transmits them to the IRS. IRS instructions.
FTE (full-time equivalent)
A worker's scheduled hours as a share of a full-time schedule, such as 0.5 for half time. HR, Finance and benefits rules may each count it differently.
Full file
A file that sends every in-scope record each time, changed or not. It catches missed changes but is larger and slower to process.

G

Go-live
The moment a new system, integration or change starts running in production. Go-live checklist.

H

HCM (human capital management)
A suite that covers the core employee record plus talent areas such as recruiting, performance, learning and compensation. Many people use HCM and HRIS to mean the same thing.
Headcount
The number of workers in a group at a point in time. Agree on who counts, such as people on leave, before you compare HR and payroll numbers.
Hire date
The date employment starts. Many systems also store an original hire date and a seniority date, which can differ after a rehire.
HRIS (human resources information system)
The system of record for employee data and HR transactions. HRIS Desk.
HRMS (human resources management system)
A term often used for a suite that includes both HR and payroll. Vendors use it loosely.
Hypercare
A period of extra support right after go-live, with faster response and daily checks, until the new setup runs smoothly.

I

I-9 (Form I-9)
The federal form employers complete for each new hire to verify identity and authorization to work in the US. Keep each form 3 years after the date of hire or 1 year after employment ends, whichever is later. USCIS.
Inbound file
A file loaded into a system from outside, such as a spreadsheet of mass changes or a feed from another vendor. Test it in a sandbox first, because a bad load can change many records at once.
Integration
A connection that moves data between systems, such as HRIS to payroll or payroll to a benefits carrier. Integration guide.
iPaaS (integration platform as a service)
Cloud middleware that connects systems, maps fields, schedules jobs and logs errors.

J

Job code
A code for one job in the job catalog. It often sets defaults such as FLSA status, grade and EEO category.
Job family
A group of related jobs, such as payroll or recruiting jobs, used for career paths, pay ranges and reporting.
Job profile
The template for a job: title, duties, grade, FLSA status and other defaults that fill in when someone is hired into it.

L

Least privilege
A security rule: give each person only the access their job needs, and remove it when the job changes. Least privilege, explained.
Leave of absence
An approved time away from work, paid or unpaid, recorded with a type, a start date and a return date. Leave status changes pay and benefit deductions.
Life event
A change such as marriage, birth, adoption or loss of other coverage that can allow benefit changes outside open enrollment. DOL guidance says to request employer health plan enrollment within 30 days of a marriage, birth or adoption. DOL.
Look-back measurement method
An Affordable Care Act method that sets full-time status for a future stability period from hours counted in a past measurement period. The other method is monthly measurement. IRS.

M

Manager self-service (MSS)
Screens where managers start or approve changes for their teams, such as pay changes, transfers and terminations.
Mass change
One transaction that updates many records at once, such as an annual merit increase. Test it in a sandbox, check the effective date and reconcile totals after the load.
Master data
The core shared records other data depends on, such as workers, jobs, locations, cost centers and legal entities. Errors in master data spread to every system that uses it.
Middleware
Software that sits between systems to move, transform and log data. An iPaaS is a cloud form of middleware.
Multi-factor authentication (MFA)
Signing in with two or more proofs of identity, such as a password and a code on a phone. Require it for administrators and for bank and tax changes.

N

New-hire reporting
Reporting new and rehired employees to a state directory of new hires within 20 days of hire, or sooner where the state requires. Multistate employers that report electronically may choose one state. 42 U.S.C. 653a.

O

Offboarding
The steps when someone leaves: final pay, benefit end dates and COBRA notices, access removal, equipment return and records. Start as soon as the last day is known.
Onboarding
The steps from offer to the first productive weeks: hire record, Form I-9, tax forms, direct deposit, benefits enrollment, system access and training.
Open enrollment
The yearly window when employees choose or change benefits for the next plan year. Test elections to deductions before the new deductions start.
Outbound file
A file a system sends out, such as a payroll feed or a benefits carrier file. Check that each one ran, was complete and was accepted.

P

Parallel testing
Running the old and new setups side by side on the same data and comparing results employee by employee. It shows whether pay would change before employees see it.
Pay group
The employees paid on the same schedule, by the same company, on the same calendar. Someone with no pay group may not be paid at all.
PII (personally identifiable information)
Data that can identify a person, such as a name with a Social Security number, bank details or date of birth. Limit who sees it, mask it in tickets and test data, and encrypt it in transit.
Position
One budgeted seat in the organization, with its own job, cost center and manager. In position management, people fill positions instead of being hired straight into jobs.
Position management
Managing headcount by creating and approving positions before anyone is hired into them. It gives tighter budget control but needs more upkeep than job management. Compared with job management.
Production
The live system that real pay, benefits and filings run on. Build and test in a sandbox, then move approved changes into production.
Provisioning
Creating, changing and removing user accounts and access in connected systems, often triggered by hires, transfers and terminations. Removing access is deprovisioning.

R

RACI
A chart showing who is Responsible, Accountable, Consulted and Informed for each task. Each task should have one Accountable owner. HRIS and payroll RACI.
Regression testing
Retesting things that already worked, to make sure a change or vendor release did not break them. Keep a standard regression script for pay, tax, deductions and integrations.
Rehire
Hiring someone who worked for the employer before. For new-hire reporting, a person rehired after at least 60 consecutive days apart counts as a new hire. 42 U.S.C. 653a.
Release
A vendor update to a cloud system, with new features and fixes. Read the release notes, test in a preview or sandbox tenant and plan for changes to pay, security and integrations.
Reporting line
The manager a worker reports to. It routes approvals and often scopes security, so a missing or wrong manager can stall workflows.
Retention schedule
A list of each record type, how long to keep it, where and how to dispose of it. For example, FLSA payroll records are kept at least 3 years and IRS employment tax records at least 4. Retention answer.
Role-based access control (RBAC)
Granting access through roles tied to job duties, instead of person by person. It makes access easier to review and remove.

S

Sandbox
A non-production copy of a system for building, testing and training. Mask or limit personal data in it, and never send its files to real banks or vendors.
SCIM
System for Cross-domain Identity Management: an open standard that automates user account setup and removal across systems.
Security group
A named set of permissions assigned to users, often limited to certain organizations, locations or populations. Review membership on a schedule.
Segregation of duties (SoD)
Splitting sensitive tasks so no one person can both make and approve a change, such as entering and approving a pay rate. Where a team is too small, add a documented independent review.
SFTP
Secure File Transfer Protocol: an encrypted way to move files between systems, common for payroll and benefits files. Protect the keys and limit who can reach the folders.
Single sign-on (SSO)
Signing in once through an identity provider to reach many applications. It also makes it easier to turn off access everywhere when someone leaves.
SSNVS
The Social Security Number Verification Service from SSA, which checks whether employee names and Social Security numbers match SSA records. Use it only for current or former employees and wage reporting, never before hiring. SSA.
Supervisory organization
A group of workers who report to the same manager, used to route approvals and limit security. Other systems call it a department or team.
System of record
The system whose data wins when two systems disagree. For employee data, it is usually the HRIS.

T

Tenant
Your organization's own instance of a cloud system. Many organizations have a production tenant and one or more test or preview tenants.
Termination reason
The coded reason someone left, such as resignation or layoff. It feeds reporting and rehire eligibility, so use a controlled list.
Test script
Step-by-step test instructions with the data to use and the expected result. Reusable scripts make every release test faster.
Transaction
Any recorded change to employee data, such as a hire, transfer or pay change, with its effective date and approvals.

U

Unit testing
Testing one piece of a change by itself, such as a single field mapping or calculation, before testing the whole flow.
User acceptance testing (UAT)
Testing by the people who will use a change, to confirm it meets the business need before go-live. It comes after the technical team's own testing.

W

Work location
Where the worker actually works, recorded on the HRIS record. It drives state and local taxes, unemployment and the new-hire reporting state, so it must match reality.
Worker type
Whether someone is an employee or a contingent worker, such as a contractor. It decides whether the person goes to payroll at all.
Workflow
The configured route a transaction follows: who starts it, who approves it and what happens next. Also called a business process.

Keep learning

Official sources

Each legal or regulatory fact on this page was checked on these official pages on November 9, 2026.

General information, not tax or legal advice. Definitions are simplified. Check the official source for the full rule.