This change ensures users can only update employee salary-related records they are allowed to access. It helps protect sensitive HR contract information and prevents unauthorized changes to employee versions.

Check that the current user can access on the employee
version which will be updated.

task-4881974

This update standardizes how HR-related features define and apply filtering rules behind the scenes. It helps keep payroll, attendance, appraisal, contract salary, and planning workflows consistent and easier to maintain without changing day-to-day user behavior.

odoo/odoo#206645

Quote PDFs for subscriptions now show the subscription end date when one is set. This gives customers clearer contract timing and reduces the need for manual edits before sending quotes.

Before:
The subscription end date was not displayed on the quote PDF, requiring users to manually adjust end of the subscription period.

After:
If a subscription end date is defined, it is now displayed next to the recurring plan on the quote PDF, reducing manual effort and improving clarity for customers.

task-4801402

Recurring planning shifts now update more predictably when a user changes dates. Depending on whether changes apply to all or only future shifts, the system rebuilds the affected recurrence from the right shift, reducing inconsistent schedules and avoiding errors when deleted shifts are involved.

If the user doesn't change any date field, the recurrence should be
impacted as expected.
However, when at least one date field is changed, with option:
- "all": the changes should be applied to the first shift, then
all other shifts in the recurrence should be deleted and recreated,
using the first one as template.
- "subsequent": the previous shift's recurrence should be unset, the
changes should be applied to current shift, the subsequent shifts should
be deleted and recreated, using the current one as template.

task-3765142

Salespersons can now view commission adjustment records when they are directly involved in the adjustment. This helps them better understand changes affecting their performance while keeping unrelated adjustment records restricted.

Purpose:
Salespersons previously had no access to achievement adjustments, even when directly involved. This change introduces conditional read access so they can view adjustments related to their own performance.

Before:
- Salespersons could not see any adjustment records — not even those they were involved in (`add_user_id` or `reduce_user_id`).
- Managers already had full access to all adjustment records.

After:
- Salespersons now have read access to adjustments only when they are involved (as `add_user_id` or `reduce_user_id`).
- Added a record rule to enforce salesperson-level visibility.
- Updated the security CSV to grant the Salesperson group read access to the adjustment model.

task:4783916

Renewed subscriptions now carry over customer-facing notes and relevant section headings from the original order. This helps sales teams preserve important context and makes renewal documents clearer without manual re-entry.

Prior to this commit, it wasn't possible to keep the sections and notes when renewing a subscription.

This commit modifies the behaviour to keep the notes and non-empty sections (sections that have at least one subscription product), in the renewed `sale.order`.

task-4554471

Appointment and Helpdesk website pages now use a clearer heading structure. This helps search engines and accessibility tools better understand the content, supporting improved discoverability and user experience.

*: website_helpdesk

Refactored enterprise modules templates to use a consistent and semantically correct heading structure (h1, h2 etc.). This improves SEO.

Spreadsheet users can now open the filter search dialog directly from the filter control, making it quicker to find and apply filters. Filter creation and editing remain available in the side panel, preserving existing configuration options while improving day-to-day use.

This commit changes the behavior of the filter component (top right corner of the spreadsheet) to open the filter search dialog instead of the side panel to configure filters. Filters can still be created and edited in the side panel, but the search dialog provides a more efficient way to search and apply filters directly from the spreadsheet.

Task: 4816193

This change streamlines an internal accounting report test by preparing accounting entries once during setup instead of repeatedly switching them back and forth for each report. It reduces unnecessary test work and should make the test suite faster without changing business functionality.

In `test_balance_sheet_balanced`, during the balance test the case first sets a bunch of lines to `posted`, then sets them (back?) to `draft`.

However this is done per report, even though in the default mode the amls involved don't change between reports. Not only that, but since f2100c2654a068fe197025aecc605fdada3a919a each CoA's test case is within a savepoint, so the AMLs get reverted implicitly.

Hence rejigger the thing to activate the relevant AMLs while setting up localization if not in `IDENTIFY_INCORRECT_ACCOUNTS` mode, that way we don't even pay for the activation, let alone do so repeatedly for each report we test.

Email and SMS templates now rely on the main customer's language automatically instead of showing technical language expressions. This makes template setup clearer for users while preserving the same customer-language behavior across affected business flows.

This PR streamlines mail templates by removing redundant `lang` assignments when the language matches the main partner's. Specifically, it eliminates calls such as `object._mail_get_customer().lang` and `object.partner_id.lang` when they are unnecessary.

