Odoo Changelog — 2026-05-15

Friday, May 15, 2026

4 changes · 19.0

Bug Fixes(4)

Resolved issues and error corrections

[FIX] hr_work_entry_attendance: tolerance doesn't seem to work with Timing rules

Enterprise19.0hr_work_entry_attendance

This update resolves an issue where overtime calculations weren't correctly accounting for lunch breaks. The fix adjusts the overtime check to consider lunch hours, ensuring more accurate overtime tracking. This change was prompted by a related update in the Odoo community repository.

Original PR description

**Version:**
- 19.0

**Issue:**
- test_14_overtime_rule_per_day_period test case was failing due to the changes in the community PR.

**Fix:**
- Updated the overtime check_work_entries to take lunch hours in consideration.

**Community PR:**
- https://github.com/odoo/odoo/pull/257079

**Task-6064081**

#hr#overtime#lunch breaks

[FIX] l10n_cl_edi_pos: prevent error when loading the paid orders

PR #117422

Enterprise19.0l10n_cl_edi_pos

This update corrects a technical error that occurred when loading paid orders. The previous process incorrectly referenced an account move, which was already being handled by another part of the system. This change ensures paid orders load correctly and efficiently.

Original PR description

Before this commit, when loading the paid orders it would load the account move with the "account_move" key, but this key is wrong as the account move model is loaded with the "account.move". Also, the account move is already loaded by the "read_pos_data" method in the point_of_sale module, so we can just remove it from here.

opw-6218467

#order processing#reporting#cl_edi

[FIX] l10n_pe_reports: sort entires in PL report for "Other income/expenses"

PR #117309

Enterprise19.0l10n_pe_reports

This update fixes a reporting issue in the Peruvian Profit & Loss report. Previously, depreciation entries were incorrectly categorized as 'Other Income'. The change ensures that depreciation entries (expenses) are now correctly classified within the 'Other Operating Expenses' section, providing accurate financial reporting for Peruvian businesses.

Original PR description

**Steps to reproduce:**
- Install Accounting and l10n_pe_reports
- Switch to a Peruvian company (e.g. PE Company)
- Create a MISC journal entry with a line using a depreciation account (e.g. 6841000) and a debit value (e.g. 1000)
- Post the entry
- Check "Profit and Loss" report"

**Issue:**
The "Other operation income" section has an amount of 1000, even though a depreciation account (i.e. expense) was used.
The amount should be in "Other operating expenses" section.

**Cause:**
A unique formula including accounts starting with 61, 66, 68, 71, 73, 74, 75, 76, 78, 79 and 99900 is used for "Other operation income" and "Other operating expenses" and depending on the sign of the sum, the result is reported in one of the section.

**Solution:**
Only report entries on "Income" accounts in "Other operation income" section and those on "Expense" accounts in "Other operating expenses".

opw-6073666

Forward-Port-Of: odoo/enterprise#114362

#reporting#peru#financials

[FIX] l10n_it_reports: Fix test for partner and bank account import

PR #117275

Enterprise19.0l10n_it_reports

This update resolves a test failure related to importing partner and bank account data for Italian reporting. The team restored a necessary data state within the test file, ensuring the tests now run successfully. This prevents disruptions to the Italian reporting functionality.

Original PR description

The related PR brings a data change in a test file that is used here. We bring back the state of that data in the test class, so that the tests don't fail anymore.

Community PR: odoo/odoo#254505

Task [link](https://www.odoo.com/odoo/project.task/6046189)
task-6046189

Forward-Port-Of: odoo/enterprise#117001
Forward-Port-Of: odoo/enterprise#112794

#reporting#italian#test

**Version:** - 19.0 **Issue:** - test_14_overtime_rule_per_day_period test case was failing due to the changes in the community PR. **Fix:** - Updated the overtime check_work_entries to take lunch hours in consideration. **Community PR:** - https://github.com/odoo/odoo/pull/257079 **Task-6064081**

Before this commit, when loading the paid orders it would load the account move with the "account_move" key, but this key is wrong as the account move model is loaded with the "account.move". Also, the account move is already loaded by the "read_pos_data" method in the point_of_sale module, so we can just remove it from here. opw-6218467

**Steps to reproduce:** - Install Accounting and l10n_pe_reports - Switch to a Peruvian company (e.g. PE Company) - Create a MISC journal entry with a line using a depreciation account (e.g. 6841000) and a debit value (e.g. 1000) - Post the entry - Check "Profit and Loss" report" **Issue:** The "Other operation income" section has an amount of 1000, even though a depreciation account (i.e. expense) was used. The amount should be in "Other operating expenses" section. **Cause:** A unique formula including accounts starting with 61, 66, 68, 71, 73, 74, 75, 76, 78, 79 and 99900 is used for "Other operation income" and "Other operating expenses" and depending on the sign of the sum, the result is reported in one of the section. **Solution:** Only report entries on "Income" accounts in "Other operation income" section and those on "Expense" accounts in "Other operating expenses". opw-6073666 Forward-Port-Of: odoo/enterprise#114362

The related PR brings a data change in a test file that is used here. We bring back the state of that data in the test class, so that the tests don't fail anymore. Community PR: odoo/odoo#254505 Task [link](https://www.odoo.com/odoo/project.task/6046189) task-6046189 Forward-Port-Of: odoo/enterprise#117001 Forward-Port-Of: odoo/enterprise#112794