Hours, supplements, meal deductions, and meal contributions with supported cause codes and salary codes will be transferred to Fortnox only for the employees included in the mapping between Planday & Fortnox.
​
Pay rates or monthly salaries will not be synced to Fortnox, but depending on your integration settings, Planday can fetch pay rates and salaries of mapped employees from Fortnox to Planday daily at 03:00 am.

The file export can still be used for other Swedish payroll systems, but we recommend using the dedicated integration for Fortnox sync since it supports the functionality of the file export and much more.

Yes, but this needs to be set up per employee in Planday. Read more in the Setup Fortnox integration with Planday Step 2 article.

Scheduled hours.

No, employee accounts will not be automatically created in Planday. If you wish to push Fortnox employee data to Planday, you can navigate to the Fortnox integration and choose which employees you'd like to import from Fortnox. Read more in the Setup Fortnox integration with Planday Step 1 article.

This is not done automatically, but when creating new employees in Planday, admins can select Create new user in Fortnox to send the newly created employee over.

When Fortnox is active and running, you can add the employee directly to Fortnox and save them to the existing mapping while creating their account.
​
For your new hires, you'd go to People > Employees > Create employee and fill in their details as you normally would. You will also find a Fortnox section where you can press Add to add the employee mapping.
​
Here, you can choose whether to add them to an existing employee entry from the Fortnox user dropdown or decide to create a new employee automatically, which also means that you will not need to add them in Fortnox manually.

Please keep in mind that if you choose to Create a new user in Fortnox, you will need to make sure that none of the required fields in Fortnox is left empty, in addition to any required fields you might have set in Planday.
​

At this step, the required information for the employee entry in Fortnox will also be required in Planday, and if anything is missing, it will be highlighted as required when you try to Save.
​

Once everything is in place, you'll see a confirmation message when you save your employee's data.
​
To verify, if you click on quick-edit for the newly created employee entry, you will see a confirmation that the employee data is being successfully synced to Fortnox.
​
However, if the sync fails, a red error message will be shown, explaining what went wrong or how to fix it.

To check that an existing employee in Planday is mapped in Fortnox, go to People > Employees, find the employee and open the quick edit view (✏️ icon).
​
The employee profile will have a Fortnox section, where you can see a label showing the name of the connected Fortnox account. If the data is mapped and synced correctly, a confirmation message will be shown in green.

Navigate to People > Employees > select the employee you need to remove and click on the quick edit icon ( ✏️ ). In the Fortnox section, click the X icon next to the Fortnox account label to remove the mapping and click Save to confirm.

Yes, you can sync data with Cost centre allocation by enabling that functionality in the integration editor and adding your Fortnox Cost centre codes into Department numbers in Planday.

No, please use Shift types with the Cause code / Salary code “SEM” instead.

No.

No.

The integration recognises only the main “Salary identifier” field, but it is still possible to use the integration. If salary identifiers do not appear to be correct on your employee mapping, you might need to make edits in the Employee form and payroll preview.

Yes.

All the previous data for the same employees for the same salary codes/cause codes and date ranges will be cleared in Fortnox, before new data will be transferred.

In Planday, the following fields are always required to create an employee.

In addition, there may be customised settings for your organisation that you may want to keep in sync. You can see or update your Employee form settings by visiting Settings > People > Employee form setup.

Cause codes are the equivalent of a Swedish term, Registreringskoder, which defines groupings of salary codes that can be found in Fortnox. These Cause codes determine whether the shift/hours represent working time, different types of absence, or supplements.
​
The data synchronised is grouped by Employee and per Cause code for all pay types, except meal contributions and meal deductions which use Salary codes instead.
​
Using Cause codes can save you a lot of time and tedious work. For example, you do not have to record personal leave and sickness as two different Shift types (with different Salary codes), but instead with one Shift type with one Cause code. Based on the Cause code, Fortnox will use its built-in logic to determine which Salary codes to assign to different hours for sick pay or vacation pay based on the employees’ settings in Fortnox and their current balances.

Salary codes in Planday are similar to what Cause codes are in Fortnox. Essentially Salary codes in Planday are used to identify specific types of shifts to match with their corresponding Cause code values in Fortnox.

This means that the employee data has no value for “Contracted hours” in Planday, prior to the first monthly salary being added by the integration. In these cases, the Contracted hours field is empty, and the system cannot calculate the correct hourly rate. You can fix this by editing the monthly salary and entering a number into the “Contracted hours” field.

The Sync status will show how many employees could not have the payroll data successfully exported. It will also list any employees whose payroll data could not be synced. (as shown in the screenshot below). By clicking on each employee’s name or the row, you'll see more details about the specific pay items that failed to sync, including:

If the error is not immediately apparent, review the checklist described in this Setup Fortnox integration with Planday Step 2 article or contact our support team for assistance.

This could be because one of the cost code values is not in use or misspelt. Please ensure you use the correct cost codes when entering them in the salary code fields in Planday. See the supported Cost codes values here.

Please verify that the employee has indeed given you the correct bank details.

If the employee has a five-digit bank reg. number from Swedbank - the bank reg. should be shortened to 4 digits, as the last digit is a control number, it can be deleted.