Tripletex Integration

 

Table of contents

Set up the integration

• Multiple connections
• Required permissions
• 1. Get an employee token from Tripletex
• 2a. Connect Huma to Tripletex
• 2b. Configure integration settings
• 2c. Map absence types
• 3. Sync users and choose how to handle conflicts and missing values
• 4. The connection between Huma and Tripletex is active

Active integration

• How to sync users
• Deactivated or deleted users
• Supported profile fields

FAQ

• Position sync from Huma to Tripletex
• Absence sync between Tripletex and Huma
• Salary sync between Tripletex and Huma

 

 

---

 

Multiple connections

If you need to set up multiple integration instances, follow the guide described here.

If you set up a connection for a group (teams/location/company), Huma will place employees in the first active department.

 

 

 

Required permissions in Tripletex

For the Huma integration to work, the employee token, and therefore the employee who owns it, must have:

• Active «System access»
• Access to «Employee-related accounting reports»
• Full access to: Company information, Employee information and Salary settings

 

 

Absence sync also requires:

• Access to all timesheets (including approval) for the whole company. Remember to check «Timesheets: Whole company» for the API key.

 

 

 

1. Get an employee token from Tripletex

To set up an integration in Huma, you need a «System role with full access to Organization» in Huma.

• If you are unsure which roles are required in Tripletex to complete the setup, contact Tripletex support for guidance.

• You must be logged in to Tripletex and have the right authorization to create an employee token. Contact your Tripletex system administrator if you are missing the necessary permissions.

• If the employee does not have the necessary permissions for the Huma integration when you try to create the token, Tripletex will show an error message and the token will not be created.

• If the employee who owns the token later loses any of these permissions, the token loses them too, and the integration will stop working correctly.

• See Required permissions for details.

 

 

Set up the integration

1. Log in to Tripletex
2. In the left menu, go to «Company > Employees»
3. Open the employee who should own the token
4. Select the «API access» tab
5. Click «New key» under «API user keys»
6. Select «Huma» in the «Application» dropdown
7. Give the key a name
8. Click «Create key»
9. A new API key has been created. Copy the key and store it somewhere safe

 

💡 For more information about tokens/API, see Tripletex (Norwegian only).

 

 

 

2a. Connect Huma to Tripletex

To set up integrations in Huma, the user must have a «System role with full access to Organization».

1. Log in to Huma, go to «Integrations» and select Tripletex
2. Read all the information about the Tripletex integration before you continue:
   • «Overview»
   • «Details»
3. Click «Set up» in the top right corner
4. Give the connection a name and choose who should be part of it (everyone/teams/locations/company)
5. Click «Continue», paste the Tripletex employee token you created, and confirm that you have the necessary authority
6. Click «Continue» and check the settings you want. Read more about the settings in the next step
7. Click «Set up». The connection between the systems is now established

 

 

 

 

 

2b. Configure integration settings

1. Choose whether users added through this integration should have «login access in Tripletex»

2. Enable «Users: Create in Tripletex when added in Huma»

1. 1. If this is disabled, you must do a manual sync when you add a new user in Huma for them to be synced to Tripletex.
   2. If you use the Teamtailor integration or the CV-Video integration, users added to Huma through these will also be added to Tripletex.
   3. Users without a date of birth will be created in Tripletex, but will be inactive. To activate them, add the date of birth in Huma and then sync manually.
   4. Users are added with basic access. If they need more access in Tripletex, an administrator must grant it manually in Tripletex.

1. Enable «Positions: Create, update and delete» when updated in Huma

1. 1. Changes to the supported fields of existing positions in Huma are sent to Tripletex automatically.
   2. Position data is only sent from Huma to Tripletex, not from Tripletex to Huma.

   3. Only positions updated after the integration is activated will be transferred.

1. Enable «Salary: Create, update and delete in Tripletex when updated in Huma» if you want to transfer salary data

1. 1. Only salary created or updated after activation will be transferred.

   2. Salary is only sent from Huma to Tripletex.

1. Enable «Absence: Create, update and delete in Tripletex when updated in Huma» to transfer absence

1. 1. Only approved absence registered as working days is transferred.
   2. Changes or deletions in Huma will also be updated or deleted in Tripletex.

 

Click «Save» to complete the setup.

 

 

 

 

 

2c. Map absence types

