Odoo Changelog — 2026-03-07

Saturday, March 7, 2026

2 changes · 19.0

Bug Fixes(2)

Resolved issues and error corrections

[FIX] base_vat: ensure valid NRI GSTINs are accepted

Core19.0base_vat

Odoo now correctly accepts valid GSTIN tax IDs for certain Non-Resident Indian taxpayers. This prevents companies from being blocked when saving official, verifiable tax IDs in Indian localization setups.

Original PR description

Currently, valid GSTINs for certain Non-Resident taxpayers are rejected. **Steps to reproduce:** - Install the `l10n_in` module. - Navigate to Settings > Users & Companies > Companies. - Open `IN…

Currently, valid GSTINs for certain Non-Resident taxpayers are rejected.

**Steps to reproduce:**
- Install the `l10n_in` module.
- Navigate to Settings > Users & Companies > Companies.
- Open `IN Company` and set `Tax ID` to `9922JPN29001OSU` and try to `save`.

**Error:**
`The VAT number [9922JPN29001OSU] for partner [IN Company] does not seem to be valid.` 
`Note: the expected format is 12AAAAA1234AAZA`

The system rejects the GSTIN, although it is valid and verifiable on the 
official GST portal: https://services.gst.gov.in/services/searchtp

**Root cause:**
At [2], the GSTIN validation regex for NRI taxpayers only supports formats 
ending with `NRX` (X = any alphanumeric character). However, certain valid 
GSTINs follow a different structure and are not matched by the existing regex.

**Fix:**
This commit ensures that valid NRI GSTIN formats are accepted during validation.

Confirm with IN PO.

[1]:
https://services.gst.gov.in/services/searchtp

[2]:
https://github.com/odoo/odoo/blob/5e59f4b3def44aa84c06ba4c2ed34bf2e8da928f/addons/base_vat/models/res_partner.py#L712-L723

opw-5956299

Forward-Port-Of: odoo/odoo#252647
Forward-Port-Of: odoo/odoo#251760

#India#GSTIN#tax ID#non-resident

[FIX] l10n_co_dian: prevent crash when printing duplicated support document

PR #109907

Enterprise19.0l10n_co_dian

This update fixes a bug that caused printing of vendor bills using DIAN support documents to fail. The issue stemmed from a report template that incorrectly processed duplicate bills, leading to a parsing error. The fix ensures that printing only occurs when a valid DIAN attachment exists, improving printing reliability.

Original PR description

**Steps to reproduce:**
* Install the **l10n_co_dian** module.
* Enable DIAN 2.1 operation mode: **Support Documents** in settings.
* Create a vendor bill using a **DIAN support document** journal.
* Confirm the vendor bill.
* Click **Print**.

**Observed behavior:**
* Printing fails with `ValueError: can only parse strings`.

**Cause:**
* The report template unconditionally called `_l10n_co_dian_get_extra_invoice_report_values()`, which parses `l10n_co_dian_attachment_id.raw` via `etree.fromstring()`.
* On duplicated bills, `l10n_co_dian_document_ids` (and thus the computed `l10n_co_dian_attachment_id`) is empty, so `.raw` is `False`.

**Fix:**
* Wrap the QR code / CUFE / signing section in the report template with `t-if='o.l10n_co_dian_attachment_id'` so it is only rendered when the DIAN attachment exists.

opw-5930173

Forward-Port-Of: odoo/enterprise#108645

#DIAN#support documents#printing

Currently, valid GSTINs for certain Non-Resident taxpayers are rejected. **Steps to reproduce:** - Install the `l10n_in` module. - Navigate to Settings > Users & Companies > Companies. - Open `IN Company` and set `Tax ID` to `9922JPN29001OSU` and try to `save`. **Error:** `The VAT number [9922JPN29001OSU] for partner [IN Company] does not seem to be valid.` `Note: the expected format is 12AAAAA1234AAZA` The system rejects the GSTIN, although it is valid and verifiable on the official GST portal: https://services.gst.gov.in/services/searchtp **Root cause:** At [2], the GSTIN validation regex for NRI taxpayers only supports formats ending with `NRX` (X = any alphanumeric character). However, certain valid GSTINs follow a different structure and are not matched by the existing regex. **Fix:** This commit ensures that valid NRI GSTIN formats are accepted during validation. Confirm with IN PO. [1]: https://services.gst.gov.in/services/searchtp [2]: https://github.com/odoo/odoo/blob/5e59f4b3def44aa84c06ba4c2ed34bf2e8da928f/addons/base_vat/models/res_partner.py#L712-L723 opw-5956299 Forward-Port-Of: odoo/odoo#252647 Forward-Port-Of: odoo/odoo#251760

**Steps to reproduce:** * Install the **l10n_co_dian** module. * Enable DIAN 2.1 operation mode: **Support Documents** in settings. * Create a vendor bill using a **DIAN support document** journal. * Confirm the vendor bill. * Click **Print**. **Observed behavior:** * Printing fails with `ValueError: can only parse strings`. **Cause:** * The report template unconditionally called `_l10n_co_dian_get_extra_invoice_report_values()`, which parses `l10n_co_dian_attachment_id.raw` via `etree.fromstring()`. * On duplicated bills, `l10n_co_dian_document_ids` (and thus the computed `l10n_co_dian_attachment_id`) is empty, so `.raw` is `False`. **Fix:** * Wrap the QR code / CUFE / signing section in the report template with `t-if='o.l10n_co_dian_attachment_id'` so it is only rendered when the DIAN attachment exists. opw-5930173 Forward-Port-Of: odoo/enterprise#108645