Attendance Overview
Summary
Attendance provides tenant-scoped daily attendance outcomes derived from entered or punched working time. It supports review and approval, controlled reopening, and a payroll-period attendance snapshot.
Audience
- Employees, managers, HR and attendance administrators
- Payroll administrators, business analysts, product owners, QA engineers, and implementation partners
Overview
Purpose and outcomes
Attendance connects an employee and attendance date to a business outcome: attendance status, work hours, overtime, shortfall, paid units, and approval state. Its goals are consistent time capture, policy-based calculation, accountable review, correction under control, and a stable payroll handoff.
Main user groups
Employees can view and submit their own attendance context through supported self-service experiences. Source-confirmed approver capabilities are available to administrator-, HR-, manager-, or approver-labelled identities, or an identity with explicit attendance approval permission. The final organizational approval hierarchy is Requires confirmation. Payroll administrators consume approved period results; source evidence does not establish that they administer attendance.
Business capability map
Relationships and maturity
| Area | Confirmed relationship | Maturity |
|---|---|---|
| Employee | Attendance uses an employee profile snapshot for active status, joining date, attendance mode, manager, and fallback calculation context. | Transitional projection |
| Organization | Tenant scope is enforced; manager context is present, but organization-driven attendance policy assignment is not confirmed. | Transitional |
| Shifts | An active effective employee shift can supply scheduled time, grace, standard hours, and overtime threshold. | Implemented |
| Weekly offs | Tenant day-of-week rules prevent manual attendance entry; punch capture can still represent work performed. | Implemented |
| Leave and holidays | The current user experience checks conflicts, while comprehensive leave and holiday composition remains outside the Attendance Service. | Transitional |
| Payroll | Approved attendance is available for period consumption and a payroll-approved snapshot is retained; reopen approval respects a payroll lock. | Implemented with transitional ownership |
| Workflow | Attendance has its own submit, approval, rejection, and reopen behavior. A reusable Workflow-module integration was not confirmed. | Requires confirmation |
| Reporting | Attendance queries provide summaries; ownership of enterprise reports is not confirmed. | Requires confirmation |
Current lifecycle
Context is resolved, attendance is captured, hours and outcomes are calculated, an unapproved record is submitted for review, an authorized reviewer approves or rejects it, and Payroll consumes approved results. A user may request reopening; approval recalculates and restores an approved outcome unless the payroll period is locked.
Transitional ownership
The Attendance Service is the current foundation for attendance and Time Office concepts. Compatibility routing and legacy application behavior remain during transition. Leave, holiday, and payroll composition must therefore be understood as cross-boundary behavior, not as exclusively owned by Attendance.
Source References
microservices/src/attendance-service/Domain/Attendance/AttendanceRecord.csmicroservices/src/attendance-service/Domain/Attendance/AttendancePunchRecord.csmicroservices/src/attendance-service/Application/Services/AttendancePolicyResolver.csmicroservices/src/attendance-service/Application/Services/PayrollSnapshotService.cs
Related Articles
See Also
Keywords
- Attendance capabilities
- Time Office
- Attendance maturity
Revision Information
- Status: Draft
- Last reviewed: 2026-07-15
- Review cycle: Quarterly