This update improves the Swiss payroll payslip report by incorporating the necessary source tax rate information. This ensures accurate tax calculations and reporting for Swiss businesses using the Odoo Enterprise system. It's a key update for compliance with Swiss tax regulations.

This commit adds the source tax rate in the payslip report for Swiss payroll.

task-4979330

Forward-Port-Of: odoo/enterprise#112842

This update improves the D300 VAT report for Romanian businesses. The report's name has been changed to better align with local regulations and reporting requirements. This ensures accurate and compliant financial reporting for our Romanian customers.

Rename VAT report fom Romania

task-5423935

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

Forward-Port-Of: odoo/odoo#252511

This update improves the generation of the D300 VAT report for Romanian businesses, aligning with the latest requirements from the ANAF (Romanian tax authority). It now creates an XML file to streamline the reporting process and ensure compliance with current regulations.

Rename VAT report fom Romania and generate XML file to complete flow for D300 return complying with the latest ANAF specifications.

https://static.anaf.ro/static/10/Anaf/Declaratii_R/300.html

task-5423935

Forward-Port-Of: odoo/enterprise#109849

This update improves the D300 VAT report for Romanian businesses. The report's name has been changed to better align with local regulations and reporting requirements. This ensures accurate and compliant financial reporting for Odoo users in Romania.

Rename VAT report fom Romania

task-5423935

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

Forward-Port-Of: odoo/odoo#252511

This update improves the Romanian VAT reporting process within Odoo Enterprise. It renames the VAT report and generates an XML file, aligning with the latest requirements set by the Romanian tax authority (ANAF). This ensures accurate and compliant D300 returns.

Rename VAT report fom Romania and generate XML file to complete flow for D300 return complying with the latest ANAF specifications.

https://static.anaf.ro/static/10/Anaf/Declaratii_R/300.html

task-5423935

Forward-Port-Of: odoo/enterprise#109849

This update improves the D300 VAT report for Romanian businesses. The report's name has been changed to better align with local regulations and reporting requirements. This ensures accurate and compliant financial reporting for Odoo users in Romania.

Rename VAT report fom Romania

task-5423935

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

Forward-Port-Of: odoo/odoo#252511

This update improves the generation of the D300 VAT report for Romania, aligning with the latest requirements from the ANAF (Romanian tax authority). It now creates an XML file, completing the necessary flow for submitting the report, ensuring compliance and accurate tax reporting.

Rename VAT report fom Romania and generate XML file to complete flow for D300 return complying with the latest ANAF specifications.

https://static.anaf.ro/static/10/Anaf/Declaratii_R/300.html

task-5423935

Forward-Port-Of: odoo/enterprise#109849

This update introduces a time limit for query profiling within Odoo. By tracking query execution times and periodically committing this data, we're improving the performance and reliability of the profiler tool. This ensures that profiling data is captured efficiently and doesn't negatively impact system performance.

Modify the query collector so that it add an entry before the query runs and updates the time after it runs.

use the async collector periodic sampling to commit the profiler after a time limit.



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

Forward-Port-Of: odoo/odoo#268467
Forward-Port-Of: odoo/odoo#215034

This update enhances the synchronization of financial transactions with Fiskaly for both retail and restaurant orders. It streamlines the process by sending complete transaction data only upon order validation, improving efficiency and data accuracy. This change ensures seamless integration with Fiskaly's reporting system.

In this commit:
------------------
- Maintain separate Fiskaly transaction flows for retail (short tx) and restaurant (long tx)
  orders as discussed with the Fiskaly team.
- `Initialize order transactions` with an empty payload when the `first product` is added.
- Start `receipt transactions` with an empty payload when the `first payment line` is added.
- For retail flows, no intermediate order updates are sent to Fiskaly before finalization.
- For restaurant flows, create additional transaction updates during kitchen synchronization.
  Ensure already synchronized products are not resent, and only newly added or updated
  quantities are included in the payload.
- `Finalize order and receipt transactions` with complete order lines and payment details
  when we validate the order.

task: 6208963

Reference:
<img width="1863" height="1285" alt="de_tss_flow" src="https://github.com/user-attachments/assets/9140788e-7948-4a08-9f11-27197b22ca8b" />

Forward-Port-Of: odoo/enterprise#119765
Forward-Port-Of: odoo/enterprise#117526

This update clarifies who created replenishment orders in the Odoo chatter logs. Previously, all replenishments were attributed to 'OdooBot,' making it difficult to track manual actions. Now, the creator is accurately recorded, enhancing accountability and auditability for replenishment orders.

