New Conversation Template and Altinn 3.0 integration (FAQ)

0: Definitions

• Main template: The conversation template “Follow-up plan”, which is the 4human standard template for sickness absence follow-up.
• Old Main template: The conversation template “Follow-up plan”, which is the 4human standard template for sickness absence follow-up that could be sent to NAV via Altinn 2.0.
• New Main template: The conversation template “Follow-up plan”, which is the new 4human standard template for sickness absence follow-up that can be sent to NAV via Altinn 3.0.
• Launch day: The day we launch the integration to production (15.01.2026)

1: What happens to the conversation template “Follow-up plan“ in Library → Templates → Conversations?

When we launch the new integration, all programme templates you have in the solution will automatically be updated with the new conversation template if our standard template (which previously could be sent to NAV) has been used. The new template contains the updated structure defined by NAV, and all new sickness absence follow-ups you start will work exactly as you are used to.

Note: From launch day onwards, only conversations completed using the New Main template can be submitted.

2: What is the difference between the old and the new follow-up plan?

The old follow-up plan looks like this: 

.

The new follow-up plan as it appears in NAV (Follow-up plan LPS) and as it appears in 4human HRM:

.

3: What happens to the programme templates for sickness absence follow-up in Library → Templates → Programmes?

If the sickness absence follow-up programme template contains a step where the Old Main template is used, these conversations will automatically be updated on launch day.
 The conversations will then be replaced with the New Main template, which can be submitted to NAV.

This applies to all programme templates:

• Standard sickness absence follow-up programme template
• New/Customised/Copied sickness absence follow-up programme templates that include the main conversation as a step

No action is required from you as a customer.

Note 1: From launch day onwards, if this programme is assigned to an employee, it will contain the New Main template which can be submitted to NAV according to the new setup.

Note 2: If you have created your own copies of the conversation template “Follow-up plan” to adapt it to your needs, these copy-based templates will not be automatically updated. In that case, please read here for information on what you need to do.

4: What happens when a sickness absence follow-up programme was started before launch and is still ongoing?

• Planned dialogue meetings (status “For planning”) will automatically receive the new conversation template so they can be submitted to NAV after they have been completed. No action is required.
• Follow-up meetings already in progress (status “In progress”) using the old template unfortunately cannot be submitted to NAV after 16 January 2026. We therefore strongly recommend completing all follow-up conversations started with the old template and submitting them to NAV before launch day.

5: What happens if I have not submitted the conversation before launch day?

If it is not possible to complete conversations before 16 January 2026, you have two options:

• You can copy and submit the content directly in NAV by logging in there.
• Alternatively, you can conduct a new conversation with the new template within the same sickness absence follow-up, which can then be submitted to NAV as normal.

6: What will this require from me as a customer?

As a customer, we recommend that all started conversations are completed and submitted before the launch day xx.01.2026. In addition, you must grant access for submitting follow-up plans to 4human HRM AS in Altinn.

• Here is NAV’s explanation of who can grant API access 
• How to grant API access is explained simply by us here. More information is also provided by NAV on how to grant or revoke access here.  

7: When must the access in Altinn be granted to 4human?

The changes take effect from 16 January 2026. After this date, it will no longer be possible to submit previously completed sickness absence follow-ups.

8: What happens if I do not do this by the deadline?

If the necessary measures are not completed by the deadline, it will not be possible to submit follow-up conversations to NAV via the old solution. Old templates will no longer be valid for submission, and you must use the new solution for further sickness absence follow-up.

9: What about enterprise certificates?

Do I still need an enterprise certificate as a customer? 

An enterprise certificate is not required to submit sickness absence follow-up to NAV after the launch date.

Note – an enterprise certificate is still required to import sick leave into the solution until June 2026. After that, the requirement will be removed.

Will the cost be removed?

No. The cost of the enterprise certificate has been a combination of certificate cost and maintenance of the integration. The development and maintenance of the integration with NAV will continue, and therefore the licence cost for this integration will still apply. 
 

10: What must we do if our company has several companies/legal entities?

• The integration can be configured at the top level and will be inherited downwards in the structure to units and companies.
• If there is a separate company structure, these must be configured individually.

This is arranged directly with you as a customer by our consultants. 

11: We use the old platform (V4/Evolution), does this still apply to us?

Yes. The current integration on Altinn 2.0 for submitting follow-ups will stop working for both platforms. This new integration will work as long as you delegate API access to 4human HRM. 

Note that when NAV shuts down Altinn 2.0 for receiving sick leave as well, there will be no new integration for the V4/Evolution platform because it is being completely phased out. You will need to migrate to the new platform to continue using the solution. 

12: We do not use the module / have not started using it yet – does this still apply to us?

There is nothing you need to do if you do not yet use or have not started using the Sickness Absence module. When you are ready to begin, you must grant API access to 4human HRM, but aside from that, there is nothing else you need to do regarding the new integration with NAV being launched now.