Daily updates from Odoo
Tuesday, November 4, 2025
12 changes · master
Enhancements to existing features
This update improves how employee benefits, such as Belgian eco vouchers, are handled across contracts, salary offers, and payslips. It helps payroll teams avoid unwanted automatic copying of benefit values while making salary rule settings more flexible and reliable.
Brazilian invoices, sales orders, and point-of-sale orders for foreign customers now include the required export details when sent to Avalara and EDI services. This helps ensure export-of-goods transactions are correctly identified and processed for Brazilian localization compliance.
Original PR description
Purpose: By allowing the user to add a foreign partner as a customer on an invoice, we will need to include the export of goods information in the requests sent to Avalara and EDI. The required information under goods to be sent for export invoices are: - header.goods.idDest = 3 (indicates export operation) - header.goods.exportInfo.shippingState (indicates the state the products will ship from) - header.goods.exportInfo.place (incoterm_location) - header.locations.entity.address.neighborhood = "EXTERIOR" - header.locations.entity.address.zipcode = "99999999" - header.locations.entity.address.cityCode = "9999999" - header.locations.entity.address.cityName = "EXTERIOR" - header.locations.entity.address.state = "EX" - header.locations.entity.federalTaxId = "9999999999" task-4802462
Warehouse teams can now print Starshipit shipping labels in batches, reducing repetitive work when processing multiple deliveries. Labels also include the sales order reference in the order number, making it easier to match each label to the correct customer order.
Original PR description
Adds two improvements to the usability of the module by supporting printing starshipit labels in batch, and also adding the SO reference to the order number to more easily match the label with it. task-4821727 Forward-Port-Of: odoo/enterprise#91405
Account lists now show the current applicable fiscal rate and fiscal category, making review work easier. Fiscal report warnings about multiple rates are more accurate because they only consider accounts used in the selected period, and Belgian chart data was corrected to remove a duplicate rate assignment.
Original PR description
[IMP] account_fiscal_categories: enhance list view of account_account ====================================================== With this commit, we add a new field `current_rate` in `account.account`.…
[IMP] account_fiscal_categories: enhance list view of account_account ====================================================== With this commit, we add a new field `current_rate` in `account.account`. This `current_rate` is a non-stored compute field, used to compute the current applicable rate on the given account. This `current_rate` and `fiscal_category_id` has been introduced in the list view of `account.account`. [IMP] account_fiscal_categories: enhance multiple rate warning in fiscal report =========================================================== Before this commit, the "multiple rate" warning was shown even when no entries for accounts with multiple rates existed in the selected period. This happened because all accounts were considered for multiple rates, regardless of journal entries in that period. After this commit, only accounts with entries in the selected period are considered for the "multiple rates" warning. The warning is now clickable, redirecting the user to the accounts having multiple rates. [FIX] l10n_be_fiscal_categories: remove redundant rate on CoA ================================================= This commit removes the redundant fiscal rate on account-613311. Both fiscal categories 1206 and 1073 were assigned to this account, resulting in two rates. Only 1073 should be there. ref-https://github.com/odoo/enterprise/commit/f2579a80833ac129b2f21613b93c4e3203646a1b **task**-5163392 ----------------------- Forward-Port-Of: odoo/enterprise#97324
The Belgian POS blackbox integration now prompts users to update their IoT device so it can support an upcoming queued communication flow. This prepares retailers for a more reliable connection between POS terminals and the fiscal blackbox in the next update.
Original PR description
This commit is the first of two which will introduce a queue mechanism in the communication between the POS and the blackbox. This commit adds an action to the iot and invites users to update their iot to be prepared for the next commit which will effectively add the queue mechanism and use the new action. Second part: https://github.com/odoo/enterprise/pull/90747 Forward-Port-Of: odoo/enterprise#96904 Forward-Port-Of: odoo/enterprise#96639
All IoT-related code has been brought together into the Enterprise IoT module, simplifying where these capabilities are maintained. This should make future improvements and support for connected devices, point of sale hardware, and self-ordering integrations more consistent.
Original PR description
As it was decided to move all IoT related code to Enterprise, this commit merges back `iot_base` into `iot`. odoo/odoo#231746
This update makes the small buttons in the top menu bar show clearer visual states, such as hover, active, and dropdown behavior. It creates a more consistent experience across apps, light and dark themes, and enterprise navigation areas.
Original PR description
*: documents, hr_contract_salary, hr_payroll, industry_fsm_stock, mail_enterprise, mrp_workorder, stock_barcode, test_l10n_be_hr_payroll, voip, web_studio, website_enterprise This PR improves the…
*: documents, hr_contract_salary, hr_payroll, industry_fsm_stock, mail_enterprise, mrp_workorder, stock_barcode, test_l10n_be_hr_payroll, voip, web_studio, website_enterprise This PR improves the different button states within the `.o_menu_systray element` - requires https://github.com/odoo/odoo/pull/227858 | ///////// | Master | This PR | |--------|--------|--------| | AppSwitcher (**Light**) | <img width="489" height="43" alt="image" src="https://github.com/user-attachments/assets/39638af5-3bf4-4489-bd28-d409e74130a7" /> | <img width="493" height="49" alt="image" src="https://github.com/user-attachments/assets/0ae1a53f-457d-408e-847c-e4cbe187b6d1" /> | | AppSwitcher (**Dark**) | <img width="487" height="40" alt="image" src="https://github.com/user-attachments/assets/926c499f-18a0-4e8b-b71c-50ff0dd2d73a" /> | <img width="493" height="47" alt="image" src="https://github.com/user-attachments/assets/3983d593-2cdc-4184-a325-36a4bda4dd03" /> | | In App (**Light**) | <img width="494" height="47" alt="image" src="https://github.com/user-attachments/assets/c82bd674-00c3-47e6-9fd6-7b8abb29c873" /> | <img width="475" height="46" alt="image" src="https://github.com/user-attachments/assets/7d3829ae-17cf-42b0-940f-5b3eb7b57209" /> | | In App (**Dark**) | <img width="490" height="44" alt="image" src="https://github.com/user-attachments/assets/e1583d60-1ec9-4954-b63a-d6adcf55c070" /> | <img width="482" height="45" alt="image" src="https://github.com/user-attachments/assets/fd64aba7-921b-4d4e-97f5-c5e36de5ebf3" /> | | Front-end (**Light**) | <img width="487" height="48" alt="image" src="https://github.com/user-attachments/assets/b7421589-cb20-447c-9b81-80dcb4f00b66" /> | <img width="507" height="48" alt="image" src="https://github.com/user-attachments/assets/a7bdc284-e949-481c-a20d-849221cebee7" /> | | Front-end (**Dark**) | <img width="502" height="47" alt="image" src="https://github.com/user-attachments/assets/aefb1260-6a0a-4c69-a4db-d30865427b91" /> | <img width="505" height="49" alt="image" src="https://github.com/user-attachments/assets/0411a78f-807f-42bb-b88c-3fb4b65fb67f" /> | --------- Currently, these buttons are either: - `<button>` elements with only the .btn class, which does not provide a complete set of CSS properties. - `.dropdown-toggle` elements with an inherited background-color, which ends up being the transparent background set on the `<nav>` element. This commit harmonizes these approaches into a single one, aligned with the implementation used in .o_menu_sections. This increases consistency and also improves the accessibility of these items. task-5098241
This update adds a dedicated PDF version of Mexican payroll CFDI documents, making it easier for companies to generate and share compliant payroll receipts. It improves payroll reporting and presentation for employees and administrators using Mexico payroll localization.
Original PR description
Forward-Port-Of: odoo/enterprise#94551
Brazilian point-of-sale invoicing now uses updated NFC-e QR code links required by several states. This helps prevent invoice issuing errors caused by outdated links when sending tax and goods invoice requests through Avalara.
Original PR description
In This PR:
- Several states have updated their NFC-e QR-code URLs, which caused errors when issuing invoices due to invalid or outdated links. This commit updates the 'nfceQrCode' parameter in Avalara requests ('calculate-tax' and 'submit-invoice-goods') to ensure the correct QR-code links are used.
task- 5115845
Forward-Port-Of: odoo/enterprise#95726Salary adjustments can now be linked to a beneficiary bank account, ensuring payments are directed to the correct account in payment reports. The beneficiary details are also shown on payslips, giving employees and payroll teams clearer payment information.
Original PR description
This commit introduces the concept of a beneficiary for salary adjustments. A bank account can now be linked to an adjustment, so that the adjustment payment is directed to it in the payment report and also displayed on the payslip. Task: 5040786
Hong Kong payroll declaration forms now include chatter, making it easier for users to follow discussions and track activity directly on the reports. This improves collaboration and visibility for teams managing local payroll declarations based on user feedback.
Original PR description
Based on HK feedback, chatter is added on their declaration forms task:5067386
Accounting reports can now include multiple text-based columns, making it easier to present items such as tax box numbers. This improves clarity for VAT reports in countries like Germany, South Africa, and North Macedonia without changing core reporting workflows.
Original PR description
Add a simple text engine to reports to be able to add multiple text columns. This is useful for reports that have box numbers eg. DE/ZA/MK VAT Reports