Payroll integration
Rippling to Loket integration: Dutch employees from Rippling with pay and hours to the payroll run
With an integration between Rippling and Loket, a new employee of the Dutch entity from Rippling arrives in Loket as a concept employee, and pay, working hours and termination go to the employment in Loket. Contractors and staff employed through an EOR stay outside Loket.
What the integration does
Organisations that use Rippling worldwide for HR but have their own Dutch entity paid in Loket send new hires and pay changes to the payroll bureau by hand. Rippling mixes permanent staff, contractors and people through an EOR, and the bureau has to work out itself who belongs in the payroll run.
- HR hires an employee at the Dutch entity in Rippling.
- KoppelHet sees the worker with status accepted or active and creates a concept employee in Loket at the matching employer.
- Payroll completes BSN, collective agreement, payroll tax credit and pension and converts the concept.
- A new salary or a different working schedule in Rippling goes to the pay or working hours in Loket, with the effective date.
- A termination in Rippling ends the employment in Loket per the end date.
What to watch for with Rippling and Loket
- A legal entity in Rippling has a management type, such as PEO or EOR. Someone working in the Netherlands through an EOR is on that party's payroll, not in your Loket. KoppelHet only includes workers of your own Dutch entity.
- Rippling calculates the hourly rate of a salaried employee and the annual amount of an hourly worker on a forty-hour week, which does not fit a Dutch working week. KoppelHet therefore uses the amount HR actually entered, and never the derived amount.
- Rippling has country fields for, among others, the American and Canadian tax numbers, but not for the BSN. KoppelHet therefore leaves the BSN empty in the concept, and payroll completes it before converting the concept. If the BSN is in a custom field in Rippling, KoppelHet includes it.
- Rippling has the status accepted for someone who has signed the offer but has not yet started. KoppelHet creates the concept in Loket at that status, so payroll can complete everything weeks before the first payroll run.
- A termination in Rippling has a type, including a declined or withdrawn offer. If a concept already exists in Loket, KoppelHet deletes nothing but notifies payroll, so no employment is started for someone who is not coming.
- Rippling provides for every worker the earliest start date across all their employments. When someone returns, KoppelHet sees from the difference with the new start date that it is a return, and starts a new employment for the employee already in Loket.
- Fields the integration has no right to in Rippling come back as redacted with a reason. KoppelHet checks for every concept that salary and dates are readable, and notifies HR when a right is missing instead of putting an empty wage in Loket.
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
Rippling also runs payroll in the Netherlands itself. Why Loket then?
If your payroll bureau works in Loket and that stays the case, the payroll run belongs there. The integration makes sure Loket knows the same people and amounts as Rippling.
What if the salary is not in euros?
Every amount in Rippling has its own currency. KoppelHet does not pass on an amount that is not in euros; payroll gets a notification.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Rippling REST API (rest.ripplingapis.com) with a bearer token with workers.read and the scopes needed for nested objects, version pinned through the Rippling-Api-Version header. GET /workers with filter on status and updated_at, expand on user, legal_entity (management_type PEO, EOR or COR), employment_type (type, compensation_time_period, amount_worked) and compensation (annual_compensation, hourly_wage, salary_effective_date, currency_type per amount); fields number, start_date, original_start_date, end_date, termination_details, custom_fields; redacted fields in __meta.redacted_fields. Cursor pagination, limit up to 100.
- Loket is written through the Loket REST API (api.loket.nl/v2) with OAuth 2.0: concept-employee, convert to employee, create-employment, wage, working-hours and ending the employment. Testing in the acceptance environment (api.loket-acc.nl/v2).
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Rippling | Field in Loket | Notes |
|---|---|---|
number (worker) | Personeelsnummer | |
user (naam) | Voornaam, voorvoegsel en achternaam | |
legal_entity (management_type) | Werkgever in Loket, of buiten de koppeling bij EOR of PEO | |
employment_type.type | Alleen EMPLOYEE naar Loket | |
start_date en original_start_date | Begindatum dienstverband | |
employment_type.compensation_time_period | Maandloon of uurloon | |
compensation.annual_compensation of hourly_wage | Loon per verloningsperiode | |
compensation.salary_effective_date | Begindatum van het loon | |
employment_type.amount_worked | Arbeidstijd | |
end_date en termination_details | Einde dienstverband |
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