> ## Documentation Index > Fetch the complete documentation index at: https://docs.hitaji360.com/llms.txt > Use this file to discover all available pages before exploring further. # Leave Types & Settings > A leave type is the master definition of one kind of leave — Annual, Sick, Maternity, Leave Without Pay, Compensatory, and so on. A **leave type** is the master definition of one kind of leave — Annual, Sick, Maternity, Leave Without Pay, Compensatory, and so on. It owns the rules that govern how that leave behaves: whether it accrues over time, whether unused days carry forward, how many days an employee may hold, whether it is paid, and what restrictions apply when someone tries to take it. Everything else in the leave module ultimately points back to a leave type. Leave types live alongside **leave policies** (which layer approval and notice rules on top), **entitlements**, **leave periods**, and **block lists** on the leave settings screen. This page focuses on leave types; the others are summarised at the end. **You'll find this at:** `/settings/erp/people/leave` (the **Leave Types** tab) > Leave types are defined per tenant. The same type can then be used by policies that are scoped to a particular business, so a multi-business organisation usually keeps one shared list of types and varies the *policies*. > 📷 *Screenshot: the Leave Settings page with its Leave Types / Leave Policies / Entitlements / Leave Periods / Block Lists tabs — to be added.* *** ## Creating or editing a leave type On the **Leave Types** tab choose **New Leave Type** (or click an existing type to edit). The form is grouped into sections; only the name is required, and the optional rules only show their detail fields once you tick the relevant box. ### Basic info | Field | Required | Notes | | --------------- | -------- | ------------------------------------------------------ | | **Name** | Yes | E.g. *Annual Leave*. Must be unique within the tenant. | | **Description** | No | Free text. | ### Accrual settings (Earned Leave) Tick **Earned Leave (Accrual)** to make the type drip days into balances automatically over the year, rather than being allocated as one lump. | Field | Notes | | --------------------------- | ------------------------------------------------------------------------------------------------------------------------- | | **Frequency** | How often the accrual cron credits days: *Monthly*, *Quarterly*, *Half-Yearly*, or *Yearly*. | | **Allocate On** | Which day of the window the credit lands: *First Day*, *Last Day*, or *Date of Joining* (the contract's anniversary day). | | **Rounding** | Rounds each credit to *No Rounding*, *0.25*, *0.5*, or the nearest *Integer* — avoids awkward fractions like 1.6667 days. | | **Earned Leave Allocation** | Days awarded per tick (e.g. 1.5 days per month). | ### Carry forward Tick **Carry Forward** to let unused days roll into the next leave period. | Field | Notes | | -------------------------- | ------------------------------------------------------------------------------------------------------ | | **Carry Forward %** | The fraction of the unused balance that rolls over (0–100). | | **Max Carry Forward Days** | Absolute cap on carried days. The rollover applies *the lower of* the percentage figure and this cap. | | **Expire After (days)** | Days after the new period starts before unused carry-forward expires. Leave blank for "never expires". | ### Encashment Tick **Allow Encashment** to let this type be paid out as cash. | Field | Notes | | --------------------------------- | --------------------------------------------------------------------------------------------------------- | | **Non-Encashable Leaves** | A reserve floor — this many days can never be cashed out, so an employee can't drain their whole balance. | | **Max Encashable Leaves** | Cap on days encashed in a single payout. | | **Allow Self-Service Encashment** | Lets employees request encashment from the self-service portal. | (The encashment workflow itself is covered on the [Leave encashment](/hr/user/leave/leave-encashment) page.) ### Limits & restrictions These guard how and when the leave can be taken. All are optional; leave blank to disable. | Field | Notes | | --------------------------------- | --------------------------------------------------------------------------------------------------------------------------- | | **Max Leaves Allowed** | The most an employee may hold at any one time. An application that would push the holding above this is refused. | | **Applicable After (days)** | A probation gate — the type cannot be applied for until this many days after the contract start date. | | **Max Continuous Days** | Refuses an application longer than this many consecutive days. | | **Min Days Between Applications** | Forces a cool-down: a new application of this type is refused if it starts within this many days of the previous one's end. | ### Flags | Flag | Effect | | ------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **Compensatory Leave** | Marks the type used for comp-off (earned by working extra). Mutually exclusive with Earned Leave. | | **Leave Without Pay (LWP)** | Payroll treats days under this type as unpaid. Mutually exclusive with PPL. | | **Partially Paid Leave (PPL)** | Payroll pays a fraction of salary for these days. When ticked, set **Fraction of Daily Salary** (0–1, e.g. 0.5 for half pay). | | **Optional Leave** | The type may only be taken on dates flagged as *optional* in the contract's holiday list. | | **Allow Negative Balance** | When on, an application is allowed to drive the balance below zero (advance leave against future accrual). When off (default), the application is refused if it would go negative. | | **Include Holidays as LWP** | Public holidays falling inside an application count as Leave Without Pay. | | **Validate Attendance** | Refuses an application covering any date where the employee already has an attendance record of *Present* or *Work From Home*, so a back-dated leave can't silently rewrite payroll/timesheet history. | > **The form stops invalid combinations.** Ticking *Compensatory* clears *Earned Leave* (and vice-versa); ticking *LWP* clears *PPL* (and vice-versa). Carry-forward % must be 0–100, the salary fraction 0–1, and the numeric limits cannot be negative — the form rejects values outside these ranges. *** ## Deleting a leave type Deleting a leave type is a **soft delete** — the record is hidden, not erased, so historical balances and ledger entries that reference it stay intact. The name then becomes free for reuse. *** ## Leave policies (the approval layer) A **leave policy** is the companion object that adds the rules deciding *how a request is handled* — the notice period, the longest stretch allowed, and whether an approver is required. Today's policy form is deliberately short: **Name**, **Description**, **Min Days Notice**, **Max Consecutive Days**, **Requires Approval**, and **Active**. Accrual and carry-forward rules live on the **leave type**, not the policy. > **Adding a leave type does not create a policy, and the Leave Policies tab has no field that lists or selects leave types** — so a new type will not "appear" under policies. Types and policies are two independent lists today; you create each separately and bring them together when you allocate. This is covered in full on the [Leave policies](/hr/user/leave/leave-policies) page. Managing policies needs **`hr:admin`**. You'll find them on the **Leave Policies** tab of the same settings page. > Because policies — not types — are what employees actually hold balances against, the names shown on the leave list, the calendar, and the apply form come from the **policy** name. Name your policies clearly (e.g. "Annual Leave", "Sick Leave") so they read well everywhere. > **No gender or eligibility rule.** Neither a leave type nor a policy can be restricted to one gender — you cannot mark "Maternity" as women-only and have the system enforce it. The only built-in gate is **Applicable After (days)** above. Keep gender-specific leave on the right people by only allocating it to them. See [Leave policies → Eligibility and gender restrictions](/hr/user/leave/leave-policies#eligibility-and-gender-restrictions). *** ## The other tabs * **Entitlements** — the standing per-policy day allowance that feeds allocation. Managed with `hr:admin`. * **Leave Periods** — the calendar windows (usually a year) that balances and carry-forward roll against. See [Leave periods](/hr/user/leave/leave-periods). * **Block Lists** — date ranges (e.g. year-end freeze) when leave of certain types is blocked, optionally with roles allowed to bypass. See [Leave block lists](/hr/user/leave/leave-block-list). *** ## Permissions | Action | Permission | | ------------------------------------------- | ------------------------- | | View leave types | Any authenticated HR user | | Create / edit / delete a leave type | `hr-leave:config` | | Create / edit a leave policy or entitlement | `hr:admin` | *** ## Related * [Leave overview](/hr/user/leave/overview) — how the pieces fit together * [Leave policies](/hr/user/leave/leave-policies) — the approval/notice layer and how it relates to a type * [Leave allocations (control panel)](/hr/user/leave/leave-allocations) — turn types/policies into real balances * [Leave periods](/hr/user/leave/leave-periods) — the windows balances roll against * [Leave block lists](/hr/user/leave/leave-block-list) — freeze leave over set dates * [Leave encashment](/hr/user/leave/leave-encashment) — pay out unused leave * [Holiday lists](/hr/user/leave/holiday-lists) — how holidays interact with leave types