Daily updates from Odoo
Friday, March 27, 2026
4 changes · saas-19.2
Enhancements to existing features
This update adjusts how Odoo handles Indonesian NPWP (tax identification numbers) to accurately reflect whether a business is an individual or a company. The change ensures correct classification based on the NPWP prefix, improving data accuracy for Indonesian accounting and tax reporting. This update aligns with evolving Indonesian regulations regarding company identification.
Original PR description
For Indonesia, NPWP is distinguishable between an individual and company by prefix If an NPWP starts with 001, 002, or 003, treat it as a Company. Anything else is likely an Individual (local or foreign). For Indonesia, NPWP is distinguishable between an individual and company by prefix An NPWP must consist 16 digits How to distinguish between individual and company details: - Individual (Local) -> first two digit is province code start from 11 to 92 - Individual (Expat/Foreign) -> first digit = 0, second and third digit 07-09 - Company (Local or Foreign) -> first digit = 0, second and third digit 01-03 Task [#5915988](https://www.odoo.com/web#model=project.task&id=5915988) --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#250840
This update enhances the Taiwanese localization of Odoo by refining tax and fiscal position settings to align with local regulations and e-invoicing requirements. Specifically, it adds support for VAT exemptions and simplifies tax structures, ensuring accurate reporting and compliance.
Original PR description
This commit improves the Taiwanese localization by refining fiscal positions and their associated tax mappings to better align with local accounting practices and e-invoicing terminology. Key…
This commit improves the Taiwanese localization by refining fiscal positions and their associated tax mappings to better align with local accounting practices and e-invoicing terminology. Key changes: - Updated Chinese translations (`name@zh_TW`) for B2B/B2C fiscal positions to explicitly include e-invoices (電子發票). - Added a new fiscal position for VAT Exempt (`l10n_tw_fiscal_position_vat_exempt`). - Removed redundant purchase-specific fiscal positions (Unified Invoices, Duplicate/Triplicate Cash Register) and Deemed Sales. - Remapped purchase taxes to standard B2B/B2C fiscal positions to simplify the fiscal position structure. - Updated `original_tax_ids` and `fiscal_position_ids` across sales and purchase taxes to reflect the consolidated fiscal positions. - Fixed a typo in the invoice label for the "2% ART 11 GBRT" tax (changed "25" to "2%"). Task-6007589 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#256143 Forward-Port-Of: odoo/odoo#254826
This update allows developers to customize the creation of sale orders when using the repair module. Previously, this process couldn't be modified, but now it's designed to provide a clear point for integration, making it easier for partners to tailor the sale order creation process. This enhancement supports our strategic partnerships and expands the flexibility of the repair module.
Original PR description
**Description of the issue/feature this PR addresses:** Let the possibility to inherit the creation of a sale order based on the repair. Extract the `dict` to create the SO but also the SO (record) to maybe call some function on it. **Current behavior before PR:** The creation of sale order (on repair) could not be inherited. **Desired behavior after PR is merged:** Have 2 inherit points (used by integrators like us) --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#255781
This change adds a small amount of spacing between employee images and names in the HR module. Previously, the images and names were visually close together, which has now been improved for a cleaner and more professional look. This is a minor cosmetic update.
Original PR description
Before this PR, a spacing was missing between the employee image and the employee name. It was added by switching the noSpacing to false. | Before | After | |--------|--------| | <img width="567" height="142" alt="Screenshot 2026-03-25 at 13 35 42" src="https://github.com/user-attachments/assets/e513600c-7019-490d-bc2f-da9819ccce89" /> | <img width="567" height="142" alt="Screenshot 2026-03-25 at 13 35 31" src="https://github.com/user-attachments/assets/744f36f6-52e3-4ad3-91cc-135071c9e0c9" /> | task-5960515 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#255812