OCA modules for Odoo

Disallow the modification of the code of accounts that have journal items.

This module adds a field 'code' to model 'account.account.tag'. This field 'code' is useful to search specific tags without having problems with the translations.

The goal of this module is to restore the Analytic Tags fields (tag_ids) on the Analytic Account (account.analytic.account) model that was present until Odoo 11. It allows to classify analytic accounts according to different categories.

This module allows to propagate analytic distribution from branded analytic distribution models on account moves.

This module adds the ability to set a default analytic account on accounts.

This modules sets default values for analytic accounts in purchases. Fixes issue described here: Odoo issue #22896.

This module provides an easy way to quickly autocomplete analytic accounts on any model that has a field for analytic accounts.

This module introduces Start Date and End Date fields for manual distribution. This functionality enforces stricter management of distributions by ensuring only relevant distributions within the specified time periods are shown, based on the invoice date, the Journal Entry date or the today's date

This module allows you to regenerate the analytic distribution of the journal items, that were generated by the distribution model. It adds the posibility to add a Start Date and End Date for the distribution models too.

This module extends account_analytic_required and adds 2 policies to control the use of analytic distributions. The policies behave as follow · never: no analytic account nor analytic distribution allowed · always: analytic account required · always_plan: analytic_distribution required · always_plan_or_account: analytic distribution or analytic account required · optional: do what you like, In any case analytic account and analytic distribution are mutually exclusive.

This module adds a "Rebalance" button to the analytic distribution widget, that let's adjust a line percentage to make the plan total exactly 100%.

The module introduces a new field in the accounting records to specify the "Accrual Date" for income and expenses. This field is crucial for accurately tracking when the revenue or expense is earned or incurred, regardless of the invoice creation date. For instance, if an invoice is created in December but refers to sales made in November, the Accrual Date allows us to reflect this correctly in our accounting records. This ensures compliance with accrual-based accounting…

This module adds the Commercial Entity field (technical name commercial_partner_id) to analytic items and allows users to group _Analytic items_ by this field.

Changes account analytic line name field to Text.

This module adds analytic distribution support to maintenance equipment. The analytic distribution stored on the equipment can be reused by other modules, such as purchases or inventory integrations

This module hides analytics lines from accounting menus and disable their generation from a move line. In many situations (i.e. when there are no analytic distribution, and when people don't consider timesheets as analytic entries), the generation of analytic entries for each account move is redundant, creates overhead and poses a risk of desynchronization between analytic data and GL entries. In such situations, users are happy to do their analytics reporting on account…

This module adds a new field on the partner. This organization field is also added on the account analytic line and account move line so you can filter and group by it.

This module reintroduces the hierarchy to the analytic accounts as it was in previous versions of Odoo. This module is a base module for other modules to manage the hierarchy concept in analytics. It also exposes a computed Level field expressing the depth of each account within its subtree: level 0 for a leaf account (no children), level 1 for a parent whose children are all leaves, level 2 for a grandparent...

This module extends the analytic account hierarchy introduced by the account_analytic_parent module. It forces every account in a parent/child tree to belong to the same analytic plan, so a hierarchy can never belong to more than one plan.

This module adds an option analytic policy on accounts. You have the choice between 4 policies : always, never, posted moves and empty (optional).