> For the complete documentation index, see [llms.txt](https://docs.coreway.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coreway.com/coreway-hr/payroll-management/payroll-settings.md).

# Payroll Settings

* Transform the company's compensation policies and regulations into calculation rules that can be automatically and accurately executed within the HR system, thereby achieving the standardization, automation, and efficiency of payroll calculations.

## Salary setting process: 

* \[Set Wage Items] > \[Set Wage from Template] > \[Set Attendance Payroll Rule] > \[Associate Salary Group]

First, set up the company's wage items and payroll template in **\[Payroll Settings]**, then add **\[Salary Rules]** (Daily Average Wage Rule > Hourly Wage > Piece Rate Wage > Performance Wage > Mandatory Provident Fund Rules > Allowance Rules > Attendance Deduction Rules > Attendance Leave Payroll Rules) > Finally, **\[Associate Salary Group]**.


---

# 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://docs.coreway.com/coreway-hr/payroll-management/payroll-settings.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.