Odoo Changelog — 2025-10-10

Friday, October 10, 2025

2 changes · 17.0

Bug Fixes(2)

Resolved issues and error corrections

[FIX] l10n_es_edi_verifactu: select the right "Clave Regimen" based on taxes

Core17.0l10n_es_edi_verifactuMedium

Spanish Veri*Factu invoices now choose the correct regime key when export or exempt taxes are used. This prevents affected invoices from being marked as general regime operations when they should be classified as exports, improving compliance accuracy.

Original PR description

### Steps to reproduce:
- Install l10n_es_edi_verifactu and switch too Spanish company
- Create an invoice for a partner outside Spain (or with the tax "0% EX G")
- Check the "Veri*Factu Regime Key" under the page "Veri*Factu"
- It should be "Export" (02) but it's "General Regime Operation" (01)

### Cause:
`_l10n_es_edi_verifactu_get_suggested_clave_regimen()` is called on the tax "0% EX G". The line
```taxes.filtered(lambda tax: (tax.l10n_es_type not in main_tax_types or tax._l10n_es_edi_verifactu_get_applicability() != forced_tax_applicability))```
doesn't do what the comment says: remove the main taxes with a different applicability.

### Solution:
Change the `!=` to `==` so that the line does the same thing as the comment.

opw-5071665

#Spain#VeriFactu#invoicing#taxes#compliance

[FIX] l10n_in_reports_gstr: handle purchase journal lookup in multi-company tax unit

PR #96838

Enterprise17.0l10n_in_reports_gstrMedium

GST return creation now looks for a valid purchase journal across all companies in a tax unit, instead of only the main company. This prevents setup-related failures when the main company lacks a purchase journal but another company in the tax unit has one configured.

Original PR description

Before this PR:
- The system searched for a purchase journal only in `company_id`.
- In a tax unit with multiple companies, if the main company had no purchase journal configured, record creation failed with a 'NOT NULL constraint violated' error.

After this PR:
- The journal search now checks all companies in `company_ids` (or falls back to `company_id`),
- allowing the system to find a valid purchase journal across the tax unit.

OPW: 5159518

#India GST#multi-company#tax unit#purchase journal

### Steps to reproduce: - Install l10n_es_edi_verifactu and switch too Spanish company - Create an invoice for a partner outside Spain (or with the tax "0% EX G") - Check the "Veri*Factu Regime Key" under the page "Veri*Factu" - It should be "Export" (02) but it's "General Regime Operation" (01) ### Cause: `_l10n_es_edi_verifactu_get_suggested_clave_regimen()` is called on the tax "0% EX G". The line ```taxes.filtered(lambda tax: (tax.l10n_es_type not in main_tax_types or tax._l10n_es_edi_verifactu_get_applicability() != forced_tax_applicability))``` doesn't do what the comment says: remove the main taxes with a different applicability. ### Solution: Change the `!=` to `==` so that the line does the same thing as the comment. opw-5071665

Before this PR: - The system searched for a purchase journal only in `company_id`. - In a tax unit with multiple companies, if the main company had no purchase journal configured, record creation failed with a 'NOT NULL constraint violated' error. After this PR: - The journal search now checks all companies in `company_ids` (or falls back to `company_id`), - allowing the system to find a valid purchase journal across the tax unit. OPW: 5159518