> 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/explain-the-night-audit-process-and-the-mandatory-pre-audit-checks.md). # Explain the night audit process and the mandatory pre-audit checks? The **Night Audit** is a critical day-end process (typically started after 23:59) that finalizes all transactions, closes the current account date, and opens a new one. Once completed, the system prevents any further modifications or postings to the closed date. ### **Mandatory Pre-Audit Checks** Before executing the audit, it is mandatory to verify and complete several processes to ensure data integrity: * **In-House Guest & Registration Verification:** Ensure all expected arrivals have been checked in and assigned registration numbers. You can use the **Guest Information Amendment** window to update guest or tariff details if needed. * **Tariff and Rate Code Accuracy:** Verify that the correct room tariffs and rate codes are applied to all in-house guests. The **Room Tariff Report** can be used for this verification. * **Settlement and Check-Out Details:** All settlement bills and checked-out guest details must be cross-referenced with printed bills and system reports. This includes verifying voided bills through the **Void Bill Report**. * **Revenue Posting:** Ensure all miscellaneous revenues, such as room service and telephone calls, are properly posted to the correct guest ledgers. * **Clear Pending Bills and KOTs:** All outlet bills must be settled, and any pending **Kitchen Order Tickets (KOTs)** in restaurants or room service must be cleared. * **Resolve Overdue Departures:** Guests scheduled to leave but still showing as in-house must either be checked out or have their stay extended. * **Mandatory Tariff Posting:** Room tariffs for all in-house guests must be posted before the audit can begin. This is done via the **Post Tariff All** option, which is available after 10:00 PM. ### **The Night Audit Process** You can verify your preparedness using the **Night Audit Check List**, which will display any pending jobs (like unposted plans or unpaid bills) that would block the audit. Once the list is empty, follow these steps: 1. **Navigate:** Go to the **Night Audit Main Menu >> Night Audit**. 2. **Create Night Balance:** Click **Create Night Balance** and select **Proceed**; the system will show "Completed" once finished. 3. **Open New Day:** Click **Open New Day**, enter the new accounting date, and re-confirm. 4. **Completion:** Click **Proceed** to finalize the audit and open the new business day. 5. **GL Posting:** After the audit is finished, use the **NA GL Posting** option to transfer the night audit revenue data to the **General Ledger.**
--- # 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/explain-the-night-audit-process-and-the-mandatory-pre-audit-checks.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.