Account Analytic Spread by Tag
This module distributes the amount of the accounting entry among all the analytical accounts that share the same analytical tag. This module is particularly useful for managing costs in projects, departments, or any other analytic dimensions.
auto_awesome What this module does
AI-generated from the code · Odoo 18.0Lets you mark an analytic tag so that journal item amounts carrying that tag are automatically split equally across all analytic accounts linked to the same tag.
This module adds a spreading option to analytic tags. On an analytic tag you can tick "Spread analytic amounts"; when that tag is used on a journal item, the amount of the item is divided equally among all analytic accounts that are mapped to that tag.
- On the analytic tag form you also get "Spreading Filters": choose Include or Exclude and pick specific analytic accounts, so only those accounts (or all except those) receive a share.
- On each analytic account you can fill in "Tags Mapping" (also shown in the analytic accounts list), which is how an account is linked to a tag.
- The analytic tags list gains a "To Spread" filter to quickly find tags with spreading enabled.
When an invoice or bill line is posted, the module checks its analytic tags. For every tag with spreading enabled it finds the matching analytic accounts, divides the line balance by their number, and creates one analytic line per account with the same date, partner, product, quantity and reference. The original analytic line is kept, so the total analytic amount is not reduced.
It touches account.move.line, account.analytic.tag and account.analytic.account. No new menus are added; the new fields appear inside the existing analytic tag and analytic account screens.
Depends on
Models and fields (3)
- account.move.line · extends an existing model
- account.analytic.tag · extends an existing modelto_spread (Spread analytic amounts), spread_filter_operation (Operation), spread_filter_analytic_account_ids (Analytic Accounts)
- account.analytic.account · extends an existing modelmapped_analytic_tag_ids
Text generated by AI (DeepSeek) from reading the Odoo 18.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: 2 confirmed, 7 with no information of 9 versions.
Sources · Odoo 18.0
Confirmed on 2026-11-03 in branch 18.0 of OCA/account-analytic.
terminal Installation and usage
OCA documentation · Odoo 18.0Configuration
Source · Odoo 18.0- Configuration
Before using the module, you need to configure the Analytic Tags and Analytic Accounts.
Analytic Tags: Go to Accounting > Configuration > Analytic Accounting > Analytic Tags. Create a new tag a enable 'Spread analytic amounts'. Include or exclude analytic account while spreading setting filter in the same view.
Analytic Accounts: Go to Accounting > Configuration > Analytic Accounting > Analytic Accounts. Create new accounts as needed and set tags mapping field.
Usage
Source · Odoo 18.0Usage
- When creating an invoice or a move line, you can assign Analytic Tags to each invoice line. These tags will be used to distribute the cost of the line across the associated Analytic Accounts.
Go to Accounting > Customers > Invoices. Click on "Create" to create a new invoice.
In the invoice lines, select the product, enter the quantity and price, and set an analytic tags preconfigurated for spreading.
- Posting the invoice or move, the module will automatically create analytic lines for each invoice line based on the associated analytic tags.
Click on "Post" to post the invoice.
- Go to Accounting > Analytic Accounting > Analytic Items to see the created analytic lines.
Cancelling the invoice the module will automatically delete the associated analytic lines.
- Go to the invoice and click on "Action" > "Cancel". The associated analytic lines will be deleted.
No verified information in OCA: Installation.
Installation 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.