Odoo 20.0 Community · Persistent

hr.employee.departure: fields, relations and API

The hr.employee.departure model ("Employee Departure") is a persistent model declared by the Employees module, then extended by 3 other modules. It exposes 17 fields, 11 of them declared directly on the model; 2 fields from other models point to it. Below you will find every field with its technical name, type, label and relations, followed by an Odoo 20 JSON-2 API call.

View source code Search another model

Model identity

Technical name: hr.employee.departure
Label: Employee Departure
Type: Persistent (models.Model)
SQL table: hr_employee_departure
Origin module: Employees (hr)
Extended by: hr_fleet, hr_holidays, hr_maintenance

Model fields

11 own fields, 0 inherited from mixins and 6 automatic ORM fields. Click a name to get a direct link to that field.

Hide inherited fields

17 of 17 fields shown

Technical name	Label	Type	Details
action_date	Archive Employee On Date at which the departure actually takes place.	`date`	computed, stored
apply_date	Apply Date	`date`	read-only
apply_immediately	Apply Immediately	`boolean`	computed
country_code	Country Code	`char`	related: `employee_id.company_id.partner_id.country_id.code`
departure_date	Departure Date Date at which the departure actually takes place.	`date`	computed, stored
departure_description	Additional Information	`html`
departure_reason_id	End Reason	`many2one` → hr.departure.reason	required
dismissal_date	Dismissal Date Date at which the departure process starts. Differs from the actual departure date in case of a notice period.	`date`	required
employee_id	Employee	`many2one` → hr.employee	required
is_user_employee	Is User Employee	`boolean`	computed
last_contract_date_end	Last Contract Date End	`date`
create_date	Created on	`datetime`	read-onlyautomatic
create_uid	Created by	`many2one` → res.users	read-onlyautomatic
display_name	Display Name	`char`	read-onlycomputedautomatic
id	ID	`integer`	read-onlyautomatic
write_date	Last Updated on	`datetime`	read-onlyautomatic
write_uid	Last Updated by	`many2one` → res.users	read-onlyautomatic

Relations

Models linked from this model

hr.departure.reason: departure_reason_id
hr.employee: employee_id

Fields of other models pointing here

hr.employee: departure_id
hr.version: departure_id

Reading this model through the API

Odoo 20 JSON-2 API call reading the first five records with real fields of the model. Replace the instance, database and API key with your own.

curl

curl -X POST "https://your-instance.odoo.com/json/2/hr.employee.departure/search_read" \
  -H "Authorization: bearer $ODOO_API_KEY" \
  -H "X-Odoo-Database: your-db" \
  -H "Content-Type: application/json" \
  -d '{"domain":[],"fields":["departure_reason_id","dismissal_date","employee_id","action_date","apply_date"],"limit":5}'

Python (requests)

import requests

BASE_URL = "https://your-instance.odoo.com/json/2"
headers = {"Authorization": f"bearer {API_KEY}", "X-Odoo-Database": "your-db"}

res = requests.post(
    f"{BASE_URL}/hr.employee.departure/search_read",
    headers=headers,
    json={"domain": [], "fields": ["departure_reason_id","dismissal_date","employee_id","action_date","apply_date"], "limit": 5},
)
res.raise_for_status()
print(res.json())

External API access requires Odoo's Custom plan.
XML-RPC and JSON-RPC will be removed in Odoo 22 (fall 2028): use JSON-2.
The access rights and record rules of the key's user apply.

Cite this tool

Writing a tutorial, internal documentation or a forum answer? Copy this link to send your readers to the up-to-date reference.

<a href="https://aidoo.ai/en/outils/explorateur-modeles-odoo/hr-employee-departure">hr.employee.departure (Odoo 20.0)</a>

Sources

Data verified on September 25, 2026 · Odoo 20.0 Community

Have an Odoo project, or want to put your ERP to work with AI? Let's talk

Implementation, custom module development, connecting Claude or ChatGPT to your data: tell us about your context and we will reply within 24 business hours.