Skip to content
English
  • There are no suggestions because the search field is empty.

Netvisor integration

Save time and increase data quality by connecting to Netvisor. A simple way to import and synchronize people between your organization in Huma and your Netvisor account.



Table of Contents

Set up integration

Active integration

 

 

 

Netvisor

Netvisor integration lets you connect Huma with your Netvisor account to automatically sync employee data. This saves time and keeps your HR and payroll information accurate and up to date.

  • To configure an integration in Huma, you must have a "System role with full access permissions for Organization".
  •  If you are unsure which roles are required on the Netvisor side to complete the integration setup, please contact Netvisor support for guidance.

 

Multiple connections

If you need to configure multiple integration instances, follow the setup guidance provided here.

 

 

Step 1: Create an API identifier in Netvisor

  1. Log in as administrator
  2. Open the company menu > API identifiers

    Screenshot 2024-07-04 at 12.13.50

  3. Create a new API identifier by clicking the button to the right





  4. Copy and paste the User ID and the Key to a separate document/note for later





  5. Make sure you have the correct API resource access rights. Open the company menu > API resource access rights



    Screenshot 2024-07-04 at 12.14.14

  6. Scroll down to the Salaries section and Allow these if they're not already allowed:



    Screenshot 2025-11-03 091654
    1. 'employee.nv' - Allow
    2. 'getemployee.nv' - Allow
    3. 'getemployees.nv - Allow
    4. patchemployee.nv - Allow
  7. Get the Business ID. Open the company menu > Service Management

Screenshot 2024-07-04 at 13.22.02
  1. Copy and paste the Business ID to a separate document/note for later

 

 

 

Step 2: Connect Huma to Netvisor

  1. Login to your Huma account as administrator
  2. Go to 'Integrations'
  3. Open Netvisor
  4. Read through the documentation
  5. Click 'Set up' in the upper right corner
  6. Decide if positions should be sent to Netvisor when created, updated or deleted in Huma 
  7. Paste the Netvisor User ID, Key,  Business ID and check the box to verify you have the proper authority.

Screenshot 2025-11-03 091232

 

 

Step 3: Activate the integration. Synchronize users and choose how to handle conflicts or missing values

  • After clicking 'Save' you will end up in the Synchronize users step
  • Huma will inform you of any conflicts or inconsistency between Huma and Netvisor and you will have to decide how to handle conflicts and/or missing values. You can decide wether or not you want to update Netvisor based on values in Huma or the other way around.



  • Click 'Next' and decide how you want to sync users between Huma and Netvisor.


    • If users in Netvisor does not exist in Huma, you can add users to Huma
    • If users in Huma does not exist in Netvisor, you can add users to Netvisor
  • After deciding on the above click 'Syncronize users'
  • Huma will now start synchronizing users with Netvisor. You will receive an email confirming the result.

 

 

Step 4: Your connection between Huma and Netvisor is active 🥳

  • Any changes made to supported fields in Huma (listed below) will be automatically updated in Netvisor in real-time. 
  • Please be aware that you need to sync users to get the latest changes from Netvisor. Changes made in Netvisor will not be automatically be updated in Huma. 

 

How to sync users

Use “Synchronize users” whenever you have updated one of the supported fields in Netvisor, or when you want to create new users. For user synchronization to work, the email address must always be identical in both systems.

  1. Go to the Netvisor-integration in Huma

  2. Click “Synchronize users”

  3. Follow the steps. Read more about the steps here.

 

Note

  • If you have created a user in Huma, you must perform a “Manual synchronization” to create the user in Netvisor through the integration.

  • If an error occurs during synchronization, you can see detailed information in the “Error log” on the Netvisor integration page in Huma.

  • Please be aware that you need to sync users to get the latest changes from Netvisor. Changes made in Netvisor will not be automatically be updated in Huma. 

 

 

 

Deactivated or deleted users

When a user is deactivated in Huma...

  • the user will not be deactivated in Netvisor.
  • the user will be locked for updates and this will only occur through a manual synchronization.

When a user is deleted in Huma...

  • the user will not be deleted in Netvisor.
  • and not the other integration, the manual sync will ask you to create this user in Netvisor.
  • the user cannot be synced if there have been changes to their record in Netvisor.

 

 

Important informations to the payroll clerk

Make sure the payroll clerk in your organization is informed about this before starting to use the integration.

Creating users in Netvisor via sync

