> 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.md).

# Setup Compensatory Off Rules

**Available on:** Desktop · Web

Navigate to **Payroll Setups** and click on "Setup Compensatory Off Rules".

A **compensatory off** (comp-off) is a day off earned by working on a holiday or week-off. The employee claims it on the **Logic Workforce** app, it goes to the approvers set for comp-off claims in **Setup Attendance Approval Rules**, and once approved it can be taken later like a leave. **Setup Compensatory Off Rules** decides, grade by grade, who earns a comp-off, how long they have to claim it, when it lapses, and how much work earns a full day or a half day. How the whole cycle works is explained in [How Comp-off Works](https://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/payroll/payroll-setups/setup-compensatory-off-rules/how-comp-off-works.md).

## The grid

Every normal grade is listed, one row each. A grade with no rules yet shows **ALLOWED = No**, and its other columns are blank. When a grade that was never set up is set to **Yes**, it starts with 30 days to claim, lapsing after 90 days, 480 minutes for a full day, 240 minutes for a half day, and today as the **FROM DATE**. A grade switched off earlier gets its last values back. Change any of them.

| Column                  | What it means                                                                                                                                                                                                                 |
| ----------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **GRADE**               | The grade. A **\*** after the name means the row has changes not saved yet.                                                                                                                                                   |
| **ALLOWED**             | **Yes** - employees of this grade earn a comp-off for work on a holiday or week-off. **No** - the app tells them *Comp-off is not set up for you. Ask HR.* The other columns can be changed only when this is **Yes**.        |
| **DAYS TO CLAIM**       | How many days after the day worked the employee can still claim it, from 1 to 365. Claiming on the last of these days is allowed.                                                                                             |
| **LAPSES AFTER (DAYS)** | How many days after the day worked an unused comp-off lapses, from 0 to 730 - the day it reaches is the last day it can be taken. It cannot be fewer than **DAYS TO CLAIM**. **0** means it never lapses and shows **NEVER**. |
| **FULL DAY (MINUTES)**  | The work on the day that earns a full day off, from 60 to 1440 minutes (1 to 24 hours).                                                                                                                                       |
| **HALF DAY (MINUTES)**  | The work that earns a half day off - at least 30 minutes and less than a full day. **0** means no half days and shows **NONE**: less work than a full day then earns nothing, and comp-off can be taken only as full days.    |
| **FROM DATE**           | The date comp-off starts from for this grade. Work on a holiday or week-off before this date is paid as before and cannot be claimed. Required when **ALLOWED** is **Yes**.                                                   |

The line under the grid counts the grades, how many have comp-off, and how many are changed but not saved. It also reminds you that 0 lapse days means never and 0 half-day minutes means no half days, and that holiday work before the from date is paid, not comp-off. After a save it shows how many grades were saved.

## Saving

* Press **Save** and answer **Yes**. Every changed grade is saved; **No** saves nothing.
* Each change is recorded in the Change Log Viewer (User Access): choose the document **Comp Off Rule**. Each entry shows the old and new values, who changed them, and the screen Setup Compensatory Off Rules.
* Closing with changes not saved asks first - **No** keeps the screen open.

## What the rules change

* **Earning** - work on a holiday or week-off of **FULL DAY (MINUTES)** or more earns 1 day; at least **HALF DAY (MINUTES)** earns half a day; less earns nothing. The work is the time between the day's time in and time out or, when the day has no times (or the same time in and out), the hours worked entered for the day.
* **Payroll** - for a grade with **ALLOWED = Yes**, work on a holiday or week-off from the **FROM DATE** on is no longer paid as extra work or overtime: the day is paid as the holiday it is, and the employee can claim a comp-off for it instead. This applies whether or not the comp-off is claimed, and uses the rules as they are when payroll is generated. Grades with **ALLOWED = No**, and work before the **FROM DATE**, are paid as before.
* **Changing a rule later** - comp-offs already approved keep the days earned and the lapse date they were given. But a grade switched to **No** can no longer take its comp-off on the app, and with **HALF DAY** 0 only full days can be taken. Claims not yet finally approved are checked again under the new rule.

> **Example - setting up two grades**
>
> Staff should earn a comp-off for holiday work from 1 November: 8 hours for a full day, 4 hours for a half day, claimed within 30 days and taken within 90 days. Managers should get a full day only, for 7 hours of work, claimed within 15 days, and it never lapses. HR sets **Staff**: ALLOWED Yes, DAYS TO CLAIM 30, LAPSES AFTER 90, FULL DAY 480, HALF DAY 240, FROM DATE 01/11/2026. Then **Managers**: ALLOWED Yes, DAYS TO CLAIM 15, LAPSES AFTER 0, FULL DAY 420, HALF DAY 0, FROM DATE 01/11/2026. HR presses **Save** and answers **Yes**.

## Messages you may see

| Message                                                                           | Why                                                     | What to do                           |
| --------------------------------------------------------------------------------- | ------------------------------------------------------- | ------------------------------------ |
| Save the comp-off rules of ... grade(s)?                                          | Asked before saving                                     | **Yes** to save                      |
| Nothing to save.                                                                  | **Save** with no grade changed                          | -                                    |
| ...: a comp-off must be claimable for 1 to 365 days.                              | **DAYS TO CLAIM** is out of range for that grade        | Correct it                           |
| ...: a comp-off must lapse after 1 to 730 days (0 = never).                       | **LAPSES AFTER (DAYS)** is out of range                 | Correct it                           |
| ...: a comp-off cannot lapse before the days to claim it are over.                | **LAPSES AFTER (DAYS)** is less than **DAYS TO CLAIM**  | Raise it, or set it to 0             |
| ...: the work for a full day must be 1 to 24 hours.                               | **FULL DAY (MINUTES)** is under 60 or over 1440         | Correct it                           |
| ...: the work for a half day must be less than for a full day (0 = no half days). | **HALF DAY (MINUTES)** is not less than **FULL DAY**    | Lower it, or set it to 0             |
| ...: the work for a half day must be at least 30 minutes.                         | **HALF DAY (MINUTES)** is between 1 and 29              | Raise it, or set it to 0             |
| ...: choose the date comp-off starts from.                                        | After **Yes**: an allowed grade has no **FROM DATE**    | Enter the date and save again        |
| ... grade(s) have changes not saved yet. Close without saving?                    | Closing with changes not saved                          | **No** goes back so you can **Save** |
| Modification rights are not available...                                          | **Save** pressed when your user may only view this menu | Ask for modify rights in User Access |

## On the web

The same screen is on the web, with **Save** and **Close**. **FROM DATE** is a date box: type the date or pick it from the calendar. On a phone the grid scrolls sideways.


---

# 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.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.
