Odoo Changelog — 2026-05-15

Friday, May 15, 2026

6 changes · master

Bug Fixes(6)

Resolved issues and error corrections

[FIX] l10n_pe_edi: prevent error when sending the invoice to Peru UBL

Enterprisemasterl10n_pe_ediMEDIUM

This update resolves an issue that prevented invoices with combo products lacking taxes from being processed correctly when generating Peru UBL invoices. The fix corrects a validation error related to a 'grouping_key' setting, ensuring these invoices can now be successfully submitted. This ensures accurate and compliant invoice generation for Peru.

Original PR description

A traceback occurs when sending an invoice to Peru UBL if a combo product
invoice line does not have any taxes applied.

Steps to reproduce the error:
- Install ``l10n_pe_edi`` module with demo data
- Switch to PE Company
- Create an invoice > Add a Office Combo product > unset the taxes > Confirm
- Process now

https://github.com/odoo/enterprise/blob/d7f71a68fbd5ff9c7cd52f96e1616671a6b8d77c/l10n_pe_edi/models/account_edi_xml_ubl_pe.py#L549-L552
Here, the ``grouping_key`` becomes ``None`` when no taxes are present on the invoice line.
Normally, invoices without taxes are restricted at [1],
but combo products are excluded from this validation at [2].
As a result, combo product lines without taxes bypass the restriction and trigger a traceback.

[1]: https://github.com/odoo/enterprise/blob/d7f71a68fbd5ff9c7cd52f96e1616671a6b8d77c/l10n_pe_edi/models/account_edi_format.py#L928-L929

[2]: https://github.com/odoo/odoo/blob/42b8852df9b323984364c41a13cf27d19fbe04a7/addons/account/models/account_move_line.py#L3433-L3434

sentry-7430552834

Forward-Port-Of: odoo/enterprise#117365
Forward-Port-Of: odoo/enterprise#114798

#accounting#peru#ubl

[FIX] l10n_be_hr_payroll: use modular days_per_week when generating DMFA report

PR #117278

Enterprisemasterl10n_be_hr_payrollMEDIUM

This update fixes a bug in the Belgium Payroll DMFA report that incorrectly displayed 'Days Per Week' as 5 when employees worked fewer than 5 days a week. The fix accurately calculates the number of working days based on the employee's schedule, ensuring accurate reporting for Belgian payroll compliance.

Original PR description

## Issue
When generating a DMFA report with a working schedule with more or less than 5 days a week, the *Days Per Week* value in the report is still appearing as 5.

## Steps to reproduce
1. Install *Belgium - Payroll* (`l10n_be_hr_payroll`)
2. In Payroll's Settings:
    - set *ONSS Registration Number* to `0830123456`
    - set *DMFA Employer Class* to `083`
    - create a *Work Address DMFA code* (any name, any numeral code, but set the *Working Address* to the Belgian company used for the rest of the steps)
3. In Employees' Settings, set the *Company Working Hours* to a new Working Schedule, with 9 hours/day, 4 days/week. E.g from Monday to Thursday included:
    - Work from 8:00 to 12:00
    - Lunch from 12:00 to 13:00
    - Work from 13:00 to 18:00
4. Create an Employee E for the Belgian company:
    - In the *Payroll* tab, set the start date of the contract to 01/01/2026.
    - In the *Personal* tab, set the *NISS Number* to `85073003328`
5. Create the payslip for January 2026 for the Employee E.
6. In Payroll > Reporting > Belgium > DMFA, create a new DMFA for the first quarter of 2026 and generate the PDF report
7. **In the generated PDF report, the _Days per Week_ line is set to 5.**

## Cause
The number of days was calculated by multiplying `5` with the `work_time_rate` of the related calendar. This is inaccurate in the case of a company where employees are only expected to work 4 days a week.

opw-6103934

Forward-Port-Of: odoo/enterprise#117116
Forward-Port-Of: odoo/enterprise#113804

#payroll#belgium#dmfa#reporting

[FIX] planning_attendance: view correct analysis with overlapping shift

PR #117442

Enterprisemasterplanning_attendanceMEDIUM

