> 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-setups/setup-compensatory-off-rules.md).

# Setup Compensatory Off Rules

Logic ERP now supports **Compensatory Off** (comp-off) - a day off earned by working on a holiday or week-off. The employee claims it on the **Logic Workforce** app, it is approved like their other requests, and it is taken later as a day off. **Setup Compensatory Off Rules** is where HR decides, grade by grade, who earns a comp-off and on what terms.

***

### **Step 1: Set the rules for each grade**

* Navigate to **Payroll Setups** and open **Setup Compensatory Off Rules**. Every grade is listed.
* Set **ALLOWED** to **Yes** for the grades that earn a comp-off. A grade left at **No** cannot claim one.
* **DAYS TO CLAIM** - how many days after the day worked the comp-off can still be claimed.
* **LAPSES AFTER (DAYS)** - how many days after the day worked an unused comp-off lapses; **0** means never.
* **FULL DAY (MINUTES)** and **HALF DAY (MINUTES)** - the work that earns a full day and a half day off; a half day of **0** means no half days.
* **FROM DATE** - the date comp-off starts from for the grade. Holiday work before it is paid as before.
* Click **Save**. Each change is recorded in the change log.
* The screen is also available on the web.

***

### **Step 2: Claiming a comp-off on the app**

* In the **Logic Workforce** app, the employee taps **Comp-off** - on the **Requests** page or under **More**.
* The app lists the holidays and week-offs they worked that can still be claimed, with how much each one earns (a full day or a half day, worked out from the time worked). They pick the day, type a reason and submit.
* The app also shows the grade's rules and the comp-off they still have to take, with each one's lapse date.
* The claim goes through the approval steps set in **Setup Attendance Approval Rules** (request type **COMP-OFF**). It is checked again at the last approval.
* A claim is refused for a working day, a future day, a day past the claim limit or before the from date, a day with no work or too little work, or a day already claimed.

***

### **Step 3: Taking a comp-off**

* On the app the employee applies for leave and picks **COMP OFF** - a full day or, where the grade allows, a half day.
* In the **Attendance Register**, choose **Absent** and **Comp Off** or **Half Day (Comp Off)**. In **Attendance Register Month Wise** it is under **Absent** > **Others**, as **COMP OFF** and **HALF DAY - COMP OFF**.
* A comp-off can be taken only after the day it was earned and up to its lapse date. The one lapsing first is used first. The Attendance Register refuses the save when there is not enough comp-off for the day.
* Deleting or changing a comp-off day gives the comp-off back; if its lapse date has already passed, that part lapses instead.

***

### **Step 4: Reminders and lapsing**

* When a comp-off is 7 days or less from its lapse date, the employee gets one reminder on the app (in branches where app reminders are switched on).
* Whatever is not taken by the lapse date lapses overnight, and the employee is told on the app.
* Comp-offs carry over into the next payroll year until they lapse.

> **Example - Asha's Sunday**
>
> Asha works on her week-off, Sunday 4 October, from 9:00 AM to 6:00 PM. Her grade earns a full day for 8 hours and a half day for 4 hours, lapsing after 90 days. She claims it on the app; once her manager and HR approve, she has 1 day of comp-off to take by 2 January 2027. She takes a half day on 15 October. On 26 December the app reminds her to take the other half.

***

### **Also in this release**

* **Payroll Generation** shows comp-off in its own **COMP OFF** column, and work on a holiday or week-off by a comp-off grade is no longer paid as overtime - see Payroll Generation.
* **Employee Comp-off Register** is a new report of every comp-off earned, used and lapsed.
* **Employee Leave Ledger**, **Payroll Summary Report**, **Register of Leaves with Wages**, **Attendance Status Report**, **Attendance Summary Report** and **Employee Request & Approval Register** include comp-off - see each report.
* **Employee + Allow Ded + Month Wise Payroll Report** counts comp-off days with casual leave (a half day with half day + casual), and **Employee + Salary Range Wise Report** counts them in the days like casual leave.
* **Setup Attendance Approval Rules** can set approval steps for comp-off claims, and **Attendance App HR Review** shows the claims waiting for HR.

***

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