By unsetting these values, the form view will now display the new placeholder "Main partner's language" in the `lang` field for those records. This change provides a clearer and more user-friendly alternative to technical inline expressions.

See: odoo/odoo#189743

task-4365019

The online sales experience for rentals, subscriptions, and appointments was updated to stay compatible with recent platform changes. This helps keep product selection, order handling, and related checkout tests working consistently for customers using these sales options.

Installing the main AI module now automatically includes AI Fields and AI Server Actions. This makes setup simpler and ensures users get the full AI feature set without needing to install related modules separately.

Improving UX by adding all of the AI related functionalities when AI module is installed.

issue ticket
task-4855178

Divagations
---
In the future the ai_fields and ai_server_actions modules should be merged into the ai module.
with ticket
task-4889610

Documents gets a clearer default folder structure, including Inbox, Finance, Legal, HR, Project, Marketing, and Admin areas, so teams can organize files more consistently. Related document actions are simplified and better scoped, while the Support folder is now created only when needed for traceback uploads.

#### **Objective**

Enhance the server actions management and folder structure.

---

#### **1. Server Actions**

* **Add Domain Filter**: When accessing server actions from **Documents**, apply a domain filter to show **top-level actions only** (not a default search).
* **Update Existing Server Actions**:

  * Refactor “Send to Finance” and any server action in `documents_account` to use **Update Records** instead of custom code with `sudo`.
* **Convert Server Actions to MultiAction**:

  * Change demo/data server actions from **Code** to **MultiAction** to eliminate the requirement for user coin usage.

---

#### **2. Folder Structure Updates**

  * Rename folder `Administrative` to `Admin`.
  * Remove folder `Administrator`.

  * Add and order folders as follows:
    * **Inbox**
    * **Finance**
    * **Social**
    * **Taxes**
    * **Annual Closing**
       * **2025**:
    * **Legal**
       * **Insurances**
       * **Loans**
       * **Registrations**
       * **Contracts**
    * **HR**
    * **Project**
    * **Marketing**
    * **Admin**


* **Support Folder**:  Create folder when explicitly needed (saving a traceback).
---

#### **3. Tags Clean-up**
  
Task-4690653

The budgeting app can now be used without installing the purchasing app, making it suitable for simpler budget management needs. Purchase-related committed amount tracking is moved into a separate add-on, so businesses can choose a lighter setup or keep purchase integration when needed.

Allow using budgets without installing purchase, for simple budgetting without committed amounts.

Currently, there are two ways of doing budgets:
* using accounting entries, using the budget feature of account reports: this works in some cases where we only need one plan, and that plan can be reduced to accounts or groups of accounts determined by the accounting reports
* using `account_budget`: it gives a lot more flexibility, can be integrated with other apps/concepts, can use multiple plans, but it requires `purchase` to be installed.

This gives the opportunity to use the budget feature for simpler use cases, including on the one-app-free plan of Accounting.

Assigned users can now open worksheets linked to their tasks, even when another user created the worksheet. This removes an access blocker in Field Service and related worksheet flows, helping teams collaborate without needing elevated permissions.

Steps to Reproduce
-----------
- Install field service
- Open project, create a task with worksheet enabled on project
- Assign two user A and B on the task
- Create the worksheet
- Login using user B

Issue
--------
- User B doesn't have access to the worksheet
- Similar issue in the quality app

Cause
----------
- User B not able to edit the existing worksheet because it triggers an SQL constraint making sure that 1 worksheet is related to only 1 task.

Fix
----------
- We remove this  [('create_uid', '=', user.id)] record rule.

task-3891011

This fix updates several business modules to use the current file conversion setting after an older option was deprecated. It helps keep appraisal, marketing automation, CRM marketing, and product classification features compatible with platform changes and reduces the risk of future errors.

The spreadsheet edition test coverage was adjusted to reflect the corrected handling of empty labels in global filters. This helps ensure future updates preserve the expected spreadsheet behavior and reduces the risk of regressions.

Task: 4876003

`hr_contract` was merged into `hr` in https://github.com/odoo/enterprise/pull/83136

`hr_contract` was merged into `hr` in https://github.com/odoo/enterprise/pull/83136

This update reorganizes shared HTML formatting helpers so several apps use the common web foundation instead of maintaining separate copies. The change is internal, reducing duplication and helping keep AI chat, VoIP, barcode, and live chat behavior consistent without changing day-to-day workflows.

