> 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/cai-wu-yu-bao-biao/reports.md).

# 使用和解读报表

在左侧菜单中打开报告. 报告可用于管理员和企业管理职位,在其酒店分支机构的访问范围内.

![管理概况](https://923543600-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFYpr3SG1RnMm4DANLHfW%2Fuploads%2Fgit-blob-353c217673e91ee13edff16d1543136c7aa37980%2Freport-dashboard.png?alt=media)

## 准备一份报告

1. 选择你需要的报告. 开始从管理总体图片.
2. 设定开始和结束日期. 截止日期包括在内.
3. 检查酒店分支和货币选择, 缩小其他过 ?? 器.
4. 阅读总结卡,图表和表.
5. 如果没有结果,首先检查时间和过 ?? .

一个查询可持续366天. 如果达到数据量限量,缩短该期限并创建单独的报告. 报告日期使用伊斯坦布尔时区.

## 收入和收到的钱不同

住宿收入与提供服务的夜晚有关. 收到的付款与货币到达时有关. 在两项措施中,今天收到的未来月住宿资金不必出现在同一日期.

![收到的每日收入和支付](https://923543600-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFYpr3SG1RnMm4DANLHfW%2Fuploads%2Fgit-blob-b3345a39180e7289ae7fdbe372615266b88f7116%2Freport-revenue.png?alt=media)

货币不会自动转换,也不会被合并成一个总数. 经营业绩不包括税收和融资后的净利息. 单位级成绩仅包括单位分配的费用;单独检查未分配的费用的情况.

## 阅读占用率

物理容量和可销售容量使用不同的命名器. 销售关闭的单位可能会影响结果. 历史容量变化没有被存储,因此历史占用率计算依赖于当前的物理定义. 客人数量和客人容量不同.

![每日使用的房间比例](https://923543600-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFYpr3SG1RnMm4DANLHfW%2Fuploads%2Fgit-blob-cff40710d246698cd84d549e5b59e33d525613fd%2Freport-occupancy.png?alt=media)

## 审查支付方式

比较信用卡,银行转账,现金和其他支付方式. 单独阅读收据和退款. 在解释图表之前检查日期和货币.

![支付方式](https://923543600-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFYpr3SG1RnMm4DANLHfW%2Fuploads%2Fgit-blob-89ba5864ff3d15d89d6cfd8c2e4ede1e68cee7cb%2Freport-payments.png?alt=media)

## 出口和编制报告文件

选择报告中的 CSV 包含所有行. 使用当前的过 ?? 器创建可编辑的报告. 在浏览器中添加解释并下载HTML或打印到PDF. 可编辑文档最多包含 1,000 行表格数据。 如果错过行列,则使用全数据集的CSV.

选择一个报告 [57报告目录](/zh-cn/cai-wu-yu-bao-biao/report-catalog.md). 使用完整的缺失源数据 [交易记录](/zh-cn/cai-wu-yu-bao-biao/transactions.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/cai-wu-yu-bao-biao/reports.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.