Payroll integration
Infor HCM to YouForce integration: personnel messages from Infor ION as requests in YouForce
With an integration between Infor HCM and Visma Raet YouForce, every personnel message about a Dutch employee that Infor ION sends becomes a hire or contract change request in YouForce. HR in the Netherlands completes the request with the collective agreement grading; a leaver from Infor reaches payroll as a task.
What the integration does
Organisations that record HR in Infor HCM and process Dutch pay in YouForce have HR in the Netherlands retype every new employee and contract change from Infor. Different codes for departments and jobs between both systems lead to requests that have to be sent back.
- HR records a Dutch employee or change in Infor HCM; ION sends the personnel message.
- KoppelHet receives the message and checks in YouForce whether the person is already known.
- A new person becomes a hire request, a known person a rehire or contract change.
- HR in the Netherlands adds scale and step and completes the request.
- An end date in Infor becomes a task for payroll.
What to watch for with Infor HCM and Visma Raet YouForce
- Infor ION sends the personnel message to every receiver with an active document flow. KoppelHet gets its own flow with only Sync.Personnel and Sync.CodeDefinitions, and ignores messages about employees outside the Dutch entity.
- YouForce requires an existing organisational unit and an existing job profile on a request. KoppelHet uses the code lists Infor publishes through Sync.CodeDefinitions to report a new Infor code straight away when it has no YouForce counterpart yet.
- KoppelHet's connection point in ION is one-way. ION sends messages to KoppelHet, but KoppelHet sends nothing back to Infor, not even a confirmation from YouForce.
- A rehire is the same person in Infor with a new employment. YouForce only finds an existing person by surname at birth, date of birth and a few other personal details; KoppelHet then uses the Infor number in the extension field to stick to the right person.
- YouForce cannot process a message with an end date as a leaver. KoppelHet turns it into a task with the last working day; a change of that date in Infor becomes a new task.
- Every request in YouForce runs asynchronously, and Infor's ION API Gateway applies throttling. For an initial load of all Dutch employees, KoppelHet spreads the work over several rounds, so neither system rejects requests.
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
Is a new employee from Infor in YouForce straight away?
As a request yes, as an employee only after HR in the Netherlands has completed it.
What if an Infor department does not exist in YouForce?
KoppelHet then holds the request and reports the code to HR, who adds it to the lookup table. The request then goes ahead.
Do employees from other countries go to YouForce as well?
No. KoppelHet only processes messages about the Dutch entity; which Infor organisation that is, is recorded at the start.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Infor HCM through Infor ION - IMS connection point through the ION API without an IMS endpoint on the application side (one-way), Backend Service app with client ID, document flows for Sync.Personnel and Sync.CodeDefinitions.
- YouForce through the Recruitment API (persons/search, hires, persons/{personId}/contracts, Adjustments with effectiveDate; 202 and a status check until hrssWorkflowStatus.isActive is false) and the Extensions API for the Infor number. No termination endpoint.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Infor HCM | Field in Visma Raet YouForce | Notes |
|---|---|---|
Personeelsnummer Infor | Extensieveld op de persoon in YouForce | Fixed key for later messages |
Achternaam en geboortedatum | persons/search (lastNameAtBirth, birthDate) | |
Datum in dienst | hireDate | |
Afdelingscode | organizationUnit | Through the Infor code list and a lookup table |
Functiecode | jobProfile | |
Uren | amountOfHours | |
Datum uit dienst | Taak met laatste werkdag |
Related
Infor HCM → AFAS Profit
Infor HCM to AFAS integration: personnel messages from Infor ION as employee and contract in AFAS Profit
Infor HCM → Nmbrs
Infor HCM to Nmbrs integration: Dutch employees from Infor ION in Nmbrs
Infor HCM → TOPdesk
Infor HCM TOPdesk integration: persons and onboarding tickets from Infor ION
ADP Workforce Now → Visma Raet YouForce
ADP Workforce Now to YouForce integration: requests for new Dutch hires and contract changes