> 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/l-ke-yu-wen-jian/documents.md).

# 合約、收據與文件範本

## 準備預訂檔案

1. 開啟正確的預訂或房間卡.
2. 選擇所需的合同,預訂確認,支付收據或取消檔案.
3. 檢查文件語言和模板.
4. 在預覽中檢視客人,酒店分公司,日期和金額的欄位.
5. 如果需要的話,請使用編輯本文字的文字,只能更改即將建立的文件.
6. 發行檔案並使用可用的下載或列印操作.

對於支付收據,請驗證金額,貨幣,方法和日期. 發行檔案不收取銀行賬戶或支付終端費用,自動記錄財務支付,或提交KBS客戶通知.

## 編輯業務模板

1. 開啟一個授權帳戶的文件模板.
2. 選擇檔案型別和語言.
3. 準備標題和身體.
4. 插入自動資訊欄位線上索器,而不是手動輸入客戶或酒店分支的詳細資訊.
5. 用標題,列表,表格和調整工具格式化內容.
6. 在新檔案預覽中儲存並檢查結果.

每種語言都有自己的標題和體格. 準備缺失語言內容,而不是假設另一個語言將自動取代.

## 之前的檔案是否發生了變化?

發行檔案儲存文字和支付欄位,如其建立時. 更新一個模板不會改變現有檔案. 在預覽中編輯單個文件不會改變共享業務模板.

對於報告檔案,請關注 準備檔案 [使用報告](/zh-tw/cai-wu-yu-bao-biao/reports.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/l-ke-yu-wen-jian/documents.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.
