Skip to main content

Rejection and Reopening

Summary​

Rejection clears a pending attendance outcome; reopening provides a reasoned, lock-aware route to replace an earlier outcome.

Audience​

Employees, managers, HR and attendance administrators, payroll administrators, analysts, and QA engineers.

Confirmed behavior​

An authorized reviewer may reject attendance. Rejection clears status, work hours, overtime, shortfall, and paid units, leaves the record unapproved, retains a supplied or default business note, and records audit activity.

A reopen request requires an employee, past or current date, reason, and requested status/hours. Only one pending request is allowed for an employee and date. A pending request may be approved or rejected. Approval checks the Payroll period lock, recalculates requested values, creates attendance if none exists, applies an approved outcome, and records audit activity. Rejection stores the decision reason and leaves attendance unchanged. Future dates are prohibited.

Who may initiate on behalf of another employee and the final organizational approval hierarchy require confirmation. Reopen approval changes attendance values, not punch history.

Source References​

  • microservices/src/attendance-service/Domain/Attendance/AttendanceRecord.cs
  • microservices/src/attendance-service/Domain/Attendance/AttendanceReopenRequest.cs
  • microservices/src/attendance-service/Application/Services/ReopenRequestWorkflow.cs

See Also​

Keywords​

  • Attendance
  • Rejection and Reopening

Revision Information​

  • Status: Draft
  • Last reviewed: 2026-07-15
  • Review cycle: Quarterly