> 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-learning-hub-tutorials-and-best-practices/payroll/payroll-setups/setup-compensatory-off-rules/how-comp-off-works.md).

# How Comp-off Works

A comp-off goes through five steps: the employee **works** on a holiday or week-off, **claims** it on the Logic Workforce app, it is **approved**, it is **taken** later as a day off, and whatever is not taken by its lapse date **lapses**. The rules for each grade are set in [Setup Compensatory Off Rules](https://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/payroll/payroll-setups/setup-compensatory-off-rules.md).

### **Step 1: Claim on the app**

* On the **Logic Workforce** app the employee taps **Comp-off** on the **Requests** tab (or under **More**).
* The page shows the grade's rules, the comp-off they have to take with each one's lapse date, and the holidays and week-offs they worked that can still be claimed.
* They pick the **Day worked** - each day shows the holiday and how much it earns, for example *Sun 4 Oct (WEEK-OFF) - 1 day* - type a **Reason** and tap **Submit**. The employee does not choose full or half day: it is worked out from the time worked that day.
* Under **Other holidays / week-offs worked** the days that cannot be claimed are listed with the reason - *already claimed*, or the hours worked when they are too few.

A claim is refused when the grade has no comp-off, the day is a working day, the day is in the future, it is past **DAYS TO CLAIM**, it is before the grade's **FROM DATE**, no work is recorded that day, the work is too short, or the day was already claimed.

### **Step 2: Approval**

* The claim goes through **Setup Attendance Approval Rules** like any app request. A rule for the request type **COMP-OFF** applies only to claims; without one, a rule for **(ANY)** request is used, and otherwise the company default (the reporting manager, then HR).
* HR sees claims waiting for HR in **Attendance App HR Review** as **COMP-OFF**, with the days and the hours worked.
* At the last approval the claim is checked again against the grade's rules and the work recorded at that moment. If the work now earns a different amount, the comp-off is given for the new amount and the approver is told. It is refused if the grade's comp-off has been switched off, the day is no longer a holiday or week-off, no work is recorded now, the work recorded now is too short, or the comp-off would already have lapsed.
* When it is approved, the employee gets the comp-off: 1 day or half a day, lapsing **LAPSES AFTER (DAYS)** after the day worked (**NEVER** = it does not lapse). The holiday or week-off itself stays as it is in attendance.

### **Step 3: Take it as a day off**

* **On the app** - the employee applies for leave and picks **COMP OFF**, for a full day or, when the grade has half days, a half day. The days available are the comp-offs not yet taken or lapsed, less their other comp-off leave waiting for approval. This leave follows the approval rules for **LEAVE**.
* **In the Attendance Register** - choose **Absent** and **Comp Off** or **Half Day (Comp Off)**. In **Attendance Register Month Wise** pick **COMP OFF** or **HALF DAY - COMP OFF** under **Others**. Once the month is loaded, a full comp-off day shows as **A(CO)** and a half day as **P(HCO)**.
* A comp-off can be taken only after the day it was earned, and on or before its lapse date. When several are open, the one lapsing first is used first.
* Not enough comp-off for the day refuses the save, with the days that can be taken then.
* On a compulsory attendance date comp-off is not given: the register saves the day as leave without pay (a half day as **HD**), and the app refuses it.
* Deleting a comp-off day in the register, or changing it to another status, gives the comp-off back - unless its lapse date has already passed, then that part lapses.

### **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 the late morning: *Take your comp-off for ... by ... - after that it lapses.* It is sent only in branches where app reminders are switched on.
* Whatever is left after the lapse date lapses overnight, and the employee gets a notice on the app.
* A comp-off can be used up to and including its lapse date. Comp-offs carry over into the next payroll year until they lapse. One that never lapses gets no reminder.

### **Cancelling a claim**

* A claim still waiting for approval is withdrawn at once.
* An approved claim can be cancelled through the same approvers - but not once any of it has been taken. After the cancellation the day can be claimed again, within its **DAYS TO CLAIM**.

### **Payroll and reports**

* **Payroll Generation** - comp-off days are paid leave and count as days worked; a half day of comp-off counts as a full day worked, as the employee worked the other half. They show in their own **COMP OFF** column (a half day counts as half) - select the column in the report's configuration. In payroll formulas **TOTAL LEAVES** 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, work on a holiday or week-off from the **FROM DATE** on is paid as the holiday only - no overtime, no extra day - whether or not the employee claims it.
* **Pay slip** - the fields **COMP\_OFF** and **HALF\_DAY\_COMP\_OFF** can be added to a pay slip design.
* **Payroll Summary Report** and **Register of Leaves with Wages** have a **COMP OFF** column; **CASUAL LEAVE** no longer includes comp-off.
* **Employee Leave Ledger** - a **COMP OFF** row with **EARNED** and **LAPSED** columns. Its opening is not limited to the payroll year.
* **Employee Comp-off Register** - every comp-off earned, with the days used, lapsed and left.

> **Example - Asha's Sunday**
>
> Asha's grade earns 1 day for 8 hours and half a day for 4 hours, claimed within 30 days, lapsing after 90 days. She works on Sunday 4 October 2026, a week-off, from 9:00 AM to 6:00 PM. On 6 October she opens **Comp-off** on the app, picks *Sun 4 Oct (WEEK-OFF) - 1 day* and submits. Her manager and HR approve: she now has 1 day of comp-off, lapsing after 2 January 2027. On 15 October she takes a half day of comp-off - 0.5 day is left. On 26 December the app reminds her once to take it. She does not, so overnight after 2 January the last half day lapses and the app tells her.


---

# 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-learning-hub-tutorials-and-best-practices/payroll/payroll-setups/setup-compensatory-off-rules/how-comp-off-works.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.
