Skip to main content

HRIS & payroll integrations

Connect the HR or payroll system your people already live in, and Oho imports — and keeps importing — workers and the credentials they hold.

Who it's for: Admins setting Oho up, and the IT teams who help them

Availability: Available — per-connector status, including Beta and Assisted setup, is listed on the Add a data source hub

What you get​

  • Maintain one list, not two — your source system stays the place you edit people
  • Import workers, applicants, and the credentials they hold, on the schedule you choose
  • Map your source's organisations, qualifications, and status values to Oho's once, then reuse that on every sync
  • Have returning workers recognised rather than duplicated, on a stable match key
  • Feed synced credentials into verification exactly like anything typed in by hand

Turn it on​

→ Add a data source — the shared five-step setup, plus every source Oho supports with its current status and its own step-by-step guide.

How it works​

Every source follows the same five steps: get your auth details, connect it in Oho under Admin → Integrations, map your fields, set a one-off or recurring schedule, then run and verify the first sync. After that your connected system owns the facts it sends — identity, contact details, employment, position, and the credentials it holds — and Oho refreshes them on every run.

→ Integrations — every system Oho can connect to, and what each one imports → Keeping data in sync — who owns which data once a system is connected → Ingest your data — every route into Oho, in the journey

For developers

For a large one-off load, or to create and update workers from your own code rather than through a connector, use the REST API.

→ Bulk import → Workers & credentials → API Basics

Good to know​

  • Your system owns the facts it sends; Oho owns whether a credential is valid. A sync never overwrites a verification outcome, and the place to correct a synced field is your source system, not Oho.
  • Syncing never deletes a person — off-boarding flows through as a change of status, so the compliance history is preserved.
  • Matching is by your upstream record ID for HRIS and ATS connectors, and by the Worker ID column for file imports. Never by email. See Map your fields.
  • Sources marked Beta work but may not import every field yet. Assisted setup sources are configured with you by Oho's team rather than through the self-serve builder.
  • Syncing a worker in doesn't start the re-check loop on its own — add a verification source for the credential types you hold.
  • For recruitment platforms rather than HR or payroll systems, see ATS integrations.
  • Don't see your system? Request a connector, and load your people from a spreadsheet or SFTP in the meantime.
  • Integrations is an admin area. If it isn't in your menu, ask an admin in your organisation.