> 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/register-of-leaves-with-wages.md).

# Register of Leaves with Wages

Logic ERP has corrected the **SUNDAYS AND HOLIDAYS** column of the **Register of Leaves with Wages**.

***

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

* Navigate to **Payroll Reports** and open the **Register of Leaves with Wages**.

***

### **What's corrected**

* **SUNDAYS AND HOLIDAYS** now counts the employee's own week-offs and holidays. Earlier it counted only Sundays, and holidays were not counted.
* For an employee whose week-offs and holidays are set employee-wise (for example by their roster), their own days are counted. When none have been entered for the period, Sundays and the branch holidays are counted.
* For other employees, Sundays and the holidays of their branch are counted.
* Only days entered in attendance are counted.
* Some figures will change. Most will go up because holidays are now counted. An employee with employee-wise week-offs that are not on Sunday may show fewer days. This is intended.

***

### **Comp-off**

* A new **COMP OFF** column shows the comp-off days taken; a half day counts as half.
* Comp-off days show under **COMP OFF**, not **CASUAL LEAVES**. This is intended.
* **ABSENT DAYS** includes comp-off days, and **DAYS WORKED** the worked half of a half day of comp-off.


---

# 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/register-of-leaves-with-wages.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.
