This update simplifies how businesses can customize the website event registration process. By separating the registration logic, developers can now easily inherit and modify the underlying code, leading to more flexible and tailored event experiences. This change enhances the extensibility of our website event functionality.

Since this controller returns raw markup, it is impossible to inherit.

By splitting the controller `registration_new`, allows to manage custom developments with the inheritance of the prepare method instead.


---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Forward-Port-Of: odoo/odoo#264242
Forward-Port-Of: odoo/odoo#244156

This update removes a restriction on the fiduciary VAT field within the connection wizard. This change provides more flexibility for users managing fiduciary accounts, allowing for adjustments as needed. The change is intended to improve the user experience and streamline processes related to VAT configuration.

This commit will remove the readonly on the fiduciary_vat in the connection wizard. It will give more flexibility for fiduciary.

task-6148930

Forward-Port-Of: odoo/enterprise#115752

This update simplifies how businesses can customize the website event registration process. By separating the registration logic, developers can now easily inherit and modify the underlying code, making it simpler to tailor events to specific needs. This enhances flexibility and reduces the complexity of adding custom features to our website events.

Since this controller returns raw markup, it is impossible to inherit.

By splitting the controller `registration_new`, allows to manage custom developments with the inheritance of the prepare method instead.


---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Forward-Port-Of: odoo/odoo#264242
Forward-Port-Of: odoo/odoo#244156

This update removes a restriction on the fiduciary VAT field in the connection wizard. This change provides greater flexibility for users configuring VAT settings related to Codabox, streamlining the process and improving usability. It allows for more adaptable configurations within the Odoo Enterprise system.

This commit will remove the readonly on the fiduciary_vat in the connection wizard. It will give more flexibility for fiduciary.

task-6148930

Forward-Port-Of: odoo/enterprise#115752

This update aligns the subheaders and numerical data within Odoo's financial reports, ensuring a more professional and consistent visual appearance. Previously, the formatting was uneven, and this change corrects that to improve readability and user experience. This is a minor improvement to the reporting system.

Before this commit, subheaders of numeric columns were centered, while the figures in the columns were aligned to the end. This commit ensures that both the subheader and the figures are aligned the same way (center or end).

task-6197223

Forward-Port-Of: odoo/enterprise#116578

This update simplifies how businesses can customize the website event registration process. By separating the registration logic, developers can now easily inherit and modify the setup, making it simpler to tailor events to specific needs. This change enhances flexibility and reduces complexity for custom development.

Since this controller returns raw markup, it is impossible to inherit.

By splitting the controller `registration_new`, allows to manage custom developments with the inheritance of the prepare method instead.


---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Forward-Port-Of: odoo/odoo#264242
Forward-Port-Of: odoo/odoo#244156

This update removes a restriction on the fiduciary VAT field within the connection wizard for the l10n_be_codabox module. This change provides greater flexibility for users managing fiduciary VAT settings, streamlining the configuration process. It's a minor improvement intended to enhance usability.

This commit will remove the readonly on the fiduciary_vat in the connection wizard. It will give more flexibility for fiduciary.

task-6148930

Forward-Port-Of: odoo/enterprise#115752

This update enhances the Windows IoT version tracking by automatically recording the build date in a VERSION file, mirroring the format used for Raspberry Pi IoT images. Additionally, the Windows version is now logged upon startup, providing clearer identification of the installed version. This ensures consistent versioning across IoT deployments.

Before this commit, the Windows IoT version was hardcoded to '23.11'.

After this commit, the installer now writes a VERSION file to the IoT install directory (which will remain between git checkouts). This file contains the build date in `YYYY.MM.DD` format, the same as the current Raspberry Pi IoT images.

In addition, the Windows version is now logged on startup.

task-6196801

**Image version:**
<img width="306" height="39" alt="image" src="https://github.com/user-attachments/assets/f0252d44-4b5c-4bb5-aac8-4b8f56dc6ee2" />

**Windows version:**
> INFO ? odoo.addons.iot_drivers.main: Windows version: Windows-11-10.0.26100-SP0 


---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Forward-Port-Of: odoo/odoo#263089

This update adds a test to ensure the payment data sent to Odoofin remains consistent. This safeguards against unexpected changes that could disrupt payment processing and highlights the need for corresponding updates on the Odoofin side. It’s a preventative measure to maintain reliable payment functionality.

Add a test asserting the payment payload structure sent to Odoofin.

The goal is to safeguard against unintended payload changes that are not
handled on Odoofin's side by making such changes explicit during testing,
and reminding developers that corresponding updates may also be required
there.

No task ID

Forward-Port-Of: odoo/enterprise#117260

This update standardizes the handling of employee legal names (first and last) across all Odoo localization modules. Previously, each localization had unique logic for these names, leading to inconsistencies. This change aligns with a new, unified approach, ensuring accurate and consistent name formatting in payroll reports and documents for all supported countries.

Replace l10ns specific logic for legal first name and legal last name with the generic one introduced in https://github.com/odoo/odoo/pull/262180

