NAV / Altinn integration

Table of Contents

• Multiple connections
• What you need
• Enable "Graded absence"
• Set up integration
• Active integration
• Sick leave follow up process
• FAQ

Multiple connections

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

What you need

• System role in Huma

• Someone at your company with the "Tilgangsstyring" (Access Manager) role in Altinn — usually the CEO. This can be you or a colleague.

• BankID

• Enabled "Allow graded absence" in Huma 

• Sick leaves from NAV can only be created for users who have a valid Norwegian national identity number or D-number registered in Huma.

• When activating this integration there will be some limitations to the sick leave follow-up process. Read more here.

Enable "Graded absence"

To connect the integration, you first need to enable graded absence for the sick leave type in the absence settings.

1. Go to the "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"

Set up integration

After you have enabled graded absence, you can set up the integration.

Already have an integration to NAV/Altinn and need to "Reauthorize"? 🔗 Read the steps here. 

1. Go to the "Integration module"
2. Navigate to NAV and click "New connection"
3. Click "Set up"
4. Fill out name and who should be a part of this integration
5. Click "Continue"
6. Fill out organization number
   1. For organizations that have only a single "underenhet", it doesn’t matter whether they connect the "hovedenhet" or "underenhet".
   2. For organizations that have one "hovedenhet" with multiple underenhet, connect the "hovedenhet".
   3. For organizations with several "underenheter" and only want to connect one of them, connect only the relevant "underenhet".
7. Toggle on for "Legal authority" and click "Continue"
8. Choose the date from which you want to start fetching sick leaves
9. Another window will open
   1. Login with Bank ID
   2. Approve system access
10. Click "Close and continue to Huma", and the integration is now active

💡 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.

💡 Huma will recognize sick leaves that match those fetched from NAV and automatically cancel the duplicates.

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 between 8:00 AM and 6:00 PM (UTC).

⚠️ 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.

Sick leave follow-up process

If you're using Huma's sick leave follow-up 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.
• If you receive a graded sick leave from NAV, the follow up process will only support the first degree.
• If you receive an extended sick leave, the follow up will automatically stop.
• The follow up will not automatically start a process from the Processes module.

🔗 Read more about the sick leave follow up process here.

FAQ

Information regarding the Sick leave from Nav/Altinn

• You cannot view the physical sick leave in Huma; it will only appear as a type of absence.
• When the sick note is entered into Huma, it will be automatically approved.
  
  

What if an absence record in Huma already exists for the same dates as the sick leave from NAV?

Example 1 — Vacation and NAV sick leave: Anna has a vacation registered from June 1 to June 10. She receives a sick leave from NAV for June 5 to June 15. The vacation entry for June 5–10 remains, and the sick leave overlaps for that period.

Example 2 — Manual sick leave and NAV sick leave: Anna has a sick leave registered manually in Huma from June 1 to June 10. She receives a sick leave from NAV for June 5 to June 15. The manually created sick leave entry for June 5–10 is cancelled.

🔗 Read more about overlapping absence here.

What if I have integrated with another system that is fetching absence data from Huma?

• 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.
• If you have integrated with Webhooks, the process functions identically to a manual absence registration in Huma. The payload will include details such as the period, type of absence, the employee associated with the sick leave, and the current status. Read more about absence events and Webhook here. 

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,  "sick leave follow up" is started in Huma, and the system will automatically create tasks.

• Read more about the norwegian or swedish tasks. 

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.
• If "sick leave follow up" is enabled, administrators with absence permissions will also receive a separate email notification related to this process.