Attendance Validation Reference

Summary

This matrix catalogs confirmed validation categories; exact internal messages and numeric thresholds are not published.

Developers, QA, support, and administrators.

Area	Rule	Layer	Error category	Maturity
Context	Tenant and employee context are required	API/application	Unauthorized or invalid request	Implemented
Daily record	One outcome per employee/date	Domain/persistence	Conflict	Implemented
Employee	Profile must be active and date-valid	Application/domain	Invalid request	Implemented
Manual capture	Resolved weekly off blocks manual marking	Application	Invalid request	Implemented
Hours/status	Values must satisfy the selected mode	Domain calculator	Validation	Implemented
Shift assignment	Effective dates cannot overlap	Domain/application	Conflict	Implemented; UI absent
Reopen	Only one pending request per employee/date	Application/persistence	Conflict	Implemented
Reopen	Future dates are prohibited	Application	Validation	Implemented
Reopen approval	Payroll-locked periods cannot be reopened	Application/integration	Conflict/dependency	Implemented
Workflow	Transition must be valid for current state	Domain/application	Conflict	Implemented

The source-backed catalog above is the normative reference content for this Draft page.

microservices/src/attendance-service/Application/Services/AttendanceCommands.cs
microservices/src/attendance-service/Application/Services/ReopenRequestWorkflow.cs
microservices/src/attendance-service/Application/Services/ShiftPolicyCommands.cs