Leave Impact on Attendance

Summary

Leave and Attendance mutually prevent conflicting approved outcomes, while cross-service ownership remains Transitional.

Audience

Leave/Attendance administrators, employees, managers, Payroll, product owners, and QA.

Overview

Leave creation checks for Attendance in the selected range; approval checks approved Attendance again. If the Attendance dependency cannot provide a reliable answer, the Leave operation fails safely in the reviewed service behavior. The monolith Attendance path blocks marking on approved Leave and the weekly board displays approved Leave.

Automatic creation or mutation of an Attendance record by Leave approval is not confirmed. Event-based synchronization into extracted Attendance ownership requires confirmation. Holiday/weekly-off precedence across both services remains Transitional.

Source References

• microservices/src/leave-service/Application/LeaveWorkflows.cs
• microservices/src/leave-service/Infrastructure/AttendanceServiceConflictClient.cs
• Controllers/AttendanceController.cs
• UI/salary-ui/apps/client-hrms-portal/src/pages/AttendanceStatus.tsx

Related Articles

• Leave overview
• Leave business documentation

See Also

• Attendance module
• Employee module

Keywords

• Leave
• Leave Impact on Attendance
• Workforce management

Revision Information

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