Enterprise counter-part.

https://github.com/odoo/odoo/pull/215145

The salary package setup experience was converted to Odoo’s newer interaction framework across core, payroll, and Belgian localization modules. This is mainly an internal modernization that should preserve existing behavior while making the feature easier to maintain and extend.

Changed hr_contract_salary of
- hr_contract_salary
- hr_contract_salary_payroll
- l10n_be_hr_contract_salary
modules, following refactoring
Refacto in the continuity of the PublicWidget to Interaction conversion

task-4367641

Before this commit, the payrunId prop definition said it is a required prop and an integer. However, that property is not really required. This commit changes the property definition to make that property optional. runbot-error-226806 Forward-Port-Of: odoo/enterprise#88328

Before this commit, the payrunId prop definition said it is a required prop and an integer. However, that property is not really required.

This commit changes the property definition to make that property optional.

runbot-error-226806

Forward-Port-Of: odoo/enterprise#88328

Forward-Port-Of: odoo/enterprise#88471

Forward-Port-Of: odoo/enterprise#88471

Since 5f001cbf0ea5e382f00602e3307ffd1fc2eb5bf1, it was possible to save a global filter with an empty label, which is not intended. This commit restore the previous behavior by preventing the saving of a global filter with an empty label. Task: 4876003 Forward-Port-Of: odoo/enterprise#88403 Forward-Port-Of: odoo/enterprise#87847

Since 5f001cbf0ea5e382f00602e3307ffd1fc2eb5bf1, it was possible to save a global filter with an empty label, which is not intended. This commit restore the previous behavior by preventing the saving of a global filter with an empty label.

Task: 4876003

Forward-Port-Of: odoo/enterprise#88403
Forward-Port-Of: odoo/enterprise#87847

The current code of `_recompute_shifts_in_leave_periods` explicitely calls the compute method `_compute_allocated_hours` of planning.slot to recompute the allocated hours according to modifications done to the public holidays. Calling the method directly like that is far from ideal as we are missing proper batching, fields protection, etc.. that the ORM usually does for computed fields. This commit replaces the explicit call by an `add_to_compute`. This essentially marks the field as "to be r

The current code of `_recompute_shifts_in_leave_periods` explicitely calls the compute method `_compute_allocated_hours` of planning.slot to recompute the allocated hours according to modifications done to the public holidays. Calling the method directly like that is far from ideal as we are missing proper batching, fields protection, etc.. that the ORM usually does for computed fields.

This commit replaces the explicit call by an `add_to_compute`. This essentially marks the field as "to be recomputed". This recomputation then happens at the next flush_model/recompute_model call and can applies the proper ORM optimizations of batching by `PREFETCH_MAX` size, protecting fields to avoid triggering loops of recomputations. This speeds up the import of new Public Holidays in an already populated database.

#### speedup

In a customer database with 50K planning.slots, 1300 of which needs to recompute their allocated_hours, the import timing Before PR vs After PR is the following:
- 40 min -> 4 min

opw-4782452

Forward-Port-Of: odoo/enterprise#88351

Currently when using Fiskaly, the receipt gets printed with the technical names of the tss values. Steps to reproduce: ------------------- * Set up the db to use fiskaly * Open restaurant * Place and pay an order > Observation: On the receipt screen the name of the tss values are shown as: transaction_number, signature_algorithm, client_serial_number, .... Why the fix: ------------ Beore this commit https://github.com/odoo/enterprise/commit/d1a94147060083da54f9423f8c379676fbb7db66#

Currently when using Fiskaly, the receipt gets printed with the technical names of the tss values.

Steps to reproduce:
-------------------
* Set up the db to use fiskaly
* Open restaurant
* Place and pay an order
> Observation: On the receipt screen the name of the tss values are shown as:
transaction_number, signature_algorithm, client_serial_number, ....

Why the fix:
------------
Beore this commit https://github.com/odoo/enterprise/commit/d1a94147060083da54f9423f8c379676fbb7db66#diff-960ffa6839618d084dd5de6e29458ef68766a31250fc7d296512ec5358f04056 we were using a dictionnary `name, value` when using tss information, cf `_initTssInformation()` in `l10n_de_pos_cert/static/src/overrides/models/models.js`.

