> For the complete documentation index, see [llms.txt](https://help.rbsgo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rbsgo.com/front-office-module/fo-nightaudit/faq-on-night-audit/what-are-the-common-pending-scenarios-in-the-night-audit-checklist.md).
# What are the common pending scenarios in the Night Audit Checklist?
The Night Audit Checklist identifies specific pending tasks and "jobs" that must be completed or cleared before the system allows the Night Audit to proceed. The most common pending scenarios listed in the checklist include:
* **Tariff Not Posted:** This indicates that the room tariff for all in-house guests has not yet been posted. This must be done using the "Post Tariff All" option, typically after 10:00 PM.
* **Plan Not Posted:** This scenario appears when plan charges for in-house guests have not been finalised.
* **Overdue Departures:** The system blocks the audit if guests scheduled to depart on the current date are still showing as in-house. These guests must either be checked out or have their stay extended.
* **Checked Out Guest Unpaid Bills:** This occurs when a final bill has been created for a guest, but the settlement has not yet been recorded in the system.
* **Pending KOT (Kitchen Order Tickets):** The audit cannot run if there are pending KOTs in the Restaurant or Room Service outlets. These must be either settled with a bill or cancelled in the Point of Sale (POS) module.
* **Pending Bills:** This refers to bills generated in the POS module that remain unsettled or not cancelled.
Clearing these pending items ensures that all revenue is accounted for and that the system can accurately transition to the new accounting date.
---
# 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://help.rbsgo.com/front-office-module/fo-nightaudit/faq-on-night-audit/what-are-the-common-pending-scenarios-in-the-night-audit-checklist.md?ask=&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.
