The module restores the possibility of defining analytical tags in expenses so that the analytical items generated have those tags.
auto_awesome What this module does
AI-generated from the code · Odoo 19.0Adds an "Analytic Tags" field to expense forms so users can tag expenses with analytic tags, which are then carried over to the accounting entries and payments generated from those expenses.
This module brings back the ability to attach analytic tags to employee expenses. On the expense form, right after the analytic distribution field, a new "Analytic Tags" field appears where users can select one or more tags. The field is only visible to users who belong to the analytic tags group and is editable only while the expense is still editable.
When the expense is posted and its accounting move lines are created, the selected tags are automatically copied onto those lines. The same happens for the payment entries generated for the expense: the tags are added to the move lines that are linked to that specific expense.
- Adds a multi-tag selector on
hr.expenseforms. - Copies the chosen tags to the journal items created from the expense.
- Copies the chosen tags to the journal items created for the expense payment.
- Tags are restricted to the expense's company.
It touches the hr.expense model and the expense form view. No new menus or reports are added; the change is visible directly in the existing Expenses screens.
Depends on
Models and fields (1)
- hr.expense · extends an existing modelanalytic_tag_ids (Analytic Tags)
Text generated by AI (DeepSeek) from reading the Odoo 19.0 code on GitHub; it may contain mistakes, so check the code before deciding. View the code on GitHub
Availability by version
Reviewed: 2026-11-03Confirmation status: 3 confirmed, 6 with no information of 9 versions.
Sources · Odoo 19.0
Confirmed on 2026-11-03 in branch 19.0 of OCA/account-analytic.
terminal Installation and usage
No verified informationInstallation instructions, the distribution package, dependencies and configuration steps are not shown because they have not yet been verified in the module documentation for any version.
Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.