Carerix logoNmbrs logo

Recruitment to HR

Carerix to Nmbrs integration: a placement becomes an employee with schedule and hourly wage

With an integration between Carerix and Nmbrs, a new placement in Carerix automatically becomes an employee in Nmbrs, with start date, end date, hours per weekday and gross hourly wage from the placement. Payroll only adds the BSN and payroll tax details, and the temporary worker is in the next run.

What the integration does

Agencies and secondment firms that employ temporary workers themselves plan placements in Carerix and run payroll in Nmbrs. For every new placement payroll retypes hours, hourly wage and end date, and an extension processed only in Carerix is noticed only when someone does not get paid.

  1. The consultant creates the placement in Carerix, with hours per day, hourly wage and duration.
  2. KoppelHet sees the new placement and fetches the candidate and the placement.
  3. In the Nmbrs company that belongs to the branch, KoppelHet creates the employee, then employment, schedule and hourly wage.
  4. Payroll adds BSN, payroll tax credit and the collective agreement details.
  5. KoppelHet updates an extension or new hourly wage from Carerix in Nmbrs, with the effective date.
Carerix → KoppelHet → NmbrsSOURCECarerixTARGETNmbrsKoppelHetmapping · logging · monitoringCarerix → KoppelHet → NmbrsSOURCECarerixTARGETNmbrsKoppelHetmapping · logging · monitoring
Out: Employee with name, name prefix, date of birth and address · Employment with start and end date · Schedule from the hours per weekday · Gross hourly wage · Nmbrs company per Carerix branch

What to watch for with Carerix and Nmbrs

  • A placement in Carerix records per weekday how many hours the temporary worker works. Nmbrs calculates pay from the employee's schedule, which is mandatory. KoppelHet therefore builds the Nmbrs schedule from those seven daily values, not from the weekly total alone.
  • A Carerix placement holds a gross hourly wage next to purchase and selling rates for the client. Only the gross hourly wage goes to Nmbrs; rates and margins stay in Carerix, so payroll does not see commercial agreements.
  • A placement in Carerix has an end date. If the consultant extends it, KoppelHet adjusts the contract end date in Nmbrs instead of creating a new employee, based on the placement number stored on the employment.
  • If a temporary worker works again through another placement afterwards, KoppelHet recognises the candidate in Carerix and looks up the existing employee in Nmbrs. A new employment is added to the same person, not a second person with the same BSN.
  • Agencies with several BVs have a company per BV in Nmbrs, and whoever grants consent in Nmbrs decides which companies the integration sees. KoppelHet picks the company through the Carerix branch of the placement; a new BV must also be opened up for the integration.
  • Carerix records the notice period of a placement in days and the contract type as a pick list. KoppelHet translates that pick list to the contract types in Nmbrs and reports an unknown value, so an agency clause does not silently become a regular contract.
  • Nmbrs retires the SOAP API on 1 March 2027. This integration writes through the REST API, so it does not need rebuilding at that switch.

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

Do rates and margins also go to Nmbrs?

No. Only the gross hourly wage goes along. Selling and purchase rates stay in Carerix.

What happens with an extension?

KoppelHet adjusts the contract end date in Nmbrs. No new employee is added.

Do worked hours go along as well?

Not in this integration; it prepares the temporary worker for payroll. Hours from Carerix timesheets can follow later as an extension.

What about the GDPR?

You are the controller and KoppelHet is the processor, under a data processing agreement. Only placed candidates go to Nmbrs, and every action is in the audit logging.

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. CRJob with startDate, endDate, hoursPerWeek, monWorkHours through sunWorkHours, hourlyWageGross, noticePeriodDays, toContractTypeNode, toEmployee, toMatch and modificationDate; rates (sellingPrice, purchaseRate) are not read. Fetched per page through pageable.
  • Nmbrs is written through the Nmbrs REST API with OAuth 2.0 and a subscription key; first the employee per company, then employment, contract, schedule and hourly wage. The SOAP API is retired from 1 March 2027.

Which fields are transferred

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

Field in CarerixField in NmbrsNotes
CRJob jobIDVrij veld bij het dienstverbandTo link an extension to the right placement
CREmployee initials, firstName, lastNamePrefix en lastNameVoorletters, voornaam, tussenvoegsel en achternaam
CREmployee birthDateGeboortedatum
CRJob startDateBegindatum dienstverband
CRJob endDateEinddatum contract
CRJob monWorkHours tot en met sunWorkHoursRooster (uren per dag)
CRJob hourlyWageGrossUurloon
CRJob toContractTypeNodeSoort contractThrough a lookup table

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.