This update simplifies the generation of 281.XX payroll reports by centralizing the process and improving the user interface. The changes consolidate report creation, standardize data formats, and enhance error handling, resulting in a more efficient and reliable payroll reporting system.

**Container, Mixin & Generation**
* 281_xx is now the single entry point for all 281.xx reports.
* Introduced a shared mixin (`l10n_be.281.mixin`) to centralize common logic (employee validation, payslip filtering) and enforce a standard structure across all 281.xx forms.
* Child reports (281.10, 281.45) are systematically created and linked to the container.
* Forms are only generated for employees who require them (e.g., skipping 281.45 if the employee has no IP).
* XML generation is centralized at the container level: subreports provide data, while the container defines header-level information.
* Record names are adapted to include the year and a suffix sequence (e.g., `YEAR_281_suffix`).

**UI & View Simplification**
* Removed dedicated 281.10 and 281.45 form views, consolidating them into a unified container using tabs instead of smart buttons.
* Updated list view to display the year as the first column, and expose reference, form types, sending type, treatment type, and state.
* Introduced a shared employee declaration list view used across all 281 report types.

**Sequence, Error Handling & Finalization**
* The container holds the state (Draft, Error, Ready, Done). Draft state allows generating test XML; Ready state corresponds to final XML.
* Validation errors from subreports are aggregated and set the container to an "Error" state, blocking the XML generation.
* Confirmation wizard sets the final Belcotax reference, triggers the PDF generation, and sends the documents to the employees.

Task: 5911065

This update introduces a new report required by the Slovak Financial Administration, enabling businesses to accurately file their VAT Control Statement (KVDPH). The report covers key sales and purchase data, automating calculations and ensuring compliance with Slovak tax regulations. It includes features like XML export and bad debt flagging for improved accuracy and efficiency.

*=l10n_eu_oss_reports

This commit introduces the VAT Control Statement report (Kontrolný výkaz DPH)
as required by the Slovak Financial Administration.

The report covers all eight sections of the KVDPH:
- A.1: standard issued invoices to registered entities
- A.2: domestic reverse-charge sales (§69) with commodity codes
- B.1: reverse-charge purchases (EU acquisitions, triangular, imports)
- B.2: standard domestic purchases with VAT deduction
- B.3.1/B.3.2: simplified invoices (split by €3,000 threshold)
- C.1/C.2: corrections to issued/received supplies (credit & debit notes)
- D.1/D.2: e-KASA aggregates and other supplies (manual entry)

Each section uses a custom SQL engine that handles grouping by move,
partner, tax rate, and commodity tag depending on the section context.
Sections A.2 and C.1 resolve product commodity codes (TK) and goods
types (TD) from account tags defined in XML data.

Also adds:
- XML export following the KVDPH_2025 XSD schema
- `l10n_sk_is_bad_debt` field on `account.move` for bad debt flagging
- `l10n_sk_uom` selection on account.move.line for KVDPH unit of measure
- product tag data for 54 commodity codes and 2 goods types
- views to expose the new fields on invoices, journal items and products
- Added dedicated return type and submission wizard with direct XML download

Documentation: https://www.financnasprava.sk/sk/podnikatelia/dane/dan-z-pridanej-hodnoty/kontrolny-vykaz-dph

Related: https://github.com/odoo/odoo/pull/241860
Related: https://github.com/odoo/upgrade/pull/9102

task-5213902

This update allows administrators to exclude specific employees from payruns directly within the payrun version list. When an employee's payslip is excluded from a payrun version, the payslip itself is also removed, providing greater control over payroll processing and ensuring accurate reporting.

This commits adds a button to the versions list in payruns to allow users to exclude employees from the payrun. If the employee has a payslip for that payrun, the payslip will also be excluded.

Task-5955126

This update streamlines the calculation of prices on the website, particularly for subscription-based products. By directly using recurring plan prices when available, the system now computes prices faster and more accurately, leading to a better customer experience. The changes also incorporate updates from the Odoo community.

* website_sale_subscription: speed up prices computation when the plan is known

When the cart already holds a recurring product (and therefore a recurring plan),
it can be forwarded to the price computation logic to directly compute the right
unit price (instead of the sales price).

* Adapt to community changes

This update ensures compliance with UAE minimum wage laws for Emirati employees within the Odoo Enterprise HR payroll system. A warning is now displayed on payslips and the payroll dashboard if an employee's wage doesn't meet the minimum wage requirements or if their contract starts after January 1, 2026, promoting accurate payroll processing.

[IMP] l10n_ae_hr_payroll: minimum wage for Emirati employees

Warning is added to the payslip of Emirati Employees when their wage does not satisfy minimum wage conditions and when their contract starts after 01/01/2026.

task - 6110277

This update streamlines the process of reconciling invoices from sale orders. By automatically passing a context key, the system now directly reconciles invoices created from sale orders, reducing manual effort and improving accuracy. This enhancement simplifies invoice management and ensures consistent record-keeping.

This commit will allow to automatically reconcile the invoice create from the sale order by passing a context key that will be used in the create_invoices function.

task-5502964