> 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/can-i-filter-the-night-audit-report-for-multiple-properties.md).
# Can I filter the Night Audit Report for multiple properties?
Yes, you can filter the Night Audit Report for multiple properties within the system.
By selecting the property from the top left-hand side of the report screen, you can view the specific revenue and collection data for that individual location. Additionally, if you select the **“All Properties”** option, the system will generate a consolidated report that includes data from all properties in your group.
**Key Features of the Night Audit Report**
* **Detailed Financial Breakdown:** The report displays figures for today’s closed day, **Month Till Date (MTD)**, and **Year Till Date (YTD).**
* **Net Revenue Calculation:** Each column is sub-divided into the total amount, any allowances issued, and the resulting Net Amount (Amount - Allowance = Net).
* **Cumulative Period Filtering:** While the report defaults to the last closed day, you can use a "From and To" date filter to view collective revenue and collections for any specific period.
* **Comparison Tools:** A filter is available to compare current revenues and collections against the same period from the previous year, providing insights for management.
Other analytical reports, such as the Occupancy Analysis and the Manager Report, also support this multi-property functionality, allowing you to switch between individual properties or view a group-wide summary
---
# 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/can-i-filter-the-night-audit-report-for-multiple-properties.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.
