Attendance Capture
Summary
Confirmed capture modes are manual entry, authorized entry for an employee, punch-based entry, and employee self-service.
Audience
Employees, managers, HR and attendance administrators, analysts, implementation partners, and QA engineers.
Confirmed behavior
Manual capture requires tenant and employee context, a date, and a status; hours may be supplied and multiple dates may be submitted. Punch capture retains every observation and calculates attendance when worked duration is available. Authorized actors may enter and approve for another employee; other users are constrained to their own context.
Where a local employee profile exists, inactive employees and dates before joining are rejected. A resolved weekly off blocks manual entry. One daily result is maintained per employee and date; later saves update it. Multiple punches are supported, but domain-wide duplicate and sequence rules require confirmation. Future dates are prohibited for reopen requests; a universal ordinary-entry restriction was not confirmed.
Device/biometric ingestion and file import are Not implemented in reviewed evidence.
Source References
microservices/src/attendance-service/Application/Services/AttendanceCommands.csmicroservices/src/attendance-service/Application/Services/PunchWorkflow.csmicroservices/src/attendance-service/Api/Endpoints.cs
Related Articles
See Also
Keywords
- Attendance
- Attendance Capture
Revision Information
- Status: Draft
- Last reviewed: 2026-07-15
- Review cycle: Quarterly