Leave Business Rules
Summary
This register separates confirmed, transitional, unresolved, and absent Leave rules.
Audience
Leave/HR/Payroll administrators, managers, analysts, product owners, QA, and implementers.
Reference Content
Confirmed rules
| Area | Rule | Source |
|---|---|---|
| Tenant/employee | Tenant and active employee are required; dates cannot precede joining. | Leave request and commands |
| Date range | End date cannot precede start; calculated days must be positive. | Leave request/calculator |
| Conflict | Existing Attendance and approved overlapping Leave block creation; approved Attendance blocks approval. | Commands |
| Calculation | Inclusive range is default; enabled policy can exclude holidays/weekly offs; half day applies to one effective day. | Calculator |
| Submission | Ordinary compatibility self requests are Pending; tenant administration may auto-approve while Workflow is off. | Controller/commands |
| Approval | Only Pending can be approved; approval applies balance usage. | Request/commands |
| Rejection | Only Pending can be rejected and a reason is required. | Request/commands |
| Cancellation | Pending/Approved can become Cancelled; prior approved usage is reversed. | Request/commands |
| Balance | Balance is per user/type/year and available incorporates opening, accrued, adjusted, carried, used, and encashed units. | Balance |
| Auditability | Request decisions and balance changes produce timeline/audit evidence. | Commands |
Transitional rules
| Area | Rule |
|---|---|
| Workflow | Direct approval is default; optional Workflow ownership suppresses direct decisions for managed requests. |
| Leave types | First-class type metadata coexists with legacy textual conventions. |
| Calendar | Leave and Attendance weekly-off/holiday compatibility ownership overlaps. |
| Payroll | Approved Leave is consumed through legacy read behavior; extracted consumer timing requires confirmation. |
| Authorization | Monolith self/team/tenant scope and extracted service ownership are not yet a final unified model. |
Requires confirmation
Policy activation, minimum notice, maximum duration, annual cap, balance sufficiency/negative-balance governance, accrual execution, type eligibility, date restrictions beyond joining, Pending-overlap policy, resubmission, cancellation after Payroll, calendar precedence, final approver hierarchy, notification parity, and cross-service synchronization.
Not implemented
Supporting documents, request editing, reserved Pending balance, employee/group policy assignment, policy effective dates, carry-forward execution, encashment workflow, team calendar, cancellation approval, and a governed post-Payroll correction flow.
Source References
microservices/src/leave-service/Domain/Leave/LeaveRequest.csmicroservices/src/leave-service/Domain/Leave/LeaveBalance.csmicroservices/src/leave-service/Domain/Leave/LeaveDayCalculator.csmicroservices/src/leave-service/Application/LeaveWorkflows.csControllers/LeaveRequestsController.cs
Related Articles
See Also
Keywords
- Leave
- Leave Business Rules
- Workforce management
Revision Information
- Status: Draft
- Last reviewed: 2026-07-15
- Review cycle: Quarterly