Leave Attendance Integration

Summary

Leave depends on Attendance for conflict detection but does not own or automatically mutate Attendance records.

Audience

Leave/Attendance developers, architects, QA, support, and product engineers.

Overview

Creation and approval invoke the same approved/non-rejected Attendance check. Unavailable or invalid responses fail the normal Leave operation safely. Exact dependency addressing and any non-production relaxation are intentionally excluded.

Compatibility Attendance reads approved Leave and prevents conflicting marking. Leave approval does not create or modify an Attendance record. Holiday/weekly-off ownership overlaps with Attendance Time Office, and cross-service synchronization requires confirmation.

Source References

• microservices/src/leave-service/Application/LeaveWorkflows.cs
• microservices/src/leave-service/Infrastructure/AttendanceServiceConflictClient.cs
• Controllers/AttendanceController.cs

Related Articles

• Technical overview
• Known limitations

See Also

• Leave business documentation
• Leave overview

Keywords

• Leave Service
• Leave Attendance Integration
• Technical architecture

Revision Information

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