Dyflexis integrations

Dyflexis integrations

→Dy

Workday → Dyflexis

Workday to Dyflexis integration: workers, positions and contract hours automatically in scheduling

→Dy

AFAS Profit → Dyflexis

AFAS to Dyflexis integration: employees per employer to scheduling, paid hours back as payroll changes

Dy→

Dyflexis → Nmbrs

Dyflexis to Nmbrs integration: locked payroll periods to Nmbrs, employees back to scheduling

→Dy

HiBob → Dyflexis

HiBob to Dyflexis integration: employees and working patterns from Bob automatically in scheduling

→Dy

Personio → Dyflexis

Personio to Dyflexis integration: new employees and contract hours straight into scheduling

→Dy

SAP SuccessFactors → Dyflexis

SAP SuccessFactors to Dyflexis integration: Employee Central employments as contracts in scheduling

Systems you can connect Dyflexis with

How KoppelHet connects to Dyflexis

Dyflexis System to System API (REST, JSON) with endpoints for employees, contracts, offices, payroll hours and attendance. There is also a queue for locked payroll periods.

Authentication: Token van Dyflexis in de Authorization-header, met scopes per onderdeel

Objects we connect

• External employees and their contracts
• Offices and contract types
• Hours per locked payroll period, per wage component
• Attendance registration (clock-in and clock-out)

What a Dyflexis integration does

• Visma Raet YouForce, AFAS Profit → to Dyflexis

  Employees and contract hours ready for scheduling

  New employees and contracts from YouForce or AFAS arrive in Dyflexis as external employees. An administrator links them once to a Dyflexis employee.

  Visma Raet YouForce integrationsAFAS Profit → Dyflexis integrationLeave, absence and time

• Dyflexis → to Nmbrs, Loket, AFAS Profit

  Payroll hours per locked period to payroll

  When the planner locks a payroll period it enters the queue. The integration fetches the hours per wage component and posts them as changes in Nmbrs, Loket or AFAS.

  Dyflexis → Nmbrs integrationDyflexis → Loket integrationAFAS Profit → Dyflexis integrationLeave, absence and time

• Dyflexis → to Visma Raet YouForce, Nmbrs

  Contract change mid-period

  After a contract change the same employee appears several times in the hours, per office and contract type group. The integration combines those lines correctly.

  Visma Raet YouForce integrationsDyflexis → Nmbrs integrationLeave, absence and time

What to watch for

• An employee sent through the API first becomes an external employee. An administrator must link it once to a Dyflexis employee.
• Hours come per combination of office, contract type group and period. After a contract change within the period, the same employee appears more than once.

In your IT landscape

• Runs as a managed integration on the KoppelHet platform, next to your existing integration layer. No VPN into your network.
• Only the fields in the design you approve are transferred. The platform keeps no register of its own.
• Tested first in the test or acceptance environment where there is one. You choose the go-live moment.
• ISO 27001 certified, hosted in Amsterdam. When the contract ends you receive the configuration and the audit logs.

Implementation, architecture and compliance

Processes with this system

• Leave, absence and time

Topics that involve Dyflexis

• Hours and allowances to payroll
• Corrections after closing
• Employees and contract hours to scheduling

Customer case

ROVA

Public services

Employee data flows from Visma Raet YouForce to Dyflexis for scheduling.

Articles about Dyflexis

• Hours corrected after payroll close: how not to pay them twice
• Mapping hour types to pay components in your payroll system