We re-introduce this behavior and revert the following commit https://github.com/odoo-dev/enterprise/commit/9f75e3fe092bd838fffb11a35a8d854afff71869 to use the official names instead of the technical ones.

opw-4822342

Forward-Port-Of: odoo/enterprise#88179
Forward-Port-Of: odoo/enterprise#87717

UI-wise, there are two types of VoIP errors: blocking and non-blocking. Blocking errors are unrecoverable, they're displayed at the top of the UI and prevent further use of the softphone. Non-blocking errors, on the other hand, can be dismissed by a simple click on the error screen. Problem: the handler that hides the error screen in case of non-blocking errors wasn't attached to anything, and even if it was, its implementation was wrong! This commit makes it work as intended. Part of [tas

UI-wise, there are two types of VoIP errors: blocking and non-blocking. Blocking errors are unrecoverable, they're displayed at the top of the UI and prevent further use of the softphone. Non-blocking errors, on the other hand, can be dismissed by a simple click on the error screen.

Problem: the handler that hides the error screen in case of non-blocking errors wasn't attached to anything, and even if it was, its implementation was wrong! This commit makes it work as intended.

Part of [task-4891947](https://www.odoo.com/odoo/project/5778/tasks/4891947).

Forward-Port-Of: odoo/enterprise#88358

**Issue:** - In sale order, first select the quotation template with a recurring plan, then, change the quotation template to without a recurring plan. After changing the quotation template, the 'Recurring Plan' (`plan_id`) field still shows the value from the previously selected template. This happens because the `plan_id` is not reset when the new template has no recurring plan. - In version 17, this case was handled in the else part and set [default value](https://github.com/odoo/enterp

**Issue:**

- In sale order, first select the quotation template with a recurring plan, then, change the quotation template to without a recurring plan. After changing the quotation template, the 'Recurring Plan' (`plan_id`) field still shows the value from the previously selected template. This happens because the `plan_id` is not reset when the new template has no recurring plan.

- In version 17, this case was handled in the else part and set [default value](https://github.com/odoo/enterprise/blob/17.0/sale_subscription/models/sale_order.py#L490) (company_id.subscription_default_plan_id), but in version 18.0, the field was [removed](https://github.com/odoo/enterprise/pull/55355/files).

**Steps to reproduce:**

- Install the Sales and Subscriptions modules.
- Create two quotation templates — one with a recurring plan and one without.
- Create a Sale Order and first select the quotation template 'with a recurring plan'. 
- Then, change the quotation template to 'without a recurring plan'.

**Solution:**

- Reset `plan_id` to `None` before computing the new value to ensure accurate computation. If the selected quotation template has a recurring plan, it will be assigned; otherwise, the plan_id field will remain empty.

**Runbot v18.0 (without fix)**

![Quotation-Templates-06-17-2025_11_46_AM](https://github.com/user-attachments/assets/ce47c352-8b0e-4c85-99c9-143aaa7dab61)

![S-06-17-2025_11_45_AM](https://github.com/user-attachments/assets/e2ec4d4c-5cf1-4c1f-9035-add7bd79d897)

OPW: [4845478](https://www.odoo.com/odoo/70/tasks/4845478)

Forward-Port-Of: odoo/enterprise#87821

We adapt a studio test to the changes brought by https://github.com/odoo/odoo/pull/215437. Forward-Port-Of: odoo/enterprise#88281

We adapt a studio test to the changes brought by https://github.com/odoo/odoo/pull/215437.

Forward-Port-Of: odoo/enterprise#88281

### Steps to reproduce: - Create 2 storable products: Product A, Product B - Create a control point pass/fail control by quantity on receipt and set both products on it. - Create and confirm a receipt with 2 moves: - 2 x Product A - 2 x Product B - Click on the "Quality Check" button and mark one unit of Product A as failed. > This should open the QC for product B. - Close the QC for prodcut B wihtout setting it as failed or passed. - Click on the "Quality Check" button ####

### Steps to reproduce:

- Create 2 storable products: Product A, Product B
- Create a control point pass/fail control by quantity on receipt and set both products on it.
- Create and confirm a receipt with 2 moves:
    - 2 x Product A
    - 2 x Product B
- Click on the "Quality Check" button and mark one unit of Product A as failed.
> This should open the QC for product B.
- Close the QC for prodcut B wihtout setting it as failed or passed.
- Click on the "Quality Check" button
#### > Nothing happends

### Expected behavior:

The QC for product B should open.

### Cause of the issue:

When the quality check is marked as failed, the related move is picked: https://github.com/odoo/enterprise/blob/679c81924e05e7544eecfdb960c9ed9611e9cdd5/quality_control/models/quality.py#L438-L451 However, the move for your second porduct is not and hence, its product is not considered to be checkable by the `check_quality` action: https://github.com/odoo/enterprise/blob/679c81924e05e7544eecfdb960c9ed9611e9cdd5/quality_control/models/stock_picking.py#L61-L69
Since these lines were added in c83728f3a7f1504b272f4ef97e4187868338adb3 to not bypass the QC of the unpicked move at validation we should probably only add that filtering condition in that case and continue to consider the unchecked moves as checkable prior to validation.

opw-4765075

Forward-Port-Of: odoo/enterprise#84743

### Issue: The tour test_add_component_from_shop_foor_in_multi_step_manufacturing makes an assert on the value of an input before waiting for this input to be updated. runbot-build-error-226734 Forward-Port-Of: odoo/enterprise#88241

### Issue:

The tour test_add_component_from_shop_foor_in_multi_step_manufacturing makes an assert on the value of an input before waiting for this input to be updated.

runbot-build-error-226734

Forward-Port-Of: odoo/enterprise#88241

Case 1: How to reproduce ================ - Select a record in any folder in Kanban view - Display its chatter - Add an activity from the kanban tile --> the chatter is not updated and needs a refresh Expected behavior ================= Chatter should update instantly Case 2: How to reproduce ================ - Select a record in any folder in Kanban view - Display its chatter - Mark done or cancel one or more activities from Chatter - Click on the activity button of the r

Case 1:

How to reproduce
================
- Select a record in any folder in Kanban view
- Display its chatter
- Add an activity from the kanban tile --> the chatter is not updated and needs a refresh

Expected behavior
=================
Chatter should update instantly

Case 2:

How to reproduce
================
- Select a record in any folder in Kanban view
- Display its chatter
- Mark done or cancel one or more activities from Chatter
- Click on the activity button of the related kanban record --> stack trace

Expected behavior
=================
Corresponding KanbanRecord should update.
Note: v. 17.4 raises a missing record exception for the same case

task-4690165

Forward-Port-Of: odoo/enterprise#87422
Forward-Port-Of: odoo/enterprise#84128

To reproduce the issue, on a Belgian company: 1) Create and post an entry impacting line "Other Appropriations of the Year", typically by using an account prefixed 69 in it. 2) Enable totals below sections in the settings 3) Open the Belgian BS at a date including the move created in 1). 4) Enable 'unfold all' in the report ===> "Other Appropriations of the Year" displays no amount This happens because this line is considered as having sublines by the engine (has_sublines is Tr

To reproduce the issue, on a Belgian company:

1) Create and post an entry impacting line "Other Appropriations of the Year", typically by using an account prefixed 69 in it.

2) Enable totals below sections in the settings

3) Open the Belgian BS at a date including the move created in 1).

