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.
Feature · Leave and time
Example screen with sample data
Leave and time
Connect employee requests, manager decisions, balance movements and weekly hours.
OverviewMy leave requests×
HRMS · Leave and time
New
My leave requests
Leave requests
| Request number | Leave type | Start date | End date | Days | Status | |
|---|---|---|---|---|---|---|
| LR-43771 | LT-2954 | 07 Oct | 13 Oct | DYS-149 | Draft | |
| LR-90924 | LT-1629 | 07 Oct | 10 Oct | DYS-131 | Submitted | |
| LR-81384 | LT-6049 | 11 Oct | 15 Oct | DYS-875 | Approved | |
| LR-96424 | LT-5793 | 14 Oct | 18 Oct | DYS-756 | Taken | |
| LR-63481 | LT-2992 | 26 Oct | 04 Nov | DYS-761 | Draft |
6 of 6 records
DYS-149Leave requests · LR-43771
DraftLeave typeLT-2954
Start date07 Oct
End date13 Oct
What you can do
Review the dates and the balance together
A leave request identifies the employee, leave type and requested interval. Its balance holds accrued, taken, pending and carryover amounts for that employee and leave type. The assigned manager needs both the dates and balance context when deciding the request.
Time work uses a separate weekly timesheet with linked daily entries. Hours can carry a category, project and cost center. Payroll Admin reads time and leave during pay preparation. Employee self-service keeps the request and hours connected to the correct person, with approval handled through the assigned approver’s action.
How the work is organized
- Request ownership. Employee prepares a Draft request and submits it. When the approver is blank, the defaulting workflow resolves the employee’s manager. It preserves an existing approver and leaves the record unchanged when the employee or manager cannot be resolved.
- Balance movements. Submission reserves pending days. Approval releases pending days, adds taken days and records the approval date. Rejection or cancellation releases the pending amount. The workflow creates a needed employee and leave-type balance when the pair has none.
- Weekly hours. The timesheet identifies the week, total hours, approver and status. Daily entries explain the hours and their categories. Draft, Submitted, Approved, Rejected and Posted distinguish preparation, decisions and later processing.
What to agree during setup
Review the leave type’s country, employee class, accrual method, rate and documentation requirement. Requested days count the start and end dates and include weekends. Reconcile a request spanning a weekend before adopting that calendar-day basis for your leave policy. Approval moves the recorded amount into taken days; use that interpretation consistently when reconciling balances.
Map each login to its employee record and configure the assigned manager’s approval route. Test both with ordinary accounts. Agree the accrual basis and how timesheet approval dates are recorded. Decide how Payroll Admin reviews approved time before any separately configured pay adjustment uses it.
Check the handoff on an actual case
Create a leave request for an employee with a manager, leaving its approver blank. Inspect the resolved approver, submit the request and compare pending days before a decision. Approve through the assigned action, then compare pending days, taken days and the approval date with their starting values. Repeat with rejection and cancellation so the team can explain each release. A Friday-through-Monday request includes the weekend in its requested days.
Try an employee and leave-type pair without a balance. Confirm the movement reaches the newly created balance. Prepare a weekly timesheet with daily entries, reconcile the total hours and submit it to the intended approver. Ask Payroll Admin to distinguish the approved week from one still waiting for a decision. Keep unresolved entries with their employee and approver until corrected.
What your team sees
- My leave requests — Follow your own requests, dates and assigned approver.
- Leave request schedule — Review permitted submitted and approved leave intervals; Employee access stays within personal requests.
- Submitted timesheets — Follow permitted submissions by employee, week and approver without granting decision authority.
Follow the work through
Use leave and time to payroll pre-check to rehearse balance movements and the payroll handoff. Agree account scope through roles.
What it keeps track of
Data model- Leave requests
- Employee-submitted leave requests requiring manager approval.
- Leave types
- Leave categories with country- and class-scoped accrual rules.
- Leave balances
- Current leave balance per employee per leave type, maintained by accrual.
- Timesheets
- Weekly timesheet header per employee.
- Time entries
- Hours against a day, project or cost center.
- Employees
- The central person record that every transaction in the suite ties back to.
Who uses it
Permissions- Employee
- , Payroll Admin, CHRO / VP People.
- Employee
- Submits personal requests and hours; an assigned manager uses the configured approval action.
- Payroll Admin
- Reads preparation inputs, while CHRO / VP People reads the overall position.
Set up HRMS your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.