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

For HRIS, payroll, benefits and IT

HRIS and payroll integration guide

Payroll can only pay what the HRIS sends it. This guide maps the data that moves between HR and payroll, how it moves, how to test it and how to prove it arrived.

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

See what flowsGo-live checklist

What flows from HR to payroll, and back

The HRIS is the system of record for people data. Payroll is the system of record for pay results. Each event below starts in one and finishes in the other.

10 events that move from the HRIS to payroll
EventWhat the HRIS sendsWhat payroll does with itWatch for
New hireLegal name, SSN, address, hire date, job, pay rate, pay group, FLSA status, work location, tax forms and cost center.Creates the payroll record and pays from the hire date.A hire entered after the cutoff misses the first payday. New hires must be reported to the state within 20 days of hire, or sooner where the state requires.
RehireThe same data as a new hire, on the original person record if your process reuses it.Reactivates the person and resets pay group, tax setup and deductions as needed.Duplicate records, and old deductions or bank details coming back. A rehire after 60 or more consecutive days apart is reported as a new hire.
Job, pay or status changeThe new values and the effective date.Pays the new rate from the effective date, and recalculates past periods when the change is back-dated.Back-dated changes create retro pay. Future-dated changes must not apply early.
Location changeThe new work or home address and its effective date.Updates state and local tax withholding and unemployment reporting.A new state may need new tax accounts first. Remote workers' home and work locations can differ.
Leave of absenceLeave type, start date, expected return date and paid or unpaid status.Stops or changes pay and decides how deductions are handled while away.Benefit deduction arrears, and leave pay from outside insurers or state programs.
TerminationTermination date, last day worked, reason and final pay details.Pays final pay, stops recurring pay and ends deductions.Late terminations cause overpayments. Federal law does not require an immediate final paycheck, but some states do (DOL).
Tax setupFederal Form W-4 and state withholding forms, often from self-service.Sets income tax withholding.Forms captured in HR but never sent to payroll.
Benefit deductionsPlan, coverage level, employee and employer amounts, and start and stop dates.Takes deductions and records employer contributions.Start dates in the middle of a pay period, and deductions that miss the first paycheck.
Time and attendanceApproved hours, overtime, time off and premiums, by day.Pays hours and premiums.Unapproved time, and time for people not yet active in payroll.
Bank detailsAccount and routing numbers and split rules, from a verified channel.Pays by direct deposit.Payroll diversion fraud. See the direct deposit controls.

New-hire timing: Office of Child Support and 42 U.S.C. 653a.

What payroll sends back

Pay results
Gross pay, deductions, taxes and net pay by pay date, for total rewards and analytics.
Deduction status
Deductions that were not taken in full, and arrears to collect.
Hours of service
Hours paid by month, when the HRIS or benefits team tracks ACA full-time status.
Year-to-date and W-2 data
Totals HR may need for reports and employee questions.
Costing
Pay and employer costs by cost center, for Finance and the general ledger.
Errors and rejects
Records payroll could not load, back to the HRIS team to fix at the source.

Preview what a single change will do with the employee change impact tool.

Effective dating and retro

Every HR change carries two dates: the day someone entered it and the day it takes effect. Payroll pays from the effective date.

A fictional back-dated raise

A made-up employee and employer. Not a real person or company.
StepDetail
EmployeeRiley Sample (fictional), paid biweekly at Juniper Ridge Supply (fictional)
Old rate$24.00 an hour
New rate$25.50 an hour, effective the first day of pay period 20
EnteredDuring pay period 22, after periods 20 and 21 were already paid
Hours already paid at the old rate160 straight-time hours in periods 20 and 21
Retro owed160 × $1.50 = $240.00, paid as a retro earning on the next payroll

If those periods had overtime, the overtime pay changes too. Try your own numbers in the retro pay calculator.

House rules for effective dates

Integration methods

Most organizations use more than one. Whatever suite you use, such as Workday, UKG, ADP, SAP SuccessFactors or Oracle, check its current integration documentation. Ask which methods it supports for your setup.

File-based (SFTP)

The HRIS writes a file on a schedule and sends it over SFTP. Payroll loads it before each cutoff.

Good for: Clear audit trail, easy to replay and simple to test.

Watch for: Run times, failed transfers, format changes and missed delta records.

API

One system calls the other's API to read or send changes, on a schedule or as they happen.

Good for: Faster updates and quick error feedback.

Watch for: Rate limits, retries, credential expiry and how effective dates are handled.

