The job of this console
Approve or reject a week, resolve overlapping hours, and understand when lock freezes the period. Do not re-key hours here unless the product offers a correction path.
HRMS · Timesheet · Approval
Timesheet Approval
Submit weeks (or day batches) for manager approval, resolve conflicts, and lock payroll periods.
Flowcharts cover submit → approve/reject → lock. Entry grid: Timesheet.
Week decisions
Submit, conflict, lock — the manager pass
Timesheet approval is the manager pass: submitted weeks (or day batches), conflict resolution, and payroll-period lock. It sits on the same timesheet records the grid wrote.
People → Timesheets (approval)
Route
/people/timesheet
Manager · HR Admin · Payroll (lock window)
Seat at the table
Managers of people who submit. Employees submit from the grid. Payroll cares about lock, not individual cells.
The working rhythm
Open the approval queue, filter the week, open conflicts, approve or reject, then lock when the org’s payroll calendar says so.
Moments that bring you here
Monday after submit. Two projects claiming the same afternoon. Payroll cutoff. A missing leave row that should have filled hours.
ⓘ
Same timesheet, second seat
This is not a second timesheet table. Lock is part of the protected timesheet flow.
Interactive data flow
Same timesheet simulator — toggle partialWeekSubmissionEnabled for full-week vs day-batch pending, enableTimeSheetSubmissionOnBehalfOf for submit-on-behalf, manager/delegate approve, and lock/reopen paths.
Flowcharts
Each diagram auto-plays steps when it scrolls into view. Use Play / Pause, or click a step to jump.
1 — Approval lifecycle
From open week to payroll lock.
flowchart TD
O[Open week] --> Sub[Submit]
Sub --> Pend[Pending manager]
Pend --> Dec{Decision}
Dec -->|Approve| Apr[Approved]
Dec -->|Reject| Rej[Reject + comment]
Rej --> Fix[Employee fixes]
Fix --> Sub
Apr --> Lock[Payroll lock]
- 1Open weekHours entered on Timesheet.
- 2SubmitEmployee submits for approval.
- 3Pending managerAppears in pending panel / Approvals.
- 4DecisionApprove or reject with comment.
- 5ApprovedWeek accepted for payroll.
- 6Reject + commentEmployee notified to fix.
- 7Employee fixesEdit open week and resubmit.
- 8Payroll lockManager/HR locks; corrections need unlock.
2 — Conflict handling
When overlapping entries block approve.
flowchart TD
Pend[Pending week] --> Conf{Conflicts?}
Conf -->|Yes| Modal[Conflict modal]
Modal --> Resolve[Resolve / edit]
Resolve --> Pend
Conf -->|No| Approve[Approve]
- 1Pending weekManager opens approval item.
- 2Conflicts?Overlaps or policy violations.
- 3Conflict modalShows conflicting rows.
- 4Resolve / editFix hours or send back.
- 5ApproveProceed when clean.
Overview
Timesheet approval adds submit, manager review, conflict resolution, and payroll lock on top of the weekly grid. Delegation may allow acting approvers. When Work-Time late-workflow is on, late weeks can require a late reason on submit and may route through published late bands (TIMESHEET-LATE-LTE7 / TIMESHEET-LATE-GT7) instead of the standard chain.
On-behalf submit (timeSheet.enableTimeSheetSubmissionOnBehalfOf) only widens who may click Submit / Resubmit for an already-saved in-scope week. It does not change who can approve, reject, or lock. The week owner stays the selected employee; the actor is stored as submittedBy. Auto-approve-others is a separate role flag and stays independent.
Partial-week flag (timesheetAdditional.partialWeekSubmissionEnabled, default off):
- Off — employee submits the full week; one pending week; week locked until approve/reject; inbox id
WEEK:{id}. - On — employee selects days (chips) and may submit multiple batches per week; each batch is a separate approval request (
ts_timesheet_submission_model); leftover DRAFT/REJECTED days stay editable; approve/reject by submission; inbox idSUBMISSION:{id}. Fully APPROVED weeks still require reopen before edit.
How to use
1. Employee submits
Full week when partial is off; select day chips and submit a batch when partial is on. If Work-Time late-workflow is on and the week is past cut-off, the employee must complete a late reason first. A permitted actor can instead use Submit on behalf for that already-saved week — the owner’s manager/delegate still reviews it.
2. Manager reviews
Pending panel or Approvals inbox (week or submission card). Late weeks may arrive on the moderately late chain (
TIMESHEET-LATE-LTE7, business-unit) or the significantly late chain (TIMESHEET-LATE-GT7, business-unit then finance) when those policies are published.3. Resolve conflicts
Clear overlaps before approve (scoped to the pending week or batch). Late reason is audit context — the employee does not pick the approval route.
4. Approve or reject
Approve to complete the step, or reject with a comment so the employee can fix and resubmit.
5. Lock when ready
Payroll / role month lock still applies. With
timesheet.period-lock on and lockAfterDays set (often 7), approved weeks also auto-lock via TIMESHEET_PERIOD_LOCK; reopen may require a reason.