Odoo Changelog — 2025-12-30

Tuesday, December 30, 2025

3 changes · 19.0

Bug Fixes(3)

Resolved issues and error corrections

[FIX] hr_work_entry_attendance: prevent work entry when ruleset has no pay extra hrs

Enterprise19.0hr_enterpriseMEDIUM

This update fixes an issue where overtime work entries were incorrectly generated when an overtime ruleset had no 'Pay Extra Hours' rules enabled. Now, work entries are only created for overtime if at least one rule in the ruleset allows for extra pay, ensuring accurate payroll calculations.

Original PR description

## Steps to Reproduce

1. Create a Overtime ruleset with **none** of the rules have "Pay Extra Hours" checked.
2. Assign this ruleset to an employee.
3. Generate attendances that normally produce overtime.
4. It will create work entries based on these attendances. Navigate to work entries in payroll. 

## Issue

Even when none of the rules are checked as  "Pay extra hours", It will still generates overtime work entries.

## Fix

Skipped work entries inside `_get_real_attendance_work_entry_vals` if there is no paid rules in a ruleset.

task - [5189151](https://www.odoo.com/odoo/project/1251/tasks/5189151)

#payroll#overtime#ruleset

[FIX] hr_payroll: monetary properties missing currency on payslip

PR #102896

Enterprise19.0hr_payroll

This update fixes an issue where payslips were not displaying currency symbols correctly. A small, hidden field was added to the payslip form to ensure the correct currency is associated with monetary amounts, improving the accuracy of payroll reporting.

Original PR description

The properties widget relies on the presence of the currency field in the view. Add an invisible currency_id field to the payslip form to properly display monetary symbols.

task-5357836

#payroll#currency#reporting

[FIX] l10n_br_edi_pos: fix NFC-e sequence

PR #102275

Enterprise19.0l10n_br_edi_pos

This update fixes an issue where Brazilian POS orders weren't correctly displaying their NFC-e sequence number in the backend. The fix adjusts a key method to ensure order names accurately reflect the defined sequence (e.g., POS-1234 instead of POS-00001), aligning with Brazilian tax regulations.

Original PR description

Brazilian order shoud follow the NFC-e sequence defined in the POS config.

Steps to reproduce:
-------------------
* Setup a POS in Brazil with NFC-e sequence (set the sequence to 1234)
* Create a new order in the POS
* Validate the order
* Check the order name in backend
> Observation: The order name is like: POS-00001 instead of POS-1234

Why the fix:
------------
We adapt the method _compute_order_name to get the correct sequence number if the country is Brazil.

opw-5243454

#Brazil#NFC-e#POS#Tax

## Steps to Reproduce 1. Create a Overtime ruleset with **none** of the rules have "Pay Extra Hours" checked. 2. Assign this ruleset to an employee. 3. Generate attendances that normally produce overtime. 4. It will create work entries based on these attendances. Navigate to work entries in payroll. ## Issue Even when none of the rules are checked as "Pay extra hours", It will still generates overtime work entries. ## Fix Skipped work entries inside `_get_real_attendance_work_entry_vals` if there is no paid rules in a ruleset. task - [5189151](https://www.odoo.com/odoo/project/1251/tasks/5189151)

Brazilian order shoud follow the NFC-e sequence defined in the POS config. Steps to reproduce: ------------------- * Setup a POS in Brazil with NFC-e sequence (set the sequence to 1234) * Create a new order in the POS * Validate the order * Check the order name in backend > Observation: The order name is like: POS-00001 instead of POS-1234 Why the fix: ------------ We adapt the method _compute_order_name to get the correct sequence number if the country is Brazil. opw-5243454