> For the complete documentation index, see [llms.txt](https://kb.logicerp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.logicerp.com/logic-erp-version-release-notes/october-2026/payroll/payroll-reports/employee-request-and-approval-register.md).

# Employee Request & Approval Register

Logic ERP has introduced a new **Employee Request & Approval Register**. It lists the requests employees make from the attendance app — leave, missed punch and profile change — with every approval level, how long the approval took and, for leave, how many days reached attendance.

***

### **Step 1: Open the Report**

* Navigate to **Payroll Reports** and open the **Employee Request & Approval Register**.
* Enter **Date From** and **Date To**. The report lists the requests **applied on** these dates.
* Select branches or employees if needed.
* In the report settings, tick the request types and statuses to show. When nothing is ticked, all of them are shown.

***

### **Step 2: Read the report**

* **REQUEST TYPE** shows Leave, Missed Punch or Profile Change. A cancellation shows the request it cancels, for example **LEAVE - CANCEL OF #12**.
* **DETAIL** shows the leave type (and HALF DAY), the missed punch with its time, for example **IN 09:30**, or each changed profile field with its old and new value.
* For leave and missed punches, **DATE FROM** and **DATE TO** show the first and last day asked for. **DAYS** (leave only) counts the working days asked for; a half day counts as half a day.
* **APPROVAL TRAIL** lists every level with the approver, the action and its time, for example **L1 MANAGER RAVI: APPROVED 05/10 10:12 | L2 HR: WAITING**. A level never reached because an earlier approver rejected the request shows **NOT REACHED**. Levels left open when the employee withdrew the request, or when the leave rules refused it, show **SKIPPED**. A level that a higher approver acted ahead of shows **PASSED OVER**.
* **TURNAROUND HOURS** shows the hours from applying to the final decision; for a cancelled request, to the cancellation. It is blank while the request is pending.
* For leave, **DAYS APPLIED** shows the days written to attendance, and **DAYS NOT APPLIED** shows approved days that could not be written, for example because the day already had attendance. HR should look at these days.
* A total row at the end shows the number of requests and the days (the days of a cancellation are counted too).

***

### **Comp-off claims**

* Comp-off claims are listed with **REQUEST TYPE** **COMP-OFF**. **DETAIL** shows the part claimed and the work, for example **1 DAY, WORKED 9:00 AM - 6:00 PM (9 h)**, and **DATE FROM** / **DATE TO** the day worked.
* Tick **Comp Off** under **Request Types** in the report settings; tick only it to show just comp-off claims.

***

For more detailed information, [Click Here](/logic-erp-learning-hub-tutorials-and-best-practices/payroll/payroll-reports/employee-request-and-approval-register.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://kb.logicerp.com/logic-erp-version-release-notes/october-2026/payroll/payroll-reports/employee-request-and-approval-register.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
