Odoo Changelog — 2026-01-29

Thursday, January 29, 2026

4 changes · 19.0

Bug Fixes(4)

Resolved issues and error corrections

[FIX] l10n_*_reports: include expense_other in Balance Sheet unallocated earnings

Enterprise19.0accountaccount_reportsMedium

This update fixes a discrepancy in Odoo's Balance Sheet reports for several localized versions (CO, EC, KR, US, TW, and ZM). It ensures that 'Other Expenses' (expense_other) are now correctly included in the unallocated earnings calculations, aligning them with standard reports. This improves financial reporting accuracy for these localized businesses.

Original PR description

*= co, ec, kr, us, tw, zm

Currently, the `Other Expense(expense_other)` account type, introduced in 
saas-18.3, is missing from the Balance Sheet reports of certain `localizations`, 
even though it's correctly implemented in the standard reports.

**Steps to reproduce:**
- Install the `l10n_co_reports` and `accountant` modules.
- Switch to `CO company `and navigate to Accounting > Reporting > Balance Sheet.
- Ensure the `report` smart button is set to `Balance Sheet (CO)`.
- Equity > Previous Years Unallocated Earnings and click the `info icon`.
- Observe the formula of `balance_domain`.

**Observation:**
The formula does not include the `expense_other` account type.

**Root Cause:**
After PR [1], at [2] `expense_other` was added to the Previous Years Unallocated 
Earnings balance domain only in the main `account_reports` module. The 
corresponding localization reports mentioned above were not updated 
accordingly, resulting in incomplete Balance Sheet formulas.

**Fix:**
This commit updates the Balance Sheet report and includes the `expense_other` 
account type in the Previous Years Unallocated Earnings balance domain, 
aligning them with the standard reports.

[1]:
https://github.com/odoo/enterprise/pull/101591

[2]:
https://github.com/odoo/enterprise/blob/316a5965e5fae83bd7d901929160c87eb28d13cf/account_reports/data/balance_sheet.xml#L205

opw-5491639

Forward-Port-Of: odoo/enterprise#105262

#financial reporting#balance sheet#localization

[FIX] l10n_se_bban: adding RfdDocAmt in iso20022 for bankgiro account

PR #105817

Enterprise19.0l10n_se_bbanMedium

This update resolves an issue preventing Odoo payments using Swedbank's Bankgiro accounts. Swedbank requires a specific 'RfdDocAmt' field in payment XMLs, which Odoo was previously missing. This fix adds this field, ensuring successful payment processing and avoiding bank rejections.

Original PR description