This update fixes an issue where the attendance report incorrectly displayed double the hours for employees with flexible schedules and overlapping shifts. The fix ensures that the report accurately reflects the total planned time, addressing a discrepancy in how overlapping shifts were counted.

Original PR description

__ ## Short functional explanation of the error When for an employee with a Flexible schedule, we set a shift overlapping on two days. The attendance report displays twice the worked hours. ##…

__

## Short functional explanation of the error
When for an employee with a Flexible schedule, we set a shift overlapping on two days. The attendance report displays twice the worked hours.

## Reproduction Steps
1. Create an employee with a flexible schedule and with Work Entry Source set at Planning.
2. Go to Planning. Create a Planning Slot for this employee from 9 pm to 5 am, then Send and Publish it.
3. Click on the Reporting tab > Planning / Attendance Analysis.

### Expected behavior
The total for this Month for this employee under the Planned Time field should be equal to 8 hours, which is the duration of the planning slot.

### Unexpected behavior
The total for this Month for this employee under the Planned Time field is equal to 16 hours.

## Origin of the issue
This report is a view, for which the SQL is defined starting this line: https://github.com/odoo/enterprise/blob/7362f1c5be7f496bdab660ed8fad37a6dd283616/planning_attendance/report/planning_attendance_analysis_report.py#L27 the issue stems from here:
https://github.com/odoo/enterprise/blob/7362f1c5be7f496bdab660ed8fad37a6dd283616/planning_attendance/report/planning_attendance_analysis_report.py#L56 where we don't select distinct the planning entries based on their ID. As our shift overlaps 2 days, there will be only one entry for this shift in the `planning_slot`, but because of that, it will be duplicated.

__
opw-6146052

Forward-Port-Of: odoo/enterprise#117276
Forward-Port-Of: odoo/enterprise#115447

#attendance#flexible schedule#reporting

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

PR #117405

Enterprisemasterl10n_pe_reportsMEDIUM

This update fixes a reporting issue in the Profit & Loss report for Peruvian companies. Previously, depreciation entries were incorrectly categorized as 'Other Income'. The change ensures that depreciation expenses are now correctly classified within 'Other Operating Expenses', improving the accuracy of financial reporting.

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_mx_edi: Fix rounding issue when distributing discount on m…

PR #117401

Enterprisemasterl10n_mx_ediMEDIUM

This update corrects a problem that caused invoices with many items to fail SAT validation (CFDI40111 & CFDI40108) due to currency precision issues when applying per-line discounts. The fix ensures accurate discount calculations, preventing invoices from being rejected by tax authorities.

Original PR description

…any lines

Fix SAT validation errors CFDI40111 and CFDI40108 that occur when invoices
with many lines contain a small negative line, causing per-line discounts
to be hidden due to currency precision.

opw-6187014

Forward-Port-Of: odoo/enterprise#117375
Forward-Port-Of: odoo/enterprise#117297

#tax#validation#discount

[FIX] planning_field_service: map domains

PR #117461

Enterprisemasterplanning_field_serviceMEDIUM

This update fixes a bug that prevented multi-day shift records from appearing on the live map. It now correctly displays shifts with a partner and ensures the Gantt and Calendar views scale appropriately to 'day', improving the map's usability for technicians and managers. This enhancement ensures accurate shift tracking and visualization.

Original PR description

This commit changes the domains for the "My Map" and "Map By Resource" to only include shifts with a partner.

Previously, it was including 'today' as part of the domain, which is incorrect as users may still want to view other days' shifts.

task-6180159

Forward-Port-Of: odoo/enterprise#115813

#map#shifts#location

