Daily updates from Odoo
Tuesday, December 30, 2025
7 changes · 19.0
New functionality added to Odoo
This update reflects changes to Mexican withholding tax rates (ISR) mandated by the latest tax resolution. The update adds a new parameter value to ensure Odoo accurately calculates and reports ISR withholdings for the 2026 fiscal year, aligning with current regulations. This ensures compliance and accurate financial reporting for Mexican businesses using Odoo Enterprise.
Original PR description
According to the Mexican Tax Resolution (Resolución Miscelánea Fiscal 2026: https://dof.gob.mx/2025/SHCP/SHCP_281225_01.pdf), the ISR withholding tax tables applicable for the fiscal year have changed, effective January 1, 2026. It is necessary to add a new parameter value for “Mexico: ISR Table” to reflect the new values. target: 19.0 task: 5448019
This update introduces new Profit & Loss and Balance Sheet reports for Ireland, utilizing account tags instead of traditional account codes. This change simplifies reporting and allows for more granular financial analysis. The previous account code-based reports have been disabled.
Original PR description
This pr introduce new PL and BS reports based on account tags. And old PL and BS reports based on account codes are inactive now. So now user have to now manually enable them via Enable more on each report. Related Community PR: https://github.com/odoo/odoo/pull/222186 Task: 4978415 Forward-Port-Of: odoo/enterprise#103002 Forward-Port-Of: odoo/enterprise#91903
Enhancements to existing features
This update enhances the onboarding experience for new users of the Live Chat feature. The tour now explicitly opens the Live Chat information panel, ensuring users immediately understand its functionality. This change improves usability and guides users more effectively.
Original PR description
The livechat info panel is no longer opened by default. The tour now opens it explicitly before asserting its content. Related PR: odoo/odoo#238472 Task-5291258
This update adjusts payroll rule parameters to reflect changes in US tax regulations for the 2026 tax year. Ensuring these parameters are current is crucial for accurate salary calculations and maintaining compliance with US payroll laws. This update addresses a necessary improvement to the system.
Original PR description
Purpose: Certain US Payroll values changes yearly. The payroll rule parameters must be updated for accurate salary calculation for 2026 for compliance. task-5409739 Forward-Port-Of: odoo/enterprise#102759 Forward-Port-Of: odoo/enterprise#102711
Resolved issues and error corrections
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)
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
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