The ADP Turnkey Connector setup process for clients in Europe, the Middle East, and Africa (EMEA) differs from the process for clients in the United States and Canada. EMEA setup is initiated through ADP's regional partner channel rather than a direct purchase from the ADP Marketplace, which introduces additional steps, a consent-based authorization flow, and an extended setup timeline. This article outlines what EMEA clients can expect.
Why the EMEA Setup Process Differs
ADP operates separate infrastructure for clients outside North America through its Employer Services International (ESI) division. ESI does not use the same self-service ADP Marketplace purchase and authorization flow available in the US and Canada. Instead, partner integrations such as the Absorb ADP Connector are enabled by ADP's regional integrations team after the client submits a service request and signs a consent form. This means EMEA clients work with both ADP and Absorb across several hand-off points before the connector can be configured.
Process Comparison
The table below summarizes the key differences between the US/Canada and EMEA setup flows. The configuration phase, which covers field mapping, Department mapping, sync filtering, and Admin access rules, is the same across both regions once the connector is enabled.
| Step | US / Canada | EMEA |
| Initial Engagement | Client purchases the Absorb Connector directly from the ADP Marketplace. | Client is engaged through the ADP Partner Portal via an ADP Channel Sales representative. |
| Integration Enablement | Authorized live during the setup call using a Secret Key issued by Absorb (valid for 30 minutes). | Client submits a service request via the ADP eService portal; ADP Integrations sends a consent form for the client to sign and return. |
| Credential Delivery | Issued in real time during the setup call. | Issued by ADP Integrations to Absorb approximately one to two days after the signed consent form is processed. |
| Backend Enablement | Completed during the same setup call. | Completed by Absorb after credentials are received; expect approximately two weeks. |
| Configuration Meeting | Combined with the authorization step in a single guided setup call. | Scheduled separately once backend enablement is complete. |
EMEA Setup Steps
EMEA clients should expect the following sequence of events from initial engagement through to the configuration meeting. Several of these steps depend on actions taken by both ADP and the client, so timelines may vary based on how quickly each hand-off is completed.
- The client is introduced to the ADP Partner Portal through an ADP Channel Sales representative.
- Absorb works with the client to close the partnership through ADP's regional channel.
- Once the deal is closed, the client submits a service request through the ADP eService portal to enable the partner integration. The request must be routed to the Marketplace Client Support queue.
- The ADP Integrations team sends a consent form to the client. The client signs and returns the consent form to ADP.
- ADP processes the consent and issues the integration credentials (Client ID and Secret) to Absorb. This typically takes one to two days.
- Absorb completes the back-end enablement of the connector. The expected service-level objective for this step is approximately two weeks.
- Absorb schedules a configuration meeting with the client to set up field mapping, Department mapping, sync filtering, Admin access rules, and to enable the sync.
When submitting the ADP eService request, the ticket must be routed to the Marketplace Client Support queue and identified as a marketplace integration activation request. Submitting the wrong ticket type will delay the integration enablement. Your Implementation Project Manager can provide guidance on the required ticket details before submission.
Expected Timeline
Because EMEA setup depends on multiple handoffs between the client, ADP, and Absorb, the end-to-end timeline is longer than the standard three-to-six-week window cited for US and Canada setups.
Clients should plan for the consent and back-end enablement phases to take approximately two to three weeks on their own, in addition to the time required for marketplace engagement and configuration.
What to Prepare
To help keep the EMEA setup on track, clients should be ready to provide the following information and resources before the configuration meeting.
- A nominated ADP System Administrator who also holds Absorb System Admin privileges.
- A clear understanding of how the client's ADP department structure should be represented in Absorb.
- Any Custom Fields that need to exist in Absorb before the sync is enabled.
- Confirmation that all associated ADP-side costs are understood and approved internally.
- Any required Admin access rules that should be applied to synced Users.
EMEA Support Contact
For questions specific to the EMEA marketplace activation process, ADP provides a dedicated support address. This address is intended for activation-related queries and should not be used in place of submitting the eService ticket.
- ADP ESI EMEA Marketplace Support: Marketplace_ESI_Integration@adp.com
Related Articles
Once back-end enablement is complete, the configuration steps for EMEA clients are the same as those documented for US and Canada clients. The following articles cover the configuration phase in detail.
Comments
Article is closed for comments.