A traceback occurs when sending an invoice to Peru UBL if a combo product invoice line does not have any taxes applied. Steps to reproduce the error: - Install ``l10n_pe_edi`` module with demo data - Switch to PE Company - Create an invoice > Add a Office Combo product > unset the taxes > Confirm - Process now https://github.com/odoo/enterprise/blob/d7f71a68fbd5ff9c7cd52f96e1616671a6b8d77c/l10n_pe_edi/models/account_edi_xml_ubl_pe.py#L549-L552 Here, the ``grouping_key`` becomes ``None`` when no taxes are present on the invoice line. Normally, invoices without taxes are restricted at [1], but combo products are excluded from this validation at [2]. As a result, combo product lines without taxes bypass the restriction and trigger a traceback. [1]: https://github.com/odoo/enterprise/blob/d7f71a68fbd5ff9c7cd52f96e1616671a6b8d77c/l10n_pe_edi/models/account_edi_format.py#L928-L929 [2]: https://github.com/odoo/odoo/blob/42b8852df9b323984364c41a13cf27d19fbe04a7/addons/account/models/account_move_line.py#L3433-L3434 sentry-7430552834 Forward-Port-Of: odoo/enterprise#117365 Forward-Port-Of: odoo/enterprise#114798

## Issue When generating a DMFA report with a working schedule with more or less than 5 days a week, the *Days Per Week* value in the report is still appearing as 5. ## Steps to reproduce 1. Install *Belgium - Payroll* (`l10n_be_hr_payroll`) 2. In Payroll's Settings: - set *ONSS Registration Number* to `0830123456` - set *DMFA Employer Class* to `083` - create a *Work Address DMFA code* (any name, any numeral code, but set the *Working Address* to the Belgian company used for the rest of the steps) 3. In Employees' Settings, set the *Company Working Hours* to a new Working Schedule, with 9 hours/day, 4 days/week. E.g from Monday to Thursday included: - Work from 8:00 to 12:00 - Lunch from 12:00 to 13:00 - Work from 13:00 to 18:00 4. Create an Employee E for the Belgian company: - In the *Payroll* tab, set the start date of the contract to 01/01/2026. - In the *Personal* tab, set the *NISS Number* to `85073003328` 5. Create the payslip for January 2026 for the Employee E. 6. In Payroll > Reporting > Belgium > DMFA, create a new DMFA for the first quarter of 2026 and generate the PDF report 7. **In the generated PDF report, the _Days per Week_ line is set to 5.** ## Cause The number of days was calculated by multiplying `5` with the `work_time_rate` of the related calendar. This is inaccurate in the case of a company where employees are only expected to work 4 days a week. opw-6103934 Forward-Port-Of: odoo/enterprise#117116 Forward-Port-Of: odoo/enterprise#113804

__ ## Short functional explanation of the error When for an employee with a Flexible schedule, we set a shift overlapping on two days. The attendance report displays twice the worked hours. ## Reproduction Steps 1. Create an employee with a flexible schedule and with Work Entry Source set at Planning. 2. Go to Planning. Create a Planning Slot for this employee from 9 pm to 5 am, then Send and Publish it. 3. Click on the Reporting tab > Planning / Attendance Analysis. ### Expected behavior The total for this Month for this employee under the Planned Time field should be equal to 8 hours, which is the duration of the planning slot. ### Unexpected behavior The total for this Month for this employee under the Planned Time field is equal to 16 hours. ## Origin of the issue This report is a view, for which the SQL is defined starting this line: https://github.com/odoo/enterprise/blob/7362f1c5be7f496bdab660ed8fad37a6dd283616/planning_attendance/report/planning_attendance_analysis_report.py#L27 the issue stems from here: https://github.com/odoo/enterprise/blob/7362f1c5be7f496bdab660ed8fad37a6dd283616/planning_attendance/report/planning_attendance_analysis_report.py#L56 where we don't select distinct the planning entries based on their ID. As our shift overlaps 2 days, there will be only one entry for this shift in the `planning_slot`, but because of that, it will be duplicated. __ opw-6146052 Forward-Port-Of: odoo/enterprise#117276 Forward-Port-Of: odoo/enterprise#115447

**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

…any lines Fix SAT validation errors CFDI40111 and CFDI40108 that occur when invoices with many lines contain a small negative line, causing per-line discounts to be hidden due to currency precision. opw-6187014 Forward-Port-Of: odoo/enterprise#117375 Forward-Port-Of: odoo/enterprise#117297

This commit changes the domains for the "My Map" and "Map By Resource" to only include shifts with a partner. Previously, it was including 'today' as part of the domain, which is incorrect as users may still want to view other days' shifts. task-6180159 Forward-Port-Of: odoo/enterprise#115813