> 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/how-do-i-use-the-flash-budget-report.md).
# How do I use the Flash Budget Report?
The Flash Budget Report is a management tool used to compare your property's Actual Sales against the Budget Defined in the **Night Audit (NA)** Masters for any selected period.
**Key Components of the Report**
The report displays performance data in rows, allowing you to track specific metrics alongside revenue, including:
* **Actual vs. Budgeted Sales.**
* **Rooms Sold.**
* **Average Room Rate (ARR).**
* **Average Revenue per Pax (ARP).**
**Filtering and Analysis Options**
You can customize the report to view business trends using the following filters:
* **YTD (Year Till Date):** To see cumulative performance for the current fiscal year.
* **Last Year:** To compare current sales and budget figures against the same period from the previous year.
* **Average/Year:** To view average performance metrics over the course of the year.
**Related Master Setup**
For the Flash Budget Report to display accurate data, several configurations must be completed in the Masters section:
* **Defining Budgets:** Budgets for specific periods must be entered in the NA Monthly Budget master.
* **Grouping Data:** You can use Flash Budget Grouping to create specific Group IDs and names that organize how Night Audit Group Names appear in the report.
* **Adding Statistics:** If you need to track custom metrics, you can use the Flash Budget Statistics master to add new items with defined sequence numbers and decimal preferences.
---
# 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/how-do-i-use-the-flash-budget-report.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.
