> 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-cn/bang-zhu-yu-can-kao/glossary.md).

# 术语表

| 术语      | 含义                       |
| ------- | ------------------------ |
| 酒店/商业   | 酒店分支和许可属于的主要业务.          |
| 住宿设施／分店 | 运营地点;记录范围为所选择的酒店分公司.     |
| 单位      | 在租用建筑物中的公寓,房间,宿舍或床.      |
| 实体床位    | 床或床单家具;不一定是单独租用的单元.      |
| 床位      | 物理结构中的位置或层次;客人容量是单独定义的.  |
| 确认预订    | 已保存但尚未办理入住的预订。           |
| 预计到达/出发 | 预期预订日期.                  |
| 实际抵达/出发 | 实际上登记和退出的时间.             |
| 分配      | 在特定的时间间隔内被保留的单位.         |
| 客房账单    | 预订的费用、服务及付款流水汇总。         |
| 应计收入    | 在某个期内提供的服务价值;支付可能到达其他日期. |
| 已收款项    | 公司收到的钱.                  |
| 费用／支出付款 | 费用是已经发生的成本；付款是实际流出企业的资金。 |
| 押金      | 按约定条件退还的押金，不是住宿收入。       |
| 房源夜数    | 一个单位的使用或销售一夜.            |
| 实体容量入住率 | 与实体容量相比,使用的单位夜晚.         |
| 可售容量入住率 | 与可销售的容量相比的使用量.           |
| 转型      | 同一产品类型的收入除以已售夜数。         |
| 雷普AR    | 同一产品类型的收入除以可售夜数。         |
| 经营结果    | 报表中的收入减去经营费用，并非会计净利润。    |
| 档案      | 从日常视图移出，不是永久删除。          |

解释每个状态标签,以及记录的日期和类型. 看看 [使用报告](/zh-cn/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-cn/bang-zhu-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.