Odoo Changelog — 2025-07-20

Sunday, July 20, 2025

2 changes · saas-18.1

Bug Fixes(2)

Resolved issues and error corrections

[FIX] l10n_fr_facturx_chorus_pro: remove `schemeName` in BIS3 XML

PR #219586

Coresaas-18.1l10n_fr_facturx_chorus_proMedium

French electronic invoices sent through Peppol now use the expected identifier attribute in BIS Billing 3.0 XML. This helps prevent invoice submission failures caused by XML that Peppol rejects.

Original PR description

### Issue: BIS3 XML is not valid for Peppol ### Steps to reproduce: - Install l10n_fr_facturx_chorus_pro and switch to french company - Activate peppol - Create a French customer - Under Sales and…

### Issue:
BIS3 XML is not valid for Peppol

### Steps to reproduce:
- Install l10n_fr_facturx_chorus_pro and switch to french company
- Activate peppol
- Create a French customer
- Under Sales and Purchase tab, set SIRET to "11000201100044"
- Under Accounting tab, set the following:
	- Invoice sending = Peppol
	- Einvoice format = BIS Billing 3.0
	- peppol_eas = France SIRET
	- peppol endpoint = 11000201100044
- Use Invoice/Invoiced smart button, then select New to create an invoice for this french customer
- Add any non-zero invoice line, then confirm
- Send and print, send to peppol
- Download the XML. The /PartyIdentification/ID element will have the schemeName attribute set.

### Cause:
Previous [commit](https://github.com/odoo/odoo/commit/0f3a9dee5cf15fa978a1857c184413003147c4a6#diff-10c62c279423109c43458eab15a3177ff5592d6570451f890fead74389bc3740) added `schemeName`. But Peppol doesn't want any `schemeName`, see the [doc](https://docs.peppol.eu/poacc/billing/3.0/rules/ubl-tc434/UBL-DT-08/).

### Solution:
The correct attribute here seems to be `schemeID`. See an [example from the docs of Peppol](https://docs.peppol.eu/poacc/billing/3.0/bis/#_parties_2). Change `schemeName` to `schemeID`.

opw-4934436

Forward-Port-Of: odoo/odoo#219012

#Peppol#France#e-invoicing#BIS Billing 3.0

[FIX] sale_renting: apply local timezone in "To Do Today" filter

PR #90358

Enterprisesaas-18.1sale_rentingMedium

The rental schedule and sales order filters now correctly account for each user's local time zone when showing items due today. This prevents rentals from being incorrectly included or missed for users outside UTC, improving daily operational accuracy.

Original PR description

__Issue:__
The "To Do Today" filter used the user's local date to build a datetime range but treated it as if it were already in UTC. This caused incorrect filtering in non-UTC timezones

__Fix:__
- Convert those datetimes to UTC using `.to_utc()` in the filter domain

opw-4886069

Forward-Port-Of: odoo/enterprise#89718

#timezone#rental#filtering#to-do

### Issue: BIS3 XML is not valid for Peppol ### Steps to reproduce: - Install l10n_fr_facturx_chorus_pro and switch to french company - Activate peppol - Create a French customer - Under Sales and Purchase tab, set SIRET to "11000201100044" - Under Accounting tab, set the following: - Invoice sending = Peppol - Einvoice format = BIS Billing 3.0 - peppol_eas = France SIRET - peppol endpoint = 11000201100044 - Use Invoice/Invoiced smart button, then select New to create an invoice for this french customer - Add any non-zero invoice line, then confirm - Send and print, send to peppol - Download the XML. The /PartyIdentification/ID element will have the schemeName attribute set. ### Cause: Previous [commit](https://github.com/odoo/odoo/commit/0f3a9dee5cf15fa978a1857c184413003147c4a6#diff-10c62c279423109c43458eab15a3177ff5592d6570451f890fead74389bc3740) added `schemeName`. But Peppol doesn't want any `schemeName`, see the [doc](https://docs.peppol.eu/poacc/billing/3.0/rules/ubl-tc434/UBL-DT-08/). ### Solution: The correct attribute here seems to be `schemeID`. See an [example from the docs of Peppol](https://docs.peppol.eu/poacc/billing/3.0/bis/#_parties_2). Change `schemeName` to `schemeID`. opw-4934436 Forward-Port-Of: odoo/odoo#219012

__Issue:__ The "To Do Today" filter used the user's local date to build a datetime range but treated it as if it were already in UTC. This caused incorrect filtering in non-UTC timezones __Fix:__ - Convert those datetimes to UTC using `.to_utc()` in the filter domain opw-4886069 Forward-Port-Of: odoo/enterprise#89718