Odoo Changelog — 2026-05-14

Thursday, May 14, 2026

3 changes · master

Bug Fixes(3)

Resolved issues and error corrections

[FIX] sale_subscription: fix TypeError

Enterprisemastersale_subscriptionMEDIUM

This update resolves a technical issue preventing v19.1 upgrades of subscription orders. The problem stemmed from a comparison between a boolean value and a date field during invoice calculation, causing an error. This fix ensures correct invoice generation for subscription orders.

Original PR description

**Steps-to-Reproduce** - In v19, install subscriptions. - create new subscription + service product with allow one time sale enabled. - make a SO with that product,any reccuring plan and any end…

**Steps-to-Reproduce**
- In v19, install subscriptions.
- create new subscription + service product with allow one time sale enabled.
- make a SO with that product,any reccuring plan and any end date. 
```
id |  name  | subscription_state | next_invoice_date |  end_date  
----+--------+--------------------+-------------------+------------
  1 | S00001 | 1_draft            |                   | 2026-05-02
```

- confirm the SO
```
 id |  name  | subscription_state | next_invoice_date |  end_date  
----+--------+--------------------+-------------------+------------
  1 | S00001 | 3_progress         | 2026-05-01        | 2026-05-02
```
- remove its recurring plan (some product sold for months for testing then converted to one time sale )
```
 id |  name  | subscription_state | next_invoice_date |  end_date  
----+--------+--------------------+-------------------+------------
  1 | S00001 | 3_progress         |                   | 2026-05-02
```

- upgrade to v19.1 will fail or opening sales > To Invoice > Orders To Invoice gives this error or add amount_to_invoice in list view using studio to produce in v19 :
```
File "/home/odoo/odoo18/enterprise/sale_subscription/models/sale_order_line.py",
 line 175, in _compute_amount_to_invoice
    and (not order.end_date or order.next_invoice_date < order.end_date)
                               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
TypeError: '<' not supported between instances of 'bool' and 'datetime.date'
```

