> 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/fo-night-audit-check-list.md).

# Night Audit Check List

Steps to view night audit checklist

### **NIGHT AUDIT CHECKLIST**

The Night audit checklist shows the report of all the pending works left out before proceeding with the night audit process. This report shows the pending works in all the major transaction modules. It is necessary to check this report once and make sure it's empty before proceeding on with the night audit.

1. To view the report, go to the “FRONT OFFICE” module “NIGHT AUDIT” “NIGHT AUDIT CHECKLIST”
2. Here the common pending scenarios shown are:

![](https://4060887901-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2ktZUs9CJyincVDXEmrM%2Fuploads%2Fgit-blob-739994e6e94bbb5d57fc0960c4b126a247f6f121%2FScreenshot%202023-07-21%20124026.png?alt=media)

1. Tariff not posted – post tariff for all in-house guests
2. Plan not posted – post plan for all in-house guests
3. Overdue departures – check out today’s departures or extend their stay as per the requirement
4. Checked out guest unpaid bills – final bill created but not settled
5. Pending KOT – pending KOT in the point of sale module which must be either settled with the bill or canceled in the POS module
6. Pending bills – pending bills in point of sale which also must be settled or canceled accordingly
7. To view the report only with the list tariff not posted, enable ![](https://4060887901-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2ktZUs9CJyincVDXEmrM%2Fuploads%2Fgit-blob-22cdf98b4e786b42941c165d7d2834c34efc7b34%2F1%20\(19\).png?alt=media)
8. Clearing out all these pending things will allow the user to perform 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-nightaudit/fo-night-audit-check-list.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.