Skip to content
Scope an integration

Guides

How to Integrate with an HRIS

What HR system integrations actually involve, from worker data models and effective dating to file feeds, terminations and reconciliation.

To integrate with an HRIS, agree which worker data you need, get scoped access from the customer, and read it through the vendor’s API or a scheduled report feed. Match people on a stable employee ID, handle effective-dated hires, transfers and terminations explicitly, and reconcile source and target before writing to production.

What is an HRIS integration?

An HRIS integration moves employee data between an HR system and another application, usually one way out of HR, sometimes with results written back.

The HRIS (or the broader HCM suite) is the system of record for who works at a company, in what role, where and for whom. Almost every other workplace system depends on that data. Typical integrations:

  • User provisioning Create, update and deactivate accounts in a SaaS product when people join, move or leave. See user provisioning.
  • Org and access sync Departments, locations, cost centres and managers drive groups, permissions and approval chains.
  • Learning and compliance New hires enrolled in training automatically; completions written back for HR records. See the LMS integration guide.
  • Payroll and time Hours, absences and accruals flow between HR, time tracking and payroll.
  • Analytics Headcount and attrition data loaded into a warehouse or BI tool.

For SaaS vendors, “Do you integrate with our HRIS?” is one of the most common questions in enterprise deals.

What does HRIS data actually look like?

HR data is not a flat list of users. It is a set of related, time-dependent records, and most integration bugs come from treating it as a simple table.

ConceptWhat it meansWhy it matters
Person / workerThe human, with a stable ID that survives job changesYour identity key should be this ID, not email
Employment / jobA role held for a period: title, department, location, manager, statusPeople can have several over time, sometimes at once
OrganisationDepartments, divisions, cost centres, legal entities, hierarchiesDrives groups and permissions in your product
StatusActive, on leave, terminated, pending startPending hires and leave states need explicit rules
Effective dateThe date a change takes effect, not the date it was enteredFuture-dated changes must not apply early
Custom fieldsTenant-specific fields and tablesEvery customer configures these differently

Effective dating deserves special attention. HR teams enter a transfer today that takes effect next month, back-date a correction, or schedule a termination for the end of a notice period. An integration that applies whatever it reads, the moment it reads it, will grant or remove access on the wrong day.

How do you get access to a customer’s HRIS?

Access is granted by the customer, from their own tenant, and it often takes longer than the build. Plan for it from day one.

  1. Identify the product Confirm the exact HR product and modules. Large vendors sell several products with different APIs under one brand.
  2. Choose the auth model API keys tied to an integration user, OAuth 2.0 for partner apps, or certificate-based service accounts, depending on the vendor.
  3. Request a least-privilege user Ask the customer’s HR systems admin for an integration user that can see only the fields you need.
  4. Send an access guide A step-by-step document for the admin cuts weeks of back-and-forth. Include screenshots and the exact permissions required.
  5. Test in a sandbox Use a sandbox or test tenant where the vendor offers one; otherwise agree a read-only phase on production.
  6. Store credentials safely Keep secrets in a secrets manager, rotate them and log every use.

Security reviews are normal at this stage, since HR data includes personal information. Have your data-handling answers ready; see Security & Trust.

Have an integration request in your backlog?

Send it over. You get a written scope and a fixed quote within 2–3 days.

Scope an integration

Should you use the API or a file feed?

Use the API when the tenant exposes what you need. Expect file feeds anyway, because many enterprise HR environments rely on scheduled reports and SFTP exports.

MethodHow it worksStrengthsWeaknesses
REST / SOAP APIRead and write records directlyFresh data, write-back possiblePermissions, rate limits, vendor-specific models
Webhooks / eventsThe HRIS pushes changes as they happenNear real-timeNot universal; events can be missed
Report-as-APIA saved report exposed as an endpointCustomer controls fieldsReport changes break the integration
SFTP file exportScheduled CSV or flat fileWorks almost everywhereLatency, format drift, no write-back
Unified APIOne normalised API across many HR systemsFast coverageCustom fields and effective dating may be limited

A robust design often combines two: webhooks or a change feed for freshness, plus a nightly full or incremental read to reconcile. For file feeds, see SFTP integration: validate headers, row counts and checksums before processing, and alert on files that are late, empty or malformed.

Whatever the transport, you need reliable change detection. Some vendors offer a “changed since” endpoint or event log; with full-file exports you compare each file against the previous one. Either way, keep a copy of the last state you processed so you can tell a genuine termination from a record that simply dropped out of a filtered report. See change data capture.

How do you match people across systems?

Identity matching is where most HRIS integrations go wrong. Pick one stable key, agree it with the customer in writing, and never change it quietly.

  • Use the employee ID The HRIS worker or employee number survives name changes, email changes and transfers. Store it on the target record.
  • Treat email as an attribute Emails change on marriage, rebranding and domain migrations. Matching on email creates duplicates and orphaned accounts.
  • Handle pre-existing accounts When users already exist in your product, run a one-time match report and resolve conflicts with the customer before the first sync.
  • Align with SSO The identity your SAML SSO setup asserts must map to the same person the HRIS creates. Mismatches lock people out.
  • Plan for contractors Contingent workers often live in a different module or system. Decide whether they are in scope.

