Recruitment to HR
Oracle Taleo to Nmbrs integration: Dutch hires per legal entity in Nmbrs
With an integration between Oracle Taleo and Nmbrs, a candidate hired in Taleo for a Dutch entity arrives as an employee with employment, contract, schedule and salary in the right Nmbrs company. KoppelHet collects the hires with a scheduled export from Taleo and leaves only the Dutch payroll tax details to the payroll office.
What the integration does
Organisations with international recruiting in Oracle Taleo and Dutch payroll in Nmbrs, often through a payroll office, have new employees forwarded as a spreadsheet. The office enters them by hand into Nmbrs and asks by email which BV someone is joining.
- KoppelHet requests the hires for Dutch entities from Taleo on a schedule.
- For each hire the Taleo organisation determines which Nmbrs company the employee goes into.
- KoppelHet creates the employee and then employment, contract, schedule and salary.
- KoppelHet skips applications that were already processed in a next export.
- The payroll office adds BSN and payroll tax details and checks before the run.
What to watch for with Oracle Taleo and Nmbrs
- Nmbrs creates an employee per company, and an international organisation often has more than one BV in the Netherlands. KoppelHet records which Taleo organisation belongs to which Nmbrs company, so the payroll office no longer has to ask where someone is joining.
- Taleo sends no message on a hire; KoppelHet requests an export set up in Taleo Connect on a schedule. The result is a CSV file whose columns must match that setup, so a change to the export also needs a change in the integration.
- A next export can contain the same hire again. KoppelHet stores the Taleo application number with the employee, so the same new colleague never appears twice in Nmbrs.
- A Taleo offer usually has an annual salary. KoppelHet converts it to the amount per period of the Nmbrs company and only takes amounts in euro; that way the office does not accidentally pay an amount in dollars.
- Without hours per week Nmbrs cannot fill a schedule. If the hours are not in the offer, KoppelHet takes them from the requisition; if they are missing there too, the integration creates no schedule and the payroll office gets a notification.
- Oracle recommends making the step used for export mandatory in the selection workflow. That way a recruiter does not skip the hire and the payroll office does not miss a new employee.
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
Does Oracle Taleo have an integration with Nmbrs?
Not as standard. KoppelHet builds and manages the integration on the Taleo export service and the Nmbrs API.
Our payroll office manages Nmbrs. What does this ask of them?
Grant consent once for the integration on the Nmbrs companies. After that new employees appear by themselves.
How quickly is a hire in Nmbrs?
Within a few hours, depending on how often the export runs. Well in time for the next payroll run.
Are hires for Belgium or Germany included?
No, only Dutch entities. Other countries 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.
- Taleo through an export configuration from Taleo Connect Client (TCC) and the Taleo Enterprise export service; submit document returns a message key, the status is checked until there is a correlation key, then the CSV result follows. Large results are processed in segments.
- To Nmbrs through the Nmbrs REST API with OAuth and consent per company; first the employee per company, then address, employment, contract, schedule and salary. 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 Oracle Taleo | Field in Nmbrs | Notes |
|---|---|---|
Kandidaat: voornaam en achternaam | Voornaam, tussenvoegsel en achternaam | Split off the name prefix |
Kandidaat: geboortedatum | Geboortedatum | |
Kandidaat: adres | Adres | Can be a foreign address |
Aanbod: startdatum | Begindatum dienstverband | |
Aanbod: salaris | Salaris | Annual amount converted to the company's period; euro only |
Aanbod of vacature: uren per week | Rooster | |
Vacature: organisatie | Nmbrs-bedrijf en afdeling | Through a lookup table |
Vacature: soort dienstverband | Contract bepaalde of onbepaalde tijd |
Related
Oracle Taleo → AFAS Profit
Oracle Taleo to AFAS integration: Dutch hires from international recruiting into AFAS
Oracle Taleo → HiBob
Oracle Taleo to HiBob integration: hires from a Taleo export as new employees in Bob
Oracle Taleo → Loket
Oracle Taleo to Loket integration: hired candidates from the Taleo export as concepts in Loket
Oracle Taleo → Personio
Oracle Taleo to Personio integration: hires from a Taleo export as a person in onboarding in Personio