> 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/shuo-ming-yu-can-kao/glossary.md).

# 詞彙表

| 術語      | 含義                       |
| ------- | ------------------------ |
| 酒店/商業   | 酒店分支和許可屬於的主要業務.          |
| 住宿設施／分店 | 運營地點;記錄範圍為所選擇的酒店分公司.     |
| 單位      | 在租用建築物中的公寓,房間,宿舍或床.      |
| 實體床位    | 床或床單傢俱;不一定是單獨租用的單元.      |
| 床位      | 物理結構中的位置或層次;客人容量是單獨定義的.  |
| 確認預訂    | 已儲存但尚未辦理入住的預訂。           |
| 預計到達/出發 | 預期預訂日期.                  |
| 實際抵達/出發 | 實際上登記和退出的時間.             |
| 分配      | 在特定的時間間隔內被保留的單位.         |
| 客房賬單    | 預訂的費用、服務及付款流水彙總。         |
| 應計收入    | 在某個期內提供的服務價值;支付可能到達其他日期. |
| 已收款項    | 公司收到的錢.                  |
| 費用／支出付款 | 費用是已經發生的成本；付款是實際流出企業的資金。 |
| 押金      | 按約定條件退還的押金，不是住宿收入。       |
| 房源夜數    | 一個單位的使用或銷售一夜.            |
| 實體容量入住率 | 與實體容量相比,使用的單位夜晚.         |
| 可售容量入住率 | 與可銷售的容量相比的使用量.           |
| 轉型      | 同一產品型別的收入除以已售夜數。         |
| 雷普AR    | 同一產品型別的收入除以可售夜數。         |
| 經營結果    | 報表中的收入減去經營費用，並非會計淨利潤。    |
| 檔案      | 從日常檢視移出，不是永久刪除。          |

解釋每個狀態標籤,以及記錄的日期和型別. 看看 [使用報告](/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/shuo-ming-yu-can-kao/glossary.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.