ADP Workforce Now logoAllSolutions logo

HR to ERP

ADP Workforce Now to AllSolutions integration: employees with department, cost centre and manager in AllSolutions

With an integration between ADP Workforce Now and AllSolutions, every employee from ADP appears automatically in AllSolutions, with the department and cost centre of their primary position, their manager and their ADP number in a custom field. KoppelHet updates a transfer, a new manager or a termination in ADP in AllSolutions, so hours and projects land in the right place.

What the integration does

Organisations that run HR and payroll in ADP Workforce Now and projects and hours in AllSolutions create employees in AllSolutions by hand. A new department or manager in ADP reaches AllSolutions later, so hours sit on the wrong cost centre or go to the wrong person for approval.

  1. HR records a hire or change in ADP Workforce Now; ADP sends an event notification.
  2. KoppelHet fetches the worker and picks the primary position.
  3. KoppelHet creates or updates the employee in AllSolutions, in the company that belongs to their ADP company.
  4. On a different manager or department KoppelHet only changes those fields.
  5. After a termination KoppelHet sets the end date in AllSolutions.
ADP Workforce Now → KoppelHet → AllSolutionsSOURCEADP Workforce NowTARGETAllSolutionsKoppelHetmapping · logging · monitoringADP Workforce Now → KoppelHet → AllSolutionsSOURCEADP Workforce NowTARGETAllSolutionsKoppelHetmapping · logging · monitoring
Out: Employee with name, work email and start and end date · Department and cost centre from the primary position · Manager · ADP number in a custom field

What to watch for with ADP Workforce Now and AllSolutions

  • ADP has one workerID per employee, and a separate positionID per position. Someone with two positions in ADP is one employee in AllSolutions. KoppelHet takes the department and cost centre of the position ADP marks as primary, the same one ADP uses to decide whether someone is still employed.
  • ADP sends one event when the home department, cost number or business unit changes, and a separate event for a different location. KoppelHet translates the first into department and cost centre in AllSolutions, and only uses the second when the location determines which AllSolutions company someone belongs to.
  • ADP reports a new manager with its own event. KoppelHet looks up the manager in AllSolutions through the ADP number in the custom field and sets them on the employee, so submitted hours go straight to the new manager for approval.
  • ADP only creates an event for changes in Workforce Now itself, not for changes through the API, and the workers list returns at most a hundred per page. KoppelHet therefore walks through all workers every night in pages of a hundred and compares them with the active AllSolutions view.
  • AllSolutions only shows the integration what is in the active REST API view, with its own labels per field. In AllSolutions those settings can be moved from the acceptance to the production environment as a zip file. KoppelHet tests the integration on acceptance and the administrator then moves the same settings across in one go.
  • ADP reports separately when the worker category changes, for example from temporary to permanent. AllSolutions has custom fields that can be changed through the API. KoppelHet puts the category in such a custom field, so project managers in AllSolutions can filter on own and temporary staff.
  • Personal data such as date of birth is masked by default in ADP and can only be requested unmasked with extra setup. AllSolutions does not need it for hours and projects. KoppelHet does not request it, so the integration works with ADP's default setup.

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

What if a department does not exist in AllSolutions yet?

Then KoppelHet reports which department is missing and processes the employee again once it exists.

Do hours from AllSolutions go back to ADP?

Not in this integration. Hours for payroll can be added 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 Workforce Now through the Worker Management API: GET /hr/v2/workers ($top at most 100, $skip, $filter, asOfDate; workerID unique per client, positionID per position, primaryIndicator) and event notifications worker.hire, worker.rehire, worker.terminate, worker.workAssignment.homeOrganizationalUnits.modify, worker.workAssignment.homeWorkLocation.change, worker.reportsTo.modify and worker.workAssignment.workerType.change. PII and SPI are masked by default.
  • AllSolutions through the REST API: POST /api/v1/Login with signature, then the token in every call and POST /api/v1/RefreshToken when the token expires (validity per interface). GET on the active REST view, POST to create, PUT with only changed fields; custom fields with a REST API label. Switching company through Inlogbedrijven/-afdelingen (MWZBDR). Export and import of settings as a zip from version 20.0.01.

Which fields are transferred

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

Field in ADP Workforce NowField in AllSolutionsNotes
workerID (idValue)Vrij veld met REST API-labelFixed key
legalName (givenName, familyName1)Naam
Werk-e-mailE-mailadres
CompanyAllSolutions-bedrijf (inlogbedrijf)
Home Department (primaire positie)Afdeling
Home Cost NumberKostenplaatsIf the view exposes this field
reportsToLeidinggevendeThrough the manager's ADP number
hireDate en terminationDateDatum in dienst en datum uit dienst

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.