Identity and access management
ADP GlobalView to Entra ID integration: accounts per country from international payroll
With an integration between ADP GlobalView and Microsoft Entra ID, a new employee from GlobalView automatically gets a Microsoft account with country, legal entity, organisational unit, job and manager. After the termination date in GlobalView, KoppelHet blocks sign-in in Entra ID, for every country GlobalView processes.
What the integration does
Multinationals without a global HR system, which have outsourced payroll per country to ADP GlobalView, often only hear about new employees in a country through an email from local HR to IT. A departure in a smaller country reaches the central IT team late, and the account stays active.
- The customer has a communication user created in GlobalView and registers the integration with ADP with read-only rights on worker data.
- KoppelHet retrieves the workers per country, a hundred per request.
- For a new employee KoppelHet creates the account with country, entity, organisational unit, job and manager.
- The work location country sets the usage location, so Microsoft 365 licences can be assigned right away.
- After the termination date in GlobalView KoppelHet blocks sign-in and records the leave date in Entra ID.
What to watch for with ADP GlobalView and Microsoft Entra ID
- GlobalView only returns workers of several countries per country. Every list request must pass the ISO country code in a separate header. KoppelHet therefore goes through all countries GlobalView processes for you, and reports it when a country is added that is not yet in the integration.
- Entra ID requires a usage location before a user can get a licence. GlobalView has the country code per work location. KoppelHet sets it as the usage location, so a new colleague in Poland or Brazil has a licence on the first day.
- Besides the full Worker API, ADP has a Worker Demographics API, intended for use without sensitive personal data. KoppelHet uses that variant where possible, so date of birth, address and pay data from GlobalView do not reach KoppelHet or Entra ID.
- A move to another legal entity or a rehire gets a new personnel number in GlobalView, and the earlier, ended assignment then no longer appears in the API. KoppelHet therefore keeps its own record of which account belongs to which employee, so the move produces neither a second account nor an unjustified block.
- GlobalView runs on the SAP payroll engine. The organisation consists of SAP units such as personnel area, personnel subarea and organisational unit. KoppelHet uses the organisational unit for the department and the legal entity for the company name, so dynamic groups per country and entity work.
- The business email address is a separate communication record in GlobalView, which is often still empty for a new employee. KoppelHet creates the address according to the naming rule; putting it back into GlobalView stays outside the integration, because the Worker API only reads.
- GlobalView does not support concurrent employments with several personnel numbers in one country. Someone who works in two countries does have two records. KoppelHet links them to one account based on the primary assignment.
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 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.
Frequently asked questions
We also have a global HR system. Is GlobalView the right source then?
Usually not. If everyone is in an HR system such as Workday or SAP SuccessFactors, that is the source for accounts. This integration is for organisations where GlobalView is the only complete record per country.
Who arranges access at ADP?
You, together with ADP: the communication user in GlobalView and the registration of the integration. KoppelHet supplies the details ADP asks for.
Can we start with a few countries?
Yes, and we recommend it. We start with the countries with the most employees; the rest can follow later as an extension.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- ADP GlobalView Worker API: GET /hr/v2/workers or /hr/v2/worker-demographics with header ADP-Context-ExpressionID country='XX' (one country per request), OData $top, $skip, $filter, $select and $count, at most 100 records per request. Scope through the Consumer Application Registry (…/workerProfileManagement/worker.read or workerDemographic.read); in GlobalView a Communication User (Practitioner).
- Entra ID is written through Microsoft Graph (user) with employeeId (at most 16 characters), givenName, surname, userPrincipalName, mailNickname, jobTitle, department (at most 64 characters), companyName, employeeOrgData, usageLocation, country, manager, employeeHireDate, employeeLeaveDateTime (requires User-LifeCycleInfo.ReadWrite.All) and accountEnabled.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in ADP GlobalView | Field in Microsoft Entra ID | Notes |
|---|---|---|
associateOID | Vaste sleutel in KoppelHet | Unique across ADP products |
payrollFileNumber | employeeId | At most 16 characters in Entra ID |
legalName.givenName, nickName | givenName | |
legalName.familyName1 | surname | |
businessCommunication.emails (object 0010) of naamgevingsregel | userPrincipalName en mail | |
assignedWorkLocations.address.countryCode | usageLocation en country | |
legalEntityID | companyName | |
homeOrganizationalUnits (type ORGEH) | department | |
assignmentCostCenters.costCenterID | employeeOrgData.costCenter | |
jobTitle | jobTitle | |
reportsTo.associateOID | manager | |
hireDate | employeeHireDate | |
terminationDate | employeeLeaveDateTime en accountEnabled = false |
Related
ADP GlobalView → Active Directory
ADP GlobalView to Active Directory integration: domain accounts per country from outsourced payroll
ADP GlobalView → Google Workspace
ADP GlobalView to Google Workspace integration: Google accounts per country from payroll
ADP GlobalView → Okta
ADP GlobalView to Okta integration: Okta users from all countries in GlobalView
ADP GlobalView → SailPoint
ADP GlobalView to SailPoint integration: identities from all GlobalView countries in SailPoint