Odoo Changelog — 2026-01-25

Sunday, January 25, 2026

4 changes · master

Improvements(4)

Enhancements to existing features

[IMP] l10n_be_intervat: Cron for refresh token

Enterprisemasterl10n_be_intervatMEDIUM

This update enhances the Intervat integration by automatically refreshing refresh tokens every two days, ensuring a continuous connection. It also addresses a key issue for accounting firms submitting VAT returns, allowing them to use their VAT number instead of the client's company number for authentication. Small fixes were also implemented to improve stability and data handling.

Original PR description

### 1) Refresh Token & Cron Intervat API's provide use both access & refresh tokens. As long as we keep a valid refresh token, we can keep the connection opened by requesting a new refresh token.…

### 1) Refresh Token & Cron

Intervat API's provide use both access & refresh tokens. As long as
we keep a valid refresh token, we can keep the connection opened by
requesting a new refresh token.

Currently, we force the connection to close after 4 hours, but it's
too short.

This commit goes to the opposite way, and keep the connection opened
as long as the user wants.

As we need to keep a valid refresh token, we add a cron who execute once each 2 days
to fetch new refresh tokens.

Also, to prevent being stuck, add a new button in res settings to
manually close the connection.

### 2) Accounting firm

When submitting vat return to Intervat API, we have 2 situations:
1. The user submit his own declaration
2. An accounting firm submit the declaration for the client

The current implementation works nicely with situation 1, but not 2. The problem is
when starting the authentication proccess, we give Intervat a company number, the current
company number. But when an accounting firm is set on the company, we should use the
VAT number of the firm instead of the current company, as it will be an accountant from
the accounting firm who will submit the return.

So this commit try to find the accounting firm VAT before the current company VAT for
the authentication proccess. Also, add a new settings in Intervat settings to change the
accounting firm from there.

### 3) Small fixes

Small fixes done for corner cases, see commits messages.

task-5420287,5500052,5495079

Forward-Port-Of: odoo/enterprise#104572

#intervat#vat#accounting

[IMP] account_edi_ubl_cii: rearrange test files subfolder

PR #245178

Coremasteraccount_edi_ubl_cii

This update reorganizes the UBL test files within the Odoo system, moving them to a more structured folder. This change prepares the system for future support of different invoice formats and enhances the ability to validate schema compliance. It’s a technical update to improve testing capabilities.

Original PR description

This commit rearranges the UBL test files' subfolder to be one level higher, from `export/bis3/be` to `export/bis3/invoice/be`, in preparation for supporting different move formats and for better ignore schema support.

task-4891206

Forward-Port-Of: odoo/odoo#244886
Forward-Port-Of: odoo/odoo#244665

#testing#UBL#invoice

[IMP] account_edi_ubl_cii: Complete the VAT exemption reason codes (EN16931)

PR #245256

Coremasteraccount_edi_ubl_ciiMEDIUM

This update adds a complete list of VAT exemption reason codes (VATEX) to the Odoo system. This ensures accurate VAT handling for businesses, aligning with European regulations (EN16931) and improving compliance. Previously, the list was incomplete, and this change provides a more robust and reliable solution.

Original PR description

The list is there but not exhaustive.

Make the exhaustive list of VAT exemption reason codes (VATEX) available.

task-5443294


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

Forward-Port-Of: odoo/odoo#244555

#VAT#tax#exemption#UBL#EN16931

[IMP] mail: show confirmation dialog with last message when leaving livechat

PR #245363

Coremasterim_livechatMEDIUM

This update enhances the livechat exit confirmation dialog to provide agents with more context. Specifically, the dialog now displays the visitor's name and the last message from the conversation, reducing the risk of accidentally closing the wrong chat, especially with frequent list updates.

Original PR description

Previously, the confirmation dialog shown when leaving a livechat session was too generic and did not provide enough context to help agents ensure they were closing the correct conversation. As a…

