HRMS · Leave Management

Route /hrms/leaves · /people/leaves Flag leaveManagementEnabled

Leave Management

Apply for leave, track balances, submit for approval, and see manager decisions — with working-week and holiday aware day counts.

Scroll to Flowcharts for animated step-by-step diagrams. Admin setup: Leave Configuration.

Apply and track

Balances, a request, and a manager decision

Leave management is where people apply, watch balances, submit for approval, and see decisions — with working-week and holiday aware day counts. Policy is authored elsewhere; this is runtime.

People → Leave management Route /hrms/leaves Org flag leaveManagementEnabled Employee · Manager · HR Admin

The job of this console

Apply for leave, read the balance the policy assigned, submit, and respond if you are the manager. Do not edit policy math here. Documents and absence cases have their own admin registers when those flags are on.

Seat at the table

Every employee with leave enabled. Managers approve in this flow or in My Approvals. HR may apply on behalf when the product allows.

The working rhythm

Open leave, check balance, choose type and dates, review the day count, submit, then watch status. Managers approve or reject with a comment. Cancel only while the engine still allows it.

Moments that bring you here

A long weekend. Balance looks wrong after a policy publish. A rejection that needs a resubmit. Overlap with a holiday.

ⓘ

Runtime, not policy center

Global Policy Center, employee leave config, and shift policies own the rules. This page only creates leave on that engine.

One-stop leave guide

Configuring leave for the first time? Use the one-stop guide (configure, dry-run, schedulers, approval + data-flow debug). Policy catalogue and screen setup remain available below.

Start hereOpen Leave One-Stop Guide → Admin setupLeave Configuration → Policies catalogue

Interactive data flow

Toggle leave org/role flags live — trace fs_emp_leave_master_model, balance reserve, approve, and promotion without touching production.

Primary simulatorLeave request & approve → Also seePolicy & accrual → All simulators

Flowcharts

Each diagram auto-plays steps when it scrolls into view. Use Play / Pause, or click a step to jump. Matching flowchart nodes highlight as you go.

1 — End-to-end leave

The full path from “policy ready” to timesheet impact. Use this when explaining leave to a new team.

flowchart TD
  A[Policy and balances ready] --> B[Apply]
  B --> C[Submit]
  C --> D[Approve or Reject]
  D --> E[Balance + timesheet]

1
Policy and balances readyPublished leave policy plus balances from Employee leave config (OB import / Adjust balance) or accrual.
2
ApplyEmployee opens Leave Management, picks type and dates; day count uses their working week and holidays.
3
SubmitOverlap and working-day checks run; pending balance is reserved; approver is notified.
4
Approve or RejectManager or delegate decides. Reject requires a comment and releases pending balance.
5
Balance + timesheetOn approve: debit ledger, promote leave TaskActivities, optional attendance sync.

2 — Request lifecycle statuses

How a leave row moves through workflow statuses, including reject and withdraw paths.

flowchart TD
  C[CREATED] --> S[SUBMITTED]
  S --> A[APPROVED]
  A --> P[Promoted / Synced]
  S --> R[REJECTED]
  S --> W[Withdraw / Cancel]
  W --> Rel[Pending released]
  R --> Rel

1
CREATEDDraft leave after create; not yet in the manager queue.
2
SUBMITTEDAwaiting approval; balance held as pending.
3
APPROVEDAuthority accepted; debit starts; promotion may still be pending/retrying.
4
Promoted / SyncedTimesheet leave activities exist; attendance may show LEAVE when sync is on.
5
REJECTEDManager declines with comment; pending balance released.
6
Withdraw / CancelEmployee or HR stops the request per status rules.
7
Pending releasedHeld days return to available after reject/withdraw.

3 — Employee apply leave

What the employee does in the Apply leave drawer, including fixing overlap or non-working ranges.

