> 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/cost-center/cost-statement.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/cost-center/cost-statement.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.
