> 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/zh-hk/salary-management/salary-setting.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://docs.coreway.com/coreway-hr/zh-hk/salary-management/salary-setting.md?ask=&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.