> 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/hr-and-admin-portal/cloud-configuration/setting/payroll/pay-settings.md).
# Pay Settings
### **How To Configure Separation Settings?**
**Path**: Cloud > Settings > Payroll > Pay Settings > Separation Setting
The Separation Setting page controls how employee separations are handled — whether master details stay editable after a separation is recorded, how far in advance a separation date can be set, and whether separations can go through after payroll has already been processed for that period.
**Step 1:** Log in to the **Cloud Portal**, open **Payroll**, go to **Pay Settings**, and select **Separation Setting**.
\
**Step 2**: Set **Master details** can be edited after separation made to **Yes** or **No**, depending on whether HR should still be able to edit an employee's master details once their separation is recorded.
\
**Step 3:** Enter a **value in No. of months** upto which separation date can be given. This is mandatory — it sets how far into the future a separation date can be set.
**Step 4:** Set **Allow Separation After Payroll Process** to **Yes** or **No**, depending on whether separations can still be processed after payroll has already run for that period.
**Step 5:** Under **Separation Processing Control (Cloud)**, choose Separate Now to process the separation immediately, or Approve & Separate Later to route it through approval first. Click **Save**.
**Important Note:** Separate Now processes the separation immediately. Approve & Separate Later first approves the resignation, then auto-separates the employee at the end of day on their Last Working Date — Separate Now can still be used afterward to separate them immediately if needed.
**Path 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/hr-and-admin-portal/cloud-configuration/setting/payroll/pay-settings.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.
