Change Log
Check out our Change Log
| Release Date | Title | Description | System | Version | Type | Feature toggle |
|---|---|---|---|---|---|---|
| 2026-07-14 | Payroll settings: "Calculate vacation days at reconciliation" moved to Automation tab | The setting "Calculate vacation days at reconciliation" in the payroll processing settings has been moved to the Automation tab. | Payroll | 2026.127 | Change | No |
| 2026-07-14 | Import of deviating vacation entitlement no longer resets to standard | When importing a vacation entitlement for an employee who already has a personal vacation agreement, the agreement is now kept and updated directly. Previously, the import could incorrectly reset the employee to the standard agreement. | Payroll | 2026.127 | BUG | No |
| 2026-07-10 | Supplement an existing journal voucher | A new Supplement button has been added to the journal voucher toolbar. It lets you add to an existing journal voucher by selecting the voucher and the employees to include. | Payroll | 2026.125 | Change | Yes |
| 2026-07-10 | New settings in the Bygglösen configuration guide | The Bygglösen configuration guide now includes the four new settings from Bygglösen 2.1/2.2: role, activity, competence and responsibility supplements. They can be configured just like the other wage type settings. | Payroll | 2026.125 | Change | No |
| 2026-07-09 | Character limit validation for notes in payroll preparation | The notes field for an employee in payroll preparation now validates the 250-character limit when saving. Notes exceeding the limit are rejected with a clear message and the previously saved text is kept. | Payroll | 2026.124 | BUG | No |
| 2026-07-08 | Statistics fields in the report generator now show inherited company defaults | Workplace (CFAR number), Association number, Agreement code and Workplace number now appear in custom reports even when the value comes from the company's salary statistics settings rather than the employee card. | Payroll | 2026.123 | BUG | No |
| 2026-07-08 | Copy company | Will no longer copy that SmartDetect has been trained to create a new training session for the new company | Payroll | 2026.123 | BUG | No |
| 2026-07-08 | Wage type import correctly updates existing wage types | When importing a wage type register, saved mappings set to "Create new" are now re-checked. If the wage type has since been added to the register, the import updates it instead of trying to create a duplicate. | Payroll | 2026.123 | BUG | No |
| 2026-07-08 | Bygglösen 2.2 - minor improvements | The agreement code for the Sheet Metal and Ventilation agreement is updated to the latest LÖSEN specification. Occupational category is now included for the Construction agreement, and piecework pay fields are reported correctly in the XML file. | Payroll | 2026.123 | BUG | Yes |
| 2026-07-07 | Improved Bygglösen reporting of wage levels | Base hourly wage and payment level in the Bygglösen report are now always reported as full values. The distribution factor is reported separately and applied by Bygglösen in their own calculations. | Payroll | 2026.122 | BUG | No |
| 2026-07-07 | Changed execution day in BNP Paribas ISO 20022 payment file | The payment file for BNP Paribas now sets the execution day to the bank day before the salary payment date, in line with the bank's updated requirements. Previously, the execution day was the same as the payment date. | Payroll | 2026.122 | BUG | No |
| 2026-07-06 | Fixed ATK/ATF year not being created in the manual year editing flow when the employment period fell within the agreement's real earning/withdrawal window | When manually changing ATK/ATF years, a year that should have been created was sometimes not created. Eligibility was checked against the plain calendar year instead of the ATK/ATF agreement's actual earning/withdrawal window (e.g. 2025-04-01 – 2026-03-31), so an employment period that fell within that real window but outside the calendar year was missed and no year was created. Eligibility is now derived from the agreement's real earning/withdrawal period, so the year is correctly created whenever the employment overlaps that window. As part of the same fix, unapproved (non-bifallen) future employment periods are no longer used as the basis for creating a year. | 2026.121 | BUG | No |