Middleware and iPaaS

An integration platform sits in the middle to map fields, schedule jobs and log errors.

Good for: Many systems, complex mappings and central monitoring.

Watch for: One more system to secure, monitor and document.

Vendor-delivered connectors

A prebuilt connector from the HR or payroll vendor, or a partner.

Good for: Common systems paired in common ways.

Watch for: Fit with your configuration, custom fields, and who supports it after go-live.

Spreadsheet loads

A person loads a template file of changes, such as a mass pay change.

Good for: One-time and annual changes.

Watch for: Bad loads change many records at once. Test in a sandbox first. See vendor import templates.

Full file or changes only?

A full file sends every in-scope person each time. It catches missed changes, but it is larger and slower. A changes-only (delta) file sends only what changed since the last run. It is smaller, but a failed run can drop changes.

Many teams send changes each run and a full file on a schedule as a safety net.

Change control and testing

Every change that can touch pay goes through the same steps. Payroll is a partner at each one.

  1. Request

    Describe the need, the people affected, the payroll impact and the date needed.

  2. Assess impact

    List every system, file, report and security role the change touches. Ask payroll, benefits and Finance.

  3. Build in a sandbox

    Never build or test in production.

  4. Test

    Run unit, integration and user tests. Add a parallel test for anything that changes pay.

  5. Approve

    Get sign-off from the data owners and payroll. The builder should not approve their own change.

  6. Release

    Move it to production away from payroll processing days, quarter-end and year-end.

  7. Watch the first payroll

    Check the first results closely, then close the change.

Types of testing

Five kinds of testing and when to use each
TestWhat it provesWhen
Unit testOne mapping, field or calculation works by itself.While building.
Integration testData moves end to end, from HRIS entry to payroll result, including errors and rejects.Before user testing.
User acceptance testThe change meets the business need, tested by the people who will use it.Before approval.
Parallel testOld and new setups give the same pay for the same data, employee by employee.Before a new system or integration goes live.
Regression testThings that already worked still work after a change or vendor release.Before every release and major change.

Test cases every HRIS to payroll integration needs

Before a vendor release, rerun these as your regression script in a sandbox or preview tenant. Use fictional or masked data.

Reconciliation: prove it arrived

An integration that ran is not the same as one that worked. These checks prove HR and payroll agree. List every difference with a reason and an owner.

Seven HR to payroll reconciliation checks
CheckCompareHow often
HeadcountActive employees in the HRIS by pay group, against people paid on the payroll register.Every payroll
New hiresHires effective in the period, against first-time payees.Every payroll
TerminationsTerminations, against anyone paid after their termination date.Every payroll
Pay ratesHRIS rates, against payroll rates for everyone.Monthly and after mass changes
DeductionsBenefit elections, against payroll deductions, against carrier invoices.Monthly
LocationsHRIS work and home locations, against payroll tax setup.Monthly and before year-end
Cost centersHRIS cost centers, against general ledger mapping.Monthly

Payroll ties its own register to the bank and the general ledger. See the payroll controls workspace.

Common integration errors and how to fix them

Fix the cause at the source, not only the paycheck. Then add a test case so it cannot return unnoticed.

12 common HRIS to payroll errors
SymptomLikely causeHow to fix it
A new hire is missing from payrollEntered after the run, a required field is blank, or the record was rejected.Check the reject report, fix the field in the HRIS and resend. Add a pre-cutoff check of hires.
Paid at the old rateEntered after the cutoff, wrong effective date, or a future-dated row was overwritten.Confirm the effective date in the HRIS, then let payroll calculate retro. Try the retro pay calculator.
The same person twice in payrollA rehire created a new ID, or records were matched on the wrong key.Inactivate the duplicate with payroll. Match on employee ID, never on name.
Paid after terminationThe termination was late or not sent, or the pay group did not end.Enter the termination, stop the payment if you can, and follow your overpayment process within state law.
Deduction missing or doubledPlan code not mapped, wrong start date, or the change was sent twice.Tie elections to deductions, fix the mapping, then refund or catch up with approval.
Wrong state taxWork or home location wrong, not sent, or not mapped to a tax code.Fix the location in the HRIS with the right effective date. Payroll then corrects withholding.
File rejectedFormat change, new required field, bad characters or a different date format.Compare the file with its specification. Check recent releases and configuration changes, then retest in a sandbox.
Names look garbledAccented letters or apostrophes are not supported by the file encoding.Agree on the encoding with the vendor, and test names with accents, hyphens and apostrophes.
Costs post to suspenseA new or inactive cost center is not mapped in payroll or the general ledger.Map new cost centers before first use, and run an unmapped code report every month.
Changes missing after a failed runA changes-only file skipped records when a run failed.Rerun from the last good point or send a full file. Add alerts for failed runs.
The integration ran, but nothing changedThe change is future-dated, or the integration's date rule leaves it out.Check how the integration picks effective dates, and write the rule down.
Name and SSN mismatch noticesA name or SSN was keyed wrong, or not updated after a legal name change.Validate with SSNVS, correct at the source with documents, and tell payroll before W-2's.

