Release Notes
Check out our Release Notes
| Release Date | Title | Description | System | Version | Type | Feature toggle |
|---|---|---|---|---|---|---|
| 2026-02-20 | Support for Citibank ISO 20022 XML payment file | There is now support for exporting payment file in the Citibank ISO 20022 XML format. The exported file was implemented according to Citibank’s MIG as we interpret it. Citibank has however not yet formally validated the structure. Note: creditor accounts currently support IBAN only. | Payroll | 2026.39 | Change | No |
| 2026-02-19 | Chatbot no longer animates on window resize | Previously, resizing the browser window caused the chatbot to visibly slide into its new position. It now repositions instantly. | Employee Payroll Plan Time Travel | 2026.38 | Change | No |
| 2026-02-19 | Delegated permissions not working for simple accounting register | Delegated permissions were not functioning when the company used a simple (non-project) accounting dimension. Users with delegated access could not see available work shifts or accounting entries in the scheduling view. | Plan | 2026.38 | BUG | No |
| 2026-02-19 | Payroll Processing: Fixed navigation arrows not disabling correctly - employees | Fixed an issue where the previous/next navigation arrows in Payroll Processing were not properly disabled when reaching the first or last item in the list. Previously, when navigating through employees using the arrow buttons, the arrows would remain active even when there were no more items to navigate to. Users could click the arrows without any effect, which was confusing.With this fix:The previous arrow is now correctly disabled when you are at the first item The next arrow is now correctly disabled when you are at the last item The arrow states update automatically as you navigate through the list Selecting a different employee now properly updates the navigation arrow states This improvement provides clearer visual feedback and a more intuitive navigation experience in the Payroll Processing view | Payroll | 2026.38 | BUG | No |
| 2026-02-19 | Automatic Payroll Debt - New Accumulator Types | Added new accumulator types for gross and net debt, enabling automatic payroll debt handling for the next pay period. | Payroll | 2026.38 | Change | Yes |
| 2026-02-19 | Accumulator codes shown in payroll deviation warnings | Warnings about mismatched accumulator values now display which specific accumulator codes are deviating, making it easier to identify and resolve discrepancies. | Payroll | 2026.38 | Change | No |
| 2026-02-18 | Report generator - Support for summarizing Travel data | Added support to summarize a few datasets in the report generator for the Car trip & Travel data sources. For car trips, the modified field is Distance. For travel, the modified fields are amount of hotel nights, amount of trips, and total distance in km. | Travel | 2026.37 | BUG | No |
| 2026-02-18 | Vacation Balance Rounding | Vacation balances displayed as net days or hours are now rounded up to the nearest whole number. Balances shown as gross days remain unrounded. | Payroll | 2026.37 | Change | Yes |
| 2026-02-18 | Additional response data from the Travel salary basis endpoint | The response now includes the employee's national identification number. If it's missing, the property will be null instead. Keep in mind that this endpoint is still in early access and may be subject to change. | Travel | 2026.37 | Change | No |
| 2026-02-18 | Include salary-transferred time reports in recalculation | A new checkbox "Include settled time reports" has been added to the time report recalculation view. When enabled, recalculation will also cover salary-transferred (settled) time reports, not just reviewed ones. | Time | 2026.37 | Change | No |
| 2026-02-18 | Feature toggle for automatic salary debt handling | Added a feature toggle to control the rollout of automatic salary debt handling (gross/net). | Payroll | 2026.37 | Change | Yes |
| 2026-02-17 | Setting Visma Connect email ignores allophones | Fixed issue where certain characters (such as v and w) were considered the same, resulting in different email addresses being considered as the same address. We now ignore allophones. | 2026.36 | BUG | No |