Payroll integration
Talentech to Loket integration: contracts, hours and salary from Talentech PeopleCore in Loket
With an integration between Talentech and Loket, a contract in Talentech PeopleCore becomes an employment in Loket, with duration, hours per week and salary from the effective date. If a fixed-term contract is followed by a permanent one, the employment in Loket continues and gets the date on which it became indefinite.
What the integration does
Organisations that use Talentech for HR in Scandinavia and the Netherlands and run Dutch payroll in Loket keep contracts twice. A fixed-term contract that becomes permanent or a change in hours often reaches Loket late or as a new employment, with consequences for contributions.
- Every night KoppelHet reads contracts and salaries of employees with a position at the Dutch entity and compares them with the previous state.
- A first contract becomes a concept employee in Loket; the Loket employment is written back as an identifier on the contract in Talentech.
- The payroll bureau completes collective agreement, payroll tax credit and pension and converts the concept.
- A follow-up contract, a change in hours or a new salary updates the existing employment from the effective date.
- A resignation in Talentech ends the employment on the employment end date.
What to watch for with Talentech and Loket
- Talentech allows external identifiers not only on an employee but also on each contract. KoppelHet writes the ID of the Loket employment back onto the contract. That way it is always clear which contract belongs to which employment, even if someone gets a second employment after a break.
- In Talentech a fixed-term contract is followed by a new contract with the indefinite flag. In Loket that is not a new employment: the existing one continues and gets the date on which it became indefinite. KoppelHet recognises that succession, so payroll does not have to clean up a second employment.
- A contract in Talentech has a sign date. Loket records per employment whether there is a written employment contract, which counts for the unemployment insurance contribution. KoppelHet sets that field to yes once the contract has a sign date, and otherwise leaves it empty for the payroll bureau.
- Talentech gives the hours per week and a calculated part-time factor per contract. Loket determines full-time hours through the administration's shift and records deviating hours per week separately. KoppelHet picks the shift that matches the full-time hours and sets the contract hours as deviating hours, so the part-time factor in Loket comes out the same.
- Contracts in Talentech can only be requested by employee or position, without a filter on change date. KoppelHet therefore keeps the previous state and compares the Dutch entity's contracts every night; only what is really different goes to Loket.
- A contract in Talentech also contains a salary amount, but without an effective date; the salary history does have a date per amount. KoppelHet takes the pay for Loket from that history, so a rise as of the first of next month also starts in that period.
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
How do we get access to the Talentech API?
Through your account manager at Talentech. According to Talentech some APIs may carry extra costs; check this beforehand.
Does absence from Talentech go to Loket too?
Not in the first version. Absence from Talentech to Loket can be added later as an extension.
What if the salary is in kronor?
Then it does not go through and HR gets an alert. For Loket the amount must be recorded in euro.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Talentech PeopleCore API (https://api.talentech.io/peoplecore) with client credentials and scopes per API. GET /v1/Contracts (filter positionId or employeeId; contractType, startDate, endDate, indefinite, signDate, probationEndDate, weeklyHours, fullTimeEmployment, isForFuture, salary), PUT /v1/Contracts/{id}/ExternalSystemIdentifiers, GET /v1/Salaries (paged; amount, currency, effectiveDate), GET /v1/Positions, GET /v1/LegalEntities and GET /v1/EmployeeResignApplications.
- Loket through the REST API with OAuth - POST conceptemployees (employmentDurationType, startDateContractOfIndefiniteDuration, writtenEmploymentContract, commissionUntilDate), workinghours (shift, deviatingHoursPerWeek), wages and PATCH terminate.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Talentech | Field in Loket | Notes |
|---|---|---|
Contract id | Dienstverband | Loket ID written back as external identifier on the contract |
Position, legal entity | Werkgever | |
contractType, indefinite, endDate | Looptijd en einddatum contract | |
signDate | Schriftelijke arbeidsovereenkomst (ja of nee) | |
weeklyHours, fullTimeEmployment | Arbeidstijd (rooster en afwijkende uren per week) | |
Salaries (amount, currency, effectiveDate) | Bruto loon met begindatum | |
Resign application (employmentEndDate) | Einde dienstverband |
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