> 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-comp-off-register.md).

# Employee Comp-off Register

Logic ERP has introduced a new **Employee Comp-off Register**. It lists every comp-off employees earned for work on a holiday or week-off - how much was earned, used and lapsed, what is left and when it lapses.

***

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

* Navigate to **Payroll Reports** and open the **Employee Comp-off Register**.
* Enter **Date From** and **Date To**. The report lists the comp-offs for days **worked** in these dates.
* Select branches, departments or employees if needed.

***

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

* Each row is one comp-off: **DAY WORKED**, **DAYS EARNED**, **DAYS USED**, **DAYS LAPSED**, **BALANCE** and **EXPIRY DATE** (**NEVER** when it does not lapse).
* **STATUS** shows **OPEN**, **PART USED**, **PART LAPSED**, **USED**, **LAPSED** or **USED + LAPSED**.
* Claims that were cancelled are left out. The figures are as on the day the report is run. A comp-off past its expiry date shows what was left as lapsed.
* In the report settings, **Show Only** limits the report to comp-offs **With Balance**, **Used** or **Lapsed**, and **List Dates Taken** lists every date each one was taken.
* A total row shows the number of comp-offs and the days earned, used, lapsed and left.

***

For more detailed information, [Click Here](/logic-erp-learning-hub-tutorials-and-best-practices/payroll/payroll-reports/employee-comp-off-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-comp-off-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.
