Integration with Fortnox

Treks and Fortnox integrates seamlessly and as an administrator there isn't much you need to do besides connecting Treks and Fortnox via Fortnox Marketplace or from within Treks by going to Settings > Apps and enable Fortnox. It does not matter which way you choose, the integration will be exactly the same.

Each project and absence type in Treks has a PAXml code. This code can be seen at the bottom of the edit project page in Treks. These codes are a Swedish stardard set by the interest group paxml.se

The codes are what connect a project in Treks with a salary type in Fortnox. The most common code is TID which represents work hour within scheduled time. But there is also SEM that represents vacation, VAB that represents care of children and so on.

Treks projects and absences comes out of the box with the correct codes already set. Fortnox also has a predefined set of codes setup.

This documentation is just to clarify that there is no other magic involved than the exchange of codes between Treks and Fortnox. It is possible for an admin to change the code for a project or absence type i Treks, just as it is possible to change how salary is calculated from a code in Fortnox.

How to recover from synchronization issues?

If, for some reason, the integration between Treks and Fortnox is disconnected there are a couple of ways to get the systems synchronized again.

Reconnect Treks and Fortnox

When you choose to enable the integration/app again after it being disconnected Treks will keep track of when it last was connected to Fortnox and will prompt you to re-synchronize*_ Treks with Fortnox. Treks will automatically suggest the date_ when the integration was disconnected. You can simply click the Yes button to synchronize. If the date is incorrect you can click the No button and manually choose the date interval to synchronize by going to Settings > Maintenance.

Manual synchronization using the Maintenance page

Go to Settings > Maintenance and select "Send Fortnox salary data" in the operation dropdown. Then select the date interval* and press the Run button. All data within the date interval will be re-synchronized**.

* Synchronization is always made for complete Periods. If the start and/or end date is not the beginning or end of a period Treks will automatically adjust them when synchronizing.

** Re-synchronization means that Treks will first remove any salary data from Fortnox withing the date interval and then add the new and correct time data from Treks. This process is asynchronos and can take some time. For large date intervals it can take several minutes. Fortnox applies thottling to requests made to them.