This module provides a core model to manage collective wage agreements in a multi-company environment. It allows defining and maintaining collective agreements with information such as code, name, scope, publication dates, official publications, state and observations.
auto_awesome What this module does
AI-generated from the code · Odoo 18.0Create and manage collective wage agreements in Odoo, with codes, scopes, publication dates, official publications and a draft/active/finished/cancelled lifecycle. HR managers can activate, finish, cancel and bulk-update agreement states.
This module adds a register of collective agreements to the Human Resources configuration area. Each agreement has a unique code and name, a scope, a publication date (with an optional end date shown as a date range), an official publication, free-text observations, a company and a list of related partners.
Agreements follow a status flow: Draft, Active, Finished and Cancelled. HR managers see buttons to Activate, Finish, Cancel and Reset to Draft, and the status bar shows the current stage. The system blocks activating an agreement whose end date has already passed, blocks finishing one that is not active, and blocks cancelling one that is already finished or cancelled. Cancelling an agreement that has linked partners asks for confirmation first, and finishing an active agreement before its end date also asks for confirmation.
A button on the agreements list, "Update agreement states", automatically finishes agreements whose end date has passed and activates draft agreements that are still valid. Codes and names must be unique, the end date cannot be earlier than the publication date, and duplicating an agreement creates a copy in Draft with "(copy)" added to the code and name.
Two small reference lists are also available: Scopes and Official Publications. All three lists are read-only for regular users and fully editable by HR managers, and agreements are filtered by company.
Depends on
Required by other modules
Menus it adds
Models and fields (3)
- collective.agreement · new modelcode, name, state, active, end_date, scope_id (Scope), company_id (Company), partner_ids (Partners), observations, publication_date, official_publication_id (Official Publication)
- collective.agreement.scope · new modelname
- collective.agreement.official.publication · new modelname
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: 1 confirmed, 8 with no information of 9 versions.
Sources · Odoo 18.0
Confirmed on 2026-11-03 in branch 18.0 of OCA/hr.
terminal Installation and usage
OCA documentation · Odoo 18.0Installation
Source · Odoo 18.0To install this module, you need to:
- Only install
Usage
Source · Odoo 18.0Collective agreements are managed from:
Human Resources → Configuration → Collective Agreements
From this menu, HR Administrators can create, review and maintain collective agreements.
Two auxiliary configuration models are available under the same menu:
- Scopes: Define the scope of application of a collective agreement.
- Official Publications: Define the official publication source of the agreement.
Collective agreements can be manually activated, finished or cancelled according to their lifecycle.
These state transitions are available from the agreement form view. Additionally, multiple agreements can be selected from the list view and processed simultaneously using the action menu.
From this action menu, users can:
- Cancel agreements that are in Draft or Active state.
- Finish agreements that are in Active state only
This module also provides a global action “Update agreement states”. This action reviews all agreements in Draft and Active states and updates their state automatically based on their validity dates.
No verified information in OCA: Configuration.
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.