> 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-installation-configuration-and-troubleshooting-solutions/faqs/payroll/set-fixed-salary-without-overtime-or-undertime.md).

# Set Fixed Salary Without Overtime or Undertime

**YouTube:** [How to Set a fixed Salary Ignoring Overtime and undertime?](https://www.youtube.com/watch?v=ib_rdlicY4I)

## How to Set a fixed Salary Ignoring Overtime and undertime?

In this tutorial, we will learn how to **keep an employee’s salary fixed**, regardless of **overtime or undertime** in **Logic ERP**.

***

### **Create a Fixed Salary Grade**

* Navigate to the **Main Menu** → **Payroll Setup** → **Setup Grades**.
* Create a new grade for fixed salary and define the following details:
  * **Grade Name**
  * **Basic Salary Amount**
  * **Leave Details** (Leave, Casual Leave, Sick Leave, etc.)

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FF8IgGGwBf9qhpuE2gMYI%2FSetup%20Grade.png?alt=media&amp;token=5905f188-aa5d-40d3-90f0-95a25aaaf105" alt=""><figcaption></figcaption></figure>

* Once all required details are entered, click **Save** to create the grade.

> Note: Skip the *Overtime* and *Undertime* settings since the salary should remain fixed and not vary based on attendance.

***

### **Create Employee and Assign Grade**

* Now, go to the **Employee Setup** window and create a new employee profile.
* In the **Payroll Information** section:
  * Define **Date of Joining**, **Basic Pay**, **Designation**, and **Department**.
  * Select the **Fixed Salary Grade** created earlier from the dropdown list.

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FY9H4TUHG1EXF6Q1xx9Vh%2FDefine%20Grade%20in%20Empl%20setup.png?alt=media&amp;token=5dbf48ae-a996-4783-ba38-c7b86d2abefc" alt=""><figcaption></figcaption></figure>

* After entering all information, click **Save**.

***

### **Mark Attendance**

* Navigate to **Payroll Entry** and then **Attendance Register**.
* Select the employee and mark attendance as per the actual working hours.
* For example:
  * If the shift time is **10:00 AM to 7:00 PM (9 hours)**, but the employee arrives **30 minutes late**, enter the actual **Time In** and **Time Out** accordingly, then click **Save**.
* The system will show **Under Time = 30 minutes** after saving.

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FIEjKtCDvMtEHTvlOrtaH%2FAttendance.png?alt=media&amp;token=a1006324-1c18-4d3e-a998-1fc7f7f1f4bc" alt=""><figcaption></figcaption></figure>

***

### **Generate Payroll**

* Next, go to **Payroll Entry** → **Payroll Generation**.
* Select the **Payroll Month** and the **Employee**, then click **Recalculate**.

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FlnEbDO97HbWUeOlzN7tJ%2Fnet.png?alt=media&amp;token=1a595711-6945-4bd5-85df-0c751b17f95c" alt=""><figcaption></figcaption></figure>

You’ll notice that the **Net Salary** remains **₹10,000**, as no overtime or undertime criteria have been defined.\
This ensures that even if the employee arrives late or leaves early, their salary remains **unchanged**.

***

### **Result**

You have successfully configured a **Fixed Salary Grade** where the employee’s salary remains constant, irrespective of **Overtime** or **Undertime** variations.


---

# 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-installation-configuration-and-troubleshooting-solutions/faqs/payroll/set-fixed-salary-without-overtime-or-undertime.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.