If you have chosen to sync absence from Huma to Tripletex, you must map absence types:

1. Go through all absence types
2. Select the corresponding absence type (activity) in Tripletex
3. Exclude types you do not want to transfer

 

🔗 Read more about how absence is handled in integrations in general, and here for Tripletex.

 

 

 

 

3. Sync users and handle conflicts

After you click «Save», you are taken to the connection's main page. To activate the integration, you must «Sync users».

1. Click «Sync users»
2. Matching users: users found in both Huma and Tripletex (same email address in both systems)
   • Click «View users» to see which supported fields do not match or are missing
   • Handle «non-matching» or «missing values»
   • Click «Next»
3. Non-matching users: users that only exist in one of the systems
   • Choose between creating «all/selected users/do not create»
   • Choose how users should be created:
     • Tripletex > Huma: add to Huma
     • Huma > Tripletex: add to Tripletex
4. Click «Sync users». You will receive an email with the result

 

💡 Note

• The error «Period between multiple names» may be caused by hidden formatting in profile fields.
• Tripletex requires a department when a user is created. Huma places employees in the first active department.
• Users who have not filled in the «Required fields» will not be synced.

 

 

 

4. The connection between Huma and Tripletex is active

Changes to supported fields in Huma are automatically updated in Tripletex in real time.

Changes made in Tripletex are not automatically updated in Huma. To bring them in, you must do a manual sync with «Sync users».

 

 

 

 

How to sync users

Use «Sync users» when you have updated one of the supported fields in Tripletex, or when you want to create new users. For user sync to work, the email address must always be the same in both systems.

1. Go to the Tripletex integration in Huma
2. Click «Sync users»
3. Follow the steps. Read more about the steps here

 

💡 Note

• If you have created a user in Huma, you must do a «Manual sync» to create the user in Tripletex through the integration (if «create users automatically» is not enabled).
• If an error occurs during sync, you can find detailed information in the «Error log» on the Tripletex integration page in Huma.

 

 

 

Deactivated or deleted users

When a user is deactivated in Huma:

• The user is not deactivated in Tripletex.
• The user is locked for updates (sync).

 

When a user is deleted in Huma:

• The user is not deleted in Tripletex.
• A manual sync will suggest creating the user again.
• The user cannot be synced if there are changes in Tripletex.

 

 

 

Supported fields: profile fields that are synced

Changes to the supported fields in Huma (listed below) are automatically updated in Tripletex in real time. Changes made in Tripletex, however, must be synced manually to Huma.

Huma field	Tripletex field	Notes
Email address	email	Tripletex does not allow updating the email address for users who have user accounts in Tripletex (access to log in) in addition to their employee records. For these users, editing will make the values in Huma and Tripletex differ, and the users will be disconnected from the integration. Huma requires this value to be unique.
First name	firstName
Last name	lastName
Phone number	phoneNumberMobile	Huma requires this value to be unique.
Bank account number	bankAccountNumber, iban, bic	Must be a valid Norwegian bank account number.
Date of birth* (REQUIRED)	dateOfBirth
Identifications	nationalIdentityNumber, dnumber
Address	address
Employee ID	employeeNumber

 

 

 

Position sync from Huma to Tripletex

📄 Read more about how employee data sync works in integrations in general.

⛓️‍💥 Please note that activating the integration does not transfer historical position data to Tripletex. Only positions created or updated in Huma after the integration is activated will be synced.

💡Position data is only synced from Huma to Tripletex, not from Tripletex to Huma.

 

Supported fields: position data that is synced

These are the position fields synced from Huma to Tripletex:

Huma field	Tripletex field
Contract start date* (REQUIRED)	employments[].startDate
Contract end date	employments[].endDate
End reason	employments[].endReason
Position percentage* (REQUIRED)	employments[].employmentDetails[].percentage
Contract type* (REQUIRED)	employments[].employmentDetails[].employmentType / employmentForm

 

 

Do I need to enable position data sync?

It depends on which positions you are going to create. If you are creating historical positions, position sync should be off while you do it. Historical positions are not meant to be sent to the payroll system and may cause errors in the payroll timeline if transferred automatically. If you are creating current or future positions, position sync should be on before you begin.

To do this:

1. Go to the Tripletex integration page in your Huma account
2. Click the three dots in the top right corner and «Edit connection settings»
3. Confirm legal authority and click «Continue»
4. Then check «Positions: create, update and delete»

 

