Skip to main content

Leave and Holiday Impact

Summary​

Weekly-off behavior is owned in Attendance; leave and holiday conflict handling remains transitional across Attendance and the legacy application.

Audience​

Employees, managers, HR, attendance and payroll administrators, analysts, and QA engineers.

Confirmed interactions​

Manual attendance is blocked on an Attendance-resolved weekly off; actual punch capture remains possible. The current user experience identifies holiday and weekly-off dates and prevents ordinary marking in those contexts. Leave-request handling checks for existing attendance, and approved leave is presented as blocking attendance in the coordinated experience.

The Attendance calculator itself does not consume approved leave or holiday context, and its monthly summary is attendance-derived rather than a blended calendar/payroll result. Automatic leave synchronization, precedence among attendance, leave, holiday, and weekly off, holiday ownership, overlap resolution, and payable treatment are Transitional / Requires confirmation. An attendance status named Leave is not confirmed; the daily status vocabulary remains Present, Half Day, and Absent.

Source References​

  • microservices/src/attendance-service/Application/Services/AttendanceCommands.cs
  • microservices/src/attendance-service/Application/Services/AttendancePolicyResolver.cs
  • microservices/src/attendance-service/Application/Services/AttendanceQueries.cs
  • UI/salary-ui/apps/client-hrms-portal/src/pages/hr/PayrollFeaturePages.tsx

See Also​

Keywords​

  • Attendance
  • Leave and Holiday Impact

Revision Information​

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