OIIdentity and access management
Visma Peple to One Identity integration: Peple as the HR source for One Identity Manager through the CSV connector
With an integration between Visma Peple and One Identity Manager, employees, organisational units and contracts from Peple are ready every day in fixed files, which the One Identity Manager CSV connector reads. One Identity Manager uses them to create accounts and rights, and sees a departure or the end of a replacement on the date from Peple.
What the integration does
Organisations that use Visma Peple for HR and One Identity Manager for identity governance often maintain employees with contracts at several units and substitutes by hand.
- In Visma Connect KoppelHet gets a client with only the export scopes for employees, contracts, organisational units and replacements.
- Together we fix the columns and keys of three files, and the folder where One Identity Manager reads them.
- KoppelHet starts the exports in Peple, fetches the files and only writes the new set once everything is in.
- One Identity Manager reads the files in one system connection, read-only, with the departments first.
- Leavers stay in the file with their leaving date until after the agreed period.
What to watch for with Visma Peple and One Identity
- An employee can have contracts at several organisational units in Peple. With duplicate keys in one file the CSV connector picks, depending on the setting, the first, the last, no row or an error. KoppelHet therefore delivers one employee row with the main contract, and all contracts as separate rows in their own file with their own key.
- Organisational units in Peple have a parent unit and their own start and end dates. The CSV connector can read one column as a path in a hierarchy and then loads parent units first. KoppelHet builds that path from the parent units and leaves out closed units.
- Peple has a separate export for replacements, with start and end date. KoppelHet adds a replacement as a row in the contract file with those dates, so One Identity Manager gives a substitute rights on the unit while the replacement runs, even if they have no contract of their own there.
- With a file as source One Identity Manager cannot mark missing persons as outstanding. Peple also only allows two full exports per day per resource. KoppelHet therefore keeps leavers with their end date and maintains the full state itself from incremental exports, with one full check per night.
- On Saturday evening Peple refuses exports for maintenance. KoppelHet only writes a new set once all Peple exports are in, and otherwise leaves the previous set in place, so One Identity Manager never reads a half file and sees employees as gone.
- The CSV connector reads dates according to the language set on the system connection. KoppelHet writes all dates from Peple as year-month-day, so the end of a replacement on 03-04 is not read as 4 March.
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
How is the contract file used in One Identity Manager?
You decide that in the mapping, for example as an extra department membership. Roles per unit can run on that.
Do BSN or private address end up in the files?
No. The integration does not request the scopes for contact and tax data.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Peple through the Visma.net HRM & Payroll Reporting API (Visma Connect client credentials) with scopes for the exports of employees, contracts, organizationunits and employeereplacement (POST command, GET query on jobId); incremental with changeTimestampAfter; two full refreshes per endpoint per tenant per 24 hours; 503 with Retry-After during maintenance. No exportcontactinformation or exporttaxinformation.
- One Identity Manager reads three files in one system connection through the CSV connector (UTF-8, one header row, text delimiters), with a key column per file, Hierarchical sort order on the department path, Uniqueness violation behavior set to Throw error, Read-only access and Data import in the synchronisation step. Access to the files directly or through a remote connection server.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Visma Peple | Field in One Identity | Notes |
|---|---|---|
Personeelsnummer | Sleutelkolom medewerkerbestand (PersonnelNumber) | |
Voornaam en achternaam volgens nameusage | FirstName en LastName | |
businessemailaddress | DefaultEmailAddress | |
functionname en orgunit (hoofdcontract) | Functie en primaire afdeling | |
orgunit met orgunitparentid | Afdelingspad (Hierarchical sort order) | |
Contracten en vervangingen per orgunit | Regel per toewijzing in het contractbestand | |
manageruserid | Personeelsnummer leidinggevende | |
Begin- en einddatum contract of vervanging | EntryDate en ExitDate (JJJJ-MM-DD) |
Related
Visma Peple → Active Directory
Visma Peple to Active Directory integration: accounts from Peple HRM & Payroll
ASVisma Peple → Arbodienst (SIVI)
Visma Peple to occupational health service via SIVI: sick and recovery notifications from Peple to the health service
Visma Peple → Microsoft Entra ID
Visma Peple to Entra ID integration: Microsoft accounts from Peple HRM & Payroll
Visma Peple → Exact Online
Visma Peple to Exact Online integration: cost centres ready in Exact and employee changes on a worklist