Skip to Content
Odoo model · Enterprise

hr.payslip.employee.depature.notice

Manage the Employee Departure - Notice Duration. Defined in module l10n_be_hr_payroll; exists in Odoo 18, 19. Across the upgrade steps we tracked: 2 fields added, 0 removed, 0 renamed.

  1. Odoo 16 not covered
  2. Odoo 17 not covered
  3. Odoo 18 l10n_be_hr_payroll
  4. Odoo 19 l10n_be_hr_payroll
  5. Odoo 20 not present

This is an Enterprise model: Odoo 16 and 17 Enterprise sources are not part of the data, so those versions show as not covered.

Odoo 17 to 18

Community only All changes in this step

Not covered: this step compares Community modules only and this model belongs to an Enterprise module.

Odoo 18 to 19

Community + Enterprise All changes in this step

Fields added (2)

FieldTypeModule
l10n_be_scale_seniorityintegerl10n_be_hr_payroll
use_seniority_at_hiringbooleanl10n_be_hr_payroll

Odoo 19 to 20

Community + Enterprise All changes in this step

Removed in Odoo 20.

1 views of this model removed
  • l10n_be_hr_payroll.view_hr_payroll_employee_departure_notice
1 actions on this model removed
  • l10n_be_hr_payroll.departure_notice_wizard_action
1 menus opening this model removed
  • l10n_be_hr_payroll.menu_l10n_be_hr_payroll_notice

All fields declared on hr.payslip.employee.depature.notice (18)

Fields this model declares itself in any version, with the versions they exist in. Inherited fields (mail.thread and other mixins) are on the parent model's page.

present not present not covered (Enterprise, Odoo 16 and 17)

Show all 18 fields
FieldTypeLabelModule1617181920
actual_notice_durationintegerActual Notice Durationl10n_be_hr_payrollE
departure_datedateDeparture Datel10n_be_hr_payrollE
departure_descriptioncharDeparture Descriptionl10n_be_hr_payrollE
departure_reason_codeintegerl10n_be_hr_payrollE
employee_idmany2one hr.employeeEmployeel10n_be_hr_payrollE
end_notice_perioddateEnd Notice Periodl10n_be_hr_payrollE
first_contractdateIn the Company Sincel10n_be_hr_payrollE
l10n_be_scale_seniorityintegerSeniority at Hiringl10n_be_hr_payrollE
leaving_type_idmany2one hr.departure.reasonDeparture Reasonl10n_be_hr_payrollE
notice_duration_month_before_2014integerNotice Duration in monthl10n_be_hr_payrollE
notice_duration_week_after_2014integerNotice Duration in weeksl10n_be_hr_payrollE
notice_respectselectionRespect of the notice periodl10n_be_hr_payrollE
oldest_contract_idmany2one hr.versionOldest Contractl10n_be_hr_payrollE
salary_december_2013selectionGross Annual Salary as of December 31, 2013l10n_be_hr_payrollE
salary_visibilitybooleanSalary as of December 2013l10n_be_hr_payrollE
seniority_descriptioncharSeniorityl10n_be_hr_payrollE
start_notice_perioddateStart Notice Periodl10n_be_hr_payrollE
use_seniority_at_hiringbooleanUse Seniority at Hiringl10n_be_hr_payrollE

Related models

Linked by its relational fields: hr.departure.reasonhr.employeehr.version

Coverage. Odoo 16 to 17 and 17 to 18 compare Community modules only (the Enterprise 16 and 17 sources are not available to us). Odoo 18 to 19 and 19 to 20 include Community and Enterprise modules. Everything here comes from a static read of the Odoo source code: a field counts as removed only when no parent model, mixin or delegated model still provides it. Fields created dynamically at run time can be missed, and entries we could not confirm are marked as low confidence.