Friday, December 12, 2025
4 changes · 17.0
New functionality added to Odoo
This update adds a new test to ensure that the Peppol status of partners is automatically updated when invoices are generated through e-commerce and linked to Peppol-based payments. This improves the accuracy of Peppol data and streamlines the process of exchanging invoices internationally. It’s a key step in supporting our international business operations.
Original PR description
When creating a SO on e-commerce leading to an automatic invoice, the invoice is automatically sent using Peppol upon the payment. This test ensures the peppol status of the partner is updated during the process. task_id: 5025176 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Resolved issues and error corrections
This update fixes an issue where the Italy e-invoicing module wasn't correctly handling zero prices on vendor bills when generating XML invoices. The fix ensures that the system now accurately reflects zero prices from the vendor bill XML, preventing incorrect pricing in the accounting system. This ensures accurate e-invoicing compliance.
Original PR description
**Steps to reproduce:** * Install the **Italy – E-invoicing (l10n_it_edi)** module. * Create a product with a non-zero cost price. * Create a **vendor bill** for an Italian vendor using the **RC…
**Steps to reproduce:** * Install the **Italy – E-invoicing (l10n_it_edi)** module. * Create a product with a non-zero cost price. * Create a **vendor bill** for an Italian vendor using the **RC fiscal position**. * Add the product with **unit price = 0**, apply **RC tax**, and set the **Origin Document Type**. * Confirm the bill and click **Send to Tax Integration** to generate the XML in the chatter. * Upload the generated XML through **Accounting → Vendors → Bills → Upload**. **Observed behavior:** * The imported bill ignores the XML value **0.00** and uses the product's default price instead. **Cause:** * The XML’s `<PrezzoUnitario>` value is mandatory and may be **0**, but the code skipped it because `0.0` evaluates as falsy in the walrus assignment. **Fix:** * Always set the parsed `PrezzoUnitario` value (including **0.0**) on the invoice line. ref: https://fex-app.com/FatturaElettronica/FatturaElettronicaBody/DatiBeniServizi/DettaglioLinee/PrezzoUnitario opw-5322187
This update improves data accuracy by adding validation for Thai VAT numbers within the Odoo system. Now, when a partner's country is set to Thailand, the system will only accept VAT numbers that meet the strict requirement of being exactly 13 digits long, ensuring data integrity.
Original PR description
This PR adds a validation method check_vat_th() to verify Thai VAT numbers. In Thailand, a VAT number must consist of exactly 13 numeric digits. For partners with country set to Thailand, the system will only allow VAT numbers that are exactly 13 digits long. Total credits go to: [Saran440](https://github.com/Saran440) `<saranl@ecosoft.co.th>` (See PR: https://github.com/odoo/odoo/pull/239164) Enterprise PR: odoo/enterprise#101905
This update corrects a test failure related to VAT number validation for Thailand. The previous test data was incorrectly formatted, now that proper validation is in place, the test passes. This ensures accurate reporting for Thai VAT transactions.
Original PR description
Following the implementation of proper validation for VAT numbers for Thailand, this now fails as the one set in the test doesn't follow the proper format. Community PR: odoo/odoo#239616 Total credits to @vin-odoo