How does Joinly sync Paycor to Active Directory?

Joinly reads each HR change in Paycor in the cloud through the Public API, then hands the action to the Joinly AD Agent inside your network, which makes the change in Active Directory. The Paycor employee record holds the authoritative employment data; the agent is the only component that touches your domain.

1. Joiner. HR completes the hire in Paycor. Joinly reads the new record, determines the role from department, job, position and location, and instructs the AD Agent to create the user in the correct OU, build the sAMAccountName and UPN from your rules, and add the right security groups — timed to the effective start date.

2. Mover. When someone changes position, department or legal entity, Joinly tells the agent to move the user to the matching OU, swap security-group membership and update attributes. Access that no longer fits the new position is removed, so permissions stay aligned with the actual job.

3. Leaver. On the termination date, Joinly instructs the agent to disable the AD account and optionally move it to a disabled-users OU. A transfer between legal entities is treated as a move rather than a leave, so an account is never disabled while the person is still employed.

Example: A home-services company runs Paycor and an on-premise AD across three branch offices. It hires a field technician with a start date next Monday. Joinly reads the effective-dated record, and on Monday morning the AD Agent creates the user in the Branch-North > Field OU, sets the sAMAccountName to a unique pattern, and adds the Field-Technicians group. When the technician later moves to the dispatch team, the agent moves the object to the new OU and swaps the groups the same day.

What manual AD account management costs

Without automation, every account starts as a Paycor ticket that an admin works through in Active Directory Users and Computers by hand — creating the object, choosing the OU, building the sAMAccountName, adding groups. Paycor exposes the data through its Public API but ships no AD provisioning connector and no role-to-group logic, so unless you build it yourself the decisions still fall to people.

• Onboarding delays. New joiners wait for an AD account and group access while a ticket sits in a queue, losing productive days in their first week.

• Permissions that don’t keep up (privilege creep). When movers change position, old security-group membership often stays attached, so people accumulate rights they no longer need.

• Forgotten offboarding. Accounts that aren’t disabled on time are a security and audit risk — and a transfer between legal entities can look like a leave and disable an account that is still in use.

Joinly vs. building Paycor-to-AD yourself

Paycor has no native AD provisioning connector, so the realistic alternative is scripting the Paycor Public API into AD or using the Entra provisioning agent. Here’s how that compares with the Joinly AD Agent for a Paycor-driven AD setup.

Watch-outs when connecting Paycor to Active Directory

A few details decide whether this connection stays reliable at scale.

• sAMAccountName uniqueness and length. AD limits the sAMAccountName to 20 characters and it must be unique across the domain. Joinly builds it from your rules with a fallback pattern, so duplicate names never produce a collision or a truncated, unreadable login.

• OU placement from Paycor structure. Legal entity, location, department and job don’t map one-to-one to your OU structure. Joinly builds explicit rules that place each user — and move them on a transfer — into the correct OU.

• Effective-dated hires and changes. Paycor stores a hire or position change with an effective date, sometimes before the first working day. Joinly reads that date and has the agent create or move the account on the right day, not before.

• Multiple legal entities. Paycor partitions data by legal entity and the API user must be permitted for each. Joinly reads every permitted entity into one combined feed, so no branch or company is left out of the AD provisioning.

• Service-account permissions. The agent acts under a service account with delegated rights. Joinly works with least-privilege delegation scoped to the target OUs, so the agent can create, move and disable users without domain-admin rights.

Joinly handles each of these by default with custom mapping and transformation.

Always audit-ready

Every account action the Joinly AD Agent performs is logged in the Joinly cloud: who was affected, when it happened, which OU and groups changed and which Paycor change triggered it. For NIS2 that matters directly: access can be traced back to an authorised HR source rather than an ad-hoc request. Joinly is ISO 27001 certified, runs in an EU data centre in Amsterdam, applies least-privilege by default, and is built to meet NIS2 and ISO 27001.

Example case

Take a home-services company with around 1,200 employees across three branch offices, running Paycor but still living in an on-premise Active Directory for its dispatch and field systems. Every new technician, dispatcher or office worker starts as a Paycor ticket that IT processes by hand in AD — creating the object, choosing the OU, building the login, adding groups. With seasonal hiring and frequent moves between branches the queue never empties, and new joiners wait until day two or three for their account.

Connect Paycor to Active Directory with Joinly and that work disappears. The Joinly AD Agent creates each user in the right OU on the start date, builds a unique sAMAccountName, adds the correct security groups, moves people on a transfer and disables accounts on the termination date with a 30-day grace window — all driven by the HR change in Paycor and across every permitted legal entity.

“An account is simply ready in the right OU when the technician shows up, branch moves move themselves, and we can show the auditor exactly which Paycor change created every bit of access.” — Head of IT, home-services company

The outcome this setup is designed for: onboarding drops from days to zero touch, privilege creep from old roles is eliminated, and the team can walk into its next NIS2 assessment with a complete, source-backed audit trail.