Payroll integration
Simployer to AFAS integration: Dutch employees from Simployer One in AFAS payroll
With an integration between Simployer One and AFAS Profit, new employees, contract and salary changes and departures of the Dutch branch reach AFAS automatically from Simployer. KoppelHet calculates the hours per week from Simployer's employment percentage, and every salary line gets the effective date from Simployer in AFAS.
What the integration does
Organisations with a Scandinavian parent that run HR in Simployer One and pay a Dutch branch in AFAS Profit retype new employees and rises. Simployer works in percentages and in Norwegian and Swedish payroll concepts; payroll in the Netherlands translates that into hours and a monthly salary themselves.
- HR records the change in Simployer One.
- KoppelHet fetches the employees and employments updated since the previous run, and keeps only those with the Netherlands as the country.
- The employee reaches AFAS with personal data, BSN, bank account, contract, hours and salary.
- A new salary in Simployer gets the effective date from Simployer in AFAS.
- An end date on the employment becomes the end date of the contract in AFAS.
What to watch for with Simployer and AFAS Profit
- Simployer records an employment as a percentage, and the employment type holds the hours of a full working week. KoppelHet multiplies the two into hours per week for AFAS, so a change in the percentage or in the type both come through.
- A salary in Simployer can be per hour, day, month or year, with its own currency and a salary code. AFAS wants a fixed salary or hourly wage per month. KoppelHet converts annual and daily amounts and sets an hourly amount as hourly wage; a salary in a currency other than euro becomes an alert.
- In Simployer One you can request employees and employments updated after a given moment, but not compensation. KoppelHet therefore compares the compensation of all Dutch employees with the previous state on every run.
- Simployer holds a social security number with the country it belongs to, and a Swedish tax table number. Only a number with the Netherlands as its country goes to AFAS as BSN; the Swedish tax data does not go along.
- An access token for the Simployer One API gets owner rights on the whole account; read-only does not exist. KoppelHet keeps the token in the platform's vault and only uses read calls, and we advise a separate token for this integration.
- Simployer has two HR platforms, each with its own API, Classic and One. This integration assumes Simployer One; if the organisation runs on Classic, we read through the HRConnect API and fields and sign-in differ.
- Simployer records per employee whether there is an occupational pension, as yes or no. Which pension scheme applies in AFAS is decided by payroll; KoppelHet only reports a new Dutch employee for whom Simployer shows no pension.
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
We use Simployer Classic. Is that possible too?
Yes, through Classic's HRConnect API. Sign-in and fields differ; we include that in the design.
What does payroll fill in AFAS itself?
Collective agreement, scale and step, payroll tax credit and the pension scheme. Simployer does not know these Dutch concepts.
Do bonuses go along too?
Not by default. A one-off bonus from Simployer as a pay component in AFAS 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.
- Simployer One through the HRM One API (api.alexishr.com/v1) with an access token as bearer. employee and employment with filters[updated][$gt]; compensation (amount, payoutPeriod HOURLY to ANNUAL, currency, effectiveDate, salaryCode) without an updated filter; employment-type (fullTimeWeeklyHours); employee with ssn, ssnCountry, bankAccount (iban, bic), hasOccupationalPension and tax (table, column).
- AFAS through the KnEmployee UpdateConnector with AfasContract, AfasTimeTable, AfasSalary and AfasBankInfo.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Simployer | Field in AFAS Profit | Notes |
|---|---|---|
employeeNumber | Medewerker (EmId) of vrij veld | |
firstName en lastName | Voornaam, voorvoegsel en achternaam | |
ssn met ssnCountry NL | BSN (SoSe) | |
bankAccount.iban en bic | Bankrekening (AfasBankInfo) | |
employment.startDate | Begindatum contract (DaBe) | |
employment.rate × employmentType.fullTimeWeeklyHours | Aantal uren per week (HrWk) | Calculated by KoppelHet |
compensation.amount, payoutPeriod, effectiveDate | Salaris (EmSa) met ingangsdatum | Converted to a monthly amount for an annual or hourly amount |
departmentId en title | Organisatorische eenheid (DpId) en functie (FuId) | Through a lookup table |
employment.endDate | Einddatum contract (DaEn) |
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
ASSimployer → Arbodienst (SIVI)
Simployer to the occupational health service via SIVI: approved sick leave as absence reports