Daily updates from Odoo
Friday, July 4, 2025
4 changes · 18.0
Enhancements to existing features
In the French accounting localization, delivery dates are no longer automatically copied from the invoice date. This ensures delivery dates are entered only when users explicitly provide them, improving accuracy for business records.
Original PR description
This commit prevents the delivery date from being set to invoice date by default in French localization. We need the delivery date to be only set by the users. task-4900043 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Grouped customer invoice payments now use a PAY/XXXXX memo instead of BATCH/XXX. This avoids confusion with the separate Batch Payment feature and makes payment references clearer for accounting users.
Original PR description
Purpose ------- This improves clarity in group payment memos: the previous BATCH/XXX prefix could be misleading as it resembled the Batch Payment feature, while the generated payment was unrelated to it. Changes ------- Replaced BATCH/XXX prefix with the more generic and consistent PAY/XXXXX format. Aligns with the syntax introduced in v18 for payments without entries. How to test ------- Go to Accounting > Customers > Invoices. Select multiple posted customer invoices. Click "Action" > "Register Payment". Tick the "Group Payments" checkbox. Validate the payment. The generated memo should now use the PAY/XXXXX format instead of BATCH/XXX. Confirm that batch payment features are not affected.
This change adds checks to make sure customer phone numbers, email addresses, and website links are properly formatted before they are saved. It helps keep contact records cleaner and reduces problems caused by incorrect customer information.
Original PR description
Added validation for phone, email, and website fields on res.partner Added validation logic to ensure only properly formatted phone numbers, emails, and website URLs are accepted when creating or updating a customer/contact. Description of the issue/feature this PR addresses: Customers could be created with invalid phone, email, or website values. Current behavior before PR: No validation exists for the format of phone, email, or website fields on res.partner. Desired behavior after PR is merged: Validation is enforced for phone, email, and website fields, preventing the creation or update of a customer/contact with invalid values. I confirm I have signed the CLA and read the PR guidelines at [www.odoo.com/submit-pr]
Saudi e-invoicing journal onboarding now creates unique identifiers using each journal's code, name, company, and internal ID. This reduces duplicate setup issues and alerts existing users to re-onboard affected journals where prior identifiers may not have been unique.
Original PR description
… common name to be unique per journal Previously, the company name was used as the common name when onboarding the journal. However, the common name has to be unique. The fix changes the common name to use the journal's short code, journal name, and company name to ensure uniquness. Additionally, an improvement is applied to the serial number on journals. Previously, users inputted this field manually. Now, the system uses the journal's id as the serial number to ensure uniqueness. A post-migration script was added to notify users that they need to re-onboard their journals. This is done in case users previously onboarded journals with non-unique serial numbers. task-4797124 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#216135 Forward-Port-Of: odoo/odoo#215012