Lease and mobility
AFAS to Shuttel integration: joiners and leavers from AFAS Profit straight into Shuttel
With an integration between AFAS Profit and Shuttel, every new employee from AFAS appears in Shuttel automatically, under the right employer and in the user group of their scheme, and a leaver is deregistered on the end date of employment. Shuttel already connects with AFAS itself to get travel and working-from-home allowances into payroll; KoppelHet handles the other side, who is in Shuttel.
What the integration does
Employers that offer a Shuttel card already get the allowances into AFAS through Shuttel's own connector. Payroll still adds new colleagues to Shuttel by hand, and an extended temporary contract or a move to another employer in the same AFAS environment often goes wrong.
- HR enters the new employee in AFAS, under the employer they join.
- KoppelHet reads the employee through a dedicated GetConnector and decides the Shuttel group from a free field or from function and organisational unit.
- The employee is in Shuttel with employee number, name, work email, employer and group.
- On a change of function, unit or employer the employee moves to the right group.
- On the end date of employment, with no new contract following on, the employee is deregistered in Shuttel.
What to watch for with AFAS Profit and Shuttel
- Shuttel lists AFAS as one of the payroll systems it connects with to process allowances in payroll. Those allowances come back on the employee number in AFAS. KoppelHet uses the same number as the key in Shuttel, so both integrations concern the same person.
- An AFAS environment can contain several employers, each with its own payroll. If an employee moves to another employer within the group, they move along in Shuttel, so their allowances end up with the new employer in AFAS.
- A renewed temporary contract is a new contract line in AFAS. KoppelHet only deregisters if no contract follows on after the end date, so a renewal does not cause a gap in using the card.
- HR can record the mobility scheme per employee in a free field in AFAS. KoppelHet reads that field and puts the employee in the Shuttel group with the same name. Without a free field we derive the group from function and organisational unit.
- The GetConnector for this integration only contains name, numbers, email, employer, scheme and dates. Salary, citizen service number and home address stay in AFAS, unless the scheme needs the address.
- AFAS can send a webhook at a workflow step. If HR completes the departure workflow for a summary dismissal, KoppelHet deregisters straight away instead of at the next run.
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
Why not just Shuttel's integration with AFAS?
That one is meant to get allowances into payroll. Whether it also registers and deregisters employees is not in Shuttel's public documentation. If it does that for you, this integration is not needed.
Does the home address go to Shuttel as well?
Only if the scheme needs it. By default the address is not in this integration's GetConnector.
What happens with an employee temporarily on zero hours?
As long as the contract in AFAS runs, the employee stays in Shuttel. If HR wants such a person in a different group, that can be done through the free field.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- AFAS Profit is read through the REST API with a dedicated app connector and a GetConnector with only the fields needed, on change date. Authentication with OAuth (client credentials) or classic token; the classic token expires on 31 August 2027. Optionally a webhook on the departure workflow.
- Shuttel publishes no public API documentation; the connection on the Shuttel side is agreed per customer.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in AFAS Profit | Field in Shuttel | Notes |
|---|---|---|
Medewerkernummer | Personeelsnummer | The same key as in Shuttel's allowance integration |
Roepnaam of voornaam | Voornaam | |
Voorvoegsel en achternaam | Achternaam | |
E-mail werk | E-mailadres | For the invitation to the app and Mijn Shuttel |
Werkgever | Werkgever | A separate group or administration in Shuttel per employer |
Vrij veld mobiliteitsregeling | Gebruikersgroep | If HR records the scheme per employee in AFAS |
Functie en organisatorische eenheid | Gebruikersgroep | Through a lookup if there is no free field |
Begindatum contract | Startdatum | |
Datum uit dienst | Afmelden |
Related
ADP Workforce Now → AFAS Profit
ADP Workforce Now to AFAS integration: Dutch employees from the US HR system in AFAS Profit
AFAS Profit → 4PS Construct
AFAS to 4PS Construct integration: payroll journal per employer in the right 4PS company
AFAS Profit → Adobe Creative Cloud
AFAS to Adobe Creative Cloud integration: users and product profiles from AFAS Profit
AFAS Profit → AG5
AFAS to AG5 integration: employees, employments and absence from AFAS Profit in the skills matrix