This update adds support for Belgium's CCT90 non-recurring results-based bonus scheme in payroll. It helps employers calculate and process these bonuses more accurately within Belgian payroll workflows.

task-4609727

This update adjusts how dropdown state is handled in the Gantt view, helping the interface behave more consistently. It is a small usability improvement for teams using planning or scheduling views.

Changes to a Mexico electronic invoicing setting are now recorded in the activity log. This helps businesses notice accidental changes to a setting that can affect the fiscal structure of generated CFDI documents.

Because the field l10n_mx_edi_cfdi_to_public affects the structure of the cfdi generated and this has a fiscal impact the field was made tracked so that if anyone by error enables or disables this field a log note is generated informing this event

Belgian CP200 payroll now supports recording salary advances separately and automatically recovering them on the regular monthly payslip. This makes payroll clearer for HR teams and reduces confusion by renaming the deduction to “Salary Advance Recovery.”

This commit improves how salary advances are managed. Now, there is a new structure type within the CP200 structure that allows to create a payslip with a salary advance amount as an other input. When generating the CP200 monthly payslip, the total salary advance already granted is added as an editable other input 'Salary Advance Recovery', which is deducted from the total net.

This commit also renamed the existing 'Salary Advance' input type and rule (which represented a recovery) to 'Salary Advance Recovery' to avoid confusion with the initial salary advance.

task-3614756

Employees can now mark bank accounts as trusted from their employee record without requiring the account to follow IBAN formatting. This makes payroll bank account handling consistent across screens and better supports countries where non-IBAN accounts are common, such as the US.

When trusting a bank account from the employee's form view, a check was performed to verify that the bank account has a valid IBAN. This check is not performed on the bank account form view as a bank account (e.g. in the US) does not necessarily follow the IBAN format. This commits remove the IBAN validity check on the employee form view for consistency with the bank account view.

task-4613593

Updated WhatsApp-related tests to match the latest message payload format, helping ensure the system continues to validate messaging behavior correctly. This is an internal quality improvement with no expected change for day-to-day users.

PR community: https://github.com/odoo/odoo/pull/180745
PR upgrade: https://github.com/odoo/upgrade/pull/6722

This update streamlines how Kenya OSCU e-invoicing information is handled for products that have only one variant. It reduces duplicated setup work and helps keep product reporting data more consistent.

Related to:
- https://github.com/odoo/odoo/pull/189001

Recruiters can now send interview scheduling emails that create meetings linked directly to the candidate application. This makes application records easier to track and avoids incorrect reuse of shared calendar invitations across candidates.

Goal
---
When a "Schedule interview" mail template is sent from an application,
if the recipient uses the link the schedule a meeting, the meeting
should be linked on the smart button on the application form.

Note
---
Previously we had a demo "Schedule Intreview" mail template, from which
a recipient could schedule an interview -- but the `appointment.invite`
was the same for all recipients and the meeting would not be linked back
to the application.

Changes
---
* Edit appointment booking route to take an applicant_code in the url
* The applicant_code makes it possible to match calendar event with
  applicants at creation time
  (not just an applicant_id to avoid "attackers" guessing ids)
* the mail template now creates an invite link for the recruiter's
  `anytime` appointment type and the current applicant.
* Remove applicant_id from appointment invites
  * instead we append the applicant_code to the url when copying the link
    to share
  * all other buttons in this view also append the applicant_code
  * Note: this is needed because the field relation made it impossible to
    use the same invite for several applicants

Beneficial "Side Effects"
---
* This makes it so we don't have to regenerate an invite for every
  applicant when sending a link for a specific appointment type
* Fix the following bug:
  * when admin has no `anytime` appointment type -- go to the
    calendar view from the applicant form button.
  * *Share Calendar* -- the invite's applicant is the current one
  * repeat for another applicant -- no new invite is generated and the
    applicant stays the same.

task-4251911