Payroll integration
Talentech to Nmbrs integration: employees, contracts and salaries from Talentech to Nmbrs
With an integration between Talentech and Nmbrs, employees, contracts, salaries and resignations of the Dutch entity go from Talentech's HR module to the right Nmbrs company, with the effective date from Talentech. The employee number from Nmbrs goes back to Talentech, so both systems recognise the same employee.
What the integration does
Northern European groups that use Talentech for recruitment and HR, and have a Dutch entity paid in Nmbrs, now enter contracts and salaries twice. A new contract that only starts next month in Talentech is sometimes already in Nmbrs earlier.
- Every hour KoppelHet reads employees, positions, contracts, salaries and resignations from Talentech.
- The legal entity of the position decides whether the employee goes to Nmbrs, and to which company.
- A new employee arrives in Nmbrs with contract, hours and salary; the employee number goes back to Talentech.
- A salary or contract with a later effective date goes to the Nmbrs period of that date.
- A resignation sets the end date in Nmbrs.
Back: The employee number from Nmbrs is stored as an external identifier on the employee in Talentech.
What to watch for with Talentech and Nmbrs
- A salary in Talentech consists of an amount, a currency and an effective date, without stating whether it is a monthly, annual or hourly amount. At the start we agree how the organisation records salaries; KoppelHet then checks whether an amount fits that range before it goes to Nmbrs.
- Contracts in Talentech have a flag for contracts that have yet to start, next to hours per week and a calculated part-time factor. KoppelHet prepares a future contract with its start date in Nmbrs, so it takes effect in the right period and not earlier.
- In Talentech an employee is linked to a position, and the position belongs to a legal entity. That entity decides the Nmbrs company. If someone moves to a position in another entity, Talentech creates a new contract and Nmbrs follows with a termination at one company and a hire at the other.
- Talentech stores national identity numbers with the country attached. KoppelHet only takes the number with country Netherlands as BSN; a Swedish or Norwegian personal number does not go to Nmbrs.
- Employees in Talentech can hold identifiers of external systems. KoppelHet writes the Nmbrs employee number back there, so a second round or a restart never creates a duplicate employee in Nmbrs.
- A resignation in Talentech has a resignation date, a last working day and an employment end date. Nmbrs gets the employment end date as the termination date; the last working day stays in Talentech.
- Talentech has no fixed field for a bank account. An IBAN can sit in a custom field section per employee; otherwise the payroll bureau completes it in Nmbrs. A position can have a collective agreement, and KoppelHet passes that name along as a check for the bureau.
- Each Talentech API requires its own scopes, and customers request API access through their account manager; Talentech notes that some APIs incur extra costs. For this integration we only ask read access to employees, positions, contracts, salaries and resignations, plus write access for the external identifier.
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
Which Talentech product is this?
The HR module with employees, positions, contracts and salaries, which Talentech exposes through the PeopleCore API. Recruitment in Talentech is separate from this integration.
What stays with the payroll bureau?
Payroll tax credit, pension, the collective agreement setup and the payroll run. The integration delivers the changes and does not overwrite those settings.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Talentech is read through the PeopleCore API (https://api.talentech.io/peoplecore) with a JWT from auth.talentech.io/connect/token (client credentials). Endpoints GET /v1/Employees (HasResigned, nationalIds, externalSystemIdentifiers), /v1/Positions (organizationInformation.legalEntityId, collectiveAgreement), /v1/Contracts (contractType, startDate, endDate, indefinite, weeklyHours, fullTimeEmployment, isForFuture), /v1/Salaries (amount, currency, effectiveDate; paged), /v1/EmployeeResignApplications (resignationDate, lastDayOfWork, employmentEndDate) and /v1/LegalEntities. Write-back through PUT /v1/Employees/{employeeId}/externalSystemIdentifiers.
- Scopes include peoplecore-employees:read and :write, peoplecore-positions:read, peoplecore-contracts:read, peoplecore-salaries:read, peoplecore-resignations:read and peoplecore-organization:read.
- Nmbrs is written through the Nmbrs REST API with OAuth 2.0 and an employer-level login. The SOAP API stops on 1 March 2027.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Talentech | Field in Nmbrs | Notes |
|---|---|---|
Medewerker-id en externe kenmerken | Personeelsnummer | Nmbrs number back as external identifier |
Persoonsgegevens (voornaam, achternaam, geboortedatum, geslacht) | Persoonsgegevens | |
Privéadres | Adres | |
Nationaal id met land NL | BSN | |
Juridische entiteit van de positie | Nmbrs-bedrijf | Through a lookup table |
Contract (contractType, startDate, endDate, indefinite) | Dienstverband en contract | |
weeklyHours | Rooster en uren per week | |
Salaris (amount, currency, effectiveDate) | Salaris met ingangsperiode | |
Ontslag (employmentEndDate) | Datum uit dienst |
Related
Recruitee → Talentech
Recruitee to Talentech integration: hired candidates with a contract on a position in Talentech
Talentech → Active Directory
Talentech to Active Directory integration: accounts in your own domain from PeopleCore
Talentech → ADP iHCM
Talentech to ADP iHCM integration: salaries and resignations from PeopleCore to Dutch ADP payroll
Talentech → AFAS Profit
Talentech to AFAS integration: employees, contracts and salaries from Talentech PeopleCore in AFAS