Attendance Business Rules

Summary

This register separates confirmed rules from transitional, unresolved, and unsupported capabilities.

HR, attendance and payroll administrators, managers, analysts, product owners, implementation partners, and QA engineers.

Category	Confirmed rule	Evidence
Tenant and employee	Attendance requires tenant and employee context; available profiles enforce active status and joining date.	Attendance commands
Uniqueness	One daily attendance outcome is maintained per tenant, employee, and date.	Attendance record and commands
Punch	Multiple observations are retained; sufficient duration can derive attendance.	Punch workflow
Shift assignment	Active assignments are effective-dated and cannot overlap when created through confirmed behavior.	Policy resolver
Policy	Shift context precedes tenant default policy; profile supplies fallback context.	Policy resolver
Calculation	Non-negative canonical hours produce Present, Half Day, or Absent and paid units.	Calculator
Submission and approval	Non-approvers submit pending outcomes; authorized approval recalculates and audits.	Attendance commands
Rejection	Rejection clears outcome values and leaves the record unapproved.	Attendance record
Reopening	One pending request per employee/date; approval recalculates and respects payroll lock.	Reopen workflow
Weekly off	Manual entry is blocked; punch capture remains possible.	Commands and resolver

Classification	Rules
Transitional	Employee profile is a local projection; leave/holiday and blended payroll calendar behavior span service and legacy ownership; compatibility routing remains during cutover.
Requires confirmation	Punch sequence/duplicates, future ordinary entry, team scope, approval hierarchy, break/rounding policy, overtime eligibility/rates, policy replacement governance, leave/holiday precedence, post-payroll correction.
Not implemented in reviewed evidence	Device/biometric ingestion, file import, employee-specific attendance-policy assignment, policy effective dates, rotating rosters, and dedicated reusable Workflow integration.

Every rule above is supported by the source paths below; tenant-specific values and internal mechanics are intentionally excluded.

microservices/src/attendance-service/Domain/Attendance/AttendanceRecord.cs
microservices/src/attendance-service/Domain/Attendance/AttendanceCalculator.cs
microservices/src/attendance-service/Application/Services/AttendanceCommands.cs
microservices/src/attendance-service/Application/Services/PunchWorkflow.cs
microservices/src/attendance-service/Application/Services/ReopenRequestWorkflow.cs
microservices/src/attendance-service/Application/Services/AttendancePolicyResolver.cs