The job of this console
Log the week, pass validation, submit if the org requires approval, and stop editing when the period locks. Leave hours should follow approved leave, not a parallel guess.
HRMS · Timesheet
Timesheet
Monday–Sunday grid for billable, non-billable, and leave hours — with week navigation, validation, and optional approval.
Scroll to Flowcharts. Approval workflow: Timesheet Approval.
Monday–Sunday grid
Hours on work already in the system
Timesheet is the Monday–Sunday grid for billable, non-billable, and leave hours — week navigation, validation, and optional approval. Rows point at projects and tasks you already have.
People → Timesheets
Route
/hrms/timesheet
Employee · Manager (approval)
Seat at the table
Employees fill their grid. Managers approve. Finance and payroll consume after lock. Project managers do not treat this as a task tracker.
The working rhythm
Pick the week, enter hours against work items, validate, submit, then wait for approval if enabled. Fix rejects on the same week. Do not invent a project code that does not exist.
Moments that bring you here
Friday fill. A week with leave in the middle. Validation blocking overtime. Before payroll lock. After a project code change.
ⓘ
Protected production flow
Entry, approval, and locking stay on the live timesheet engine. Intelligence hooks may advise; they do not replace the grid as source.
Interactive data flow
Toggle timesheet approval flags — full-week vs partial-week (partialWeekSubmissionEnabled), submit, on-behalf submit (enableTimeSheetSubmissionOnBehalfOf), manager approve, reopen, and TaskActivity promotion.
Flowcharts
Each diagram auto-plays steps when it scrolls into view. Use Play / Pause, or click a step to jump.
1 — Weekly entry loop
Navigate week, add entries, validate, submit when approval is on.
flowchart TD
W[Select week] --> E[Add / edit entries]
E --> V[Validation summary]
V --> S{Approval on?}
S -->|No| Done[Week saved]
S -->|Yes| Sub[Submit for approval]
- 1Select weekHeader arrows move Monday–Sunday weeks.
- 2Add / edit entriesBillable, non-billable, or leave hours.
- 3Validation summaryTotals, billable ratio, policy hints.
- 4Approval on?Org timesheet approval workflow.
- 5Week savedOpen weeks editable until lock.
- 6Submit for approvalManager queue — see Timesheet Approval guide.
2 — Billable entry path
Link hours to project/deliverable for utilization and invoices.
flowchart TD
Add[Add entry] --> Type{Type}
Type -->|Billable| Proj[Pick project / deliverable]
Type -->|Non-billable| NB[Internal code]
Type -->|Leave| Lv[Leave / holiday]
Proj --> Hrs[Enter hours]
NB --> Hrs
Lv --> Hrs
Hrs --> Save[Save cell]
- 1Add entryHeader Add entry or day cell click.
- 2TypeBillable, non-billable, or leave.
- 3Pick project / deliverableRequired for billable client work.
- 4Internal codeTraining, admin, etc.
- 5Leave / holidayMay sync from approved leave.
- 6Enter hoursH or H.MM per org config.
- 7Save cellRow refreshes totals.
3 — Submit on behalf
View another in-scope week and submit it without editing hours.
flowchart TD
Pick[Select employee + week] --> View[Read-only grid]
View --> Flag{On-behalf flag + team scope?}
Flag -->|No| Stop[View only]
Flag -->|Yes| Sub[Submit / resubmit on behalf]
Sub --> Pend[PENDING_APPROVAL]
Pend --> Mgr[Owner manager / delegate approves]
- 1Select employee + weekNeeds
switchEmployeesEnabled. - 2Read-only gridHours already saved by the owner. No Save / Clear / cell edit.
- 3On-behalf flag + team scope?
enableTimeSheetSubmissionOnBehalfOfand an accessible team. - 4View onlyWithout the flag, only managers/delegates can still submit via approval authority.
- 5Submit / resubmit on behalf
submittedByis you; week owner stays the selected employee. - 6PENDING_APPROVALSame week or day-batch status as a self-submit.
- 7Owner manager / delegate approvesThe on-behalf flag does not grant Approve/Reject.
Overview
HRMS → Time Sheet is the weekly hour grid. When timesheet approval is enabled, submit and manager review apply — see the Approval guide. With partialWeekSubmissionEnabled on, you can submit selected days as separate batches while leftover draft days stay editable; with the flag off (default), submit covers the whole week. Sync external leaves when integrations allow.
With timeSheet.switchEmployeesEnabled, the header employee picker can open another in-scope week (read-only). timeSheet.enableTimeSheetSubmissionOnBehalfOf then allows Submit / Resubmit on behalf for that already-saved week. It does not unlock add, edit, save, clear, or cell edits. The actor is recorded as submittedBy; the week still belongs to the selected employee and still needs the usual manager/delegate approval. Employee 360 is unchanged.
When Work-Time Governance catalog features are effective, a governance banner can appear for validation, late bands, or lock policy. With timesheet.reminders or timesheet.late-workflow on, the page loads a server deadline preview for the selected week (it does not guess Friday 18:00 locally). When late-workflow requires a reason, Submit shows a late-reason field. Submit still uses this grid — governance does not add a second timesheet.
How to use
1. Open the current week
Confirm week range in the header. Changing week or team refreshes the deadline preview.
2. Log hours daily
Prefer daily entry over Friday catch-up.
3. Link billable work
Select the correct project/deliverable.
4. Check deadline / late reason
If the week is past the configured cut-off and late-workflow is on, complete the late-reason field before Submit (Other needs detail).
5. Submit if required
Full week when partial is off; use day chips to submit batches when partial is on. See Timesheet Approval.
6. Submit on behalf (optional)
If your role has
switchEmployeesEnabled and enableTimeSheetSubmissionOnBehalfOf, pick the other employee, confirm the week is already saved, then use Submit on behalf. Do not expect Save or grid edits — those stay self-only. Approval still goes to the owner’s manager or delegate.