These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Seasonal Workers HRMS
- Features
- Time and leave
Time and leave
Review weekly hours and requested absence against the worker record.
OverviewMy leave requests×
Seasonal Workers HRMS · Time and leave
New
My leave requests
Leave requests
| Request number | Leave type | Start date | End date | Status | Approver | |
|---|---|---|---|---|---|---|
| LR-49487 | LT-7990 | 09 Oct | 13 Oct | Draft | ||
| LR-16894 | LT-9561 | 16 Oct | 21 Oct | Submitted | ||
| LR-41723 | LT-7233 | 26 Oct | 03 Nov | Approved | ||
| LR-51188 | LT-7255 | 07 Oct | 11 Oct | Taken | ||
| LR-74317 | LT-3285 | 23 Oct | 30 Oct | Draft |
6 of 6 records
LT-7990Leave requests · LR-49487
DraftStart date09 Oct
End date13 Oct
What you can do
Follow the timesheet, time entry and leave request
A weekly timesheet groups dated time entries for an employee. Each entry records hours and a work category, while a leave request carries absence dates and a named approver. A leave balance shows accrued, taken and pending amounts by employee and leave type. When overtime and time away fall in the same pay period, Admin can review both submissions before Payroll Admin prepares the run.
How the work is organized
- Starting record. Open the linked employee or transaction and verify its identifier and effective date.
- Decision owner. Give the record to the configured role that can review or update it.
- Next action. Keep the receiving record visible until its status and date reflect the completed work.
Employee enters time entries against a weekly timesheet, then submits the sheet for review. Each entry carries a date, hours and a work category such as Overtime. A leave request carries the absence dates, employee, leave type and named approver. A leave balance shows accrued, taken and pending amounts with an as-of date.
What to agree during setup
Set the weekly submission cutoff, who approves hours and leave, and how rejected entries return for correction. Agree how the payroll team receives approved overtime and leave information. Start with one representative employee and one real operating cycle. Name the person who checks the result and the person who is allowed to change it. Decide when a handoff is complete and what information the receiving team needs.
These agreements make a status meaningful in daily work. If the team cannot tell who receives the next action, assign the owner before adding more records. Review access with a normal user for each role, especially where a worker’s personal or pay information appears. Keep a correction path for an incorrect date or reference so the next cycle does not inherit the mistake.
Check the handoff on an actual case
The employee enters dated hours, submits the weekly sheet and files leave dates. Admin reviews the week and the leave balance before approval. Payroll Admin uses the approved records when preparing the pay run, while rejected items stay visible for correction. Ask the receiving role to find the linked record in its normal worklist. Compare the employee, owner, date and status with the starting record. If one link is wrong, correct it and repeat the check before the next decision.
For a worker with overtime and a leave request in the same week, Admin checks the timesheet employee, week dates and submitted hours, then checks the leave balance and request dates. Rejected submissions return for correction. Payroll Admin reads the reviewed time and leave records for the run period and checks that they belong to the same employee.
What your team sees
- My leave requests — Review the records and status that require action in this area.
- Leave approval inbox — Open related records that need another owner or decision.
Follow the work through
See requisition to hire, worker return and time to pay for connected decisions.
What it keeps track of
Data model- Timesheets
- Weekly timesheet header per employee.
- Time entries
- Hours against a day, project or cost center.
- Leave requests
- Employee-submitted leave requests requiring manager approval.
- Leave balances
- Current leave balance per employee per leave type, maintained by accrual.
- Leave types
- Leave categories with country- and class-scoped accrual rules.
- Employees
- Central person record for every worker; all suite transactions tie back to Employees.
Who uses it
PermissionsSet up Seasonal Workers HRMS your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.