Loket integrations

Loket integrations

→

Workday → Loket

Workday to Loket integration: Workday changes straight into payroll

→

Loket → Active Directory

Loket to Active Directory integration: domain accounts per employer from Loket

→

Loket → Microsoft Entra ID

Loket to Entra ID integration: Microsoft accounts from payroll

→

HiBob → Loket

HiBob to Loket integration: new hires and pay changes ready for the payroll run

→

Personio → Loket

Personio to Loket integration: employees, hours and pay components to payroll

→

SAP SuccessFactors → Loket

SuccessFactors to Loket integration: Employee Central as the source for Dutch payroll

Systems you can connect Loket with

How KoppelHet connects to Loket

Loket REST API for employers, employees, employments and pay components.

Authentication: OAuth 2.0 (code flow)

Objects we connect

• Employees and employments
• Pay components and variable changes

What a Loket integration does

• Workday → to Loket

  Workday changes as employee and employment

  New hires and changes from Workday are created as employee and employment under the right employer in Loket.

  Workday → Loket integrationPayroll integration

• Dyflexis, Quinyx → to Loket

  Variable pay components per period

  Hours, allowances and expenses from a scheduling or expense system go to Loket as variable changes, per employee and period.

  Dyflexis → Loket integrationQuinyx → Loket integrationLeave, absence and time

• Loket ↔ and Daywize

  HR file in Daywize, payroll in Loket

  Changes HR makes in Daywize go to Loket; new employers and employees from Loket are imported into Daywize.

  Daywize integrations

• Loket → to Microsoft Entra ID

  Loket as the source for accounts

  Employees and employments from Loket determine the account in Entra ID. The end date of the employment blocks it.

  Loket → Microsoft Entra ID integrationIdentity and access management

What to watch for

• Loket works with employers within an environment. With multiple entities we determine the right employer per employee.

In your IT landscape

• Runs as a managed integration on the KoppelHet platform, next to your existing integration layer. No VPN into your network.
• Only the fields in the design you approve are transferred. The platform keeps no register of its own.
• Tested first in the test or acceptance environment where there is one. You choose the go-live moment.
• ISO 27001 certified, hosted in Amsterdam. When the contract ends you receive the configuration and the audit logs.

Implementation, architecture and compliance

Processes with this system

• Payroll integration
• Identity and access management
• Payroll to finance
• Absence reporting (SIVI)
• Recruitment to HR
• HR to ITSM
• Accounts in applications
• Leave, absence and time
• Training and certificates
• HR data to BI
• HR to ERP
• Lease and mobility

Topics that involve Loket

• HR as the source
• Global HR, Dutch payroll
• Outsourced payroll
• Effective dates and retroactive changes
• Pay components
• Multiple employers and employments
• Hired candidate to HR
• Multiple employers and countries
• Hours and allowances to payroll
• Corrections after closing
• Leave balances and absence
• Project administration and hours

Customer case

Simplicate

Software

KoppelHet builds and runs the integrations with Nmbrs and Loket for Simplicate users. Leave and absence from Simplicate's HRM module flow to payroll; for Loket, employee data goes along as well.

Read the customer story

Articles about Loket

• Hours corrected after payroll close: how not to pay them twice
• Mapping hour types to pay components in your payroll system
• Retroactive pay rises: how they reach payroll correctly
• Which Dutch payroll data does a global HR system lack?