Odoo Changelog — 2026-08-14

Friday, August 14, 2026

2 changes · saas-18.4

Bug Fixes(2)

Resolved issues and error corrections

[FIX] l10n_lu_hr_payroll: compute indexed wage at payslip date

Enterprisesaas-18.4l10n_lu_hr_payrollMedium

Historical Luxembourg payslips now use the wage index that was active at the end of the payslip period, instead of using the current index. This helps ensure older payroll calculations remain accurate when wage index values change over time.

Original PR description

Historical payslips incorrectly used today's wage index instead of the index active during the payslip period.

Now, salary rules evaluate the indexed wage using `payslip.date_to` via the new `_get_l10n_lu_indexed_wage(date)` contract method.

Task: 6395557

Forward-Port-Of: odoo/enterprise#125861

#payroll#Luxembourg#payslips#wage index

[FIX] l10n_br_edi: allow import of xml bills no attributes

PR #127851

Enterprisesaas-18.4l10n_br_ediMedium

Odoo now recognizes valid Brazilian electronic invoice XML files even when the invoice tag has no extra attributes. This prevents some vendor bills from being skipped during import, helping accounting teams process compliant invoices consistently.

Original PR description

### Issue before this commit:
Certain valid Brazilian NF-e (electronic invoice) XML files fail to import because the system silently ignores them during the initial EDI recognition phase.

### Steps to reproduce the issue:
1. Download Accounting and l10n_br_edi
2. Go to Vendor > Bills
3. Try to import both xmls in the ticket
4. One of the two will not be imported correctly

### Cause of the issue:
https://github.com/odoo/enterprise/blob/3ed1721b702555e96c9774969927f6517e855704/l10n_br_edi/models/account_move.py#L819-L827 This function relies on a strict byte string search for b"<NFe " while it's also correct if the tag is only `<NFe>`.

### Reason to introduce the fix:
To make the initial NF-e file recognition more robust and compliant with standard XML namespace rules, ensuring Odoo successfully processes all valid Brazilian invoices regardless of attribute formatting.

opw-6402843

Forward-Port-Of: odoo/enterprise#126881

#Brazil#NF-e#vendor bills#XML import

Historical payslips incorrectly used today's wage index instead of the index active during the payslip period. Now, salary rules evaluate the indexed wage using `payslip.date_to` via the new `_get_l10n_lu_indexed_wage(date)` contract method. Task: 6395557 Forward-Port-Of: odoo/enterprise#125861

### Issue before this commit: Certain valid Brazilian NF-e (electronic invoice) XML files fail to import because the system silently ignores them during the initial EDI recognition phase. ### Steps to reproduce the issue: 1. Download Accounting and l10n_br_edi 2. Go to Vendor > Bills 3. Try to import both xmls in the ticket 4. One of the two will not be imported correctly ### Cause of the issue: https://github.com/odoo/enterprise/blob/3ed1721b702555e96c9774969927f6517e855704/l10n_br_edi/models/account_move.py#L819-L827 This function relies on a strict byte string search for b"<NFe " while it's also correct if the tag is only `<NFe>`. ### Reason to introduce the fix: To make the initial NF-e file recognition more robust and compliant with standard XML namespace rules, ensuring Odoo successfully processes all valid Brazilian invoices regardless of attribute formatting. opw-6402843 Forward-Port-Of: odoo/enterprise#126881