HR to ERP
Loket to 4PS Construct integration: employees per employer as employees in the right 4PS company
With an integration between Loket and 4PS Construct, every new employee from Loket becomes an employee in the 4PS company of their employer, with their name as on the payslip, department and start date. An end date of the employment in Loket ends the employee in 4PS on time, so no hours are booked on them after they leave.
What the integration does
Organisations that have payroll processed in Loket, often through an accounting firm and with several employers, and run projects, hours and finance in 4PS Construct enter new employees into 4PS by hand. That often only happens once someone cannot book hours, and departed employees stay in the lists for months.
- The accounting firm records the new employee and the employment in Loket, as today.
- KoppelHet retrieves the changes per employer and skips employees that are still a draft.
- The employee then appears as an employee in the 4PS company of their employer, with department and start date.
- A new department or name change in Loket updates the employee in 4PS.
- The end date of the employment goes to 4PS, and after that date the employee is set to terminated.
What to watch for with Loket and 4PS Construct
- Loket works with several employers within one environment, and 4PS often with one company per business. KoppelHet retrieves changes per employer and maps each employer to a fixed 4PS company, so an employee of one employer does not end up in the books of another.
- The employee number in Loket belongs to the employer. If two employers share one 4PS company, the same number can occur twice. KoppelHet then adds a fixed prefix per employer.
- Loket keeps the employee's own name and the partner's name separately, plus the name the employee wants to use. 4PS receives that name as the display name, so a site manager in 4PS sees the same name as on the payslip.
- Loket can only report changes by email, not to another application. KoppelHet therefore asks at a fixed interval per employer what has changed since the last time.
- An employee who is still a draft in Loket has not been hired definitively. KoppelHet only puts them in 4PS once they are final, so 4PS does not hold employees who never started.
- Access to Loket runs through consent from a Loket user, not a separate application password. If the accounting firm works in your Loket environment, a fixed user gives that consent; if that user lapses, the platform reports that the integration has stopped.
- Departments from Loket arrive in 4PS as a dimension value, managed by finance in 4PS. A new department in Loket without a counterpart in 4PS shows as a message in the platform; the employee still arrives.
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
Our accounting firm works in Loket. Does it notice the integration?
Hardly. It gives consent once with a fixed user and then works as usual. New employees appear in 4PS automatically.
Do salary or BSN go to 4PS?
No. 4PS only receives what is needed for hours and projects. Cost rates per employee are set by finance in 4PS.
Can the hours from 4PS go back to Loket?
Not in this integration. Hours and allowances as variable changes to Loket can be added 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.
- Loket is read through the Loket REST API with OAuth (authorization code flow with refresh token), per employer through the changes on employee and employment. Fields include employeeNumber, firstName, prefix, lastName, prefixPartner, lastNamePartner, formattedName, organisational unit and start and end date of the employment. Event notifications in Loket only go to email recipients.
- 4PS is written through the Business Central API v2.0 per company - employees (number, displayName, givenName, middleName, surname, email, mobilePhone, employmentDate, terminationDate, status) and defaultDimensions. dimensionValues is read-only.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Loket | Field in 4PS Construct | Notes |
|---|---|---|
Werkgever | Company in 4PS | Fixed mapping per employer |
employeeNumber | number | With a prefix per employer if several employers share one company |
firstName, prefix, lastName | givenName, middleName, surname | |
formattedName | displayName | Follows the name usage, including the partner's name |
Organisatorische eenheid | defaultDimensions (dimensie afdeling) | Code must exist in 4PS |
Begindatum dienstverband | employmentDate | |
Einddatum dienstverband | terminationDate en status | |
Zakelijk e-mailadres en mobiel nummer | email en mobilePhone |
Related
ADP Workforce Now → Loket
ADP Workforce Now to Loket integration: hires, pay, hours and bonuses from ADP to the Dutch payroll run
AlexisHR → Loket
AlexisHR to Loket integration: employees of the Dutch company from AlexisHR into payroll
BambooHR → Loket
BambooHR to Loket integration: HR changes from BambooHR for Dutch payroll
Bullhorn → Loket
Bullhorn to Loket integration: placement as a concept employee in the right payroll administration