Dayforce logoAFAS Profit logo

Payroll integration

Dayforce to AFAS integration: Dutch employees to local payroll

With an integration between Dayforce and AFAS Profit, the Dutch employees in Dayforce reach AFAS automatically, with contract, job, salary or hourly rate and bank account. Dayforce does not run payroll in the Netherlands itself; this way AFAS becomes the local payroll next to the global HR system, without the controller retyping data.

What the integration does

International employers that use Dayforce for HR but run payroll for their Dutch entity in AFAS Profit have new colleagues retyped into AFAS in the Netherlands. A change in hourly wage or department only shows up when payroll costs do not add up in the monthly check.

  1. HR enters a new Dutch colleague in Dayforce, as for every country.
  2. KoppelHet fetches new and changed employees of the Dutch site, including those who start in a few weeks.
  3. A new employee then appears in AFAS with personal data, contract, job, schedule, salary and bank account.
  4. A new job, department or status in Dayforce arrives in AFAS as a change with the same effective date.
  5. When someone leaves in Dayforce, the AFAS contract ends on that date.
Dayforce → KoppelHet → AFAS ProfitSOURCEDayforceTARGETAFAS ProfitKoppelHetmapping · logging · monitoringDayforce → KoppelHet → AFAS ProfitSOURCEDayforceTARGETAFAS ProfitKoppelHetmapping · logging · monitoring
Out: Employee with personal data and address · Employment status · Job and department · Salary or hourly rate · Bank account

What to watch for with Dayforce and AFAS Profit

  • KoppelHet only asks Dayforce for changes at the entities AFAS uses. That way a new phone number of a colleague elsewhere does not produce an empty change in AFAS.
  • Dayforce runs payroll itself in a limited set of countries, and the Netherlands is not one of them. The integration filters on the Dutch site, so only those employees reach AFAS.
  • In Dayforce an employee cannot be deleted; a hire that falls through remains. KoppelHet looks at the status and only creates an AFAS employee for someone who actually starts.
  • KoppelHet also fetches employees who start later, so payroll sees them in AFAS before the first run.
  • In Dayforce an employee has a fixed salary or an hourly rate. AFAS makes the same distinction, so hours worked by someone on an hourly rate are paid correctly later.
  • In Dayforce net pay can be split over several accounts. AFAS holds one account for net pay per employee; with several accounts we agree which one goes to AFAS.
  • Payroll tax credit, collective agreement and other Dutch tax choices do not exist in Dayforce. Payroll records them in AFAS, and the integration leaves them alone on later changes.

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, architecture and compliance

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.

Price indication · Complex

Leave your work email and you see the price indication right away.

We only use your address to follow up on your question about this integration.

Frequently asked questions

Can Dayforce run Dutch payroll itself?

No, the Netherlands is not among the countries where Dayforce runs payroll itself. That is why a local payroll such as AFAS is needed, plus an integration to get the data there.

Can time data from Dayforce go to AFAS too?

That is a separate flow next to this integration. We look per customer at which hours must be paid in AFAS and in what form.

What if an employee changes country?

A move into the Dutch site is a new hire for AFAS, a move out is a termination. The record in Dayforce stays whole.

Does this work with Nmbrs too?

Yes, we also connect Dayforce with Nmbrs, including for payroll providers with several end clients.

Technical details for IT

For those who want to know how it works under the hood: APIs, fields and sources used.

  • Dayforce is read through the REST API. First the XRefCodes of employees updated within a time window (limited to entities), then the details with expand for WorkAssignments, EmploymentStatuses, Addresses and DirectDeposits.
  • Separate hire date filters for employees with a start date ahead. The XRefCode is the fixed key between both systems.
  • AFAS is written through the KnEmployee UpdateConnector, with AfasContract, AfasSalary (fixed salary or hourly wage) and AfasBankInfo.
  • The Dayforce API user only has read access to the Dutch org unit and the fields in the mapping.

Which fields are transferred

The key fields. The full mapping is agreed per customer.

Field in DayforceField in AFAS ProfitNotes
XRefCodeMedewerker (EmId) of vrij veldFixed key between both systems
Voornaam en achternaamVoornaam (FiNm), voorvoegsel (Is), achternaam (LaNm)
AddressesAdres en woonlandCountry of residence outside the Netherlands also in the tax segment
Datum in dienstBegindatum contract (DaBe)
EmploymentStatusesDienstbetrekking (ViEt)Lookup per status
WorkAssignments (functie)Functie (FuId)Through a lookup table
WorkAssignments (afdeling)Organisatorische eenheid (DpId)Through a lookup table
Salaris of uurtariefSalaris (EmSa) en soort salaris (SaPe)
DirectDepositsIBAN (AfasBankInfo)
Datum uit dienstEinddatum contract (DaEn)

Related

Which systems do you want to connect?

Tell us which systems you use and what should happen automatically. Together we define the smallest working solution, with a clear design and a quote before building.