For HRIS, HR, payroll and IT
HRIS Desk: HR systems help for every role
Plain answers, a support playbook, a payroll-impacting data audit and a yearly calendar for the people who run HR systems. Pick your path below, or jump to the questions.
Start here: pick your path
Five short paths, one for each role that touches the HRIS. Each one takes you to the answers, tools and checklists you will use first.
Path 1
New to HRIS
You just joined an HR systems team, or HRIS is now part of your job.
- Learn the words in the HRIS glossary. Start with effective date, system of record and security group.
- Read what effective dating is and why back-dated changes reach payroll.
- See what moves between systems in the integration guide.
- Learn payroll basics with the free new to payroll path.
Path 2
HRIS analyst
You support the system, fix data and keep integrations running.
- Adopt the support playbook and its severity levels.
- Run the payroll-impacting data audit every month.
- Keep the common integration errors table nearby.
- Trace system issues with troubleshooting and vendor help.
Path 3
HR generalist
You enter hires, changes, leaves and terminations.
- Check what payroll needs, and by when.
- Preview a change with the employee change impact tool before you enter it.
- Read the answers on state moves, new-hire reporting and Form I-9 retention.
- Look up any unfamiliar word in the HRIS glossary.
Path 4
Payroll partner
You depend on HRIS data every payroll.
- Set up the reconciliation checks for headcount, hires, terminations and deductions.
- Figure back-dated changes with the retro pay calculator.
- Gross up a bonus with the bonus gross-up calculator.
- Agree on roles with the integration RACI and the controls workspace.
Path 5
IT and integration
You build and secure the connections between systems.
- Compare files, APIs, middleware and connectors.
- Read the answers on security roles, least privilege and segregation of duties.
- Find official vendor load instructions in vendor import templates.
- Plan a selection with find my system fit and the RFP guide.
Latest HRIS updates
New HRIS and HR systems updates appear here as they are published. All federal and state changes are on What changed.
A 15-minute weekly HRIS check
- Review integration errors and rejected records.
- Check the audit report for bank, tax and pay rate changes.
- Confirm new hires and terminations reached payroll before the cutoff.
- Scan What changed for tax and reporting updates.
- Work tickets that touch the next payroll first.
HRIS questions answered
Short answers to the questions HRIS, HR and payroll teams ask most. Each one links to a guide, a tool or the official source.
HRIS basics
What is an HRIS?
An HRIS, or human resources information system, is the system of record for employee data. It holds who people are, their jobs, pay, location and status. Payroll, benefits, time and IT systems all read from it. The HRIS glossary explains the words you will hear.
What is the difference between HRIS, HCM and HRMS?
The terms overlap, and vendors use them loosely. HRIS usually means the core employee record and HR transactions. HCM, or human capital management, usually adds talent areas such as recruiting, performance and learning. HRMS often means a suite that also runs payroll. Compare suites with find my system fit.
Who owns which employee data?
HR usually owns personal, job and status data. Payroll owns pay results, tax rules and the deduction codes it runs. Benefits owns plan elections, and IT owns system access. Write each field's owner in a data dictionary so no field is orphaned.
What does "system of record" mean?
It is the one system whose value wins when two systems disagree. For most employee data, that is the HRIS. Fix errors there first, then let the change flow downstream. A fix made only in payroll can be overwritten by the next file. See what flows to payroll.
Effective dates and changes
What is effective dating?
Effective dating stores each change with the date it takes effect, not the date someone typed it. The HRIS keeps the history, so you can see what was true on any date. Payroll uses these dates to decide which pay periods a change touches. Effective dating and retro, explained.
Why does a back-dated change create a payroll adjustment?
Payroll already paid the periods before the change was entered. A back-dated raise means those periods were underpaid, so payroll owes retro pay. A back-dated termination can mean an overpayment to recover. Estimate the amount with the retro pay calculator.
Should I correct a record or enter a new change?
Correct a record when the original entry was wrong, such as a typo in a rate. Enter a new change when something really changed, such as a raise. Corrections rewrite history, so limit who can make them and review them. Track the review in the controls workspace.
What is the difference between position management and job management?
In job management, you hire people into jobs, and one job can hold many people. In position management, each seat exists first, with its own budget, cost center and manager. People fill and leave positions, and the position's data stays. Position management gives tighter headcount control but needs more upkeep. See position management in the glossary.
How does a state move flow to payroll?
HR enters the new work or home location with its effective date. The HRIS sends it to payroll, which updates state tax withholding and unemployment reporting. Payroll may need a new state account before the first paycheck there. Tell payroll early and use the multistate registration guide.
What happens if a change misses the payroll cutoff?
The change waits for the next payroll. If it affects pay, payroll pays the difference later or runs an off-cycle check. A late termination can lead to an overpayment that is hard to recover. Check the impact first with the employee change impact tool.
Security and controls
How do HRIS security roles work?
Most HR systems grant access through roles or security groups, not one person at a time. A role bundles what someone can see and do, often limited to certain organizations or locations. Assign roles by job duty, and review them on a schedule. Payroll controls workspace.
What is least privilege?
Least privilege means each person gets only the access their job needs, and no more. Remove access when people change jobs or leave. Keep broad administrator roles for the few people who need them, and not for daily work. See least privilege in the glossary.
What is segregation of duties in an HRIS?
It means no one person can both make and approve a sensitive change. For example, the person who enters a pay rate should not approve it or pay it. Where a small team cannot split duties, add a documented independent review. Map conflicts in the controls workspace.
What should an HRIS audit trail show?
It should show who changed what and when, the old and new values and the effective date. It should also log approvals and integration loads. Review pay, bank and tax changes every payroll. Start with the HRIS data audit checklist.
Changes, testing and support
How do I request an HRIS system change?
Use your team's change request process, not a side email. Describe the business need, the fields and people affected, the payroll impact and the date you need it. Expect an impact review, testing and approval before it reaches production. How change control works.
How should we test before a vendor release?
Read the release notes and flag anything that touches pay, tax, deductions, security or integrations. Run your regression scripts in a sandbox or preview tenant before the release reaches production. Retest key integrations end to end, and record results and sign-offs. Testing types, explained.
What is the difference between a sandbox and production?
Production is the live system that pays people. A sandbox or test tenant is a copy for building and testing. Never send test files to real banks or vendors. Mask or limit personal data in test copies. See sandbox in the glossary.
How should an HRIS team triage support tickets?
Work payroll-impacting and cutoff-sensitive tickets first. Then sort by how many people are affected and whether a workaround exists. Capture the employee ID, effective date, screenshots and steps to reproduce. Read the support playbook.
Compliance and records
How long should we keep HR and payroll records?
It depends on the record. Under the FLSA, keep payroll records at least 3 years and time cards and wage rate tables at least 2 years (29 CFR 516). Keep IRS employment tax records at least 4 years after the tax is due or paid, whichever is later (IRS). Build a retention schedule with your legal team.
How long must we keep Form I-9?
Keep each Form I-9 for 3 years after the date of hire or 1 year after employment ends, whichever is later. Never discard a current employee's form. You may keep forms on paper or electronically, if you can produce them within 3 business days of an inspection request. See USCIS: retaining Form I-9.
When must new hires be reported?
Report new and rehired employees to the state directory of new hires within 20 days of hire. Some states require it sooner. Under federal law, a rehire counts after a separation of at least 60 consecutive days. See the Office of Child Support and 42 U.S.C. 653a.
How do we validate names and Social Security numbers?
Use the Social Security Number Verification Service (SSNVS) from SSA. It checks whether names and SSNs match SSA records, for wage reporting only. Do not use it before hiring. A mismatch alone is not a reason for adverse action. See SSA's SSNVS rules.
Who files the EEO-1 report, and is it changing?
EEO-1 Component 1 is an annual report from private employers with 100 or more employees. Federal contractors with 50 or more employees file if they meet certain criteria. In July 2026 the EEOC proposed removing the requirement, but the proposal is not final. Watch the EEOC data collections page for 2025 collection dates.
What changed for furnishing Form 1095-C?
Employers no longer have to send Form 1095-C automatically. Instead, they may post a clear, conspicuous and accessible website notice that people can request a copy. A requested copy is due by the later of January 31 or 30 days after the request. Filing with the IRS is still required, and state rules are separate. See IRS Notice 2025-15.
Support playbook
HRIS support playbook
A simple, repeatable way to handle HRIS tickets. The rule of thumb: anything that changes someone's pay before the next cutoff goes first.
Log every request in one queue
Use one ticket queue or form, not side emails and chats. One queue shows patterns and keeps an audit trail.
Triage: payroll impact and cutoff first
Ask five questions. Does it change pay, tax, deductions or bank data? When is the next cutoff? How many people are affected? Is there a workaround? Is personal data exposed? Payroll-impacting, cutoff-sensitive tickets go to the top.
Set the severity
Use the severity table below. Raise the severity as the cutoff gets closer.
Capture the facts
Write down what you need to reproduce it once, so nobody has to ask twice. Use the list below.
Contain, then fix at the source
Stop the damage first, such as holding a file. Then fix the data in the system of record with the right effective date, and let it flow downstream.
Escalate to the vendor when it is the product
Configuration issues are yours to fix. Suspected product defects, outages and data issues inside the vendor's service go to the vendor.
Close the loop
Confirm the fix in production, tell the requester and payroll, and record the root cause. Add a test case so it cannot come back unnoticed.
Severity levels
Use these as a starting point and set your own response times with payroll and your vendors.
| Severity | What it means | Examples | What to do |
|---|---|---|---|
| Severity 1 Critical | Payroll cannot run, or many people will be paid wrong on the next payday. Personal data may be exposed. | An integration failed before the cutoff. A bank file was not created. Tax setup is wrong for a whole state. | Start now and keep going until it is contained. Tell the payroll lead and open a vendor case at once. For possible data exposure, follow your security incident process. |
| Severity 2 High | A few people will be paid wrong this payday, or a filing or notice deadline is at risk. | A new hire is missing before the cutoff. A termination did not reach payroll. A benefit deduction did not start. | Fix before the cutoff. Agree on a workaround with payroll if the fix cannot land in time. |
| Severity 3 Medium | Data is wrong, but there is a workaround or no pay impact before the next cutoff. | A report shows the wrong manager. A cost center maps to the wrong account. | Schedule the fix. Check whether the same cause affects other records. |
| Severity 4 Low | Questions, how-to requests, cosmetic issues and enhancement ideas. | A user asks how to run a report. A team wants a new field. | Answer or add to the change request backlog. |
What to capture on every ticket
- Ticket number, requester and the date and time reported
- Employee ID and name. Never the full Social Security number or bank account number
- The effective date of the change, and the pay date and cutoff at risk
- What was expected and what happened instead
- The screen, report or integration involved, with the run ID and time stamp
- Screenshots with personal data masked
- Steps to reproduce, and whether it happens for others
- What changed recently: a release, configuration change or mass load
- How many people are affected, and who has been told
What to send the vendor
- Your environment or tenant name, and whether it happens in the sandbox too
- Exact steps to reproduce, the expected result and the actual result
- Record IDs, run IDs and time stamps with the time zone
- Logs or error messages, with personal data removed
- The business impact and the deadline, such as the next payroll cutoff
- The vendor case number, recorded in your own ticket
Find official vendor support paths in troubleshooting and vendor help.
Checklist
HRIS data audit checklist: payroll-impacting fields
Run these checks every month, before open enrollment and before year-end. Fix each error in the HRIS, with the right effective date, so the fix flows to payroll.
| Field | What to check | How to check | Why payroll cares |
|---|---|---|---|
| Legal name | Matches the Social Security card. No nicknames or extra spaces in legal name fields. | Review new hires against their documents. Run SSNVS after hire for wage reporting. | FLSA records use the full name as used for Social Security (29 CFR 516.2). Mismatches cause W-2 problems. |
| Social Security number | Present, valid format, no duplicates and no placeholders left after hire. | Run duplicate and pattern reports. IRS Publication 15 says to record the name and SSN from the card if it is available. | Wages post to the wrong record if the SSN is wrong. |
| Date of birth | Present and possible: no future dates and no placeholder defaults. | Run an age range report. | Drives benefits and retirement plan eligibility. FLSA records need it for workers under 19. |
| Home address | Complete, with a valid ZIP code, and current. | Report blanks and returned mail. | Resident state and local taxes, W-2 delivery and ACA forms. |
| Work location | Where the person really works, including remote and hybrid workers. | Compare work locations with home states and manager locations. | State and local withholding, unemployment and new-hire reporting state. |
| FLSA status | Matches the job profile and the duties. | Report employees whose status differs from their job profile. | Overtime. A wrong status means missed or wrong overtime pay. |
| Pay rate and effective date | Rate matches the approval. Effective date matches the decision. Rate is inside the grade range. | Report rates outside the range and changes with no approval. | Back-dated or missing changes become retro pay. |
| Pay group and frequency | Every active employee has one, consistent with company and location. | Report active employees with no pay group. | Someone with no pay group may not be paid at all. |
| Status and key dates | Hire, rehire, leave and termination dates are present and in order. | Report active employees with a termination date, and anyone paid after termination. | Overpayments, benefits and ACA hours. |
| Standard hours and FTE | Matches the schedule and the job. | Report part-time employees with full-time hours. | Salaried pay, benefit eligibility and ACA full-time status. |
| Tax setup | Federal Form W-4 and state forms are on file. Work and resident states are set. | Report new hires with no tax forms after the first payroll. | Withholding. |
| Benefit deductions | Elections in the HRIS match payroll deductions and carrier enrollment. | Tie elections to deductions every month. | Missed, doubled or late deductions. |
| Direct deposit | Every change came through a verified, logged channel. | Review the bank change report every payroll. | Payroll diversion fraud. See the controls below. |
| Cost center and company | Valid, active and mapped to the general ledger. | Report inactive or unmapped codes. | General ledger posting and which company's tax accounts pay. |
| Manager and approver | Present and active. | Report workers whose manager has left. | Time approvals and workflow routing. |
Direct deposit change controls
Bank detail changes move money, so they need the tightest controls. Build these in, and test them.
- Accept bank changes only through authenticated self-service or a verified process. Never from an email or phone request alone.
- Verify unusual requests by calling back on a number already on file, not one in the request.
- Send an automatic notice to the employee's contact details on file whenever bank details change.
- Require multi-factor authentication for self-service.
- Flag changes made just before a payday, from a new device, or on the same day as a contact detail change.
- Review the bank change report every payroll, with a second person signing off.
More review ideas are in the payroll controls workspace.
HRIS operations calendar
Recurring HRIS work by cadence. Dates appear only where an official page confirms them. Everything else follows your own calendars.
Every payroll
- Check integration results and rejected records before the cutoff.
- Review the audit report for pay rate, bank and tax changes.
- Confirm every new hire and termination reached payroll.
- Clear tickets that touch this payroll first.
Monthly
- Reconcile HR headcount to the payroll register.
- Tie benefit elections to deductions and carrier invoices with benefits and payroll.
- Remove access for movers and leavers.
- Run the data audit and fix at the source.
- Read vendor release notes and plan testing.
Quarterly
- Review access for sensitive roles, such as pay, bank and security administration.
- Look for segregation of duties conflicts.
- Review integration error trends and fix repeat causes.
- Support payroll's quarter-end tie-outs with clean HR data.
- Update the data dictionary.
Once a year
| Work | When | What to do | Source or guide |
|---|---|---|---|
| Open enrollment | Before the plan year starts, on your benefits calendar | Build plans and rates, test elections to deductions in a sandbox, then audit the first deductions. | What payroll needs |
| Merit and pay cycles | On your compensation calendar | Load mass changes with the right effective date, reconcile totals and plan for retro. | Retro pay calculator |
| Year-end W-2 data checks | November to January | Validate names, SSNs, addresses, state and local codes and status for everyone paid this year. 2026 Forms W-2 are due to employees and to SSA by February 1, 2027. | IRS W-2 instructions |
| ACA Forms 1094-C and 1095-C | January to March | Check hours, full-time status, offers and enrollment month by month. The IRS draft 2026 instructions give March 2, 2027 to furnish full-time employees. Under Notice 2025-15, you may instead post a website notice by that date and keep it up through October 15, 2027. File by March 1, 2027 on paper or March 31, 2027 electronically. With 10 or more returns, you must file electronically. | Draft 2026 instructions · Notice 2025-15 |
| EEO-1 Component 1 | When the EEOC opens the collection | Check job categories, race and ethnicity, sex and work location data. The EEOC has not posted 2025 collection dates. It proposed removing the report on July 23, 2026, and that is not final. | EEOC · 91 FR 46332 |
| Vendor release testing | On your vendor's published release schedule | Read release notes, run regression scripts in a preview or sandbox tenant, retest integrations and record sign-off. | Testing guide |
| Full access review | At least once a year | Have managers and data owners confirm every role. Remove what is not needed and keep the evidence. | Controls workspace |
| Records retention | Once a year | Apply your retention schedule. Dispose of records past their period unless a legal hold applies. | Retention answer |
| New tax year | December and January | Confirm payroll loaded new-year tax limits, and that new tax forms from employees reached payroll. | 2027 rates and limits |
| Organization and cost centers | Before the fiscal year starts | Load new organizations, cost centers and managers with Finance, and map them before first use. | Mapping errors |
Hiring for HRIS?
The employer hiring exercises include practical exercises for HRIS specialist and HRIS analyst roles. Each packet has fictional source data, clear tasks, a separate assessor guide and a 100-point rubric.
Building your own HRIS career? Start with the free payroll career studio.
Official sources
Each legal or regulatory fact on this page was checked on these official pages on November 9, 2026.
- eCFR, 29 CFR part 516 subpart A: records employers must keep under the FLSA (sections 516.2, 516.5, 516.6 and 516.7)
- IRS: how long should I keep records (employment tax records, at least 4 years)
- IRS Publication 15 (2026), Employer's Tax Guide: hiring new employees and recordkeeping
- IRS General Instructions for Forms W-2 and W-3 (2026): due dates
- USCIS Handbook for Employers M-274, section 10.0: retaining Form I-9
- HHS Administration for Children and Families, Office of Child Support: new hire reporting
- 42 U.S.C. 653a, State Directory of New Hires (U.S. Code, 2024 edition, GovInfo)
- Social Security Administration: Social Security Number Verification Service (SSNVS)
- Social Security Administration: SSNVS rules of use
- Social Security Administration: employer page, Business Services Online access change of November 7, 2026
- U.S. Equal Employment Opportunity Commission: EEO data collections (EEO-1 Component 1)
- Federal Register, 91 FR 46332: EEOC proposed rule, Removal of Reporting Requirements (July 23, 2026)
- IRS Notice 2025-15: alternative manner of furnishing Forms 1095-B and 1095-C
- IRS draft Instructions for Forms 1094-C and 1095-C (2026), dated September 4, 2026