Payroll integration
AlexisHR (Simployer One) to AFAS integration: the Dutch entity in AFAS Profit Payroll
With an integration between AlexisHR, now Simployer One, and AFAS Profit, employees of the Dutch company in AlexisHR reach AFAS automatically, with employment, work week, salary and IBAN. HR works for every country in AlexisHR; Dutch payroll runs in AFAS with the same data.
What the integration does
Organisations from Scandinavia that use AlexisHR and run payroll for a Dutch entity in AFAS Profit now retype new employees or send an export. Because AlexisHR is set up for Swedish and Norwegian payroll, not every field fits AFAS as it is.
- HR records an employee at the Dutch company in AlexisHR, with employment, work week and salary.
- Every hour KoppelHet reads the employees and employments changed since the previous round.
- In AFAS the onboarding process starts with the data from AlexisHR; HR completes the Dutch parts.
- New work weeks and salary entries go to schedule and salary in AFAS with their effective date.
- An end date of the employment becomes the end date in AFAS.
What to watch for with AlexisHR and AFAS Profit
- One AlexisHR account can hold several companies, each with its own organisation number. KoppelHet only takes employees and employments with the companyId of the Dutch company to the employer in AFAS.
- The personal identity number in AlexisHR has a country code. Only a number with country code NL goes to AFAS as BSN; a Swedish or Norwegian number of someone coming to work in the Netherlands is left out by KoppelHet and reported.
- AlexisHR has a tax table and column on the employee. That is Swedish payroll tax data; it does not go to AFAS. HR records the payroll tax credit in AFAS during onboarding.
- Work weeks in AlexisHR have an effective date and per day a flag whether it is a working day, with a duration. KoppelHet turns that into an AFAS schedule with hours and working days, from the same date.
- A salary entry in AlexisHR has a payout period, from hourly to annual. Only a monthly entry goes to AFAS as monthly salary; an hourly wage goes as an hourly wage, and other periods are reported to payroll by KoppelHet.
- Employment types in AlexisHR can have a maximum duration in months. KoppelHet uses that to create a fixed-term contract with an end date in AFAS instead of a permanent one.
- AlexisHR tokens have owner permissions on the whole account and the public API describes no webhooks. KoppelHet only uses the token to read and queries every hour with a filter on the update date.
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
Is AlexisHR the same as Simployer One?
Yes. AlexisHR is now called Simployer One. The API is the same and still runs on the AlexisHR domain; the documentation is at Simployer.
Why not immediately on every change?
AlexisHR's public API describes no webhooks. A round every hour is in good time for payroll; before the run KoppelHet compares everything once more.
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) with an access token in the Authorization header - GET /company, /employee (with select and relations), /employment, /employment-type, /work-week, /compensation, with filters such as filters[updated][$gte]. Sandbox at api.sandbox.alexishr.com.
- AFAS through the HrOnboarding and KnEmployee UpdateConnectors (AfasContract, AfasTimeTable, AfasSalary, AfasBankInfo), under a dedicated app connector.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in AlexisHR | Field in AFAS Profit | Notes |
|---|---|---|
id (employee) | Vrij veld bij de medewerker | Key |
companyId | Werkgever | Only the Dutch company |
firstName, lastName, birthDate, homeAddress | KnPerson | |
ssn met ssnCountry NL | BSN | |
Employment (startDate, typeId) | AfasContract | |
Work week (effectiveFrom, dagen met working en duration) | AfasTimeTable | |
Compensation (amount, currency, payoutPeriod, effectiveDate) | AfasSalary | |
bankAccount.iban | AfasBankInfo | |
Employment endDate | Datum uit dienst |
Related
AlexisHR → Active Directory
AlexisHR to Active Directory integration: accounts in your own domain from Simployer One
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
AlexisHR → Loket
AlexisHR to Loket integration: employees of the Dutch company from AlexisHR into payroll