> 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/transactions.md).

# 財務與營運紀錄

在相關報告螢幕中使用記錄交易. 可用的選項取決於報告和您的帳戶許可權.

## 選擇正確的記錄型別

| 事件              | 使用記錄                   |
| --------------- | ---------------------- |
| 客人收到錢           | 收到的付款,包括日期,金額,貨幣和付款方式. |
| 業務成本發生          | 費用,包括類別,相關人/單位和解釋.     |
| 現有債務已償還         | 實際付款，與登記費用分開記錄。        |
| 錢將或已經歸還給客人      | 退款，狀態為待處理或已完成。         |
| 已收到保證金          | 押金記錄，不應計為住宿收入。         |
| 發生故障,任務,投訴或庫存移動 | 相關的運營記錄,包含源,狀態和所需的欄位.  |

## 建立記錄

1. 開啟正確的報告和酒店分支,然後選擇記錄交易.
2. 選擇操作型別和日期.
3. 選擇記錄型別所要求的預訂,單位,員工或其他當事人.
4. 對於貨幣記錄,如有所需的全部金額,貨幣和支付方式.
5. 如有必要,新增賬戶或班級參考,期限,狀態和筆記.
6. 檢查確認步驟,然後儲存.
7. 使用相同的日期,酒店分支和貨幣檢視報告.

## 工資,租金和公用事業費用

對於員工工資,請選擇員工. 在租金費用方面,請指定房東. 對於公用事業費用,請選擇正確的型別,如電力,水,網際網路或天然氣. 記錄日期決定了報告期;您可以提到記錄中所涵蓋的月份.

登記費用並不代表已經付款。 工資頁面不會自動計算薪資。 使用費用分類來檢視總額;不要再次輸入相同的費用.

## 賬戶和班級匹配

為了結算開放的賬戶,酒店分支,貨幣和參考必須匹配. 開放,關閉和相關現金流動時使用相同的輪換參考. 選擇相同的產品程式碼,以檢視庫存收據和消費.

不要再把舊的預付作為新收據. 單獨建立檔案不是一個金融交易. 如果維護費用或損害費用也必須作為業務費用,請單獨記錄費用,並檢查是否重複.


---

# 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/transactions.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.