If you’re creating users in Netvisor via synchronization from Huma, there are some fields that should be manually reviewed in Netvisor.

  • Under ‘Employee’s information’:
    • Payroll information - Salary model will be set to ‘No salary model’
    • Settlement points - The value of TyEl will be set to ’No handling’. This will cause an error when trying to update the employee. A suitable employment pension insurance needs to be selected.

  • Under ‘Employments’: See details for sending position here

    Supported fields

    Huma field

    Netvisor field
    Email address (REQUIRED)

    E-mail

    employeebaseinformation.email

    Huma requires this field’s value to be unique.
    Identifications (REQUIED)

    Personal identity code

    employeebaseinformation.employeeidentifier

    The integration can’t unset or update this field’s value in Netvisor with the value in Huma.

    Must be unique and valid Finnish National identification number (SSA)
    Given name (REQUIRED)

     First name

    employeebaseinformation.firstname
    Family name  (REQUIRED)

    Last name

    employeebaseinformation.lastname
    Date of birth

    Date of birth

    employeebaseinformation.dateofbirth

    The integration can’t unset or update this field’s value in Netvisor with the value in Huma.
    Employment ID

    Employee number

    employeepayrollinformation.employeenumber

    Netvisor requires this field’s value to be unique.

    Max. length 10 characters
    Nationality

    Nationality

    employeebaseinformation.nationality
    Gender

    Gender

    employeebaseinformation.gender

    The integration can’t unset or update this field’s value in Netvisor with the value in Huma.
    Date of birth

    Date of birth

    employeebaseinformation.dateofbirth

    The integration can’t unset or update this field’s value in Netvisor with the value in Huma.
     Address ( REQUIRED)

     Address

    employeebaseinformation.streetaddress
    employeebaseinformation.municipality
    employeebaseinformation.postnumber
    employeebaseinformation.country

    All of the above must be filled in Netvisor if address should be synced to Huma
     Phone number

     Phone number

    employeebaseinformation.phonenumber

    Huma requires this field’s value to be unique.
    Bank account number

    IBAN account number
    Bank´s BIC code

    employeebaseinformation.bankaccountnumber
    employeebaseinformation.bankidentificationcode
    • Finnish IBAN 

     

    FAQ: Netvisor and Huma position integration

    ⚠️ Position data is sent only from Huma to Netvisor, not from Netvisor to Huma.

    ⚠️ Historical positions are not automatically transferred when the integration is activated. Only positions that are created or updated in Huma after activation will be synchronized.

    Supported fields – position data that can be synced

    These position fields are supported in the integration:

    Huma field Netvisor field
    Employment start date* (required) employmentperiods[].employmentperiod.startdate
    employmentperiods[].employmentperiod.companystartdate
    Job title* (required) employmentperiods[].employmentperiod.profession
    Contract type employmentperiods[].employmentperiod.employmentmode
    Employment percentage employmentperiods[].employmentperiod.employmentform
    employmentperiods[].employmentperiod.parttimepercent
    Probation end date employmentperiods[].employmentperiod.probationenddate
    Employment end date employmentperiods[].employmentperiod.enddate
    End reason employmentperiods[].employmentperiod.endreason

    ⚠️ If Employment start date or Job title is removed in Huma, the integration cannot remove the value in Netvisor.

     

    How are positions matched between Huma and Netvisor?

    Positions are matched using:

    • Contract start date

    • Job title

    When a position is updated in Huma, the integration uses the previous values of these fields to locate the correct position in Netvisor and update it.

    If no matching position is found, the integration returns an error to avoid updating the wrong record.

     

    When is a new position created in Netvisor?

    A new position is created when:

    • A position is added to an employee in Huma, and

    • No position with the same start date and job title exists in Netvisor.

    In this case, Huma creates a new employment period for the employee in Netvisor.

     

    What happens when a position is updated in Huma?

    When a position is updated in Huma, the integration tries to find the corresponding position in Netvisor using the previous values of:

    • Contract start date

    • Job title

    If a matching position is found, Huma updates that specific employment period in Netvisor with the new values.

    If no matching position can be found, the integration returns an error to prevent updating the wrong position in Netvisor.

     

    What happens when a position is deleted in Huma?

    If a position is deleted in Huma, the integration searches for the matching position in Netvisor using start date and job title.

    • If a match is found, that employment period is deleted in Netvisor.

    • If no match is found, the position will not be deleted to avoid accidental data loss.

     

    Can employment periods overlap?

    No. Netvisor does not support overlapping employment periods.

    If overlapping position dates are sent from Huma, the integration will return an error and the update will fail.

     

    Why aren’t all position fields synchronized?

    Huma and Netvisor structure employment data differently. Some fields exist only in one system, while others are stored in different formats. Because of these differences and some API limitations, not all position fields can be synchronized one-to-one between the systems.

     

    Synchronizing Employment type (Employment method in Netvisor)

    From Huma to Netvisor:

    Huma value   Netvisor value
    Casual will be Employed
    Consultant will be Leased employee
    Permanent will be Employed
    Temporary will be Employed
    Trainee will be Trainee

    From Netvisor to Huma:

    Netvisor value   Huma value
    Employed will be Permanent
    Leased employee will be Consultant
    Self employed will be Permanent
    Trainee will be Trainee
    Voluntary will be Temporary