- upgrade failing for v19.1 because amount_to_invoice added to list view [here](https://github.com/odoo/odoo/commit/427232efd121410380b62acf4fd2e9ee369e6542#diff-48cb4309a6006f91b2b40e4c1049860218d419fce1782c7dcc278329803129caR193-R213).

upg - [4220658](https://upgrade.odoo.com/odoo/upgrade.request/4220658)
opw - [6128033](https://www.odoo.com/odoo/project/70/tasks/6128033)

Forward-Port-Of: odoo/enterprise#116477
Forward-Port-Of: odoo/enterprise#115976

#subscriptions#invoice#error

[FIX] l10n_cz_reports_2025: correct values of discount lines in vies report

PR #117361

Enterprisemasterl10n_cz_reportsMEDIUM

This update fixes an issue where discount lines in Czech VAT reports were incorrectly calculating values. The previous method used absolute values, leading to inflated report totals. The fix now correctly handles negative discount amounts, ensuring accurate reporting of VAT liabilities. This ensures compliance with Czech regulations.

Original PR description

Step to reproduce:
- install l10n_cz_reports_2025 and switch to cz company
- create a invoice, with cz company ( as partner), of 100.
- when adding products, add "Transaction code" (optional fields) to "Goods"
- Add discount line, set to -10, add "Transaction code" in this line too.
- confirm it

Observation:
- invoice is 90$
- open vies summary report for this year
- value turn out to 110

Cause:
- commit [1](https://github.com/odoo/enterprise/commit/892268c44b1bbc838a9f03ef36a079bfff625ca6) converts every balance to +ve and only negate it, in case of refund
- in case of discount lines, price is -ve, ABS() turn it to +ve and value comes out to be wrong

Fix:
- instead of applying ABS() directly, we flip the signs only for out_* moves,
in short when a account is credited, its balance is < 0 then we flip its sign

opw- 5979262

Forward-Port-Of: odoo/enterprise#117038
Forward-Port-Of: odoo/enterprise#113087

#reporting#vat#czech

[FIX] l10n_no_reports: fix VAT declaration XML validation errors

PR #117329

Enterprisemasterl10n_noMEDIUM

This update corrects errors in the Norwegian VAT XML export that were preventing successful validation by the Skatteetaten tax authority. The changes ensure the XML adheres to strict government rules regarding decimal formatting, rounding, and required legal notes, allowing VAT returns to be submitted correctly.

Original PR description

Before commit:
The Norwegian VAT XML export fails Skatteetaten validation due to incorrect
decimal formatting, mathematical rounding mismatches between base and tax
amounts, missing mandatory legal notes, and invalid KID number formats.

Fix:
To strictly follow Skatteetaten validation rules for the Norway VAT XML, the
following changes were implemented:
- Ensured standard rates drop the decimal (e.g, `25.0` to `25`), and formatted 
  fractional rates like `11.11` to `11,11` in XML.
- Rounded down the `tax_amount` to align precisely with government mathematical
  expectations.
- `base_amount` converted into absolute value to ensuring the calculation
  (`base * rate = tax`) resolves perfectly.
- Add the mandatory `<merknad>` explaining the reverse charge method for codes
  81, 83, 86, 88, and 91.
- Clean the `company_kid` by safely stripping the 'NO' prefix, and 'MVA' suffix.

Expect:
The generated XML payload now adheres perfectly to Skatteetaten's strict
structural and mathematical rules, allowing the VAT return to pass government
validations successfully.

Related Community PR: https://github.com/odoo/odoo/pull/258390

Task-6033027

Forward-Port-Of: odoo/enterprise#117168
Forward-Port-Of: odoo/enterprise#110792

#vat#norway#tax#xml#compliance

**Steps-to-Reproduce** - In v19, install subscriptions. - create new subscription + service product with allow one time sale enabled. - make a SO with that product,any reccuring plan and any end date. ``` id | name | subscription_state | next_invoice_date | end_date ----+--------+--------------------+-------------------+------------ 1 | S00001 | 1_draft | | 2026-05-02 ``` - confirm the SO ``` id | name | subscription_state | next_invoice_date | end_date ----+--------+--------------------+-------------------+------------ 1 | S00001 | 3_progress | 2026-05-01 | 2026-05-02 ``` - remove its recurring plan (some product sold for months for testing then converted to one time sale ) ``` id | name | subscription_state | next_invoice_date | end_date ----+--------+--------------------+-------------------+------------ 1 | S00001 | 3_progress | | 2026-05-02 ``` - upgrade to v19.1 will fail or opening sales > To Invoice > Orders To Invoice gives this error or add amount_to_invoice in list view using studio to produce in v19 : ``` File "/home/odoo/odoo18/enterprise/sale_subscription/models/sale_order_line.py", line 175, in _compute_amount_to_invoice and (not order.end_date or order.next_invoice_date < order.end_date) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ TypeError: '<' not supported between instances of 'bool' and 'datetime.date' ``` - upgrade failing for v19.1 because amount_to_invoice added to list view [here](https://github.com/odoo/odoo/commit/427232efd121410380b62acf4fd2e9ee369e6542#diff-48cb4309a6006f91b2b40e4c1049860218d419fce1782c7dcc278329803129caR193-R213). upg - [4220658](https://upgrade.odoo.com/odoo/upgrade.request/4220658) opw - [6128033](https://www.odoo.com/odoo/project/70/tasks/6128033) Forward-Port-Of: odoo/enterprise#116477 Forward-Port-Of: odoo/enterprise#115976

Step to reproduce: - install l10n_cz_reports_2025 and switch to cz company - create a invoice, with cz company ( as partner), of 100. - when adding products, add "Transaction code" (optional fields) to "Goods" - Add discount line, set to -10, add "Transaction code" in this line too. - confirm it Observation: - invoice is 90$ - open vies summary report for this year - value turn out to 110 Cause: - commit [1](https://github.com/odoo/enterprise/commit/892268c44b1bbc838a9f03ef36a079bfff625ca6) converts every balance to +ve and only negate it, in case of refund - in case of discount lines, price is -ve, ABS() turn it to +ve and value comes out to be wrong Fix: - instead of applying ABS() directly, we flip the signs only for out_* moves, in short when a account is credited, its balance is < 0 then we flip its sign opw- 5979262 Forward-Port-Of: odoo/enterprise#117038 Forward-Port-Of: odoo/enterprise#113087

Before commit: The Norwegian VAT XML export fails Skatteetaten validation due to incorrect decimal formatting, mathematical rounding mismatches between base and tax amounts, missing mandatory legal notes, and invalid KID number formats. Fix: To strictly follow Skatteetaten validation rules for the Norway VAT XML, the following changes were implemented: - Ensured standard rates drop the decimal (e.g, `25.0` to `25`), and formatted fractional rates like `11.11` to `11,11` in XML. - Rounded down the `tax_amount` to align precisely with government mathematical expectations. - `base_amount` converted into absolute value to ensuring the calculation (`base * rate = tax`) resolves perfectly. - Add the mandatory `<merknad>` explaining the reverse charge method for codes 81, 83, 86, 88, and 91. - Clean the `company_kid` by safely stripping the 'NO' prefix, and 'MVA' suffix. Expect: The generated XML payload now adheres perfectly to Skatteetaten's strict structural and mathematical rules, allowing the VAT return to pass government validations successfully. Related Community PR: https://github.com/odoo/odoo/pull/258390 Task-6033027 Forward-Port-Of: odoo/enterprise#117168 Forward-Port-Of: odoo/enterprise#110792