Odoo Changelog — 2026-07-21

Tuesday, July 21, 2026

3 changes · master

Improvements(3)

Enhancements to existing features

[IMP] l10n_in_*: enhance GSTR-1 performance

PR #119477

Enterprisemasterl10n_in_edi_gstrl10n_in_reportsl10n_in_reports_gstr_posMEDIUM

GSTR-1 JSON generation now uses tax details prepared in advance on invoice lines instead of calculating them each time the file is created. This should significantly reduce waiting time for businesses that generate GSTR-1 reports with large invoice volumes.

Original PR description

Currently, when the GSTR-1 JSON is generated, we calculate and fetch the tax details at runtime. Due to this, the system takes significant time when generating JSON for a large number of invoices.

This PR proposes to precompute this computation and store it on individual lines. By doing this, we expect a reduction in JSON generation time.

task-3941950

Community PR - https://github.com/odoo/odoo/pull/268457

#GSTR-1#India localization#performance#reporting

[IMP] l10n_in_reports: support for Non ITC RC tax in GSTR-3B

PR #64864

Enterprisemasterl10n_in_reportsMEDIUM

The Indian GSTR-3B report now includes Non-ITC reverse charge tax amounts in Table 3.1(d). This helps businesses produce more complete GST return figures and reduces manual adjustments during compliance reporting.

Original PR description

With this **PR** support for Non ITC RC tax in Table 3.1(d) of GSTR-3B report has been introduced.

**task**-3973469

**Community PR** - odoo/odoo#168627

#India#GST#GSTR-3B#tax reporting

[IMP] l10n_br_*: fiscal field overrides on operation type

PR #124920

Enterprisemasterl10n_br_avataxl10n_br_avatax_salel10n_br_edi_fiscal_reformMEDIUM

Brazilian fiscal settings can now be defined on operation types, so the same product can be reused across different transaction contexts without creating duplicate product records. The system applies the most specific available setting and improves missing-data warnings to guide users toward operation type configuration when needed.

Original PR description

*: l10n_br_avatax,l10n_br_avatax_sale,l10n_br_edi_fiscal_reform

In Brazil the same physical product can have different fiscal profiles (purpose of use, source of origin, SPED type, IS taxability) depending on the nature of the transaction. Since these fields only existed on the product, users had to duplicate products per usage context (e.g. "Product X - Resale" and "Product X - Consumption").

Allow configuring them on the operation type as well. Values resolve through a priority cascade: line override operation type, then header operation type, then the document-level purpose of use, then the product. IS taxability is a tri-state selection on the operation type because a boolean could not fall through to the product value.

The missing-data banner now only warns when the whole resolution chain leaves a field empty and mentions the operation type as a way to resolve it. IS taxability is not part of the banner checks.

task-6064560

#Brazil localization#fiscal settings#operation types#tax compliance

Currently, when the GSTR-1 JSON is generated, we calculate and fetch the tax details at runtime. Due to this, the system takes significant time when generating JSON for a large number of invoices. This PR proposes to precompute this computation and store it on individual lines. By doing this, we expect a reduction in JSON generation time. task-3941950 Community PR - https://github.com/odoo/odoo/pull/268457

*: l10n_br_avatax,l10n_br_avatax_sale,l10n_br_edi_fiscal_reform In Brazil the same physical product can have different fiscal profiles (purpose of use, source of origin, SPED type, IS taxability) depending on the nature of the transaction. Since these fields only existed on the product, users had to duplicate products per usage context (e.g. "Product X - Resale" and "Product X - Consumption"). Allow configuring them on the operation type as well. Values resolve through a priority cascade: line override operation type, then header operation type, then the document-level purpose of use, then the product. IS taxability is a tri-state selection on the operation type because a boolean could not fall through to the product value. The missing-data banner now only warns when the whole resolution chain leaves a field empty and mentions the operation type as a way to resolve it. IS taxability is not part of the banner checks. task-6064560