For system-specific help, use troubleshooting and vendor help.

Checklist

Go-live checklist

Use it for a new integration, a new system or a major change. Every item needs an owner and evidence.

  1. Every field is mapped, with an owner in the data dictionary.
  2. Test scripts passed for hires, rehires, changes, back-dated and future-dated changes, transfers, leaves, terminations and name changes.
  3. Parallel test results are reviewed, and every difference has a reason.
  4. Reconciliation reports are built for headcount, hires, terminations, rates and deductions.
  5. Security roles follow least privilege and segregation of duties.
  6. Error alerts go to named people, with a backup.
  7. Run times are set around payroll cutoffs and shared on the calendar.
  8. SFTP keys, API credentials and certificates are stored securely, with expiry dates tracked.
  9. A rollback plan is written and tested.
  10. Cutover steps are timed, with an owner for each.
  11. The support model is ready: queue, severities and vendor contacts. See the support playbook.
  12. HRIS, payroll, benefits, IT and Finance have signed off.
  13. Hypercare is planned for the first payrolls.
  14. Documentation is stored where the support team can find it.

Who does what: a RACI for HRIS and payroll

A starting point to adjust for your organization. Each row has one accountable team.

R
Responsible: does the work
A
Accountable: owns the outcome and signs off
C
Consulted: gives input before
I
Informed: told after
RACI for 16 HRIS and payroll activities across five teams
ActivityHRISPayrollBenefitsITFinance
Hires, changes and terminations in the HRISA/RCIII
Data dictionary and field ownersA/RCCCC
Integration build and monitoringACCRI
HR to payroll code mappingRACCC
Earning, deduction and tax setup in payrollCA/RCIC
Benefit plans, rates and electionsCCA/RIC
Deduction tie-out to carrier invoicesIRAIC
Headcount reconciliationA/RRIII
Cost centers and general ledger mappingCRIIA
HRIS security roles and access reviewsA/RCCCI
Single sign-on and user provisioningCIIA/RI
Vendor release testingA/RRRCI
Payroll processing and the payroll registerIA/RIIC
Payroll funding and journal entriesIRIIA
Year-end W-2 dataRA/RCIC
ACA hours, offers and Forms 1095-CRCA/RII

A/R means the same team is accountable and does the work. Scroll sideways on a phone to see every team.

Keep the integration records

Integration files, logs and approvals are part of your payroll records. Store them with the same care as the payroll register.

Your own retention schedule may keep records longer. See the retention answer on the HRIS Desk.

Integration questions

What is an HRIS to payroll integration?

It is the connection that moves employee changes from the HRIS into payroll. It can be a file, an API, middleware or a vendor connector. Whatever the method, it needs mapping, testing and monitoring. Compare the methods.

Is an API better than a file?

Not always. APIs can move changes faster and give quick error feedback. Files are simpler to audit and replay. Choose what your systems support well and your team can monitor. Integration methods.

How often should the HRIS send changes to payroll?

At least once before every payroll cutoff, with time to fix errors. Sending changes daily lets problems surface before the cutoff. Agree on the schedule with payroll and share it. What payroll needs, and when.

What is a parallel test?

You run payroll in the old and new setups with the same data and compare results by employee. Every difference needs a reason before go-live. Include a regular payroll and one with unusual events. Testing types.

How do we reconcile HR headcount to payroll?

Compare active employees in the HRIS with people paid on the payroll register, by pay group. List anyone active but unpaid, or paid but inactive, with a reason. Do it every payroll. Reconciliation checks.

Who should own the HRIS to payroll integration?

Name one accountable owner, often the HRIS team, with IT building it and payroll approving mappings. Write it down in a RACI chart. Shared ownership with no single owner leaves gaps. See the RACI.

More for HRIS and payroll teams

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. Your vendors' documentation and your own policies decide how your integration works.