Agiled Docs
HRM

Leaves and Holidays

Manage leave requests, leave types, and holidays.

Leave and holiday settings help teams manage time away from work.

Keep these records current before attendance, payroll, or staffing reviews. Leave and holiday mistakes usually show up later as incorrect absences, payroll questions, or understaffed workdays.

Leave Requests

Employees can request leave where self-service is enabled. Managers review the request, check availability and policy, then approve or reject it.

Admins can also create or edit a request from HRM > Leaves. The leave form includes employee, leave type, start date, end date, reason, and comments.

Before approving, check overlapping requests, department coverage, attendance records, and whether the leave should be paid or unpaid. If the decision depends on a manager, add a clear comment so payroll and the employee understand the outcome later.

Leave Types

Leave types define categories such as vacation, sick leave, unpaid leave, or other company-specific policies.

Configure leave types in HRM settings before employees start submitting requests. Keep names plain so employees can choose the right type without guessing.

Review balances, paid/unpaid behavior, and approval expectations before opening self-service to employees. If a policy changes mid-year, document how existing requests should be handled.

Use names employees recognize, such as “Paid vacation” or “Sick leave.” Avoid internal accounting labels in employee-facing leave types unless the whole team already uses that language.

Holidays

Holidays define dates that are not treated as normal workdays. Keep holidays updated before payroll or attendance reviews.

Holiday dates also affect attendance summary interpretation. In the attendance summary grid, holidays are marked separately from normal workdays.

Add holidays before employees submit leave for that period. Missing holidays can make employees request time off that should already be treated as non-working time.

For regional teams, confirm whether holidays apply to everyone or only to a location, department, or employment group. If your workspace uses one shared holiday calendar, document exceptions outside Agiled so managers do not approve leave based on the wrong assumption.

Approval Decisions

Before approving or rejecting leave, check:

  1. The employee and leave type.
  2. The requested dates and whether they include holidays.
  3. Overlapping team leave.
  4. Attendance corrections for the same period.
  5. Paid or unpaid handling.
  6. Manager comments or policy notes.

Use rejection comments to explain what the employee should change. For example, ask for a different date range, a different leave type, or manager approval instead of leaving the reason unclear.

Operating Checklist

  • Configure leave types.
  • Add public holidays and company holidays.
  • Ask employees to submit leave from self-service.
  • Review pending requests from HRM > Leaves.
  • Approve, reject, or cancel requests with a clear reason when needed.
  • Review attendance and payroll after leave approvals.

Review Before Payroll

Before payroll or month-end HR reporting, check pending leave requests, cancelled requests, holidays, attendance corrections, and unpaid leave. Resolve source records before exporting reports.

If balances or attendance look wrong, review the employee profile, leave type, holiday calendar, attendance corrections, and approved request dates before editing payroll results. Payroll should reflect HRM source records, not patch over them.

Yearly Maintenance

At the start of a year or policy cycle, review holiday dates, leave types, approval owners, unpaid leave behavior, and any regional exceptions. Then test one sample request so managers can see the expected workflow before employees begin submitting real requests.

On this page