Skip to content
QTO ERP Docs
Try QTO ERP for FREE
EN QTO ERP

Leave Management

Leave Management is part of Attendance. It handles employee leave requests, policy validation, approval workflows, leave balances, day-level leave records, and unpaid absence records.

Page Purpose
My Leave Requests Employee view for submitted leave requests.
Apply for Leave Form for creating a leave request.
Leave Request Review queue for users with leave visibility/review access.
Leave Balance Balance view by employee, policy, and period.
Leave Records Day-level records that affect attendance summaries.
Team Leaves Team-oriented leave view where configured.
My Leave Policies Policies applicable to the current user.
  1. Open My Leave Requests.
  2. Select Apply for Leave.
  3. Select the applicable leave policy.
  4. Enter the start date and end date.
  5. Enter the reason.
  6. Add supporting documents when the policy requires them.
  7. Submit the request.

The system validates the request before it is accepted.

flowchart LR
A[Apply for Leave] --> B[Validation]
B --> C[Pending Review]
C --> D[Approved]
C --> E[Rejected]
D --> F[Leave Records]

Policies can use direct approval or approval-chain steps. In an approval chain, the current required step controls who can act. Optional steps do not block later required steps while those required steps are pending.

Review actions include Approve and Reject. If one required step rejects the request, the whole request is rejected.

Status Meaning
Pending Review Waiting for review.
Approved Approved and eligible dates can become paid leave records.
Rejected Not approved.
Cancelled Cancelled request.

Leave balances track:

  • allocated days
  • used days
  • carried-forward days
  • available days
  • period year and month
  • period disposition
  • encashment information when the policy is cashable

Balances are reduced by actual leave records. Pending and approved requests can reserve available balance during validation so users cannot over-request the same balance.

Leave records are day-level entries. A record linked to a leave policy is paid. A record without a policy is unpaid and counts as an absence.

Leave records cannot be created for future dates through the direct record flow. Future planned leave should use Apply for Leave.

The selected leave policy can control:

  • who the policy applies to
  • allocation period
  • allocated days
  • monthly accrual
  • probation requirement
  • proration
  • monthly usage cap
  • fiscal year start
  • carry forward
  • cashability
  • required documentation
  • backdated leave eligibility
  • approval mode and approval chain

Verified background behavior includes:

  • monthly accrual updates for monthly-accrual policies
  • year-end carry-forward for eligible yearly policies
  • asynchronous leave request notifications to manager/HR recipients
  • nightly workday absence processing for employees who did not check in