4) Enable 'unfold all' in the report

===> "Other Appropriations of the Year" displays no amount

This happens because this line is considered as having sublines by the engine (has_sublines is True), since it considered a non-zero number of move lines in its computation. The condition that was there before makes it so that in that case, when using unfold_all, the line would have the 'unfolded' key set to True, even though, here, the line has no means of generating any subline (no child lines, nor groupby value). Therefore, the "totals below sections" feature hid the amount of the line, since it was supposed to be displayed in the total line. The total line, however was never added, since no expand function was ever called.

Note that we could avoid doing 'groupby or has_children' in the condition here, to only use 'has_children'. We do that because that's the former behavior, and some engines (custom or standard) don't return any value for has_sublines in some cases, relying on the presence of the groupby field to properly trigger the unfold. This has changed a little in 18.1, with the introduction of a custom engine for the Trial Balance. We'll see what can be done when forward-porting, and if it's not possible, will probably do something in master later on. has_sublines should probably be mandatory everywhere.

opw-4640606

Forward-Port-Of: odoo/enterprise#88359

This mostly benefits `test_balance_sheet_balanced` as it mass activates reports on every `_set_up_localization` (so before rendering each report, something it does ~200 times). Forward-Port-Of: odoo/enterprise#88115

This mostly benefits `test_balance_sheet_balanced` as it mass activates reports on every `_set_up_localization` (so before rendering each report, something it does ~200 times).

