Odoo Changelog — 2025-08-22

Friday, August 22, 2025

2 changes · 18.0

Improvements(2)

Enhancements to existing features

[IMP] l10n_ubl_pint: new PINT rules; improve existing contraints

Core18.0l10n_anz_ubl_pintl10n_my_ubl_pintl10n_sg_ubl_pintMEDIUM

This update strengthens electronic invoice validation for Australia, New Zealand, Malaysia, and Singapore so invoices are less likely to be rejected for missing tax or address details. It adds safer fallback values when tax IDs are absent and checks required seller and buyer address information for Singapore tax categories.

Original PR description

Description of the issue/feature this PR addresses:

- AU&NZ: Current behavior is that when VAT is not set on the partner, the tax category code defaults to zero. This becomes problematic with certain rules (e.g. the tax totals of tax category code 'O' should have amount of zero, but current code can set this value to something other than zero). The change focuses on edge cases when VAT of partner is not set. Changes are not related to the Q2 2025 release changes.
- MY: Added fallback for <cac:PartyTaxScheme> to always have <cbc:CompanyID>. Currently breaks if the partner does not have VAT set. Changes are not related to the Q2 2025 release changes.
- JP: No changes are made.
- SG: Invoice with taxes of certain tax category codes must have seller and buyer street address and post code. Added constraint to make sure they are set. New PINT SG rule adds one more tax category code (Standard Rate, SRRC). New code is added to `ubl_cii_tax_category_code`

---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

#e-invoicing#PINT#tax-compliance#Australia-New Zealand#Malaysia#Singapore

[IMP] l10n_gt_edi: prevent move fields computation on install

PR #92881

Enterprise18.0l10n_gt_ediMEDIUM

The Guatemalan EDI module now avoids heavy invoice data calculations during installation, reducing the risk of memory errors on large databases. It also no longer installs automatically with the base Guatemalan localization, giving businesses more control over enabling it.

Original PR description

This commit adds `_auto_init` to the `account.move` object in the Guatemalan EDI that prefills all computed stored fields in the move object with null values. This prevents computation on those fields when installing the module, and also prevents MemoryError on large databases.

task-5031330

#Guatemala#EDI#installation#performance

Description of the issue/feature this PR addresses: - AU&NZ: Current behavior is that when VAT is not set on the partner, the tax category code defaults to zero. This becomes problematic with certain rules (e.g. the tax totals of tax category code 'O' should have amount of zero, but current code can set this value to something other than zero). The change focuses on edge cases when VAT of partner is not set. Changes are not related to the Q2 2025 release changes. - MY: Added fallback for <cac:PartyTaxScheme> to always have <cbc:CompanyID>. Currently breaks if the partner does not have VAT set. Changes are not related to the Q2 2025 release changes. - JP: No changes are made. - SG: Invoice with taxes of certain tax category codes must have seller and buyer street address and post code. Added constraint to make sure they are set. New PINT SG rule adds one more tax category code (Standard Rate, SRRC). New code is added to `ubl_cii_tax_category_code` --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

This commit adds `_auto_init` to the `account.move` object in the Guatemalan EDI that prefills all computed stored fields in the move object with null values. This prevents computation on those fields when installing the module, and also prevents MemoryError on large databases. task-5031330