How do you handle hires, transfers and terminations?

Lifecycle events carry the business risk. A late termination leaves a former employee with access; an early one locks out someone still working.

  1. New hires Create the account on or shortly before the start date, not when HR enters the record weeks ahead. Pending-start workers need a rule.
  2. Transfers and promotions Update department, location, manager and groups on the effective date, and re-run any rules that depend on them.
  3. Leave of absence Decide with the customer whether leave suspends access, keeps it, or pauses assignments such as training.
  4. Terminations Deactivate rather than delete on the effective termination date, keep history for compliance, and confirm the result in an audit log.
  5. Rehires Recognise the returning person by their stable ID and restore their history instead of creating a duplicate.

Every write should be idempotent, so a retried sync never creates a second account or applies a change twice.

How do the major HRIS platforms differ?

Each vendor has its own API style, access model and quirks. These notes reflect common patterns; always confirm details against the vendor’s current documentation and the customer’s tenant.

PlatformTypical accessNotes
UKGREST and SOAP services, scheduled reports or SFTP, depending on the productUKG Pro, UKG Ready and UKG Pro Workforce Management differ; access is provisioned by the customer
BambooHRREST API per company subdomain; API key, or OAuth 2.0 for partner appsWebhooks on monitored fields; custom fields and tables vary per account
WorkdaySOAP and REST web services, reports exposed as web services (RaaS)Integration system users and security groups set by the customer; strongly effective-dated
ADPPartner APIs via the ADP Marketplace partner programme, which partners must join before getting API accessProduct lines differ; partner onboarding and consent steps add lead time
HiBobREST API with service usersPopular in growing companies; custom fields common
RipplingREST API and app-store style partner integrationsOften combines HR with IT and device management data

If you need many of these quickly, a unified API can cover standard reads, with custom builds for customers who need more depth. Compare the options in unified API vs custom integrations.

How do you test and launch an HRIS integration safely?

HR data is sensitive and errors are visible to every employee. Launch in stages and prove the data matches before anything writes.

  1. Sandbox build Develop against a test tenant or synthetic data that covers your edge cases.
  2. Read-only dry run Run the full sync against production data without writing, and produce a reconciliation report.
  3. Review with the customer Walk through mismatches: missing IDs, duplicate emails, unexpected statuses, unmapped departments.
  4. Controlled cutover Enable writes for a pilot group or a single location first, then everyone.
  5. Monitor the first cycles Watch the first payroll period, the first batch of hires and the first terminations closely.

How do you keep an HRIS integration running?

HRIS integrations rarely fail loudly. They drift as customers add fields, reorganise departments and vendors ship new API versions.

  • Alert on failed, late or unusually small syncs, not just errors.
  • Re-run reconciliation on a schedule and track mismatch counts over time.
  • Track vendor deprecation notices and API versioning timelines.
  • Re-test after the customer changes their HR configuration.
  • Respect rate limits with batching and backoff, so large full syncs complete.

Hypogen offers this as an integration maintenance service.

FAQ

Frequently asked questions

Can't find your question? An integration engineer will answer it.

Last updated

What is the difference between an HRIS and an HCM?

An HRIS stores core employee records: people, jobs, organisation and status. An HCM suite usually adds talent management, payroll, time, performance and learning. For integration purposes the core worker data is similar; the HCM simply exposes more modules, each with its own API surface and permissions.

Can we integrate with an HRIS without a partner agreement?

Often yes. Many integrations run on credentials the customer grants from their own tenant. If you’re building a connector for many customers, a vendor partner or marketplace programme can simplify access, improve trust and sometimes unlock APIs. Requirements vary by vendor, so check before committing.

How often should an HRIS sync run?

It depends on the use case. Account provisioning and terminations benefit from near real-time updates or several runs a day. Analytics and reporting usually work fine nightly. Combine events for urgent changes with a scheduled reconciliation that catches anything events missed.

How do we handle custom fields?

Map them per customer during scoping. Build the integration so field mappings are configuration, not code, and validate that mapped fields exist before each sync. Custom fields are the norm in HR systems, especially at larger customers.

What if the customer only offers file exports?

That’s common and workable. Agree a file format, schedule and delivery method, usually SFTP. Validate every file on arrival, detect changes against the previous file, and alert on late or malformed files. File-based integrations can be just as reliable as API-based ones.

How do we protect employee data?

Sync only the fields the integration needs, encrypt data in transit and at rest, store credentials in a secrets manager, limit who can access logs, and sign a data processing agreement. Avoid copying HR data into tools, including AI tools, that don’t need it.

How long does an HRIS integration take?

Typically a few weeks from approved scope to production for a single customer, with customer-side access often the longest step, and 3–6 weeks is typical for us. Multi-customer connectors take longer because they need configuration, onboarding and support tooling.

Should we write data back to the HRIS?

Only when the customer needs it and the tenant allows it. Common write-backs are training completions, certifications and custom fields. Write-back needs broader permissions and stricter testing, because errors land in the system of record. Start read-only, prove the data flow, then add write-back for specific fields with an audit log.

Need data out of an HR system?

Tell us which HRIS and what should sync, and we'll scope it in 2–3 days.