Leave Status Reference

Summary

Leave requests use four confirmed status strings.

Audience

Employees, managers, administrators, developers, QA, support, and product owners.

Reference Content

Status	Meaning	Confirmed transitions	Balance/Attendance/Payroll relevance	UI
Pending	Awaiting a decision	Created → Pending; Pending → Approved, Rejected, or Cancelled	No confirmed used-balance application; conflict validation may already have run	Warning-style badge
Approved	Accepted absence	Pending → Approved	Applies confirmed usage; Attendance treats approved overlap as conflict; downstream Payroll relevance is eventual	Success-style badge
Rejected	Decision declined	Pending → Rejected	No approved usage; downstream rejection can remove prior projected effect where applicable	Danger-style badge
Cancelled	Request withdrawn	Pending → Cancelled in confirmed service/domain path	Confirmed cancellation reverses usage only where an approved-cancellation path exists; current UI exposes Pending only	Danger-style badge

The exact state machine differs across direct, compatibility, and current UI paths. Approved cancellation visibility and semantics must be checked against the detailed API/business pages before action.

Source References

• microservices/src/leave-service/Domain/Leave/LeaveConstants.cs
• microservices/src/leave-service/Domain/Leave/LeaveRequest.cs
• microservices/src/leave-service/Application/LeaveWorkflows.cs
• UI/salary-ui/apps/client-hrms-portal/src/ess/essApi.ts

Related Articles

• Leave Reference
• Leave business documentation

See Also

• Leave technical documentation
• Leave UI

Keywords

• Leave reference
• Leave Status Reference
• Workforce management

Revision Information

• Status: Draft
• Last reviewed: 2026-07-15
• Review cycle: Quarterly