HR to ITSM
Visma Peple Jira Service Management integration: customers per company and requests for a new or ended contract
With an integration between Visma Peple and Jira Service Management, every employee from Peple becomes a customer in Jira Service Management, a member of the organization of their company, and KoppelHet raises an onboarding request for a new contract and an offboarding request for an end date in the IT service desk. After the last working day the integration revokes portal access.
What the integration does
Organisations with several companies in Peple and one IT department in Jira Service Management often cannot see in Jira which company a new colleague is joining. Whoever leaves can still submit requests in the portal for months.
- KoppelHet requests exports of employees, contracts and users in Peple, and fetches the files once they are ready.
- Each company from Peple has an organization in Jira Service Management.
- An employee with a business email becomes a customer and a member of their company's organization.
- A new contract produces an onboarding request; without an email address it is in the manager's name.
- An end date produces an offboarding request; after that day KoppelHet revokes portal access.
What to watch for with Visma Peple and Jira Service Management
- Peple supplies the company each employee works for. KoppelHet creates an organization per company in Jira Service Management, so agents see for each request which board or foundation it is for.
- If a new colleague has no business email yet, they cannot be a customer in Jira yet. The Peple users export does give the manager's email address, so the onboarding request is raised in their name.
- Every Peple export returns a timestamp that KoppelHet passes on with the next request. That way only changes come in, and the two full exports per day remain available for a recovery.
- Which fields a request in Jira asks for depends on the request type. KoppelHet fetches that list and fills in job, org unit and start date from the Peple contract; if a mandatory field is missing, the integration reports it.
- A deleted contract appears in the Peple export as a record with only ids. KoppelHet then adds a comment to the open request in Jira instead of revoking portal access, because the employee often simply stays.
- Only a site administrator can revoke portal access in Jira. KoppelHet does that with a separate technical user and only after the end date of the last running contract in Peple, not when one of several contracts ends.
- Peple has maintenance on Saturday evening and then refuses new exports with a 503. KoppelHet plans no run in that window and otherwise waits for the time given.
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
Can boards have their own service desk in Jira?
Yes. KoppelHet picks the service desk and request type based on the company in Peple.
What if someone has several contracts?
Then it stays one customer. Portal access only closes when the last contract has ended.
Does salary data go to Jira?
No. The integration requests no scopes for salary fields, so they are not in the export.
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 with Visma Connect, per tenant. POST /v1/command/nl/hrm/{employees, contracts, users} and GET /v1/query/nl/hrm/.../{jobId}; incremental with changeTimestampAfter. Fields include businessemailaddress, formattedname, companyid, functionname, orgunitname, manageruserid, startdate, enddate and endreasonname; users export with userid, emailaddress and employeeid.
- Jira Service Management through /rest/servicedeskapi/: POST customer, organization with users, POST request with serviceDeskId, requestTypeId, requestFieldValues and raiseOnBehalfOf, the fields per request type through servicedesk/{serviceDeskId}/requesttype/{requestTypeId}/field, and PUT customer/user/{accountId}/revoke-portal-only-access (204).
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Visma Peple | Field in Jira Service Management | Notes |
|---|---|---|
businessemailaddress | email (customer) | |
formattedname | displayName | |
companyid / companyname | Organization | One organization per company |
manageruserid → users-export emailaddress | raiseOnBehalfOf | When the employee has no email address yet |
startdate, functionname, orgunitname (contract) | requestFieldValues | |
enddate en endreasonname (contract) | Offboardingverzoek en revoke-portal-only-access |
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