Tuesday, November 25, 2025
5 changes · 19.0
Enhancements to existing features
Saudi Arabia electronic invoicing now supports invoices dated earlier than the posting time. This aligns the confirmation date sent to ZATCA with the invoice date in Odoo, reducing mismatches for businesses that need to backdate invoices.
Original PR description
Previously, `l10n_sa_confirmation_datetime` represented the time where the invoice was posted, that meant that we could not backdate invoices, since it would cause disparity between what zatca receives and what we consider in odoo (i.e. `invoice_date`) This commit allows us to set the date component of `l10n_sa_confirmation_datetime` to the `invoice_date` so we can safely backdate invoices. task-5009969 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#237191 Forward-Port-Of: odoo/odoo#229517
This update enhances account reports to ensure they only display journals relevant to the currently selected company when multi-company accounting is enabled. Previously, reports could inadvertently include data from other companies' ledgers. This change improves report accuracy and simplifies the user experience for businesses managing multiple companies.
Original PR description
When multi-company, if multi-ledger is visible to one company, exclude journals of other companies when opening the report. task-5180393
This update enhances the multi-company ledger feature by preventing confusion when multiple companies are selected. It now includes the company name in the journal selection options, making it easier to manage and understand which companies are associated with a particular ledger.
Original PR description
* When a company is selected on multi-ledger, exclude other companies journal from excluded journals view. * When multi-ledger is visible for all companies, add the company name to the tags list and autocomplete options of the excluded journals to avoid confusion. task-5180393 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update introduces new tax groups for AR withholdings and perceptions, enhancing tax tracking accuracy. By creating distinct groups for withholdings and aligning with existing sales/purchase structures, this change simplifies tax reporting and improves data management. It also corrects naming conventions for key accounts.
Original PR description
Update id and tax groups on tax csv files. Before this change all the perceptions and withholdings were in the same tax group. New withholding tax groups are created on…
Update id and tax groups on tax csv files. Before this change all the perceptions and withholdings were in the same tax group. New withholding tax groups are created on addons/l10n_ar_withholding/data/template/account.tax.group-ar_base.csv and addons/l10n_ar_withholding/data/template/account.tax.group-ar_ex.csv 1) Replace/unify "ARBA" with "PBA" and "Provincia de Buenos Aires (P. Buenos Aires)" 2) Replace/unify "CABA" with "CABA" and "Ciudad Autónoma de Buenos Aires" 3) Multiply the tax groups for AR withholdings taxes: a) To improve tax tracking. Currently, all withholdings are grouped into a single group, making it very difficult to retrieve all taxes related to a specific withholding. The tax group concept fits this need well. b) Aligns with how tax groups are structured for sales/purchases. c) Also, the current single withholding group is incorrectly named "VAT Withholding". 4) Fix the name of the generic account from "Default VAT Payable/Receivable Account" to "Default Tax Payable/Receivable Account" Task Adhoc side: 57644 Task Latam side: 1361 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update improves the HTML editor's syntax highlighting by adding a dedicated read-only component, ensuring highlighting is visible even when the editor is in read-only mode. It also refactors the underlying component structure for better efficiency and maintainability, addressing several related improvements and bug fixes.
Original PR description
The syntax highlighting plugin cleans itself up on save so the `pre` is not dependent on Prism's css. But we still want to see the highlighting in readonly mode, so this adds a readonly version of the component in order to parse the `pre` in readonly as well. This also refactors the syntax highlighting embedded component so it uses an embedded state instead of reinventing it with `commitToHost`. task-5159286 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr