Payroll integration
Infor HCM to AFAS integration: personnel messages from Infor ION as employee and contract in AFAS Profit
An integration between Infor HCM and AFAS Profit receives the personnel message Infor Global HR sends through Infor ION, and puts new Dutch employees and changes from it into AFAS as employee and contract. Data Infor does not include in that message, such as schedule or cost centre, comes from a separate source or is added by payroll in AFAS.
What the integration does
Organisations that run HR in Infor Global HR or CloudSuite HCM and Dutch payroll in AFAS enter new employees twice. Departments, jobs and schedules are coded differently in both systems, and differences only surface at the payroll run.
- HR records a Dutch employee or change in Infor HCM.
- Infor ION sends the personnel message through a document flow to KoppelHet's connection point.
- KoppelHet translates the Infor codes with the code lists and looks up the employee in AFAS.
- A new employee starts the onboarding process in AFAS; a change updates contract, job or salary.
- Payroll adds schedule, payroll tax credit and collective agreement grading in AFAS where Infor does not provide them.
What to watch for with Infor HCM and AFAS Profit
- Infor HR Talent and Global HR publish employees as a Sync.Personnel message and code lists as Sync.CodeDefinitions, each in its own document flow in ION. KoppelHet subscribes to both, so a new job code in Infor also reaches the lookup table to AFAS.
- Infor describes for Global HR and Expense Management that position, cost centre, work schedule and title are not sent in a message; they are manual master data there. For AFAS we therefore agree in advance where schedule and cost centre come from.
- An external system receives ION messages through an IMS connection point. When that runs through the ION API, the API handles authentication with a Backend Service app; KoppelHet therefore only gets the messages from the document flow and no wider access to Infor.
- Infor HR Talent no longer supports the older Legacy BODs; the standard BODs replace them. An existing integration to AFAS on Legacy BODs is therefore rebuilt on Sync.Personnel.
- AFAS keeps person and employment separate. KoppelHet therefore splits the Infor message into a person part and a contract part, and for a new employee starts the onboarding process in AFAS instead of creating the employee directly.
- At Infor, Global HR is the system where employees originate. An employee who only exists in AFAS is not created back in Infor by KoppelHet; that employee goes on the difference list for HR.
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
Does Infor have to build anything new for this integration?
No. Sync.Personnel and Sync.CodeDefinitions are standard messages. In ION Desk a connection point and a document flow to KoppelHet are added.
Where does the schedule come from if Infor does not send it?
We agree that per organisation - a scheduling system, an extract from Infor or entry by payroll in AFAS. The smallest working setup is entry in AFAS; an extra source can follow later as an extension.
Does anything go back to Infor?
No, the integration only listens. Payslips stay in AFAS.
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 - an IMS connection point through the ION API (Backend Service app with client ID) and active document flows for Sync.Personnel and Sync.CodeDefinitions. Infor describes the elements of each message in Global HR and Talent Management Outbound BOD Mapping and Descriptions. The ION API Gateway applies throttling per tenant; an initial load goes in parts.
- To AFAS Profit through the UpdateConnectors HrOnboarding (new employee), KnPerson and KnEmployee (AfasContract, AfasOrguniFunction, AfasSalary).
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Infor HCM | Field in AFAS Profit | Notes |
|---|---|---|
Personeelsnummer Infor | Extra veld bij de medewerker in AFAS | Element names are in Infor's BOD mapping documentation |
Naam | KnPerson (voornaam, voorvoegsel, achternaam) | |
Geboortedatum en adres | KnPerson | |
Datum in dienst | AfasContract (begindatum) | |
Functiecode | AfasOrguniFunction (functie) | Through the code list and a lookup table |
Afdeling | AfasOrguniFunction (organisatorische eenheid) | |
Datum uit dienst | Einddatum dienstverband |
Related
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
Infor HCM → Visma Raet YouForce
Infor HCM to YouForce integration: personnel messages from Infor ION as requests in YouForce
ADP Workforce Now → AFAS Profit
ADP Workforce Now to AFAS integration: Dutch employees from the US HR system in AFAS Profit