> 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-short-leave-rules.md).

# Setup Short Leave Rules

Logic ERP now supports **Short Leave** - a few hours off on a working day, to come in late, leave early or step out for some work. The employee asks for it on the **Logic Workforce** app, the manager approves it like any other request, and the day stays a working day. **Setup Short Leave Rules** is where HR decides, grade by grade, who may take short leaves and how many are free.

***

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

* Navigate to **Payroll Setups** and open **Setup Short Leave Rules**. Every grade is listed.
* Set **ALLOWED** to **Yes** for the grades that may take short leaves. A grade left at **No** cannot ask for one.
* **FREE A MONTH** - how many short leaves are free in each pay period (the calendar month where no pay period is set up).
* **LONGEST (MINUTES)** - the longest short leave allowed, from 15 to 480 minutes.
* **WHEN** - when a short leave may be taken:
  * **Start or end of the shift** - to come in late or to leave early.
  * **Anywhere in the shift** - also in the middle of the shift.
  * **Start or end of the shift, or one mid-day slot a month** - the middle of the shift only once in each pay period.
* **EXTRA ONE COSTS** - what happens to short leaves over the free ones: **Each extra one = a half day**, or **Every two extra = a half day**.
* **HALF DAY CHARGED TO** - the leave the half day is taken from, for example **CL, THEN SL, ELSE HD**. When none of these leaves can be taken that day, the day becomes an unpaid half day (HD).
* Click **Save**. Each change is recorded in the change log.
* The screen is also available on the web.

***

### **Step 2: Asking for a short leave on the app**

* In the **Logic Workforce** app, the employee taps **Short leave** - on the **Requests** page, under **More**, or on a day's details (which fills in that day).
* The employee picks the **Day** and **When** - **Start of shift (come in late)**, **End of shift (leave early)** or **Another time** (only where the rules allow the middle of the shift).
* The **From** and **To** times are filled in from the shift (one hour at the start or the end) and can be changed. Times are shown with AM / PM, and the time off is shown under them.
* The app shows the pay period, how many short leaves are used and how many are free, the longest allowed and the day's shift. When this one is over the free ones, it says it will count as a half day of leave (or, with **Every two extra = a half day**, that every two extra ones count as a half day).
* The request goes through the same approval steps as other requests. Short leaves that are waiting for approval also count towards the free ones.
* A short leave cannot be asked for on a holiday or week-off, on a day of leave (or one already in a leave request), on a day marked absent, on a day whose payroll is processed, or twice on the same day. It must also fit inside the shift and within the longest time allowed.

***

### **Step 3: How attendance treats a short leave**

* A short leave at the **start** of the shift covers coming in late: those minutes are not counted as late.
* A short leave at the **end** of the shift covers leaving early.
* The covered time is added to the hours worked, so the day can still count as a full day - but never as overtime.
* A short leave in the **middle** of the shift is not added to the hours worked; the day is worked out from the punches as usual.
* When a short leave is approved or cancelled after the day's punches were already taken in from the app, the day is worked out again. A day entered by hand, or one whose payroll is processed, is left for HR.

> **Example - coming in late**
>
> Ravi's shift is 9:00 AM to 6:00 PM. He has an approved short leave from 9:00 AM to 11:00 AM, comes in at 11:00 AM and leaves at 6:00 PM. He is not marked late, and his day is counted as a full day.

***

### **Also in this release**

* **Employee Request & Approval Register** shows short leaves (type **SHORT LEAVE**, with the times, and **COUNTED AS HALF DAY** once converted). Tick **Short Leave** in the report configuration to show only these requests.
* **Attendance App HR Review** shows short leave requests waiting for HR, with their times.
* **Setup Attendance Approval Rules** can set approval steps for short leave requests.

***

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