Odoo Changelog — 2025-07-20

Sunday, July 20, 2025

4 changes

Branch: master

1 change

Bug Fixes(1)

Resolved issues and error corrections

[FIX] l10n_*: fixed translation refactor script

Enterprisemasterl10n_ae_reportsl10n_ar_edil10n_cl_edi_exportsl10n_cl_reportsl10n_cn_reportsl10n_co_reportsl10n_cz_reports

This fix corrects the translation refactor process across multiple country-specific reporting and electronic invoicing modules. It helps ensure translated labels and localization data remain accurate and consistent for users working with regional compliance features.

Original PR description

Forward-Port-Of: odoo/enterprise#90120
Forward-Port-Of: odoo/enterprise#84682

#localization#translations#compliance

Branch: 18.0

3 changes

Bug Fixes(3)

Resolved issues and error corrections

[FIX] account_edi_ubl_cii: fix FacturX validation issues

PR #218686

Core18.0account_edi_ubl_ciiMEDIUM

Factur-X electronic invoices now include additional XML information expected by some validators. Invoices paid by SEPA Direct Debit are also labelled with the correct payment method code, reducing validation errors when sending invoices to customers or portals.

Original PR description

### Issue:
There are several issues with the XML of FacturX.

### Steps to reproduce:
- Create a partner with a direct debit mandate
- In the Accounting tab of the partner select "FacturX" as eInvoice format
- Create an invoice with this partner, pay with SDD, confirm
- Send to FacturX
- Verify the PDF with https://www.portinvoice.com/
	1 Missing namespaces
3. In the XML the code for the payment means does not adapt to the payment method: 42 (Payment to bank account) and not 59 (SDD)

### Cause:
1. The namespaces are not there ([doc](https://fnfe-mpe.org/factur-x/factur-x_en/)).
3. We always input "42" as payment mean

### Solution:
1. Added namespaces `xmlns:qdt="urn:un:unece:uncefact:data:standard:QualifiedDataType:100"` and `xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"`
3. Added the code "59" for SDD, a lot of codes could be added but this commit only handles this one

Ticket [link](https://www.odoo.com/odoo/project/967/tasks/4907827)
opw-4907827

Forward-Port-Of: odoo/odoo#217763

#Factur-X#e-invoicing#validation#SEPA Direct Debit

[FIX] mail, im_livechat: avoid creating chat bubble when discuss is open

PR #215125

Core18.0mailim_livechat

When users receive messages while the Discuss app is open, Odoo no longer creates hidden chat bubbles that appear later after leaving Discuss. Notifications still work as expected, and livechat conversations continue to create bubbles where needed.

Original PR description

**Current behavior before PR:**
Receiving a new message while the Discuss app is open creates a chat bubble in the background. These bubbles become visible after leaving the Discuss app.

**Desired behavior after PR is merged:**
Chat bubbles are no longer created while the Discuss app is open, except for livechat messages. Messages still trigger notifications, but no background bubbles are inserted.

task-[4752392](https://www.odoo.com/odoo/project/1519/tasks/4752392)


---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

#discuss#chat#notifications

[FIX] hr_work_entry_contract_attendance: adapt for multiple days

PR #90587

Enterprise18.0hr_work_entry_contract_attendanceMEDIUM

Overnight attendances are now split into separate daily work entries instead of being recreated as one entry across multiple days. This prevents conflicts when an employee has an overnight shift followed by another attendance on the next day, improving payroll and attendance accuracy.

Original PR description

Steps to reproduce the issue:

0. Set work_entry_source to "attendance" on the running contract 
   of the employee.
1. Create an attendance from yesterday 23:00:00 UTC to today 
   06:00:00 UTC.
2. Create an attendance today from 08:00:00 UTC to 16:00:00 UTC.

Current behavior before PR:
Odoo will create a conflicting work entry with the one created 
in step 1, because the logic recreates all work entries in a 
timeframe between the start date at 00:00:00 and end date at 
23:59:59. The first entry started before this timeframe, so the 
recreated work entry does not align with the existing one, 
causing a conflict.

Desired behavior after PR is merged:
The work entries now span a single day at a time. If an 
attendance starts at night and ends the next morning, two 
entries will be created: one from the start time to end of day, 
and another from the start of the next day to the end time.

opw-4869604

I confirm I have signed the CLA and read the PR guidelines at 
[www.odoo.com/submit-pr](http://www.odoo.com/submit-pr)

#attendance#work entries#overnight shifts#payroll

### Issue: There are several issues with the XML of FacturX. ### Steps to reproduce: - Create a partner with a direct debit mandate - In the Accounting tab of the partner select "FacturX" as eInvoice format - Create an invoice with this partner, pay with SDD, confirm - Send to FacturX - Verify the PDF with https://www.portinvoice.com/ 1 Missing namespaces 3. In the XML the code for the payment means does not adapt to the payment method: 42 (Payment to bank account) and not 59 (SDD) ### Cause: 1. The namespaces are not there ([doc](https://fnfe-mpe.org/factur-x/factur-x_en/)). 3. We always input "42" as payment mean ### Solution: 1. Added namespaces `xmlns:qdt="urn:un:unece:uncefact:data:standard:QualifiedDataType:100"` and `xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"` 3. Added the code "59" for SDD, a lot of codes could be added but this commit only handles this one Ticket [link](https://www.odoo.com/odoo/project/967/tasks/4907827) opw-4907827 Forward-Port-Of: odoo/odoo#217763

**Current behavior before PR:** Receiving a new message while the Discuss app is open creates a chat bubble in the background. These bubbles become visible after leaving the Discuss app. **Desired behavior after PR is merged:** Chat bubbles are no longer created while the Discuss app is open, except for livechat messages. Messages still trigger notifications, but no background bubbles are inserted. task-[4752392](https://www.odoo.com/odoo/project/1519/tasks/4752392) --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Steps to reproduce the issue: 0. Set work_entry_source to "attendance" on the running contract of the employee. 1. Create an attendance from yesterday 23:00:00 UTC to today 06:00:00 UTC. 2. Create an attendance today from 08:00:00 UTC to 16:00:00 UTC. Current behavior before PR: Odoo will create a conflicting work entry with the one created in step 1, because the logic recreates all work entries in a timeframe between the start date at 00:00:00 and end date at 23:59:59. The first entry started before this timeframe, so the recreated work entry does not align with the existing one, causing a conflict. Desired behavior after PR is merged: The work entries now span a single day at a time. If an attendance starts at night and ends the next morning, two entries will be created: one from the start time to end of day, and another from the start of the next day to the end time. opw-4869604 I confirm I have signed the CLA and read the PR guidelines at [www.odoo.com/submit-pr](http://www.odoo.com/submit-pr)