**PROBLEM**
Swedbank requires the RfdDocAmt Element for Bankgiro account. [documentation](https://internetbank.swedbank.se/ConditionsEarchive/download?bankid=1111&id=WEBDOC-PRODE211415244). Payment batches generated by Odoo don't contains this fields, meaning they are refused by the bank.

**REPRO STEPS**
We can't reproduce the error the client have because it would require a valid bankgiro account. To generate the payment batch xml you have to:
1. Install l10n_se.
2. Create a vendor bank account of type bankgiro.
3. Create a vendor payment with this vendor bank account.
4. Create a batch payment and validate it.
5. There should be a xml in the chatter, you can look at it to see there is no RfdDocAmt element.

opw-5427505

Forward-Port-Of: odoo/enterprise#104777

#bankgiro#swedbank#payment#iso20022

[FIX] web_gantt: prevent gantt controls from overlapping the UI

PR #105708

Enterprise19.0web_ganttMedium

This update fixes an issue where the Gantt chart controls would overlap the user interface, particularly when using custom date ranges and a smaller screen size (Dutch language and iPhone SE emulation). The change ensures that Gantt controls are displayed correctly, improving usability and preventing visual clutter.

Original PR description

Steps to reproduce
==================

- Switch to dutch
- Emulate an iPhone SE viewport in the browser settings
- Open a project
- Switch to the gantt view
- Use a custom date range

-> The gantt controls are displayed on top due to the daterange format being to long

| Before | After |
|--------|--------|
| <img width="736" height="1542" alt="image" src="https://github.com/user-attachments/assets/7c573ab1-fbf8-4f31-83ba-21d66ebc504d" /> | <img width="736" height="1542" alt="image" src="https://github.com/user-attachments/assets/62ab3d47-701e-4e2d-aaef-5c92675236cb" /> | 

opw-5340869

Forward-Port-Of: odoo/enterprise#105229
Forward-Port-Of: odoo/enterprise#104821

#gantt#UI#usability

[FIX] documents_account: embed server actions to relevant journal folder

PR #102039

Enterprise19.0documents_accountMedium

This update streamlines the user experience by embedding key actions like 'Create Vendor Bill' directly into the appropriate journal folders (e.g., Purchase, Sales). This ensures users have the necessary tools readily available within the areas where they're working, improving efficiency.

Original PR description

What:
Previously, actions like "Create Vendor Bill" were only embedded in the
main "Finance" folder. Now, these actions are also embedded directly into
the specific subfolders for each journal type (e.g., "Purchase", "Sales").
All relevant actions are also kept in the parent "Finance" for general
accessibility. The purchase actions are also added to the "Inbox" folder.

Why:
The previous behavior was inefficient. A user uploading a vendor bill to
the "Purchase" folder would not see the "Create Vendor Bill" action. He
would only see it when he is in the parent "Finance" folder. By embedding
it by default this streamlines the process by ensuring the necessary tools
are available exactly where the user is working.

How:
The logic is implemented within the _documents_configure_sync method of
the account.journal model. This is the ideal location because it
handles the complete setup of a journal for the Documents app. This ensures
that actions are embedded correctly both during module installation and
dynamically whenever a new journal is created by a user.

Notes:
- Tests were rewritten to check these embeddings on install. And were
refactored to be more maintainable and cover bank statements better.
- The test for importing bank statements had to be moved to a separate
testing module, as it needs the `account_bank_statement_extract` module,
which is not in the dependencies of `account_move`.
- The tests for bank statement processing errors was improved to match
the tests in later versions

Task-5410752
Related Task-5075610

*= co, ec, kr, us, tw, zm Currently, the `Other Expense(expense_other)` account type, introduced in saas-18.3, is missing from the Balance Sheet reports of certain `localizations`, even though it's correctly implemented in the standard reports. **Steps to reproduce:** - Install the `l10n_co_reports` and `accountant` modules. - Switch to `CO company `and navigate to Accounting > Reporting > Balance Sheet. - Ensure the `report` smart button is set to `Balance Sheet (CO)`. - Equity > Previous Years Unallocated Earnings and click the `info icon`. - Observe the formula of `balance_domain`. **Observation:** The formula does not include the `expense_other` account type. **Root Cause:** After PR [1], at [2] `expense_other` was added to the Previous Years Unallocated Earnings balance domain only in the main `account_reports` module. The corresponding localization reports mentioned above were not updated accordingly, resulting in incomplete Balance Sheet formulas. **Fix:** This commit updates the Balance Sheet report and includes the `expense_other` account type in the Previous Years Unallocated Earnings balance domain, aligning them with the standard reports. [1]: https://github.com/odoo/enterprise/pull/101591 [2]: https://github.com/odoo/enterprise/blob/316a5965e5fae83bd7d901929160c87eb28d13cf/account_reports/data/balance_sheet.xml#L205 opw-5491639 Forward-Port-Of: odoo/enterprise#105262

**PROBLEM** Swedbank requires the RfdDocAmt Element for Bankgiro account. [documentation](https://internetbank.swedbank.se/ConditionsEarchive/download?bankid=1111&id=WEBDOC-PRODE211415244). Payment batches generated by Odoo don't contains this fields, meaning they are refused by the bank. **REPRO STEPS** We can't reproduce the error the client have because it would require a valid bankgiro account. To generate the payment batch xml you have to: 1. Install l10n_se. 2. Create a vendor bank account of type bankgiro. 3. Create a vendor payment with this vendor bank account. 4. Create a batch payment and validate it. 5. There should be a xml in the chatter, you can look at it to see there is no RfdDocAmt element. opw-5427505 Forward-Port-Of: odoo/enterprise#104777

Steps to reproduce ================== - Switch to dutch - Emulate an iPhone SE viewport in the browser settings - Open a project - Switch to the gantt view - Use a custom date range -> The gantt controls are displayed on top due to the daterange format being to long | Before | After | |--------|--------| | <img width="736" height="1542" alt="image" src="https://github.com/user-attachments/assets/7c573ab1-fbf8-4f31-83ba-21d66ebc504d" /> | <img width="736" height="1542" alt="image" src="https://github.com/user-attachments/assets/62ab3d47-701e-4e2d-aaef-5c92675236cb" /> | opw-5340869 Forward-Port-Of: odoo/enterprise#105229 Forward-Port-Of: odoo/enterprise#104821

What: Previously, actions like "Create Vendor Bill" were only embedded in the main "Finance" folder. Now, these actions are also embedded directly into the specific subfolders for each journal type (e.g., "Purchase", "Sales"). All relevant actions are also kept in the parent "Finance" for general accessibility. The purchase actions are also added to the "Inbox" folder. Why: The previous behavior was inefficient. A user uploading a vendor bill to the "Purchase" folder would not see the "Create Vendor Bill" action. He would only see it when he is in the parent "Finance" folder. By embedding it by default this streamlines the process by ensuring the necessary tools are available exactly where the user is working. How: The logic is implemented within the _documents_configure_sync method of the account.journal model. This is the ideal location because it handles the complete setup of a journal for the Documents app. This ensures that actions are embedded correctly both during module installation and dynamically whenever a new journal is created by a user. Notes: - Tests were rewritten to check these embeddings on install. And were refactored to be more maintainable and cover bank statements better. - The test for importing bank statements had to be moved to a separate testing module, as it needs the `account_bank_statement_extract` module, which is not in the dependencies of `account_move`. - The tests for bank statement processing errors was improved to match the tests in later versions Task-5410752 Related Task-5075610