Carerix logoLoket logo

Recruitment to HR

Carerix to Loket integration: successful placement as a draft employee in Loket

With an integration between Carerix and Loket, a candidate with a successful match in Carerix becomes a draft employee in Loket, at the employer that belongs to the entity of the vacancy, with name, date of birth, Dutch address and start date. The new employee then adds BSN and bank account themselves through Loket, so that data does not have to come from the recruitment system.

What the integration does

Organisations that recruit their own staff in Carerix and run payroll in Loket retype every successful placement as a new employee. With several employers in Loket HR has to choose the right employer per placement, and BSN and IBAN are often requested by email.

  1. The recruiter sets the match in Carerix to a status for a successful placement.
  2. Every quarter of an hour KoppelHet retrieves the changed matches and determines the employer in Loket with a table.
  3. KoppelHet retrieves the pick lists for a new draft from that employer and translates gender and nationality.
  4. The draft is created in Loket with name, date of birth, address and start date.
  5. Payroll completes the draft; the employee enters BSN and IBAN themselves.
Carerix → KoppelHet → LoketSOURCECarerixTARGETLoketKoppelHetmapping · logging · monitoringCarerix → KoppelHet → LoketSOURCECarerixTARGETLoketKoppelHetmapping · logging · monitoring
Out: Match with status and start date · Candidate with name, prefix, date of birth and address · Vacancy with legal entity · Draft employee at the employer in Loket · Workflow for new employees in Loket

What to watch for with Carerix and Loket

  • In Loket a new draft belongs to an employer, and the allowed values for the draft are retrieved per employer. A Carerix vacancy can belong to a legal entity; per entity we record the employer in Loket, so a placement never appears as a draft at the wrong employer.
  • Carerix stores initials, first name, prefix and last name separately, the way Dutch payroll also uses them. KoppelHet puts them separately in the draft, so the name on the payslip and in the tax return is right without manual work.
  • The address in Carerix has street, house number, addition, postcode and city in their own fields. That matches a Dutch home address in Loket; KoppelHet does not need to cut anything from a text line.
  • Carerix has fields for social security number and IBAN on the candidate. KoppelHet does not carry them over by default; Loket has self-service for draft employees, through which the new employee enters this data themselves. That way a BSN is not kept in the recruitment system and the integration longer than necessary.
  • Some choices for a draft in Loket depend on the chosen payroll administration and pay scale. In the first version KoppelHet only fills personal data and the start date; pay scale, hours and salary are chosen by payroll in Loket, and sending them can be added later as an extension.
  • Loket only allows integrations on production once the application has been approved, and has an acceptance environment with test data. KoppelHet first tests the translation of Carerix pick lists to Loket there, before a real draft employee is created.

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

Does Carerix have its own Loket integration?

We did not find one in Carerix's public documentation or on Loket's integrations page. KoppelHet builds on the APIs of both.

Is this also meant for temporary agency workers?

This page is about your own staff. Paying flexible workers is a different process with its own arrangements, and therefore a different integration.

Who completes the draft?

Payroll in Loket. It chooses pay scale, terms of employment and hours and converts the draft into an employee.

Technical details for IT

For those who want to know how it works under the hood: APIs, fields and sources used.

  • Carerix through the GraphQL API (https://api.carerix.io/graphql/v1/graphql), confidential client with client credentials. crMatchPage with a qualifier on statusInfoModificationDate and statusInfo.isSuccessfullyFilled; CRMatch jobStartDate; CREmployee initials, firstName, lastNamePrefix, lastName, birthDate, toGenderNode, toNationalityNode, street, houseNumber, houseNumberSuffix, postalCode and city (sofiNumber and paymentIbanCode are not read); CRVacancy toLegalEntity.
  • Loket through the REST API with OAuth 2.0 (authorization code with refresh token). Metadata for a new draft through /providers/employers/{id}/jobapplicant/metadata, then per payroll administration and salary scale type. Create a concept employee at the employer; self-service for concept employees; workflow endpoints for the follow-up. Acceptance on api.loket-acc.nl/v2; production only for approved applications.

Which fields are transferred

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

Field in CarerixField in LoketNotes
CRVacancy toLegalEntityWerkgever in LoketThrough a lookup table per entity
CREmployee initials, firstNameVoorletters en roepnaam
CREmployee lastNamePrefix en lastNameVoorvoegsel en achternaamSeparately, as Loket stores them
CREmployee birthDateGeboortedatum
CREmployee toGenderNode en toNationalityNodeGeslacht en nationaliteitTo Loket's pick list
CREmployee street, houseNumber, houseNumberSuffix, postalCode en cityWoonadres
CRMatch jobStartDateDatum in 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.