Attendance Calculation
Summary
Status, work hours, paid units, overtime, or shortfall is unexpected.
Audience
Employees or administrators affected by the scenario, first-line support, QA, service owners, and operations.
Symptoms
- Status, work hours, paid units, overtime, or shortfall is unexpected.
Scope
Direct and Hourly calculation results.
Likely causes
Unexpected inputs, mode, effective shift, active default policy, employee-profile fallback, or unconfirmed business-policy expectation.
Cause
The confirmed cause categories are listed under Likely causes above; determine the applicable category from sanitized evidence before taking action.
Safe diagnostic steps
- Collect sanitized inputs and resolved mode/shift/policy identifiers through approved telemetry; compare with the status/mode references. Do not derive or publish confidential numeric rules.
- Preserve tenant isolation and redact personal or security-sensitive data.
- Do not use direct database changes, authorization bypasses, or ad hoc broker operations.
Safe resolution
Correct source inputs/configuration through approved workflows, then use the supported recalculation/reopen path.
Resolution
Apply only the Safe resolution described above and remain within the documented ownership boundary.
Validation
Confirm the recalculated record and downstream snapshot impact where applicable.
Evidence to collect
Employee/date reference, mode, resolved-context identifiers, before/after outcome, correlation identifier.
Escalation
Attendance owner for calculator behavior; Time Office/product owner for policy intent; Payroll owner for consumed results.
Related docs
Related Articles
Source References
microservices/src/attendance-service/Domain/Attendance/AttendanceCalculator.csmicroservices/src/attendance-service/Application/Services/AttendancePolicyResolver.cs
See Also
Keywords
- Attendance
- Troubleshooting
- Attendance Calculation
Revision Information
- Status: Draft
- Last reviewed: 2026-07-15
- Review cycle: Quarterly