Monday, April 29, 2024
7 changes · 17.0
Enhancements to existing features
Indonesian e-Faktur exports now better reflect recent tax ID rule changes by using a person’s NIK when the NPWP field contains the placeholder value. This helps businesses generate compliant e-Faktur data with fewer manual corrections.
Original PR description
Due to recent rule changes for E-faktur, now NIK and NPWP are complement to each other. Which means now, when the person is filling in 000000000000000, e-faktur should be taking the NIK as NPWP column in e-Faktur 3815006 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The balance column text in the POS partner screen has been made more visible by increasing the text shade. This improvement makes it easier for staff to read customer credit information at a glance, reducing the risk of missing important balance details during transactions.
Original PR description
Before this commit: =========== - The balance column text on the partner screen had a low shade, diminishing its visibility. After this commit: =========== - The balance column text in the partner screen has a high shade, improving its visibility. task-3877793
The Belgian tax report posting wizard has been improved to only appear when posting closing entries for Belgian taxes. Previously, the wizard would incorrectly pop up for non-Belgian tax entries, creating unnecessary interruptions in the workflow. This fix ensures the wizard only displays when actually needed.
Original PR description
The Belgian "Post a tax report entry" wizard was modified to pop only when the closing entry corresponds to a Belgian tax. Prior to this commit, the "Post a tax report entry" wizard would pop when attempting to post a closing entry that corresponds to non-Belgian taxes. It should not pop up. task-3829124 Forward-Port-Of: odoo/enterprise#61556 Forward-Port-Of: odoo/enterprise#61223
This update adds a new tax type called "Exento" to Mexico's tax system in Odoo and improves how the system reads tax information from vendor invoices. The changes ensure that Mexican companies can properly handle exempt transactions and correctly process imported vendor bills with the new tax classification.
Original PR description
[IMP] l10n_mx : Update master data with new Exento tax and fix the XML reader issues Add a new tax, Exento, to the master data of the module l10n_mx, change the fiscal position 'Foreign Customer' and add a new tax group for Exento. Add the Exento tax recognition for the XML reader for vendor bills. task id: 3774996 Forward-Port-Of: odoo/enterprise#60107
The ESC key in the website image cropper now works like the discard button, closing the crop tool without accidentally hiding the side panel. This provides a more intuitive user experience when editing images, as users can now easily cancel cropping operations using the familiar ESC key.
Original PR description
**Current behaviour before commit:** In website when cropper is open, pressing ESC key hides side panel. **Desired behaviour after commit:** Now, pressing ESC works same as discard button. It closes the cropper and prevents hiding side panel. task-3787411 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update adds a new tax type called "Exento" to Mexico's tax system in Odoo, along with updates to fiscal positions and tax groups. The change also improves how vendor bills are processed by adding proper recognition of the Exento tax in the XML reader, ensuring accurate tax handling for Mexican businesses.
Original PR description
Add a new tax, Exento, to the master data of the module l10n_mx, change the fiscal position 'Foreign Customer' and add a new tax group for Exento. Add the Exento tax recognition for the XML reader for vendor bills. task id : 3774996 Forward-Port-Of: odoo/odoo#160624
This update enhances how the system identifies the correct business partner when processing electronic invoices (like Peppol invoices). It now uses endpoint and identification codes to find partners more accurately, following a prioritized search sequence: VAT number, endpoint/identification match, phone/email, or name. This reduces manual corrections and improves invoice processing accuracy.
Original PR description
In saas-16.2, the peppol_endpoint and peppol_eas fields were added to the partner. When importing an xml inheriting from EN16931 (Peppol Bis 3, A-NZ, E-FFF, NLCIUS, etc), use the peppol endpoint and eas to retrieve the correct partner, by passing a search domain to `_retrieve_partner` (through the `domain` argument). Hence, when retrieving the partner (using `_retrieve_partner`), we will sequentially: 1. search for a partner with a matching VAT 2. if there's a domain provided, search a partner matching the domain 3. search for a partner with a matching phone or email 4. search for a partner with a matching name If not partner is found, we create a new one. opw-3815296 Forward-Port-Of: odoo/odoo#163563 Forward-Port-Of: odoo/odoo#159742