Purpose:
=================
When a user replenishes a product by clicking the `Order button` in the `Master Production Schedule` view, a `Manufacturing Order` is created. Currently, the chatter logs show `OdooBot` as the creator of the record. This makes it unclear, as all replenishment records show OdooBot as the creator, preventing users from distinguishing manually placed replenishment from those automatically generated by OdooBot. Recording the actual user (logged-in user) in the chatter who triggered a manual replenishment improves accountability and provides clear visibility, making it easier to audit.

With This Commit:
=================
When a user triggers a manual replenishment, the system sets the creator of the record to `current user` for manual replenishment or otherwise to `OdooBot` for auto-generated replenishments. This ensures the chatter correctly shows who actually created the record. This makes it easier to track who placed manual replenishments and improves accountability.

Community PR : https://github.com/odoo/odoo/pull/227827
TaskID–4893809

This update introduces automated warnings for key payroll reports (281, 273S, 274, and Dmfa) to help payroll officers avoid missed deadlines. The system now provides customizable alerts with clear instructions and actions, streamlining the reporting process and reducing the risk of errors. This enhancement improves operational efficiency and ensures timely report submission.

Purpose:
A lot of reports must be done and submitted monthly, quarterly, yearly. For a payroll officer it can quickly become a mess and he can quickly miss a deadline.

Current behavior:
- added new options for `closing_on` on dashboard warnings
- added more fields to be customizable in the python code of the warning (warning_title, warning_description, warning_deadline, warning_button)
- added warnings for 281, 273S, 274 and Dmfa reports with the corresponding dialogs and needed actions

task-id: 5909165

This update introduces a new report for payroll officers, providing a clear view of employee end-of-service benefit amounts. Officers can now control the report's parameters and export the data for detailed analysis, improving payroll accuracy and reporting.

In order to facilitate the usage of odoo for payroll officers and give the required visibility over the end of service benefit amount for all employees, a separate report has been introduced which will allow the officers to control the end date and employees they are inspecting and export it for further investigation.

Task: 4860227

This update streamlines the processing of subscription renewals within Odoo Enterprise. By moving renewal logic to a queued, post-processing system, it improves efficiency and aligns with the existing deferred payment confirmation process. This change enhances the reliability and performance of subscription renewals.

*: `appointment_account_payment`, `sale_subscription`, `sale_subscription_external_tax`

See the related community commit for the motivation behind these changes.

The auto-renewal cron of `sale_subscription` was adapted to no longer assess transaction states or run business-specific logic synchronously, instead relying entirely on post-processing, thus unifying that flow with the deferred payment confirmation path.

task-4309611

See also:
- https://github.com/odoo/odoo/pull/255611

This update introduces a new button on the salary rule category list view, providing a quick way for users to see all associated salary rules – including those within sub-categories. This streamlines the process of managing salary rules and simplifies reporting.

This commit adds a fast way to access this information by introducing a smart button directly on the salary rule category list view, allowing users to view all the salary rules linked to a category (including those connected to its sub-categories).

Task Id : 6283798

This update enhances the employee calendar view within payslips by automatically graying out days with no scheduled attendance or when an employee isn't assigned to work. This provides a clearer visual representation of an employee's working hours, simplifying payroll processing. The change was implemented to improve the accuracy and usability of the payroll system.

In this commit, expected:

- Gray out the calendar when no attendance is scheduled or the employee is not supposed to work 

Step to produce

- Create Working Hours schedule, remove Friday under working hours tab
- Assign the working hours schedule to employee
- Create new payslip for employee
- Click Calender SmartButton to see Employee Calender View from Payslip

task: 6260186

This update refines how Odoo calculates worked days for payroll, ensuring more accurate and reliable pay calculations. The changes address a previous calculation error and improve the overall stability of the payroll process. This update primarily impacts the HR and Payroll modules.

This update clarifies how half-day work periods are displayed on payslips. Previously, half-days were grouped with full days, making it difficult to understand total work hours. Now, half-day entries are clearly separated, providing a more accurate and transparent view of employee earnings.

In order to clearly distinguish work days that extended full day or half day, the worked days under the payslips will not display both entries as separate types with the half days flagged

Task: 5975762

Forward-Port-Of: odoo/enterprise#118869
Forward-Port-Of: odoo/enterprise#112328

This update streamlines the configuration of delivery methods (BPost, Easypost, Envía, Sendcloud, Shiprocket, Starshipit) by consolidating settings within the main Stock configuration. This simplifies the user interface and improves overall usability for managing delivery options.

easypost, envia, sendcloud, shiprocket, starshipit

--------------------------------------------------------------------------------

