Identity and access management
Factorial to One Identity integration: employees, teams and entities from Factorial in One Identity Manager
With an integration between Factorial and One Identity Manager, all employees from Factorial are in a fixed file every day, with entity, teams, manager, entry date and the date access stops, which One Identity Manager's CSV connector reads. One Identity Manager uses it to assign rights per entity and team, and processes a departure on the day HR chooses in Factorial.
What the integration does
Organisations with One Identity Manager and Factorial as their HR system lack a connector for Factorial. Employees are then loaded from an export, so a departure or move to another entity only reaches One Identity Manager after the next export.
- Factorial gets a company token for KoppelHet and webhook subscriptions on employees and contract versions.
- KoppelHet places a file with fixed columns where the synchronisation server reads.
- The One Identity Manager administrator sets up the CSV connector, with the Factorial ID as key and a multi-value column for teams.
- After each notification from Factorial KoppelHet updates that employee's row.
- A leaver stays in the file with the date access stops, until after the retention period.
What to watch for with Factorial and One Identity
- In its release notes up to February 2026, Starling Connect only lists Workday, SuccessFactors and Oracle Fusion as HR connectors. Factorial has its own apps for Okta and JumpCloud among others, not for One Identity. One Identity Manager's CSV connector is therefore the route, with KoppelHet supplying the file.
- An employee can be in several teams in Factorial. The CSV connector supports a multi-value column with its own delimiter. KoppelHet puts all teams in that column, so One Identity Manager reads one row per employee and can still use each team for rights.
- In Factorial HR records on a termination when access stops, separate from the end of the contract. KoppelHet puts the access date as ExitDate and the contract end in its own column, so you can choose in One Identity Manager which date counts.
- One Identity Manager cannot mark a row that disappears from another system's file as outstanding. Factorial keeps returning a terminated employee with active set to false. KoppelHet keeps that row in the file with ExitDate, so the Person in One Identity Manager is not affected by a missing row.
- Moving a scheduled termination in Factorial is only possible by reverting it and entering it again, and each of those steps sends a notification. KoppelHet only updates the file after the last notification of such a sequence, so One Identity Manager does not see an active employee in the middle of the correction.
- If someone moves to another legal entity, a new contract starts in Factorial on a date, and until that day the employee belongs to the old entity. KoppelHet changes the company column on that date, so One Identity Manager does not grant the new entity's rights earlier.
- Factorial switches a webhook subscription off after twenty failed attempts or 48 hours, and the subscription can be switched on again afterwards. KoppelHet monitors the subscriptions, switches them on again after an outage and rebuilds the whole file from the API every night, so a missed notification does not make it into the next synchronisation.
This integration is also part of joiner, mover, leaver.
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
Which leaving date does One Identity Manager see?
The date access to Factorial stops, with the contract end as an extra column.
Are bank details or salary in the file?
No. Factorial sometimes sends them along in notifications, but KoppelHet does not store them or put them in the file.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- KoppelHet reads Factorial through the Factorial API (version 2026-10-01 in the path): employees with active, is_terminating, terminated_on, legal_entity_id, manager_id and country, contract versions, teams and legal entity changes, plus webhooks for employees (create_with_contract, update, terminate, unterminate) and contract versions. Webhooks without an ID per delivery; up to twenty attempts in 48 hours.
- One Identity Manager reads one file through the CSV connector (UTF-8, header row, text qualifiers, language for dates) with PersonnelNumber as key column and an MVP column with its own delimiter for teams. Synchronisation step with Data import, without MarkAsOutstanding; access directly or through a remote connection server.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Factorial | Field in One Identity | Notes |
|---|---|---|
id | Sleutelkolom PersonnelNumber | |
first_name en last_name | FirstName en LastName | |
email | Kolom werkadres | |
Teams | Kolom teams (meerdere waarden) | |
legal_entity_id | Kolom bedrijf | |
country | Kolom land | |
manager_id | Kolom leidinggevende | |
Startdatum contract | EntryDate | |
terminated_on (einde toegang) | ExitDate |
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