Skip to main content

Leave Overview

Summary

Leave provides a governed record of employee absence from request through decision and downstream workforce use.

Audience

Employees, managers, Leave/HR/Payroll administrators, analysts, product owners, QA, and implementation partners.

Overview

Business outcomes include consistent absence requests, visible decisions, balance usage, calendar-aware day counting where policy enables it, Attendance conflict prevention, and approved-leave input for workforce and Payroll processing.

Employee provides eligibility and manager context. Organization contributes tenant and reporting scope. Holidays and Leave-owned weekly offs can affect day count when policy exclusions are enabled. Attendance conflict checks reject overlapping marked/approved Attendance, while Attendance compatibility behavior recognizes approved Leave. Payroll currently consumes approved Leave through legacy read behavior and distinguishes paid/unpaid through transitional conventions. Workflow delegation is optional; direct approval remains the default behavior. Notification of approval is confirmed in the monolith path, while extracted-service notification consumption requires confirmation.

Source References

  • microservices/src/leave-service/Domain/Leave/LeaveRequest.cs
  • microservices/src/leave-service/Application/LeaveWorkflows.cs
  • UI/salary-ui/apps/client-hrms-portal/src/pages/hr/PayrollFeaturePages.tsx

See Also

Keywords

  • Leave
  • Leave Overview
  • Workforce management

Revision Information

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