Leave Service Responsibilities

Summary

Leave Service owns Leave-domain state and orchestration while depending on other bounded contexts for master data and downstream outcomes.

Audience

Developers, architects, product/technical owners, QA, DevOps, and support.

Overview

Owned: Leave requests, types, balances, policies, holidays, weekly offs, Leave-day calculation, approval/rejection/cancellation, balance usage, timeline/audit evidence, Leave integration events, a Leave-local employee projection, and carry-forward/encashment foundations.

Not owned: Employee master data, Attendance records, Payroll formulas, identity, tenant provisioning, notification delivery, Workflow-engine internals, or medical/supporting-document storage. Supporting documents are not implemented.

Calendar compatibility and monolith/extracted ownership are Transitional. Carry forward and encashment remain Foundation because domain/persistence types exist without application workflows.

Source References

• microservices/src/leave-service/Domain/Leave/LeaveRequest.cs
• microservices/src/leave-service/Application/LeaveWorkflows.cs
• microservices/src/leave-service/Domain/Leave/LeaveExtras.cs

Related Articles

• Technical overview
• Known limitations

See Also

• Leave business documentation
• Leave overview

Keywords

• Leave Service
• Leave Service Responsibilities
• Technical architecture

Revision Information

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