> 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/add-payroll-template.md).
# Add Payroll Template
* After setting the salary items, enter "Payroll Settings" and proceed to "Add Salary Template".
* The salary template is the salary table used when calculates wages. The salary structure is the sum of all salary items. The salary template is composed of the items enabled by the salary structure.
* If the salary items of all employees are the same, the administrator only needs to create one salary template.
* However, if employees have different salary items (for example, full-time and part-time salary items are different), you can refer to the following steps:
* Operation steps: \
① \[Payroll] > \[Payroll Settings] > \[Basic Setting] > \[Template] > \[Add Template] \
② Perform basic settings and fill in the template name and remarks \
③ Set up the template items and set the participating salary items. The administrator can add or remove salary items in the template according to needs. The system claim is required for the payroll calculation. You can set the item to be displayed in the wage form or not. After setting the salary table template, click "Save and take into effect" \
④ If the company has multiple similar salary templates, you can "Copy" the corresponding salary table in the operation column. Copy the same items to a new template and continue editing to reduce repeated operations.
---
# 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/add-payroll-template.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.
