Payroll integration
Dayforce to PayFit integration: French new hires and leave from Dayforce in PayFit
An integration between Dayforce and PayFit turns a new employee at a French location in Dayforce into a collaborator with a basic contract in PayFit, and passes approved leave from Dayforce on as absence in PayFit. The PayFit API cannot update a running contract, so KoppelHet reports later pay or job changes in Dayforce to payroll as a task.
What the integration does
Organisations that use Dayforce as their HR system and run French payroll in PayFit enter French new hires twice. Leave already approved in Dayforce only reaches payroll as a list at the end of the month, who then enters it in PayFit.
- KoppelHet gets an API user in Dayforce with a role that may only see the fields for PayFit.
- Every hour KoppelHet requests employees with a hire date in the past period and a work assignment at a French location.
- KoppelHet creates the collaborator in PayFit and then the basic contract.
- The payroll administrator completes working time, health insurance and other contract details in PayFit.
- Approved leave from Dayforce goes to PayFit as absence; a changed request becomes cancel and create again.
What to watch for with Dayforce and PayFit
- Dayforce can filter employees on a hire date with start and end. KoppelHet uses that filter to fetch only new French employees, because PayFit only supports creation through the API and does not update an existing employee.
- Dayforce returns data as it applies today by default. KoppelHet reads a French hire for next month with a context date on the start date, so the job and address of that moment go on the PayFit contract and not an older state.
- A field only comes out of Dayforce if the API user's role has rights to it. PayFit requires a personal email address and a full address; if either is missing, KoppelHet first checks the role instead of creating an incomplete collaborator.
- Dayforce holds employees from all countries of the organisation. PayFit can only create a contract through the API for French companies. KoppelHet therefore selects on a work assignment with a French location, and reports an employee of another entity to payroll.
- PayFit advises against creating several contracts for one collaborator at the start. If a French employee in Dayforce is moved to another position shortly after hire, KoppelHet does not create a second contract but reports the change to payroll.
- PayFit sets absences from the API straight to approved, and rejects an absence that overlaps an existing one. KoppelHet only sends leave that is approved in Dayforce and first cancels the old absence when a request is changed in Dayforce.
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
Doesn't Dayforce run French payroll itself?
This integration is for organisations that use Dayforce for HR and keep French payroll in PayFit. Which countries Dayforce pays itself is separate from this page.
Can KoppelHet write pay changes to PayFit?
Not through the public API. KoppelHet reports the change with the effective date from Dayforce to payroll.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Dayforce through the REST API on /api/{clientName}/v1/Employees with FilterHireStartDate and FilterHireEndDate for new employees, FilterUpdatedStartDate and FilterUpdatedEndDate with filterUpdatedEntities for changes, expand for Addresses, Contacts, WorkAssignments and EmploymentStatuses, and contextDate for the state on the start date. Fields only with field-level access in the role.
- PayFit through partner-api.payfit.com with the customer's API key - POST collaborators, POST contracts (France only, available after two to five minutes), POST absences and DELETE absence (scope time:write). companyId through the introspect call on oauth.payfit.com.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Dayforce | Field in PayFit | Notes |
|---|---|---|
XRefCode | Bewaard naast het PayFit collaborator-ID | Key for leave and notifications |
FirstName, LastName | firstName, lastName | |
Contacts (privé-e-mail) | personalEmail | Required in PayFit |
Addresses (thuisadres) | personalAddress | |
WorkAssignments (Position, Job) | jobTitle (contract) | |
EmploymentStatuses (startdatum) | startDate (contract) | |
Verlofsoort (Time Away From Work) | absence type, bijvoorbeeld fr_conges_payes | Lookup table |
Related
Ashby → Dayforce
Ashby to Dayforce integration: have Dayforce validate the hire first, then save it
Bullhorn → Dayforce
Bullhorn to Dayforce integration: first placement of an employee as an employee in Dayforce
Carerix → Dayforce
Carerix to Dayforce integration: successful placement as a validated new employee in Dayforce
Dayforce → 4PS Construct
Dayforce to 4PS Construct integration: technicians and site managers from Dayforce in 4PS, with cost centre and end date