Monday, February 16, 2026
4 changes · master
Resolved issues and error corrections
This update fixes a limitation in the payroll schedule wizard that prevented users from selecting resource calendars without a company assigned. The change expands the selection options to include all calendars, regardless of company affiliation, improving flexibility and usability for resource scheduling. This ensures all resources can be correctly assigned to payroll schedules.
Original PR description
Steps to reproduce: 1. Create a resource calendar without any company 2. Open the payroll set schedule wizard 3. The calendar without company is not selectable Bug cause: The domain on `resource_calendar_id` field only filtered for calendars belonging to the current company, excluding calendars with no company set. Solution: Update the domain to include both calendars from the current company AND calendars without any company using an OR condition. Task Id: 5912974
This update resolves an issue where the timesheet's systray label was not displaying correctly. The fix ensures the label accurately reflects the timesheet's status, providing a clearer visual indication for users. This improves the overall user experience and data accuracy.
This update resolves an issue where DMFA export reports were being rejected due to duplicate employee records sharing the same NISS. The fix groups employees with the same NISS and merges their payslips into a single record, ensuring accurate DMFA declarations and preventing errors.
Original PR description
In some real-life situations, multiple employee records can share the same NISS (e.g. a student contract followed by a regular contract after archiving the first employee). When exporting DMFA data, this resulted in multiple NaturalPerson nodes with identical identifiers.
This caused the DMFA declaration to be rejected with error 90017-006 ("Personne physique - Trop d'occurrences avec les mêmes identifiants").
To fix this, employees sharing the same NISS are now grouped in the DMFA export, and their payslips are merged into a single NaturalPerson node.
task-5470180The Pay Run status bubble now correctly reflects the status of payroll processing. Previously, it incorrectly showed a green status even when no payslips had been generated. This update ensures the bubble remains grey until payslips are created, providing a more accurate visual representation of the payroll process.
Original PR description
Previously, the Pay Run status bubble appeared green even with 0 payslips. This commit updates the `StatusBubble` component to check `payslip_count`. The current stage bubble will now remain grey (`bg-secondary`) until payslips are generated, only turning green (`bg-success`) when `payslip_count > 0`. - JS: Added `payslip_count` to field dependencies. - XML: Updated class conditions to respect payslip count.