> 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-entry/payroll-generation.md).

# Payroll Generation

Logic ERP has improved the **Check for Employees with Leaves Before / After Holiday** window that opens from **Payroll Generation**. It lists holidays that fall between two leave days so they can be marked as leave without pay. It no longer proposes holidays the employee worked, and it now checks the last day of the month.

***

### **Step 1: Open the window**

* Navigate to **Payroll Entry** and open **Payroll Generation**.
* In the payroll generation configuration, tick **Check and Prompt for if Leaves availed before / after Holiday**.
* Click **Re-Calculate**. The window opens and lists each employee and holiday date that is found.

***

### **Step 2: Mark the holidays**

* Tick the holidays to be marked as leave without pay, or use **Select / Unselect All**.
* Click **Update**. The ticked holidays are marked as leave without pay in attendance. Days in a month whose working days are not set up are skipped.
* Holidays follow each employee's own week-offs and holidays, including those set by their roster.

***

### **What's corrected**

* A holiday the employee **worked** is no longer listed, so it can no longer be marked as leave without pay by mistake.
* A holiday on the **last day of the month** is now checked.
* A holiday from the **previous month** (the day before the payroll period starts) is no longer listed.
* When **Checking Criteria** is **Paid Leaves Also**, the window no longer lists holidays wrongly when the day before or after the holiday has no attendance.
* If a day cannot be updated, a message now lists the employee and date. Earlier it failed without a message. (Days in a month whose working days are not set up are still skipped without a message.)
* The window now works for companies with a large number of employees in a month.

***

### **Comp-off**

* A new **COMP OFF** column shows the comp-off days taken in the month; a half day counts as half. Select it in the payroll generation configuration.
* Comp-off days are paid leave and count as days worked. In payroll formulas, **TOTAL LEAVES** now includes comp-off and **COMP OFF** gives the comp-off days; in both a half day counts as 1, like a half day of casual leave.
* For a grade with comp-off switched on in **Setup Compensatory Off Rules**, work on a holiday or week-off from the grade's **FROM DATE** is paid as the holiday only - no overtime and no extra day - whether or not a comp-off is claimed for it. The employee can claim a comp-off instead. Other grades, and work before the from date, are paid as before. The rules are applied as they are when payroll is generated.


---

# 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-entry/payroll-generation.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.