Previously, the confirmation dialog shown when leaving a livechat session was too generic and did not provide enough context to help agents ensure they were closing the correct conversation. As a result, agents could accidentally leave the wrong chat, especially when the livechat list is reordered due to new incoming messages.

This PR improves the dialog to make the action clearer and safer:
- Displays the visitor’s name in the confirmation title.
- Shows the most recent message from the conversation in the dialog body.
- Helps agents verify they are leaving the intended conversation.

task-5355106

Before this PR: 
<img width="593" height="138" alt="image" src="https://github.com/user-attachments/assets/363eeab9-0306-47cc-8f4f-4035862f7e29" />

After this PR:
<img width="1135" height="277" alt="image" src="https://github.com/user-attachments/assets/6a7b7aea-d3bf-4b52-be39-001448ba7afc" />

Before vs After (Chat Window)
<table> <tr> <td> <img width="256" height="422" src="https://github.com/user-attachments/assets/b895b831-e11d-4aee-8f35-cd79f5c77aaf" /> </td> <td> <img width="256" height="422" src="https://github.com/user-attachments/assets/d31c061d-6a6e-42cb-ae60-12a5329cd4d4" /> </td> </tr> </table>


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

Forward-Port-Of: odoo/odoo#238105

#livechat#agent experience#conversation management

### 1) Refresh Token & Cron Intervat API's provide use both access & refresh tokens. As long as we keep a valid refresh token, we can keep the connection opened by requesting a new refresh token. Currently, we force the connection to close after 4 hours, but it's too short. This commit goes to the opposite way, and keep the connection opened as long as the user wants. As we need to keep a valid refresh token, we add a cron who execute once each 2 days to fetch new refresh tokens. Also, to prevent being stuck, add a new button in res settings to manually close the connection. ### 2) Accounting firm When submitting vat return to Intervat API, we have 2 situations: 1. The user submit his own declaration 2. An accounting firm submit the declaration for the client The current implementation works nicely with situation 1, but not 2. The problem is when starting the authentication proccess, we give Intervat a company number, the current company number. But when an accounting firm is set on the company, we should use the VAT number of the firm instead of the current company, as it will be an accountant from the accounting firm who will submit the return. So this commit try to find the accounting firm VAT before the current company VAT for the authentication proccess. Also, add a new settings in Intervat settings to change the accounting firm from there. ### 3) Small fixes Small fixes done for corner cases, see commits messages. task-5420287,5500052,5495079 Forward-Port-Of: odoo/enterprise#104572

This commit rearranges the UBL test files' subfolder to be one level higher, from `export/bis3/be` to `export/bis3/invoice/be`, in preparation for supporting different move formats and for better ignore schema support. task-4891206 Forward-Port-Of: odoo/odoo#244886 Forward-Port-Of: odoo/odoo#244665

The list is there but not exhaustive. Make the exhaustive list of VAT exemption reason codes (VATEX) available. task-5443294 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#244555

Previously, the confirmation dialog shown when leaving a livechat session was too generic and did not provide enough context to help agents ensure they were closing the correct conversation. As a result, agents could accidentally leave the wrong chat, especially when the livechat list is reordered due to new incoming messages. This PR improves the dialog to make the action clearer and safer: - Displays the visitor’s name in the confirmation title. - Shows the most recent message from the conversation in the dialog body. - Helps agents verify they are leaving the intended conversation. task-5355106 Before this PR: <img width="593" height="138" alt="image" src="https://github.com/user-attachments/assets/363eeab9-0306-47cc-8f4f-4035862f7e29" /> After this PR: <img width="1135" height="277" alt="image" src="https://github.com/user-attachments/assets/6a7b7aea-d3bf-4b52-be39-001448ba7afc" /> Before vs After (Chat Window) <table> <tr> <td> <img width="256" height="422" src="https://github.com/user-attachments/assets/b895b831-e11d-4aee-8f35-cd79f5c77aaf" /> </td> <td> <img width="256" height="422" src="https://github.com/user-attachments/assets/d31c061d-6a6e-42cb-ae60-12a5329cd4d4" /> </td> </tr> </table> --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#238105