Payroll integration
AlexisHR to Loket integration: employees of the Dutch company from AlexisHR into payroll
With an integration between AlexisHR and Loket, employees of the Dutch company in AlexisHR arrive in Loket as a concept employee, with name and name prefix, BSN, contract duration, work week and salary. A salary change or an end date in AlexisHR then also goes to Loket, so payroll no longer has to wait for lists.
What the integration does
Organisations that use AlexisHR for teams in Scandinavia and the Netherlands and process Dutch payroll in Loket now retype new Dutch employees. AlexisHR is set up for Scandinavian payroll, so name structure, BSN and contract duration have to be adjusted by hand at that step every time.
- HR hires someone at the Dutch company in AlexisHR, with the personal number with country code NL.
- KoppelHet creates a concept employee in Loket at the employer that belongs to that companyId, with the name prefix separate.
- The BSN goes through the concept's own BSN part; payroll completes collective agreement and payroll tax credit.
- A new salary entry or work week in AlexisHR becomes a new record in Loket with the same effective date.
- An end date ends the employment in Loket.
What to watch for with AlexisHR and Loket
- Loket has separate fields for initials, name prefix and last name, and a setting for how the name appears on the payslip. AlexisHR only has first name and last name. KoppelHet takes the prefix out of the last name and puts it in the right field; payroll sees the split in the platform.
- The BSN has its own part of the concept employee in Loket. KoppelHet only fills it with a personal number from AlexisHR with country code NL; a Swedish or Norwegian number of someone moving to the Netherlands never goes in.
- A contract type in AlexisHR can have a maximum duration in months. KoppelHet then sets the employment in Loket as fixed-term with the calculated end date, so payroll sees in Loket when the contract expires.
- A work week in AlexisHR applies to an office or to one employee. KoppelHet takes the personal work week if there is one, otherwise the office's, and sets in Loket whether the pattern is the same every week.
- AlexisHR holds tax table and column on the employee. Those are Swedish payroll tax details; KoppelHet does not send them to Loket, where payroll sets payroll tax credit and table itself.
- A salary entry in AlexisHR has a payout period from hourly to annual. An hourly wage becomes an hourly wage in Loket, a monthly amount a periodic wage; KoppelHet converts other periods to the payroll period of the Loket employer and shows the conversion.
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 this work with an accounting firm that manages Loket?
Yes. The firm gives the integration access to your employer and sees the new concepts with a notification about the name prefix.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- AlexisHR through the HRM One API (api.alexishr.com/v1, bearer access token with owner rights, read only) - /employee (ssn, ssnCountry, bankAccount), /employment (startDate, endDate, effectiveEndDate, terminated), /employment-type (maxMonths), /work-week, /compensation (payoutPeriod) and /company, with filters on updated and companyId. No webhooks in the public documentation.
- Loket through the Loket REST API with OAuth - PostConceptEmployeeByEmployerId (initials, prefix, howToFormatLastName, employmentDurationType, commissionUntilDate), PutCitizenServiceNumberByConceptEmployeeId, PostWorkingHoursByEmploymentId (regularWorkPattern), PostWageByEmploymentId and PatchTerminateByEmploymentId.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in AlexisHR | Field in Loket | Notes |
|---|---|---|
employee.id | Vrij veld bij de werknemer | Fixed key |
firstName en lastName | Voornaam, tussenvoegsel en achternaam | Prefix split off |
ssn met ssnCountry NL | Burgerservicenummer van het concept | |
companyId | Werkgever in Loket | |
employment.startDate en employment-type maxMonths | Begindatum, duur en einddatum dienstverband | |
work-week (working en duration per dag) | Arbeidstijd en werkpatroon | |
compensation (amount, payoutPeriod, effectiveDate) | Loon per periode of per uur | |
bankAccount.iban | IBAN zonder spaties | |
effectiveEndDate of endDate | Einde dienstverband |
Related
AlexisHR → Active Directory
AlexisHR to Active Directory integration: accounts in your own domain from Simployer One
AlexisHR → AFAS Profit
AlexisHR (Simployer One) to AFAS integration: the Dutch entity in AFAS Profit Payroll
AlexisHR → Microsoft Entra ID
AlexisHR to Entra ID integration: users with employee number and groups, blocked on leaving
AlexisHR → Google Workspace
AlexisHR to Google Workspace integration: a Google account that follows the employee, from onboarding to departure