HR to ERP
Factorial to 4PS Construct integration: fitters and site managers with their cost centre as a dimension in 4PS
With an integration between Factorial and 4PS Construct, every employee of a Dutch construction or installation entity in Factorial automatically reaches that entity's 4PS company, with job, work email, start date and their main cost centre as default dimension. The contract end from Factorial becomes the end date in 4PS, and a reversed termination undoes it again.
What the integration does
Organisations with a Dutch construction or installation entity in 4PS Construct and HR in Factorial create fitters and site managers in 4PS by hand and enter their cost centre there again. A move to another cost centre only reaches 4PS once the hours are already booked wrongly.
- At the start we link every Dutch legal entity in Factorial that works with 4PS to a 4PS company.
- Factorial reports an employee; KoppelHet creates or updates them in the company of their entity.
- The cost centre with the highest percentage goes along as default dimension, if that value exists in 4PS.
- On a termination KoppelHet sets the end date, and after the last working day the status to terminated.
What to watch for with Factorial and 4PS Construct
- A cost centre in Factorial belongs to one legal entity. 4PS keeps its own dimension values per company. KoppelHet only puts cost centres of the entity that belongs to that 4PS company on the employee, so a cost centre of a sister company never ends up in the wrong company.
- Factorial can split a fitter across several cost centres, with a percentage per row. A default dimension in 4PS has one value per dimension. KoppelHet takes the row with the highest percentage valid on that day; the rest of the split stays in Factorial and payroll.
- Dimension values are read-only in the Business Central API underneath 4PS. Factorial reports a new cost centre with its own webhook. KoppelHet then immediately prompts finance to create the value in 4PS, even before the first employee lands on that cost centre.
- A cost centre code is optional in Factorial, while a dimension value in 4PS always has a code. KoppelHet only links cost centres with a code. A cost centre without a code becomes an alert to HR, so the dimension in 4PS is not guessed from a name.
- Factorial distinguishes the contract end from the date on which access to Factorial stops. 4PS uses the end date for planning and time registration. KoppelHet therefore takes the contract end as terminationDate, and only sets the status to terminated after that day.
- If HR reverses a termination in Factorial, Factorial sends a separate webhook for it. KoppelHet then clears the end date in 4PS and sets the status back to active, so the fitter stays in the planning.
- If an employee moves to another legal entity in Factorial, it applies from an effective date. For 4PS that means an end date in one company and a new employee in the other, if both entities work with 4PS. KoppelHet only carries out both on the effective date.
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 the split across several cost centres go to 4PS?
No, only the main cost centre. Fitters book hours on projects in 4PS; the split from Factorial remains for payroll and reporting.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Factorial API (version 2026-10-01) with OAuth 2.0: employees with legal_entity_id, company_identifier and email; GET /resources/finance/cost_centers (optional code, legal_entity_id, status, deactivation_date) and /resources/finance/cost_center_memberships (start_date, end_date, percentage); terminations with contract_end_date and terminated_on; legal_entity_changes with effective date. Webhooks for Employee creates, updates, terminates and unterminates and for finance/cost_center create, edit and delete.
- To 4PS through the Business Central API v2.0 per company: employees (POST and PATCH; number, givenName, surname, jobTitle, email, employmentDate, terminationDate, status Active, Inactive or Terminated) and defaultDimensions with parentType Employee (dimensionCode, dimensionValueCode). dimensionValues GET only.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Factorial | Field in 4PS Construct | Notes |
|---|---|---|
company_identifier | number | |
first_name, last_name | givenName en surname | |
email | email | |
Startdatum contract | employmentDate | |
contract_end_date | terminationDate en status | |
cost_center code (hoogste percentage) | defaultDimensions (kostenplaats) | Existing dimension values only |
legal_entity_id | Company in 4PS | Through a table |
Related
Factorial → Active Directory
Factorial to Active Directory integration: domain accounts from Factorial
Factorial → ADP iHCM
Factorial to ADP iHCM integration: contract versions and terminations of the Dutch entity to ADP
Factorial → AFAS Profit
Factorial to AFAS integration: employees and contracts from Factorial in AFAS Profit Payroll
Factorial → AllSolutions
Factorial to AllSolutions integration: employees per legal entity with their main cost centre in AllSolutions