HR Payroll Account Operating Unit
This module introduces the following features:
- Adds Operating Unit (OU) to the account moves and its lines created by the payslip, based on the Operating Unit (OU) defined in the Employee's Contract.
auto_awesome What this module does
AI-generated from the code · Odoo 15.0When a payslip is posted, the journal entry it creates is automatically tagged with the same Operating Unit as the employee's contract, and Odoo blocks any mismatch between the payslip and its journal entry.
This module links payroll accounting to Operating Units (a way of separating business by branch, division or company segment).
- On each payslip, the Operating Unit is taken automatically from the employee's contract, so users do not have to fill it in by hand.
- When the payslip generates its accounting entry, the Operating Unit is copied onto the journal entry and onto every accounting line of that entry, including the debit, credit and adjustment lines.
- A control rule prevents saving a journal entry whose Operating Unit differs from the Operating Unit of the related payslip: Odoo raises an error saying the journal entry and the payslip must have the same operating unit.
It works together with the payroll accounting, contract operating unit and accounting operating unit features, and affects the hr.payslip and account.move records. No new menus or screens are added; the change is visible directly on payslips and their journal entries.
Models and fields (2)
- hr.payslip · extends an existing modeloperating_unit_id
- account.move · extends an existing model
Text generated by AI (DeepSeek) from reading the Odoo 15.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 12.0
Confirmed on 2026-11-03 in branch 12.0 of OCA/operating-unit.
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.