> 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/ri-chang-yun-ying/check-in-out.md).

# 入住、提前入住与退房

## 为现有预订办理入住

1. 在预订列表或客房卡片中找到正确的记录。
2. 核对客人姓名、房源编号和计划入住、离店日期。
3. 确认客人已经到达，房间也已准备好。
4. 在预订列表中选择“入住”或“提前入住”。客房卡片菜单中也有针对现有预订的对应操作。核对信息后确认。
5. 确认预订已变为入住状态，并出现在“在住客人”列表中。

保存预订并不等于办理入住。创建新的住宿记录前，先确认客人是否已有预订。

## 客人提前到达

请使用原有预订办理提前入住。房源必须从实际到达时间起，到计划离店时间为止保持可用；系统还会检查清洁状态及其他住宿记录。

例如：预计晚上到达的客人在中午抵达。如果房间准备就绪，且没有冲突的住宿，使用同一预订办理入住。计划到达时间会保留，实际入住时间另行记录。不要仅为通过入住检查而将计划日期往前修改。

如果出现“未清洁”提示，请核对房源编号和最新状态。如果实际已准备好的房间已成功保存为“干净”，仍无法入住，请参阅[故障排查](/zh-cn/bang-zhu-yu-can-kao/troubleshooting.md)。

## 办理退房

1. 从在住客人的客房卡片或预订记录打开退房操作。
2. 在退房前账单中，分别查看每种货币的账户汇总。
3. 核对住宿费用、附加服务、已收款项、退款和押金。
4. 离店前补记遗漏的服务。如果其他员工修改过记录，请刷新账单。
5. 如果仍有未结费用、退款或押金余额，先审核这些项目，再确认退房后保留这些余额。
6. 选择“完成退房”。
7. 核对已完成的住宿记录、实际离店时间和更新后的房态。

退房不会清除未结余额。生成文档也不会自动登记收款。请另行确认款项确已收到且已正确记录。

相关指南：[客房账单与附加服务](/zh-cn/cai-wu-yu-bao-biao/folio.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/ri-chang-yun-ying/check-in-out.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.