HR to ERP
Factorial to AllSolutions integration: employees per legal entity with their main cost centre in AllSolutions
With an integration between Factorial and AllSolutions, every employee of a Dutch legal entity in Factorial automatically reaches that entity's AllSolutions company, with work email, start date and the cost centre they spend most of their time on. A termination in Factorial becomes an end date in AllSolutions on the contract end, and a reversed termination removes that date again.
What the integration does
Organisations that run HR in Factorial and projects, hours and invoicing in AllSolutions put new colleagues into AllSolutions by hand and keep cost centres in two systems. When someone moves to another entity or cost centre, AllSolutions lags behind.
- HR records an employee in Factorial at a Dutch legal entity, with one or more cost centres.
- Factorial reports it; KoppelHet switches to the entity's AllSolutions company and creates or updates the employee.
- The cost centre with the highest percentage on that day goes along; an equal split becomes an alert.
- On a termination KoppelHet sets the contract end as the end date.
What to watch for with Factorial and AllSolutions
- Factorial splits an employee across cost centres with a percentage and a start and end date per row. One cost centre fits on the employee in AllSolutions. KoppelHet picks the row with the highest percentage on each day, and reports an exact fifty-fifty split to finance instead of guessing.
- A cost centre in Factorial belongs to a legal entity and has an optional code. AllSolutions looks up a cost centre by code and refuses an unknown one with the same message as the screen. A Factorial cost centre without a code therefore becomes an alert, and KoppelHet does not invent a code.
- On a departure Factorial has the contract end and, separately, the date on which access to Factorial stops. For AllSolutions the contract end counts, because hours are booked on projects until that day. A leaver keeps their hours, and AllSolutions deletes nothing.
- Factorial has its own webhook for reversing a termination. When it arrives, KoppelHet clears the end date in AllSolutions again, so the project manager can keep scheduling the employee.
- An employee can move to another legal entity in Factorial with an effective date, and belongs to the old one until then. The AllSolutions integration account switches per company. On that date KoppelHet sets an end date in the old company and creates the employee in the new one.
- In Factorial every employee has a number the organisation chooses itself, next to the internal ID. AllSolutions has an employee number and free fields with their own label. KoppelHet puts the own number in the employee number and the internal ID in a free field, so a corrected number does not break the link.
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 KoppelHet create new cost centres in AllSolutions?
Not in the first version. An unknown cost centre becomes an alert to finance. Creating cost centres from Factorial can be added later as an extension, if that screen is exposed in AllSolutions.
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 in the path) with OAuth 2.0: employees with legal_entity_id, company_identifier, email and terminated_on; GET /resources/finance/cost_centers (id, name, optional code, legal_entity_id, status, deactivation_date); GET /resources/finance/cost_center_memberships (employee_id, cost_center_id, start_date, end_date, percentage); employee updates 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.
- AllSolutions through the REST API: POST /api/v1/Login and the token, with RefreshToken after the fixed validity expires. POST on the employee screen with the same checks as the form, PUT /api/v1/{browser}/{RecordID} with only changed fields. Switching company with GET /api/v1/mwzbdr and afdelingWijzig. Free fields with their own REST API label.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Factorial | Field in AllSolutions | Notes |
|---|---|---|
company_identifier | Personeelsnummer | |
id (Factorial) | Vrij veld met REST API-label | Fixed key |
first_name, last_name | Naam | |
email | E-mailadres | |
legal_entity_id | AllSolutions-bedrijf (inlogbedrijf) | Through a table |
cost_center_memberships (hoogste percentage) | Kostenplaats | Through the cost centre code |
contract_end_date | Datum uit dienst |
Related
Factorial → 4PS Construct
Factorial to 4PS Construct integration: fitters and site managers with their cost centre as a dimension in 4PS
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