Friday, January 9, 2026
5 changes · 19.0
Resolved issues and error corrections
This update fixes a discrepancy in how tax information is reported for Brazilian invoices impacted by a recent fiscal reform. Previously, tax details were optional, but now all required tax information must be included for XML reporting, ensuring compliance. This change impacts the l10n_br_edi_fiscal_reform module.
Original PR description
Before the fiscal reform, we deliberately avoid sending back informative taxes for service invoices because they may change depending on how and when the invoice is paid and they only need to appear on the XML optionally. New informative taxes specific to the fiscal reform are required to appear on the XML and therefore we must always send them. task-5450142 Forward-Port-Of: odoo/enterprise#103599
This update fixes a bug in the Italian VAT reporting tests that was causing incorrect carryover calculations. The fix ensures sales tax is applied to customer invoices and purchase tax to vendor invoices, resolving a previous error that led to miscalculated credits and debits. This ensures accurate financial reporting for Italian businesses.
Original PR description
The carryover tests were failing because they incorrectly used sales tax (tag 4v for output VAT) on vendor invoices (in_invoice type). Sales tax should only be used on customer invoices (out_invoice type). This caused VP14 to calculate as a credit instead of a debit, making the carryover go to VP8 (previous period credit) instead of VP7 (previous period debt), which caused test failures. The fix adds an invoice_type parameter to the test helper method and uses: - 'out_invoice' for sales tax (4v) tests → VP14 debit carryover to VP7 - 'in_invoice' for purchase tax (4a) tests → VP8 credit carryover Also updated test docstrings to clarify the 100.00 EUR carryover threshold. opw-5357719
This update improves the speed of the sales reconciliation feature in Odoo Enterprise. Previously, the system fetched all sales orders for a partner each time the reconciliation was opened. Now, it efficiently retrieves order counts initially, reducing unnecessary database operations and significantly speeding up the process for users.
Original PR description
Before this commit: We fetch all the sale orders for a partner every time we open unfold lines. This commit aims to reduce orm operations by fetching the sale orders counts one time upon loading the bank reconciliation for the first time or changing the pager. task-5241035
This update fixes a bug preventing credit notes created with the DIAN support document journal from successfully sending required documents. The issue stemmed from an incorrect namespace being used, which caused errors during the document generation process. This change ensures proper DIAN document transmission for credit notes.
Original PR description
**PROBLEM** When trying to create a credit notes using a journal with support documents, there is a lot of errors when sending the dian documents. **STEP TO REPRODUCE** 1. setup DIAN (knowledge page https://www.odoo.com/odoo/knowledge/5/knowledge/23114). 2. create a vendor bill, and then create a credit note with the DIAN support document journal. 3. Confirm and click on send DIAN documents. **CAUSE** `_get_document_nsmap()` uses the wrong namespace for credit notes. opw-5378540
This update resolves a bug that prevented users from correctly accessing and editing sign templates linked to certain item roles. The fix corrects record rules, ensuring proper access rights are granted when opening or modifying these templates. This improves the usability and reliability of the sign template functionality.
Original PR description
Fix record rules on sign.item.role that prevented users from reading and creating item roles linked to accessible templates, causing access errors when opening or editing sign templates. task-5428886