ADP Workforce Now logoActive Directory logo

Identity and access management

ADP Workforce Now to Active Directory integration: accounts in your own domain, with expiry date and rehire from ADP

With an integration between ADP Workforce Now and Active Directory, KoppelHet creates an account in the right OU for every new employee from ADP, with job title, department and manager. A departure in ADP sets the expiry date on the account, and on a rehire the employee gets their old account back.

What the integration does

Organisations with ADP Workforce Now as their HR and payroll system and their own Active Directory domain often have the help desk create accounts from an email from HR. Someone returning after a year gets a second account, and a leaver already entered in advance in ADP can log in until IT's last day and sometimes after.

  1. The organisation registers the integration in ADP, with read access to workers and notifications, and write access to the business email address.
  2. An agent in your own network opens an outbound connection to KoppelHet and only gets rights on the managed OUs.
  3. On a hire KoppelHet creates the account in the OU that belongs to the company or department in ADP; on a rehire KoppelHet first looks for the old account.
  4. A departure in ADP sets the expiry date on the account; after the last working day it moves to the OU for leavers.
  5. Every night KoppelHet compares all workers in ADP, including archived ones, with the domain.
ADP Workforce Now → KoppelHet → Active DirectorySOURCEADP Workforce NowTARGETActive DirectoryKoppelHetmapping · logging · monitoringADP Workforce Now → KoppelHet → Active DirectorySOURCEADP Workforce NowTARGETActive DirectoryKoppelHetmapping · logging · monitoring
Out: User account in the OU of the company or department · Job title, department and manager · Expiry date from the end date of the position · Photo for the address book · Work address back to ADP
Back: KoppelHet writes the email address that belongs to the account back as the business email address in ADP Workforce Now.

What to watch for with ADP Workforce Now and Active Directory

  • ADP sends a separate notification when someone is rehired. KoppelHet then looks up the disabled account in the OU for leavers by ADP number and restores it, so the employee does not lose their old login name, folders and groups.
  • With a departure dated in the future the position in ADP is already terminated, while the worker stays active. KoppelHet sets that date straight away as the expiry date on the account, so Active Directory closes the account itself, even if the nightly run fails once.
  • A worker can have more than one position in ADP. KoppelHet uses the main position for OU, department and manager, and only disables the account when the last position ends.
  • ADP also reports when someone goes on leave. If the organisation wants to disable accounts during long leave, KoppelHet does so on that notification and restores the account on return; by default we leave the account enabled.
  • ADP only returns former workers if the integration asks for them with a dedicated header. KoppelHet does so in the nightly comparison, so a missed departure notification still leads to a disabled account.
  • The business email address can be written in ADP through the API. As soon as the account and mailbox exist, KoppelHet puts the address in ADP, so payslips and ADP notifications go to the work address.
  • A photo from ADP can be larger than the 100 kB Active Directory allows for thumbnailPhoto. KoppelHet reduces it first, and refreshes it when ADP reports a new photo was uploaded.

This integration is also part of joiner, mover, leaver.

How we build and run it

  • The integration runs on the KoppelHet platform, hosted in a data centre in the EU.
  • Every sync and every error is visible in the functional log; on an error your administrator is notified.
  • A change that cannot go through is not half-applied but queued for another attempt.
  • KoppelHet is ISO 27001 certified. Data travels encrypted and stays on the platform no longer than needed.
  • After go-live we manage the integration and adjust it when your process changes.
  • The integration fits next to your existing integration layer. Only the fields in the design are transferred; the platform keeps no register of its own.

Implementation, architecture and compliance

Implementation and price

This is not an app you switch on. We build the integration for your organisation on our platform, with building blocks we reuse on every project. So it is custom work that does not start from scratch.

A consultant prepares the intake and analyses both systems. We then record the mapping and exceptions field by field, test in the test or acceptance environment and go live at a moment you choose. Costs are a one-off amount for the setup and a monthly amount for platform, monitoring and support.

Price indication · Basic

Leave your work email and you see the price indication right away.

We only use your address to follow up on your question about this integration.

Frequently asked questions

Does a port need to be opened in the firewall?

No. The agent opens an outbound connection itself; ADP's notifications arrive at KoppelHet's platform, not at the server.

Do we also work with Entra ID?

Yes. If the domain is synchronised to Entra ID, the Microsoft account follows automatically. Without your own domain KoppelHet writes directly to Entra ID.

Technical details for IT

For those who want to know how it works under the hood: APIs, fields and sources used.

  • ADP Workforce Now through the Worker Management API: GET /hr/v2/workers (50 per page, $top and $skip; $orderby and count with a filter not supported), Content-Type application/json;archived=true for archived workers. Notifications worker.hire, worker.rehire, worker.onLeave, worker.terminate, worker.workAssignment.modify and worker.photo.upload. Write-back with /events/hr/v1/worker.business-communication.email.add and .email.change.
  • Active Directory is written by an agent in the customer's network with an outbound connection. Attributes employeeID, sAMAccountName (at most 20 characters), userPrincipalName, givenName, sn, displayName, title, department, manager, accountExpires and thumbnailPhoto (at most 100 kB). The service account only has rights on the managed OUs.

Which fields are transferred

The key fields. The full mapping is agreed per customer.

Field in ADP Workforce NowField in Active DirectoryNotes
associateOIDemployeeIDFixed key, also after rehire
Preferred name en family namegivenName, sn, displayName
Achternaam en voornaamsAMAccountNameAt most 20 characters
Job titletitle
Department (homeOrganizationalUnits)department en OU
reportsTomanager
Termination date van de positieaccountExpires
Corporate contact photothumbnailPhotoReduced to at most 100 kB

Related

Which systems do you want to connect?

Tell us which systems you use and what should happen automatically. Together we define the smallest working solution, with a clear design and a quote before building.