Odoo Changelog — 2025-10-13

Monday, October 13, 2025

3 changes · 19.0

Improvements(3)

Enhancements to existing features

[IMP] account_edi_ubl_cii: Add Delivery Party under Delivery Information in UBL

Core19.0account_edi_ubl_ciiMedium

Peppol UBL electronic invoices now include the delivery party in the delivery information. This makes exported invoices clearer for recipients by showing who the delivery is for, using the shipping contact when available or the customer name otherwise.

Original PR description

Previously, the Peppol UBL export only covered the mandatory delivery fields and did not include the `delivery party`. This commit adds the `<cac:DeliveryParty>` element under `<cac:Delivery>` to improve the exported information.
- Include `<cac:DeliveryParty>` in the `<cac:Delivery>` section of UBL invoices.
- Use the shipping partner name if set; otherwise, fallback to the customer name
- Keep existing `<cac:DeliveryLocation>` and delivery date logic unchanged.
<img width="766" height="306" alt="image" src="https://github.com/user-attachments/assets/d07c1b37-4c6d-42d1-99b4-66c5abc8e298" />

-----
task-5022404

Forward-Port-Of: odoo/odoo#230468
Forward-Port-Of: odoo/odoo#223756

#Peppol#UBL#electronic invoicing#delivery

[IMP] account_online_payment: send email on webhook and add tests

PR #93971

Enterprise19.0account_online_paymentMedium

Users are now notified as soon as their payment initiation is activated, instead of waiting for the next account synchronization. This reduces delays and improves visibility in the online payment setup process, with added tests covering the verification flow.

Original PR description

Before this we sent activation emails when synchronizing accounts, this
could cause a delay for the users knowing when their payment initiation
was activated. Now, we send it as soon as we receive the webhook from
Odoofin.

This commit also adds tests for the KYC flow.

Part of: 4487895

#online payments#activation email#webhook#KYC

[IMP] pos_iot: use iot_http service for payment terminals

PR #96634

Enterprise19.0iotpos_iotMedium

Payment terminals connected through the IoT Box now use the same communication service as other IoT actions. This enables additional connection methods such as WebRTC and WebSocket, improving reliability and flexibility beyond long polling.

Original PR description

As for any other actions sent from the db to the IoT Box, we updated payments terminals logic to use the `iot_http` service in order to allow them using webrtc and websocket in addition to longpolling.

odoo/odoo#230970

#payment terminals#IoT Box#Point of Sale

Previously, the Peppol UBL export only covered the mandatory delivery fields and did not include the `delivery party`. This commit adds the `<cac:DeliveryParty>` element under `<cac:Delivery>` to improve the exported information. - Include `<cac:DeliveryParty>` in the `<cac:Delivery>` section of UBL invoices. - Use the shipping partner name if set; otherwise, fallback to the customer name - Keep existing `<cac:DeliveryLocation>` and delivery date logic unchanged. <img width="766" height="306" alt="image" src="https://github.com/user-attachments/assets/d07c1b37-4c6d-42d1-99b4-66c5abc8e298" /> ----- task-5022404 Forward-Port-Of: odoo/odoo#230468 Forward-Port-Of: odoo/odoo#223756

Before this we sent activation emails when synchronizing accounts, this could cause a delay for the users knowing when their payment initiation was activated. Now, we send it as soon as we receive the webhook from Odoofin. This commit also adds tests for the KYC flow. Part of: 4487895

As for any other actions sent from the db to the IoT Box, we updated payments terminals logic to use the `iot_http` service in order to allow them using webrtc and websocket in addition to longpolling. odoo/odoo#230970