How does Joinly sync Paychex Flex to Active Directory?

Joinly reads each worker change in Paychex Flex in the cloud, then hands the action to the Joinly AD Agent inside your network, which makes the change in Active Directory. Paychex Flex holds the authoritative worker record; the agent is the only component that touches your domain — and nobody on your team has to drive it.

1. Joiner. A new hire is added in Paychex Flex. Joinly reads the worker across the API’s separate worker, job, organization and communications endpoints, determines the role from department, location and job title, 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 hire date.

2. Mover. When a worker changes department, location or supervisor, 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 role is removed, so permissions stay aligned with the actual job.

3. Leaver. When a worker’s status flips to terminated on their termination date, Joinly instructs the agent to disable the AD account and optionally move it to a disabled-users OU. A status of leave keeps the account intact, so a temporary absence never locks someone out.

Example: A dental group runs Paychex Flex and an on-premise AD across four practices. It hires a hygienist with a hire date next Monday at its Riverside location. Joinly reads the worker, and on Monday morning the AD Agent creates the user in the Riverside > Clinical OU, sets a unique sAMAccountName, and adds the Clinical-Staff group. When the hygienist later transfers to the Downtown practice, the agent moves the object to the new OU and swaps the groups the same day — with no admin on site.

What manual AD account management costs

Without automation, every account starts as a note from the practice manager that someone works through in Active Directory Users and Computers by hand — creating the object, choosing the OU, building the sAMAccountName, adding groups. In a small Paychex Flex shop that someone usually isn’t a full-time AD admin, and there’s no native Paychex-to-AD provisioning at all, so every decision falls to a person.

• Onboarding delays. New joiners wait for an AD account and group access while whoever handles IT finds time, losing productive days in their first week.

• Permissions that don’t keep up (privilege creep). When workers change department or location, old security-group membership often stays attached, so people accumulate rights they no longer need — and no one reviews it.

• Forgotten offboarding. Accounts that aren’t disabled on time are a security and audit risk — easy to miss entirely when offboarding depends on someone remembering to open ADUC.

Joinly vs. manual AD for a Paychex Flex shop

There is no native Paychex-to-AD provisioning, so the real-world alternative is doing it by hand in ADUC (or buying a third-party connector). Here’s how Joinly compares for a small Paychex Flex client running on-premise AD.

Watch-outs when connecting Paychex Flex to Active Directory

A few details decide whether this connection stays reliable in a small organisation with no dedicated IT.

• 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 — common in a small firm — never produce a collision or a truncated, unreadable login.

• OU placement from a flat structure. Division, branch, department and location don’t map one-to-one to your OU structure, and small orgs change them often. Joinly builds explicit rules that place each user — and move them on a transfer — into the correct OU, and picks up new departments on the next sync.

• The worker is split across several API endpoints. The Paychex Flex API returns the base worker, the job, the organization and the email separately. Joinly joins them into one complete record, so the AD object is created with its department and email rather than half-empty.

• Worker status nuances. Paychex Flex distinguishes active, leave and terminated. Joinly maps leave to a kept-but-managed account and terminated to a disable, so a temporary absence never disables a live AD object.

• 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 — important when no one is auditing AD permissions.

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 Paychex Flex 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 dental group with around 120 staff across four practices, running Paychex Flex for payroll but still living in an on-premise Active Directory for its practice-management and imaging systems. There’s no IT department — the office manager handles AD between patients, processing each new hygienist or assistant by hand: creating the object, choosing the OU, building the login, adding groups. With seasonal cover and frequent moves between practices the work never stops, and new staff wait until day two or three for their account.

Connect Paychex Flex to Active Directory with Joinly and that work disappears. The Joinly AD Agent creates each user in the right OU on the hire date, builds a unique sAMAccountName, adds the correct security groups, moves people on a transfer between practices and disables accounts on the termination date with a 30-day grace window — all driven by the worker change in Paychex Flex, with no one on site touching AD.

“We never had an IT person to manage Active Directory. Now a hygienist’s account is simply ready in the right practice when they walk in, and when someone leaves it’s handled — we can show exactly which Paychex change created every login.” — Office Manager, dental group

The outcome this setup is designed for: onboarding drops from days to zero touch, privilege creep from old roles is eliminated, and the group can show a complete, source-backed audit trail without ever hiring an AD admin.