> For the complete documentation index, see [llms.txt](https://docs.pockethrms.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pockethrms.com/faqs/cloud-portal/attendance/transaction/ot-entry-multi.md).
# OT Entry Multi
### 1. How to remove OT (Overtime) from regular timing if not applicable?
If OT is not applicable that cannot be considered while salary processing. Also, if it is been not saved from OT entry multi option.
**Path:** Login cloud portal > Attendance > Transaction > OT Entry Multi > Select Date range > Select Shift Name > Edit > Select check box of the dates which employees OT is applicable > Save. (Only the saved OT will be calculated in Salary).
**Step 1:** Log in to the **Cloud portal**, go to the **‘Attendance’** menu, select **‘Transaction’**, and then click on **‘OT Entry Multi’**.
**Step 2:** Select the desired **‘Date range’** and **‘Shift Name’** to filter the list of employees, then Click the **‘Edit’** button to make the records editable.
**Step 3:** For each employee, select the checkbox corresponding to the specific dates on which they are applicable for overtime. Click **‘Save’** to confirm the overtime entries. Only the saved OT entries will be calculated in Salary.
**Link:**
For any queries, contact
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.pockethrms.com/faqs/cloud-portal/attendance/transaction/ot-entry-multi.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.