Leave applications that have not been approved: everything still waiting for a decision, and everything turned down, with the rejection note where one was written.
When to use it
As the approver's worklist, and when someone asks why their leave was not granted.
Before you start
- Leave applications must exist. Staff and leave types must exist in their masters.
- You need report access for Human Resource.
Where to find it
Reports > HR & Payroll > Unapproved / Rejected Leave. It is also on the menu under ERP > Human Resource > Leave Report.
The fields on this screen
| Filter (on screen) | What it does |
|---|---|
| Employee | Limits the report to one employee. Leave it blank to include everyone. |
| Department | Limits the report to one department. Leave it blank to include every department. |
| Branch | Limits the report to one branch. Leave it blank to include every branch. |
| Employee (second chooser) | Limits the report to one employee. Leave it blank to include everyone. |
Reading the report
- Every row here has the Approved tick left off. Waiting and refused requests share one list, because there is no separate refused state. Use Rejection Reason to tell them apart: a row with a rejection note was turned down, and a row without one is still waiting.
- The rejection note is only a record. Leaving Approved unticked is what refuses the request.
- Days here count towards nothing. These days are not treated as leave on attendance and are not in payroll unless the application is approved.
- There is no date range. The list runs back over the whole history, so old requests nobody acted on stay visible. That is usually what you want.
Tips and common mistakes
- Two Employee choosers appear on this screen. Use the first one; it matches the staff record named on the application.
- If a row ought to be approved, fix it on the leave application itself, not here.