These delivery connector modules no longer need to define their own Inventory
configuration entries and views since delivery methods and connectors are now
managed from a single place in the Stock configuration.

This cleanup removes obsolete views and settings so users can configure all
delivery methods from a single, cleaner interface, improving overall usability.

Community PR:- https://github.com/odoo/odoo/pull/242503
Upgrade PR:- https://github.com/odoo/upgrade/pull/9208

TaskId:- 5380595

This update streamlines the Discuss meeting experience by adding a 'Your Meeting is Ready' banner and simplifying controls for adjusting the view and inviting participants. The changes improve usability and make it easier to start and manage meetings within Discuss.

Rework the in-call/meeting experience in Discuss:

- Add a "Your Meeting is Ready" banner shown while alone in a call, surfacing the permanent share link and a shortcut to invite people; it hides once another participant joins. Starting a "New Meeting" no longer auto-opens the invite panel.
- Add an "Adjust view" dialog to pick the meeting grid layout (auto, tiled, spotlight, sidebar, discuss); the choice is persisted in user settings. Layout actions (Adjust view, Picture in Picture) move into a "More" menu in the call bar, while Fullscreen keeps its own corner button and Exit Fullscreen sits next to Chat in fullscreen.
- Mirror the meeting share link in the address bar while in a call and restore the regular Discuss URL once it ends.
- Starting a meeting now enters fullscreen and auto-hides (unpins) the meeting channel from the sidebar.
- Open the invite UI as a single centered dialog everywhere (openChannelInvitationDialog); the member-list button reads "Add People" in the meeting view. Drop the "Generate new invite link" button.

Along the way, tidy up the Discuss sidebar and messages:

- Only show the Bookmarks mailbox when it holds at least one message.
- Move "View hidden conversations" out of the sidebar (still reachable from the command palette) and restyle the "New Meeting" button.
- Keep fewer inline message quick actions (3 instead of 4): Copy Text and Copy Link move to the expanded actions menu, and "Copy Link" is renamed "Copy Message Link".
- Simplify the meeting channel name, e.g. "Meeting, Jan 1".

task-6260047

This update enhances the visual presentation of the holiday attest report within the Odoo Enterprise system. The changes focus on reworking the layout to improve readability and clarity for users reviewing employee holiday information. This ensures accurate and easily understandable reports for payroll and HR processes.

This commit reworks the layout of the holiday attest report.

task-5936242

This update enhances the Odoo Enterprise integration with Google Reserve by simplifying the synchronization process for users. It includes clearer troubleshooting guidance and prevents accidental deletion of Google Reserve merchants when linked to synchronized appointment types. This improves the overall user experience and data integrity.

…UI/UX

Make it easier for end users to synchronize their appointment type with Google Reserve by adding links to the documentation as well as more complete banner messages for troubleshooting.

Also prevent google.reserve.merchant deletion if they are used inside a synchronized appointment.type.

Task-6148700

This update enhances the Romanian VAT reporting process within Odoo Enterprise. It renames the VAT report and generates an XML file, aligning with the latest requirements set by the ANAF (Romanian tax authority). This ensures accurate and compliant D300 returns.

Rename VAT report fom Romania and generate XML file to complete flow for D300 return complying with the latest ANAF specifications.

https://static.anaf.ro/static/10/Anaf/Declaratii_R/300.html

task-5423935

This update ensures Odoo's GSTR-3B and GSTR-2B reports accurately reflect purchase composition supplies transactions, aligning with recent government regulations. The changes create dedicated lines for these supplies in the reports, improving reporting accuracy and compliance for our Indian customers.

As a new GSTR section for purchase composition supplies has been introduced, the related report domains also need to be updated accordingly.

With this commit:
GSTR-3B domains are updated to properly include purchase_composition_supplies transactions in the relevant report section.
GSTR-2B now includes a separate line for composition supplies, aligned with the government utility format.

task-6239870

This update introduces a new 'PINT' layer in the account_edi_ubl_cii module, bridging the gap between UBL and BIS3 invoice formats. This enhancement supports compliance with European regulations and standards, particularly those related to PEPPOL, by providing a standardized layer for invoice processing and data exchange.

Add the layer PINT between UBL and BIS3.

task: 5890887

This update moves a key test case related to UBL (Universal Business Language) billing in Belgium (account_edi_ubl_cii) to the new testing framework. This ensures better test coverage and reliability for our UBL billing processes, improving the overall quality of the system. The change was prompted by a previous update to the test suite.

Move test introduced by https://github.com/odoo/odoo/pull/265261 to the new test suite in account_edi_ubl_cii

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