Odoo Changelog — 2026-08-11

Tuesday, August 11, 2026

2 changes · master

New Features(1)

New functionality added to Odoo

[IMP] l10n_be_hr_payroll: flexi at work!

Enterprisemasterl10n_be_hr_payrollhr_payrollHIGH

Belgian payroll now supports sending required Flexi@Work salary declarations to the NSSO whenever validated flexi-worker payslips are created. Users get actions and warnings to help ensure these declarations are submitted, changed, or cancelled on time, reducing compliance risk for employers.

Original PR description

Belgian companies hiring flexi-workers must transmit the salary data of
each validated flexi payslip to the NSSO via the Flexi@Work eGov service
(flexi-counter on mycareer.be). A declaration must be sent every time a
flexi payslip is created.

New `l10n.be.flexi.at.work` model handles the full FLXWAGE flow: XML
generation from payslip data, XSD validation against the quarterly ONSS
schema, and batch submission. Supports submission, modification, and
cancellation operations.

The ONSS batch submission infrastructure (XML generation, schema
caching,
signature/go file handling, state machine) has been extracted into a new
abstract `l10n.be.onss.batch.declaration` model that both DMFA and
Flexi@Work now share — DMFA previously owned all of this inline.

`_get_flxwage_amounts()` on the payslip splits the flexi gross into the
two eGov financial-element buckets (remuneration 0001001000 / bonus
0002001000), pro-rating the flexi holiday pay (FLEXI_PECULE) across both
in proportion to their respective bases.

An action on validated flexi payslips triggers declaration creation, and
a warning in the payslip list alerts users when flexi payslips still
need
to be declared.

task-6180365

#Belgium#payroll#flexi-workers#NSSO#compliance

Improvements(1)

Enhancements to existing features

[IMP] ai: follow-up buttons

PR #120822

EnterprisemasteraiHIGH

AI assistants can now pause a conversation to ask for confirmation or clarification directly in Discuss, including single-choice and multi-choice answers. This makes AI-driven actions safer and more flexible, while reducing interruptions by allowing users to approve similar actions for the rest of the chat.

Original PR description

Previously, tool execution could only pause for a binary confirmation through a dedicated message action.

Generalize this flow into user input requests stored in the AI session. Tool calls can now pause and whether resume after receiving a confirmation or an answer to a question, while preserving buffered and remaining calls or completely aborted.

Add an AI tool for asking clarification questions and display its choices directly in Discuss, with single- and multi-select support. Reuse the same interface for tool confirmations, including automatic approval for the rest of the chat, and remove the legacy confirmation action and shortcut.

task-id-6140319

#AI#Discuss#approvals#clarification

Belgian companies hiring flexi-workers must transmit the salary data of each validated flexi payslip to the NSSO via the Flexi@Work eGov service (flexi-counter on mycareer.be). A declaration must be sent every time a flexi payslip is created. New `l10n.be.flexi.at.work` model handles the full FLXWAGE flow: XML generation from payslip data, XSD validation against the quarterly ONSS schema, and batch submission. Supports submission, modification, and cancellation operations. The ONSS batch submission infrastructure (XML generation, schema caching, signature/go file handling, state machine) has been extracted into a new abstract `l10n.be.onss.batch.declaration` model that both DMFA and Flexi@Work now share — DMFA previously owned all of this inline. `_get_flxwage_amounts()` on the payslip splits the flexi gross into the two eGov financial-element buckets (remuneration 0001001000 / bonus 0002001000), pro-rating the flexi holiday pay (FLEXI_PECULE) across both in proportion to their respective bases. An action on validated flexi payslips triggers declaration creation, and a warning in the payslip list alerts users when flexi payslips still need to be declared. task-6180365

Previously, tool execution could only pause for a binary confirmation through a dedicated message action. Generalize this flow into user input requests stored in the AI session. Tool calls can now pause and whether resume after receiving a confirmation or an answer to a question, while preserving buffered and remaining calls or completely aborted. Add an AI tool for asking clarification questions and display its choices directly in Discuss, with single- and multi-select support. Reuse the same interface for tool confirmations, including automatic approval for the rest of the chat, and remove the legacy confirmation action and shortcut. task-id-6140319