> 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-queries1/faq-on-queries/pending-scenarios-in-the-night-audit-checklist.md).

# Pending scenarios in the Night Audit Checklist

**What are the common pending scenarios in the Night Audit Checklist?**

The **Night Audit Checklist** identifies pending tasks that must be completed before the system allows the **Night Audit** to proceed. Common pending scenarios include:

#### **1. Tariff Not Posted**

* Indicates that room tariffs have not been posted for all in-house guests.
* Complete this task using the **Post Tariff All** option, typically after **10:00 PM**.

#### **2. Plan Not Posted**

* Appears when plan charges for in-house guests have not yet been posted or finalized.

#### **3. Overdue Departures**

* Occurs when guests scheduled to depart on the current date are still marked as **In-House**.
* These reservations must be:
  * Checked out, or
  * Extended if the guest is continuing their stay.

#### **4. Checked-Out Guest with Unpaid Bills**

* Indicates that a guest has been checked out and a final bill has been generated, but the bill has not yet been settled.

#### **5. Pending KOT (Kitchen Order Tickets)**

* The Night Audit cannot proceed if there are pending **KOTs** in the **Restaurant** or **Room Service** outlets.
* These KOTs must be:
  * Settled by generating a bill, or
  * Cancelled in the **POS** module.

#### **6. Pending Bills**

* Refers to bills created in the **POS** module that are still **unsettled** or **uncancelled**.

Clearing these pending items ensures that all guest transactions and revenue are accurately recorded before the system advances to the next accounting date during the **Night Audit**.


---

# 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-queries1/faq-on-queries/pending-scenarios-in-the-night-audit-checklist.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.