Warnings in connection with ATK/ATF turn of the year and how to handle them

Employee with an old qualifying period

In the ATK/ATF turn of the year view, you can see that some employees have not been moved to the new qualifying period when you initiate a new year. In the example below, we have initiated a new qualifying period from 2026-04-01. Employees whose qualifying periods are dated before 2026-04-01 need to be addressed.

If you try to open a new payroll run for April 2026 without addressing these, you will receive a warning and the payroll run cannot be created.

This can be due to various reasons, such as an ATK / ATF agreement having been set up incorrectly (i.e. the employee should not have accrued anything at all) or the employee having changed employment and not accruing ATK / ATF in the new employment, but the old agreement has not been properly concluded.

Example 1 The employee has been incorrectly set up with an ATK / ATF agreement

This can happen, for example, if you employ an employee in a personnel category that has a standard agreement linked. When the agreement is initiated automatically, it is not enough to change the field to No agreed ATK / ATF.

If you still see the fields for balances for qualifying period/selected period and/or withdrawal period, the agreement is active and must be deleted.

To delete an incorrectly initiated agreement, you need to activate an authorisation to be able to remove ATK/ATF year on your role. In the example below, we have added the authority to the Flex Administrator role:

In the Employee register, you can now on the ATK/ATF tab click on the Historical data button and all the way to the right you can then click the cross to delete a year.

Note: This deletes all data linked to the selected ATK/ATF year.

Example 2 The employee has been rehired and does not accrue ATK/ATF in the new employment, but the agreement is still active

To conclude an ATK/ATF agreement, final salary must always be run and the pay codes for final salary linked to the agreement must be entered in a payroll run. If nothing is to be paid out, you can zero out the amounts for the pay code, but you must let the pay code remain in a payroll run. The agreement then gets the status Final pay paid out and is no longer active.

In our example, employee 1080 had an employment period to 2025-12-31 where he had an active ATK agreement. In the employment from 2026-02-02, he is not entitled to accrue ATK or ATF.

On the ATK/ATF tab, we can see that the system is still applying the ATK agreement.

To close the agreement, we need to open an extra payroll run in the agreement period. In my example, I choose to open an extra payroll run in March 2026, which is the last month of the agreement’s qualifying period. Using the final salary function, I select the earlier employment period and only enter the pay codes linked to the ATK agreement.

In payroll preparation, I zero out any amounts calculated by erasing the value in the Amount field. You may have one or more pay codes depending on whether HRM believes there is an amount to be paid out for one or more periods (qualifying period/selected period/withdrawal period) for the agreement. Zero all amounts on all rows and leave the created pay codes in place.

I settle the payroll run. In the Employee register, I see that the ATK agreement has been updated to Final pay paid out.