Forward-Port-Of: odoo/enterprise#88115

The default_get method of the 'l10n_uk.hmrc.send.wizard' model assumed the presence of 'client_data' in the context, leading to a KeyError during test_display_name_new_record. This fix checks for the presence of 'client_data' before attempting to call import_vat_obligations. If 'client_data' is not present, it avoids calling import_vat_obligations and raises a UserError, thus preventing the KeyError. build_error-115767 Forward-Port-Of: odoo/enterprise#88297 Forward-Port-Of: odoo/enter

The default_get method of the 'l10n_uk.hmrc.send.wizard' model assumed
the presence of 'client_data' in the context, leading to a KeyError
during test_display_name_new_record.

This fix checks for the presence of 'client_data' before attempting to
call import_vat_obligations. If 'client_data' is not present, it avoids
calling import_vat_obligations and raises a UserError, thus preventing the KeyError.

build_error-115767

Forward-Port-Of: odoo/enterprise#88297
Forward-Port-Of: odoo/enterprise#84327

Before, with some errors in the regex search in the different statement line attributes, the search would just return 0, when the regex was just badly written, without giving any hint to the user. Now the method will raise an user error telling the user that the regex is badly written instead of returning 0.0 or a traceback (AttributeError was not handled). Examples of previously failing regexes: - "([^\d]*)" -> AttributeError - [\d,]* -> IndexError (was already handled by https://github.co

Before, with some errors in the regex search in the different statement line attributes, the search would just return 0, when the regex was just badly written, without giving any hint to the user. Now the method will raise an user error telling the user that the regex is badly written instead of returning 0.0 or a traceback (AttributeError was not handled).

Examples of previously failing regexes:
- "([^\d]*)" -> AttributeError
- [\d,]* -> IndexError (was already handled by https://github.com/odoo/enterprise/pull/84284)
- ValueError shouldn't arise anymore with that same PR, but better safe than sorry

Forward-Port-Of: odoo/enterprise#85881

Before, a fix was done to round column for materials and payments columns but the method was HALF-UP. This should always be DOWN as specified here https://assets.publishing.service.gov.uk/media/5d53df0040f0b6098ead46c2/cis-qsbvr-v2.2.pdf page 28 task-4881298 Forward-Port-Of: odoo/enterprise#88018

Before, a fix was done to round column for materials and payments columns but the method was HALF-UP.

This should always be DOWN as specified here
https://assets.publishing.service.gov.uk/media/5d53df0040f0b6098ead46c2/cis-qsbvr-v2.2.pdf page 28

task-4881298

Forward-Port-Of: odoo/enterprise#88018

Community: https://github.com/odoo/odoo/pull/208609 Design Themes: https://github.com/odoo/design-themes/pull/1059 Forward-Port-Of: odoo/enterprise#84782

Community: https://github.com/odoo/odoo/pull/208609
Design Themes: https://github.com/odoo/design-themes/pull/1059

Forward-Port-Of: odoo/enterprise#84782

Currently, an error occurs when finding duplicate transactions in the bank. Steps to Reproduce: - Install the `accountant` module. - In `Accounting Dashboard`, click on `Bank`. - In Actions, click `Find Duplicate Transactions`. - Clear the `Starting Date` field and click save. `TypeError: unsupported operand type(s) for -: 'bool' and 'relativedelta'` This error occurs when the system attempts to find duplicate transactions without a Starting Date. When finding duplicate transa

Currently, an error occurs when finding duplicate transactions in the bank.

Steps to Reproduce:

 - Install the `accountant` module.
 - In `Accounting Dashboard`, click on `Bank`.
 - In Actions, click `Find Duplicate Transactions`.
 - Clear the `Starting Date` field and click save.

`TypeError: unsupported operand type(s) for -: 'bool' and 'relativedelta'`

This error occurs when the system attempts to find duplicate transactions without a Starting Date. When finding duplicate transactions, it tries to calculate the `prior_date` using `date_from - relativedelta(months=3)` [1]. However, since `date_from` is `False`, this raises an error.

[1] https://github.com/odoo/enterprise/blob/acdba5ecf89ee8920f82e07e16fac2a0f9659b12/account_online_synchronization/models/account_journal.py#L314

This commit ensures that if the Starting Date is empty when finding duplicate transactions, it uses today’s date as the Starting Date.

sentry-6653835511

Forward-Port-Of: odoo/enterprise#87000