flowchart TD
  O[Open Leaves] --> B[Check balance]
  B --> A[Apply leave]
  A --> T[Pick type and dates]
  T --> D[Review day count]
  D --> V{Overlap or non-working only?}
  V -->|Yes| Fix[Fix dates]
  Fix --> T
  V -->|No| Sub[Submit for approval]

1
Open LeavesHRMS → Leaves (or People → Leaves) with leave module enabled.
2
Check balanceConfirm available days for the leave type on the balance cards.
3
Apply leaveOpen the apply drawer from the header action.
4
Pick type and datesChoose leave type, from/to, optional half-day and reason.
5
Review day countCount excludes weekly offs and holidays for this employee.
6
Overlap / non-working checkSystem blocks bad ranges; fix dates if needed.
7
Fix datesAdjust range until overlap and working-day rules pass.
8
Submit for approvalRequest becomes SUBMITTED and appears in the manager queue.

4 — Manager approve / reject

Manager or delegate decision path from pending panel or Approvals inbox.

flowchart TD
  P[Pending panel or Approvals inbox] --> Rev[Review dates and days]
  Rev --> Dec{Decision}
  Dec -->|Approve| Deb[Debit balance]
  Deb --> Pro[Promote TaskActivity]
  Pro --> Att[Attendance sync if flagged]
  Dec -->|Reject| Com[Reject + required comment]
  Com --> Rel[Pending balance released]

1
Open pendingLeave Management pending panel or Workspace Approvals inbox.
2
ReviewCheck employee, type, dates, day count, and reason.
3
DecisionApprove or reject (reject needs a comment).
4
Debit balanceApproved leave moves days from pending to used.
5
Promote TaskActivityLeave days appear on timesheet; retries if promotion fails.
6
Attendance syncWhen flagged, writes LEAVE / HALF_DAY on the attendance matrix.
7
Reject + commentEmployee is notified; request closed as REJECTED.
8
Pending releasedHeld balance returns to available.

5 — How day count is resolved

Why Saturday may count (Mon–Sat) or Friday may not (Sun–Thu). Priority: employee override → jurisdiction → team → fallback.

flowchart TD
  Emp[Leave subject employeeId] --> Res[Working-day resolver]
  Res --> P1{Override?}
  P1 -->|Yes| WD[Workdays set]
  P1 -->|No| P2{Jurisdiction rule?}
  P2 -->|Yes| WD
  P2 -->|No| P3[Team / schedule / Mon-Fri]
  P3 --> WD
  WD --> Hol[Minus holidays]
  Hol --> Days[numberOfDays]

1
Leave subjectResolver uses the employee the leave is for — not only the team.
2
Working-day resolverSingle service used by create, submit, promote, and the apply drawer.
3
Employee override?Personal working-day rule wins if assigned.
4
Workdays setISO weekdays that count (e.g. 1–5 or 7,1–4 for Sun–Thu).
5
Jurisdiction rule?Country/region pattern if the employee is assigned a leave jurisdiction.
6
Team / schedule / Mon–FriTeam-default rule, then work schedule/shift, then Mon–Fri.
7
Minus holidaysPeople holidays matching assigned calendar keys are excluded.
8
numberOfDaysServer recalculates on create/submit; drawer estimate is guidance only.

Overview

HRMS → Leaves is the employee and manager hub for time off. When leaveManagementEnabled is on, you create and submit requests here; managers approve from the pending panel or Approvals inbox.

Feature & use-case map

Use case	Who	What happens
View balances	Employee	Available / used / pending by type
Apply full-day / half-day	Employee	Create + submit; day count from resolver
Approve / reject	Manager / delegate	Debit + promote, or release pending
Withdraw / cancel	Employee / HR	Balance reverse/release per status

Balances, a request, and a manager decision

The job of this console

Seat at the table

The working rhythm

Moments that bring you here

One-stop leave guide

Interactive data flow

Flowcharts

Overview

Feature & use-case map

Related pages