> 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/banquet/banquet-module/reports/faq-on-reports/explain-the-different-types-of-financial-reports-and-sales-analysis.md). # Explain the different types of Financial Reports and Sales Analysis The banquet management system provides a variety of financial reports and sales analysis tools to monitor revenue, track transactions, and evaluate performance. **Financial Reports** Financial reports are primarily found under the Reports and Queries menus and focus on tracking revenue, taxes, and transaction history. • Banquet Sales Day Book: This report displays all banquet sales recorded for a single day. A Monthly version is also available to view these sales across a month-wise breakdown. • Banquet Settlement: This report tracks how bills were settled and can be filtered by specific users to monitor staff performance or accountability. • Advance & Refunds: The Banquet Advance report shows all deposits collected within a specific date range, while the Banquet Advance Refund report tracks any deposits returned to guests. • Tax and Discounts: The Tax Report allows users to filter by tax structure to see all taxes collected. The Discount List tracks all price reductions given, and the Void Bill report lists any bills that were canceled. • Audit and Operational Reports: The Bill Reprint Audit monitors when and by whom bills were reprinted. Operational financial data can be found in the Kot Details report or the NC KOT Summary, which specifically tracks non-chargeable Kitchen Order Tickets. • Pending Items: Under the Queries menu, you can find reports for Pending Bills and Pending KOT/Charges, which identify revenue that has not yet been finalized or settled. **Sales Analysis** The Analysis menu provides deeper insights into business trends and item popularity to help with strategic planning. • Banquet Sales: This analysis provides a breakdown of sales details that can be Grouped By categories like Market Segment to see which types of clients generate the most revenue. • Item Wise Sales: This allows management to see exactly which products are selling best. It can be filtered by Product Group, Menu Item, or Open Item. • Banquet Sales Performance: This tool focuses on how different market segments are performing compared to each other, helping to identify growth opportunities. • Business On Book: This provides a view of upcoming business and current performance, with filters for specific Properties, Venues, and Business Filters. • Weekly Forecast: Located under Queries, this provides a forward-looking view of scheduled events and expected revenue for the week. --- # 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/banquet/banquet-module/reports/faq-on-reports/explain-the-different-types-of-financial-reports-and-sales-analysis.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.