HR to ERP
Rippling to AllSolutions integration: workers of your own Dutch entity as employees in AllSolutions
With an integration between Rippling and AllSolutions, every worker of your own Dutch entity in Rippling automatically becomes an employee in the right AllSolutions company, with department, job, work email and start date. Workers through a PEO or EOR and rescinded offers stay out of AllSolutions, and a departure becomes an end date.
What the integration does
Organisations that hire people in several countries through Rippling and run the Dutch projects, hours and invoices in AllSolutions put new colleagues into AllSolutions by hand. People working through a PEO or EOR sometimes end up there as own employees by mistake.
- HR hires a worker in Rippling at an own Dutch entity.
- KoppelHet fetches the updated workers every hour and keeps only own employees of that entity.
- KoppelHet switches to the AllSolutions company of the entity and creates or updates the employee.
- An end date in Rippling becomes an end date in AllSolutions; a rescinded offer becomes an alert.
What to watch for with Rippling and AllSolutions
- A legal entity in Rippling can have a management type of PEO, EOR or COR. People who work through such an entity are formally employed by another employer. KoppelHet only puts workers of own Dutch entities into AllSolutions, and every own entity gets a fixed AllSolutions company.
- The AllSolutions integration account logs in to one default company. Through the login companies and departments function KoppelHet fetches the list of companies and switches to the entity's company before writing an employee. A worker of the second entity therefore does not end up in the books of the first.
- Rippling has terminations of the type declined, rescinded or reneged offer. Such a person never worked. If they are already in AllSolutions, KoppelHet does not try to delete them, because AllSolutions refuses that as soon as anything is linked to them; HR and project administration get an alert.
- A department in Rippling has a name and an optional reference code. AllSolutions wants an existing department code and otherwise returns the same error as on screen. KoppelHet uses the reference code as the key, and a department without a code or without a counterpart in AllSolutions becomes an alert.
- The worker list in Rippling can only be filtered on status and modification date among others, not on entity, and returns at most one hundred workers per page. KoppelHet only fetches the updated workers each round and filters on entity itself, so AllSolutions only gets the relevant changes.
- A job title in Rippling has its own effective date. AllSolutions accepts a change with only the fields that differ. KoppelHet only sends a new job on that date, and then only the job field, so whatever finance has added in AllSolutions itself stays in place.
- Besides the start date, Rippling keeps the original start date. If a former colleague returns, the two differ. KoppelHet then looks up the existing employee in AllSolutions through the free field with the Rippling ID and gives them a new start date, instead of a second record.
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
Do contractors from Rippling go to AllSolutions?
Not by default. If contractors book hours on projects, they can be added later as an extension, with a recognisable type in AllSolutions.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Rippling through the REST API: GET /workers with filter on updated_at and status, expand on user, legal_entity, employment_type and department, order_by updated_at, cursor and limit (1 to 100). Fields number, status (INIT, HIRED, ACCEPTED, ACTIVE, TERMINATED), start_date, original_start_date, end_date, title with title_effective_date, work_email, employment_type.type (EMPLOYEE or CONTRACTOR), legal_entity.management_type (PEO, EOR, COR), department.reference_code and termination_details.type (including OFFER_DECLINED, RESCIND, RENEGE). Token with only the required scopes.
- AllSolutions through the REST API: POST /api/v1/Login and then the token, with RefreshToken once the fixed validity has expired. GET on the configured view with pageSize and cursor, POST for a new employee with the same checks as the form, PUT /api/v1/{browser}/{RecordID} with only changed fields. Switching company with GET /api/v1/mwzbdr and the afdelingWijzig action. Free fields with their own REST API label.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Rippling | Field in AllSolutions | Notes |
|---|---|---|
number | Personeelsnummer | |
id (Rippling) | Vrij veld met REST API-label | Fixed key |
user (naam) | Naam | |
work_email | E-mailadres | |
legal_entity | AllSolutions-bedrijf (inlogbedrijf) | Through a table |
department.reference_code | Afdeling | |
title | Functie | |
start_date en end_date | Datum in dienst en datum uit dienst |
Related
Carerix → Rippling
Carerix to Rippling integration: successful match as a hire for review in Rippling
Greenhouse → Rippling
Greenhouse to Rippling integration: every hire straight into Rippling for review
Recruitee → Rippling
Recruitee to Rippling integration: hired candidates ready to hire
Rippling → 4PS Construct
Rippling to 4PS Construct integration: own employees of the construction entity in 4PS, with department as a dimension