Leave Balance and Policy Model

Summary

Balance, Leave type, and policy are related by employee/user, type text, and year, but enforcement is intentionally incomplete.

Audience

Backend developers, architects, QA, Payroll integrators, and product engineers.

Overview

Approval increases used units; cancellation after approval reverses usage. Balance components are normalized by domain methods, and encashment foundation checks availability. Active policy lookup drives holiday/weekly-off exclusions.

Stored notice, maximum duration, accrual, maximum carry forward, negative-balance, annual-cap, type-active, and half-day-eligibility fields are not fully enforced. Centralized policy assignment, employee/group scope, effective dates, and precedence are absent.

Source References

• microservices/src/leave-service/Domain/Leave/LeaveBalance.cs
• microservices/src/leave-service/Domain/Leave/LeaveConfig.cs
• microservices/src/leave-service/Application/LeaveWorkflows.cs

Related Articles

• Technical overview
• Known limitations

See Also

• Leave business documentation
• Leave overview

Keywords

• Leave Service
• Leave Balance and Policy Model
• Technical architecture

Revision Information

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