Follow these steps to automatically have your employees’ sick leaves in NAV added to Huma
Why should we use this integration? Read our blog post about how the NAV/Altinn integration can help your company
- 1. Set up permissions in Altinn
- 2. Connect NAV / Altinn integration in Huma
- 3. Pending integration
- 4. Active integration
- What if an absence record in Huma already exists for the same dates as the sick leave from NAV?
- What does Huma do with sick leave that contains different degrees?
- What if I have integrated with another system that is fetching absence data from Huma?
- When will sick leave follow-up process and task be created?
Sick leaves from NAV can only be created on Huma users with a valid Norwegian identification number, or D-number.
When activating this integration there will be some limitations to the sick leave follow-up process.
1. Set up permissions in Altinn
To be able to send Sick leaves to Huma, you need to give Huma access to your company's sick leaves in Altinn
It's important that you set up access in Altinn as we explain below for the integration to work.
Also, remember to set up the correct access in Altinn before configuring the integration in Huma.
Note - you will need a...
- system role to set up the integration in Huma
- role with "full access over absence" to handle the sick leave and to "allow graded absence" in Huma. Read more about graded absence here.
You cannot view the physical sick leave note in Huma; it will only appear as a type of absence.
- Log in to Altinn with a user who has access to the company.
- Ensure the user has the role of either 'Tilgangsstyring' or 'Hovedadministrator' in Altinn. This is often the CEO of the company.
- Navigate to the organization you wish to integrate sick leaves for.
- Navigate to 'Innstillinger' > 'Andre med rettigheter til virksomheten' and '+ Legge til ny person eller virksomhet'
- Choose 'Ekstern virksomhet' and add Huma's details:
Org. nr: 912159329
Navn: Huma
- Select 'Gi tilgang til enkelttjenester,' then search for 'sykmelding' and click 'Legg til.' After that, click 'Gå videre' to continue.
- Complete permission set up by clicking 'Fullfør delegering'
- For organizations that have only a single "underenhet", it doesn’t matter whether they connect the "hovedenhet" or "underenhet".
- For organizations that have one "hovedenhet" with multiple underenhet, they must connect the "hovedenhet".
Read more about sub units and what they are for at Brønnøysundregistrene.
2. Connect NAV / Altinn integration in Huma
NB! Please note the following before continuing:
- Altinn may take some time to actually process the permissions you have just granted to Huma, so if you run into a problem in completing the setup below, you may have to just wait some minutes and try again.
- To connect the integration, you first need to enable graded absence for the sick leave type in the absence settings.
- 1. Go to "Absence module"
- 2. Navigate to "Settings"
- 3. Click on absence type "Sick leave" and "Edit absence type"
- 4. Click on "Allow graded absence" and choose between "Count as full days in Huma" or "Count as partial days in Huma"
- Copy or write down the org. nr of the "hovedenhet" eller "underenhet" in Altinn
- Log in to your Huma account
- Go to 'Integrations' in the main menu and choose 'NAV / Altinn'
- Please read and make sure you understand the information about the NAV / Altinn integration before moving to the next step.
- Click 'Set up' in the upper right corner
- Accept the terms & conditions, add the org. nr. of your "hovedenhet" or "underenhet" which you got from Altinn, and click 'Continue'.
- Choose from which date you want to fetch sick leaves and click 'Save'.
- Huma will recognize sick leaves that match those fetched from NAV and automatically cancel the duplicates.
- Huma will recognize sick leaves that match those fetched from NAV and automatically cancel the duplicates.
3. Pending integration
Once you save, the integration will be marked as pending until Huma verifies that the submitted organization number matches your company. This process may take up to 10 business days. You will be notified as soon as the verification is complete, and the integration will then become active.
4. Active integration
When the NAV/Altinn integration is active, all sick leaves that are added to NAV by a doctor will be sent to Huma via your company's Altinn account.
Huma will retrieve data from NAV/Altinn daily at 8:00 AM.
When the integration is activated, users with "absence access" will receive several notifications, as Huma retrieves all sick leave records from Altinn starting from the activation date. This may feel overwhelming, but notifications will only be sent to the users the sick leave concerns, their manager, and system admins.
What if an absence record in Huma already exists for the same dates as the sick leave from NAV?
When Huma receives a sick leave from NAV, the system handles pre-existing absences in different ways:
- Any sick leave from NAV, regardless of percentage, will cancel any manually created sick leave in Huma.
- Any sick leave from NAV, regardless of percentage, will overlap with any absence type other than sick leave in Huma.
Examples:
Vacation created in Huma
- Receives sick leave from NAV
- The vacation remains, and the sick leave overlaps.
Example: Anna has a vacation registered in Huma from June 1 to June 10. If she receives a sick leave for June 5 to June 15, the vacation entry for June 5-10 will remain while the sick leave overlaps.
Sick leave manually created in Huma
- Receives sick leave from NAV
- The sick leave created manually in Huma is canceled.
Example: Anna has a sick leave registered in Huma from June 1 to June 10. If she receives a sick leave for June 5 to June 15, the sick leave entry for June 5-10 will be Canceled.
What does Huma do with sick leave that contains different degrees?
Huma do not support sick leave from Nav/Altinn that contains different degrees.
Fx.
You receive the following sick leave: October 1-5: 100% October 6-10: 80%
Huma only receives the sick leave for October 1-5 at 100%, and you will then need to manually create a sick leave for the period October 6-10 at 80%.
What if I have integrated with another system that is fetching absence data from Huma?
Sick leave records from the date selected in step 2.7, if matching, will be replaced by the sick leave from NAV in any other integrations.
If an issue occurs, a record will be created in the integration's error log, and a notification will be sent to administrators with integration access.
Example with Tripletex
1. Sick leave manually registered in Huma is synced with Tripletex.
2. After that, a sick leave is received from Altinn/Nav.
3. The manually registered sick leave in Tripletex will be replaced by the one received from Nav/Altinn.
Limitations to the sick leave follow-up process
If you're using Huma's sick leave follow-up process together with this integration, please be aware that there will be some limitations to the follow-up process for norwegian employees.
Due to technical limitations, when a sick leave is extended in NAV, a new entry will be created in Huma, which will cause the ongoing follow-up process to stop.
When will sick leave follow-up process and task be created?
If Follow-up is activated for the absence type and a sick leave is started via NAV, a sick leave process is started in Huma, but will end when the first sick leave period ends. ie. not start again if the sick leave gets extended
Who receives notifications regarding the sick leave?
Note that absence administrators (fx. system admins) will receive separate notifications for every sick leave that is fetched, including those that have already ended.
User with absence approval permissions (fx. managers, supervisor) will receive separate notifications for every sick leave concerning their subordinates.
Employees will receive separate notifications for their sick leave registrations from the chosen date.