> For the complete documentation index, see [llms.txt](https://docs.interaktifotel.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.interaktifotel.com/zh-tw/cai-wu-yu-bao-biao/folio.md).

# 客房帳單與附加服務

在客房卡片開啟「帳單」，或在訂房明細選擇「客房帳單／新增服務」。

帳單整合該筆訂房的住宿費、服務費與付款紀錄。不同幣別的合計請分別檢視。

## 新增附加服務

1. 開啟正確訂房的客房帳單。
2. 輸入或選擇服務名稱與類別。
3. 指定數量、單價及幣別。
4. 補充必要說明並核對總額。
5. 儲存後，確認服務已列入帳單明細。

例如：兩份早餐，每份 150 TRY，會產生 300 TRY 的應收服務費。這不代表已向旅客收取 300 TRY。實際收款須另外登記。

## 更正錯誤的服務費用

使用取消服務的操作並填寫原因，之後確認帳單中有取消紀錄。不要只修改說明，或另增負數服務來代替正式取消。

櫃檯員工只能為有權存取的住宿設施中尚未結束的訂房新增服務。訂房已結束或不在權限範圍內時，請聯絡主管。

## 退房前

補登最後的服務，核對已收款項及退款。其他員工修改紀錄後，請重新整理帳單。退房時確認未結餘額不會將其清除。

繼續閱讀：[交易紀錄](/zh-tw/cai-wu-yu-bao-biao/transactions.md)與[退房操作](/zh-tw/ri-chang-ying-yun/check-in-out.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.interaktifotel.com/zh-tw/cai-wu-yu-bao-biao/folio.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.