⚠️ Note

• Positions are only sent from Huma to Tripletex, not from Tripletex to Huma.

• Only positions created or updated after the integration is activated will be transferred to Tripletex.

• Users recently created in Tripletex must first have a «New employment» in the integration. This must be set up manually in Tripletex after the user has been synced.

 

 

Does the integration update position data?

Yes. When supported position fields are changed in Huma, the update is sent to Tripletex automatically.

This applies, for example, when a position is created or when fields such as contract dates, percentage or contract type are changed.

 

In which direction is position data synced?

Position data is only synced one way:

Huma → Tripletex

Changes made directly in Tripletex are not sent back to Huma.

 

How are positions matched between Huma and Tripletex?

Positions are matched based on the contract start date.

If there is an existing position in Tripletex with the same start date as the position being updated in Huma, Huma will update that position in Tripletex with the new values.

If the start date is different, the existing position will not be updated.

This means that when you edit the first position that Huma creates automatically when we launch Employment history, you must either:

• match the start date of the position with the corresponding position in Tripletex, or
• make the changes you want, save, and then click «Create new position».

 

When is position data sent to Tripletex?

Position data is sent to Tripletex when:

• A new position is created in Huma
• An existing position is updated in Huma
• The change happens after the integration is activated

 

Can historical positions be transferred?

To get historical position data registered in Tripletex, this must be done manually, or by updating the position in Huma after the integration is activated.

The integration does not transfer historical position data that existed before the integration was activated.

 

Why isn't all information from the position in Huma sent?

Not all position fields are synced between Huma and Tripletex, because the information stored in the two systems is structured somewhat differently. Some fields only exist in one of the systems, or have a different structure and meaning. In some cases, this is also due to technical limitations in either the Tripletex API or in how data is handled in Huma. Because of these differences, it is not always possible to achieve a full one-to-one transfer of all position fields between the systems.

 

 

 

Absence sync between Tripletex and Huma

🏖️ Read more about how absence works in integrations in general.

⛓️‍💥 Please note that activating the integration or turning on absence sync does not transfer historical absence records to Tripletex. Absence data is only synced to the integration when an absence is approved in Huma. Absence sync only works from Huma to Tripletex.

 

Supported fields: absence fields that are synced

These are the absence fields synced from Huma to Tripletex:

Huma field	Tripletex field
Absence type* (REQUIRED)	activity
Time period* (REQUIRED)	date
Percentage* (REQUIRED)	hours
Notes	comment

 

How do I register absence in Tripletex?

In Tripletex, absence is registered as hours on specific activities. A Tripletex administrator must set up activities for registering absence, in addition to the default activity «Vacation» that comes with Tripletex. Absence types in Huma must be mapped to these activities in the integration settings.

 

Does the integration update absence?

Yes. Huma automatically updates absence in Tripletex when it is changed (created, updated or deleted) in Huma.

 

What triggers updates to timesheets in Tripletex?

Huma automatically creates, updates or deletes timesheet entries in Tripletex based on changes made in Huma.

 

When are absence entries created in Tripletex?

Only when the absence type in Huma is mapped to a Tripletex activity and meets certain conditions, such as the absence having an end date and being approved.

 

When are absence entries updated in Tripletex?

When the date, percentage, note or status of an absence entry in Huma is changed after it has been created in Tripletex. Note that if you remove the end date of an absence, or change the status to anything other than approved, Huma will delete the absence in Tripletex.

 

What happens if a Tripletex mapping is changed?

If you change which Tripletex activity an absence type in Huma is mapped to, all existing absence entries that Huma has already created in Tripletex for this mapping will be disconnected from the absence in Huma and will no longer be updated from Huma. However, if you edit these absences in Tripletex so their activity matches the new mapping, they will receive updates again.

 

When are absence entries not created in Tripletex?

If the absence in Huma does not have an end date, or if the absence request is not approved, Huma will not create an entry in Tripletex.

 

Can historical absence be transferred to Huma?

There is no automatic import or sync of historical absence data from Tripletex to Huma.

Huma can be used as the main system for all new absence registrations going forward. If you want to register historical absence data, this must be done manually in Huma and then approved for it to be synced to Tripletex.

 

How are deletions handled?

