Payroll integration
Connect Deel to AFAS Profit: Dutch employees straight to payroll
With an integration between Deel and AFAS Profit, people employed by your own Dutch BV move from Deel into AFAS automatically, with contract, job and department, ready for payroll. Employer of record (EOR) employees and contractors stay out of AFAS, because Deel or the contractor pays them.
What the integration does
Employers that started with Deel as employer of record and now run payroll for their own Dutch entity in AFAS Profit take the data out of Deel by hand. Payroll keeps having to check whether someone works for the entity, through EOR or as a contractor.
- HR adds a new employee in Deel at the Dutch BV.
- KoppelHet notices this straight away and checks whether the person is really employed by your own BV, rather than through EOR or as a contractor.
- The employee then appears in AFAS with personal data, contract, job and department.
- Payroll completes in AFAS what is not in Deel, such as salary, schedule and tax data, possibly through the hiring workflow.
- When HR terminates the contract in Deel, the last working day appears as the end date on the AFAS contract.
What to watch for with Deel and AFAS Profit
- Deel records per person whether someone is a contractor, an EOR employee or an employee of your own entity. Only that last group belongs in AFAS. KoppelHet filters on it, so an EOR employee is not paid twice.
- Someone can have several employments in Deel, at different entities. KoppelHet only looks at the employment with the Dutch BV and ignores the rest.
- When an employee moves from EOR to your own BV, AFAS sees a new hire with a new start date. The EOR period does not belong in AFAS; any seniority arrangements are recorded separately by payroll.
- Deel reports changes to the integration straight away. On top of that KoppelHet compares Deel with AFAS at fixed moments, so a missed notification does not become a missed employee.
- Dutch data such as BSN, payroll tax credit and collective agreement can be recorded in extra fields in Deel. If you do not, payroll fills them in AFAS and the integration does not overwrite them.
- KoppelHet sets the last working day from Deel as the end date in AFAS, with a termination reason agreed per type of termination.
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
What happens to our EOR employees in the Netherlands?
They stay with Deel. Deel is their employer and runs their payroll; AFAS only receives the employees of your own BV.
Can we see contractors in AFAS as well?
Not in payroll. If you want them as a relation in AFAS for accounting, that is a separate flow we agree on separately.
Why are salary and schedule not in AFAS automatically?
That depends on what you record in Deel for your own employees. If the data is there, we include it; otherwise payroll completes it in AFAS.
How do we know the integration misses nothing?
At fixed moments KoppelHet sets the Dutch employees in Deel against the active contracts in AFAS. Differences show up in the KoppelHet platform.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Deel is read through the Deel REST API (HRIS, people list with employments) and webhooks. Deel recommends webhooks as the main route and polling as a supplement; KoppelHet verifies the signature of every webhook.
- Filter on hiring type hris_direct_employee (other values include eor and contractor) and on the client_legal_entity of the Dutch BV.
- Last working day from termination_last_day on the employment. Dutch fields optionally as custom fields in Deel.
- AFAS is written through the KnEmployee UpdateConnector (person, contract, job, organisational unit).
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Deel | Field in AFAS Profit | Notes |
|---|---|---|
id (Deel person) | Vrij veld bij de medewerker | To find the person again later |
first_name | Voornaam (FiNm) | |
last_name | Voorvoegsel (Is) en Achternaam (LaNm) | |
birth_date | Geboortedatum | |
start_date (employment) | Begindatum contract (DaBe) | |
job_title | Functie (FuId) | Through a lookup table |
department | Organisatorische eenheid (DpId) | Through a lookup table |
client_legal_entity | Werkgever in AFAS | Decides whether the person goes to AFAS |
termination_last_day | Einddatum contract (DaEn) |
Related
Ashby → Deel
Ashby to Deel integration: hires at the own entity as direct employee in Deel
Bullhorn → Deel
Bullhorn to Deel integration: first placement as a direct employee with a contract in Deel
Carerix → Deel
Carerix to Deel integration: successful placement as a person or contract in Deel
Deel → 4PS Construct
Deel to 4PS Construct integration: own employees of the construction entity in 4PS, with department and cost centre as dimensions