Skip to main content

Work Calendar and Leave Integration

Summary

Leave integrates with work-calendar data through holiday and weekly-off exclusion and with Attendance through overlap/conflict checks. It does not use shift assignments to calculate roster-specific leave days.

Audience

Employees, managers, HR administrators, product, QA and solution architects.

Reference Content

Business process

  1. A leave request supplies employee, date range, leave type and half-day choice.
  2. Leave validates joining date and checks for existing approved attendance in the range.
  3. The leave policy, holidays and weekly-off days are loaded.
  4. Leave duration is calculated, excluding holidays/weekends when the selected leave policy requires it.
  5. Approval checks attendance conflict again before finalizing.

Business rules and outcomes

  • Approved attendance prevents adding or approving overlapping leave.
  • Approved leave overlap is rejected.
  • A calculated duration must remain positive.
  • Holiday and weekly-off exclusions depend on leave-policy flags.
  • Attendance weekly UI displays holiday/weekly-off before approved leave for a date.

Responsibilities

HR owns accurate holiday/weekly-off and leave-policy configuration. Managers decide leave in their supported scope. Employees choose valid dates. Attendance/leave owners must reconcile routing and duplicated compatibility calendar surfaces.

Limitations

No roster-aware leave duration, shift-cross-midnight leave allocation, replacement staffing, shift swap, team capacity or department coverage calculation exists. Shifts themselves are not queried by Leave.

Requires confirmation

Local statutory holidays, sandwich rules, substitute holidays and operational coverage practices require confirmation.

Business Evidence Checklist

  • Business purpose: Align leave duration/conflicts with work-calendar and attendance data.
  • Actors: Employees request, managers/HR decide, Leave and Attendance enforce boundaries.
  • Business process: Validate range, check attendance, calculate days and decide.
  • Status transitions: Leave transitions exist in Leave; scheduling adds none.
  • Responsibilities: HR maintains calendars/policies and managers validate decisions.
  • Business rules: Attendance conflict, approved overlap and positive duration rules apply.
  • Integrations: Holidays, weekly offs, Attendance and downstream Payroll.
  • Limitations: No roster-aware duration or replacement staffing.
  • Requires confirmation: Statutory and tenant leave-calendar practices require confirmation.

Source References

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

See Also

Keywords

  • Leave calendar
  • Weekly-off exclusion
  • Attendance conflict

Revision Information

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