Leave Encashment

Summary

Encashment has a domain and persistence foundation but no confirmed end-to-end employee, approval, or Payroll workflow.

Audience

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

Concepts

The model contains employee/user, Leave type, year, requested units, optional monetary field, status vocabulary, requester, and processing time. Balance logic can reject non-positive units or units above available balance and can reduce availability through encashed units.

The currently defined record factory creates an approved record immediately, but no application command or exposed capability invokes it. Therefore Requested, Rejected, and Paid are vocabulary only, not a confirmed state machine. Eligibility enforcement, approver, monetary calculation, Payroll handoff, audit workflow, cancellation, and correction are Not implemented / Requires confirmation. No monetary formula is documented.

Source References

• microservices/src/leave-service/Domain/Leave/LeaveExtras.cs
• microservices/src/leave-service/Domain/Leave/LeaveBalance.cs
• microservices/src/leave-service/Application/Dtos.cs

Related Articles

• Leave overview
• Leave business documentation

See Also

• Attendance module
• Employee module

Keywords

• Leave
• Leave Encashment
• Workforce management

Revision Information

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