If an absence entry is deleted in Huma, Huma will delete the corresponding entry in Tripletex. Huma will also delete an entry in Tripletex if the related absence entry in Huma loses its end date, or if an approved absence is changed to not approved.

 

How does Huma match absence for updates or deletions?

Huma matches absence by employee, type and time period to make sure updates or deletions in Tripletex are correct.

 

How are timesheet entries calculated?

Hours are calculated based on Tripletex's standard working hours, adjusted for the individual employee and the percentage of the absence.

 

How are absence days calculated?

Days are calculated based on the work schedule and public holiday settings in Huma. If a work schedule includes weekends as working days and an absence covers these days, Huma will send the corresponding timesheet entries to Tripletex and ignore the public holiday settings in Tripletex.

 

What happens if Tripletex rejects a request?

Huma changes the status of the entry to «rejected», notifies relevant users and managers, and records the error in the integration's error log.

This is not done, however, if the request only concerns updating the note on an absence. Huma treats this as a minor error that does not put the absence so far out of sync that it needs to be marked as rejected. The error will still appear in the integration's error log, so an administrator can decide whether anything needs to be followed up.

 

Absence is rejected because of missing timesheet access. What should I do?

1. The person who set up the token (API key) must go to «My profile» in Tripletex
2. Click «More» and then «API access»
3. Click the key that is set up between the integration and Huma
4. Scroll down to «Timesheet» and check that the correct access is granted, and that it applies to «the whole company»
5. Then try approving/adding the absence again in Huma

 

For detailed explanations of specific errors, check the integration's error log on the integration page in Huma. The log describes the problems that have occurred.

 

 

 

 

Salary sync between Tripletex and Huma

💰 Please note that activating the integration or turning on salary sync does not transfer historical salary information to Tripletex. Salary data is only synced to the integration when a salary is created or edited in Huma. Salary sync only works from Huma to Tripletex.

 

Supported fields: salary fields that are synced

These are the salary fields synced from Huma to Tripletex:

Huma field	Tripletex field	Notes
From date* (REQUIRED)	date	Huma will create or update the position in Tripletex based on this date.
To date	date	Huma will create or update the position in Tripletex based on this date.
Salary amount	annualSalary, hourlyWage	Annual or monthly amounts are used to calculate the annual salary. Hourly or weekly amounts are calculated as an hourly wage based on the standard hours for the pay period, as defined in Tripletex.
Interval	remunerationType	If the salary is monthly or annual, the remuneration type is updated to Fixed salary. If the salary is hourly or weekly, the remuneration type is updated to Hourly pay.
Last salary change date		Updated with the current salary effective date.

 

Why should I sync salary data stored in Huma to Tripletex?

Syncing salary data makes sure salary calculations in Tripletex are correct and up to date, based on the latest information from Huma. The integration helps streamline HR and payroll processes by removing the need for manual data entry.

 

How do I send salary data automatically from Huma to Tripletex?

To send salary data automatically, you must first enable it manually in the integration settings. Once enabled, all salary changes made in Huma after this will automatically be sent to Tripletex.

If the integration is already set up, you can enable this in the integration settings under ··· in the top right corner and «Edit connection settings».

 

 

How is salary updated between Huma and Tripletex?

The integration uses the salary's effective date to decide whether to update an existing position or create a new position in Tripletex. If the salary is set as «hourly» or «weekly», the integration also takes the «Standard hours» setting in Tripletex into account when updating the salary.

Huma cannot create a new salary record with an effective date that falls between two existing salary records.

 

What happens if there is no existing position in Tripletex?

If there is no existing position for the salary's effective date in Tripletex, the integration will create a new position with the updated salary information, using the salary's effective date from Huma as the start date.

 

How does the integration handle different currencies?

The integration uses the currency defined in the company settings in Tripletex. Salary defined in a different currency will not be synced, and an error will be logged.

 

What happens if a salary is deleted in Huma?

If the deleted salary has the same start date as a position, the salary fields in Tripletex will be cleared. If a salary is deleted in Huma, the integration cannot delete the corresponding position in Tripletex. Instead, the integration will log an error, and the customer must update Tripletex manually.

 

How are bulk salary updates through «Salary revision» in Huma handled?

During a salary revision in Huma, the integration sends update requests to Tripletex for all affected users. If a request fails, the error is logged, but the process continues for the other users. Operations for a single user stop when the first error occurs.