Payroll integration
Simployer to Loket integration: employees, pay and bonuses from Simployer One in Loket
With an integration between Simployer and Loket, a new Dutch employee from Simployer One arrives as a concept employee in Loket, and pay and bonuses reach the employment in Loket with their date. Simployer itself has an export to Nmbrs, not to Loket; KoppelHet fills that gap without an export per employee.
What the integration does
Organisations that use Simployer One for HR in the Nordics and the Netherlands, and run Dutch payroll in Loket, currently copy changes by hand. Simployer's standard export goes to Nmbrs, so for Loket it stays retyping, with Nordic address and tax fields that do not fit Loket.
- KoppelHet fetches employees, employments and compensation updated since the previous run, and keeps only employments in the Netherlands.
- A new employee becomes a concept employee at the right employer in Loket, with address, BSN and IBAN.
- The payroll bureau completes collective agreement, payroll tax credit and pension and converts the concept.
- A new salary goes to the pay in Loket with its effective date, a bonus to the period of payout.
- A terminated employment ends the employment in Loket as of the last day.
What to watch for with Simployer and Loket
- Simployer records the payout period with a salary, from hourly to annual. Loket has an hourly wage or a wage per payroll period of the administration, per month, four weeks or week. An hourly wage goes to Loket unchanged as hourly wage; an annual or quarterly amount is converted by KoppelHet to the employer's period.
- A salary in Simployer has a currency, an exchange rate and a base amount. For a Dutch employment Loket expects euros. If the salary is in Swedish or Norwegian kronor, KoppelHet does not pass it on and asks HR to record the amount in euro.
- Bonuses are separate rows in Simployer with an amount and a payout date. In Loket that is a one-off change in the period data. KoppelHet puts the bonus in the period containing the payout date, on the pay code the payroll bureau chooses; if that period has already been processed, it goes to the next open period with an alert.
- The social security number in Simployer comes with a country. Only a number with country Netherlands goes to Loket as BSN, through the resource Loket authorises separately. A Swedish personal number of an employee moving to the Netherlands stays in Simployer; payroll gets an alert that the BSN is missing.
- The home address in Simployer has one street field, without a separate house number. Loket asks for street, house number and addition separately, with at most twenty-four characters for the street and four for the addition. KoppelHet splits the address; if that is ambiguous, the concept goes ahead and KoppelHet flags the address for the payroll bureau.
- The employee number in Simployer is text, while Loket has a numeric employee number and assigns it itself when empty. KoppelHet lets Loket choose the number and keeps the Simployer ID as key, so a number with letters does not block creation.
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
Do the Swedish tax tables from Simployer go along?
No. They do not apply in the Netherlands. Payroll tax credit and other fiscal data are recorded by the payroll bureau in Loket.
Do fixed allowances go along too?
Not in the first version. Additional compensation with a duration can become a fixed pay component in Loket 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.
- Simployer One through the HRM One API (api.alexishr.com/v1) with a bearer access token with owner rights; filters on updated. employee (employeeNumber as text, ssn, ssnCountry, homeAddress with street, postalCode and city, bankAccount with iban and bic, hasOccupationalPension), employment (companyId, country, effectiveEndDate, terminated), compensation (amount, currency, exchangeRate, baseAmount, payoutPeriod HOURLY to ANNUAL, effectiveDate) and bonus-compensation (amount, payoutDate, currency).
- Loket through the REST API with OAuth - POST conceptemployees (address with street at most 24 and houseNumberAddition at most 4 characters, iban without spaces, employeeNumber as integer or empty), PUT citizenservicenumber, wages (grossWageType hourly or periodic), PATCH payrollperioddata for the bonus, PATCH terminate.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Simployer | Field in Loket | Notes |
|---|---|---|
employee.id | Vrij veld in Loket | Fixed key; the Loket employee number is a number |
firstName, lastName | Voornaam, voorvoegsel en achternaam | |
ssn met ssnCountry NL | Burgerservicenummer | |
homeAddress (street, postalCode, city) | Straat, huisnummer, toevoeging, postcode en plaats | |
bankAccount.iban | Betaalgegevens (SEPA) | |
employment.companyId en country NL | Werkgever | |
compensation (amount, payoutPeriod, effectiveDate) | Bruto loon per uur of per periode, met begindatum | |
bonus-compensation (amount, payoutDate) | Periodegegevens in de periode van uitbetaling | |
employment.effectiveEndDate (terminated) | Einde dienstverband |
Related
Recruitee → Simployer
Recruitee to Simployer integration: hired candidates with employment and salary in Simployer One
Simployer → Active Directory
Simployer to Active Directory integration: accounts in your own domain from Simployer
Simployer → ADP iHCM
Simployer to ADP iHCM integration: salary, bonuses and end of employment from Simployer One to ADP iHCM
Simployer → AFAS Profit
Simployer to AFAS integration: Dutch employees from Simployer One in AFAS payroll