> 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/dineplan/front-desk/report/entity-reports.md). # Entity Reports ## **Overview** The Entity Reports category provides reports related to ticket activity associated with restaurant entities such as tables. These reports help restaurant managers monitor ticket details, table utilization, and transaction activity for operational analysis.
## **Reports Available** The Entity Reports category includes the following report: * Ticket Table Report
#### **Screen Elements** The following screen elements are common to all reports in the Entity Reports category. **View Mode** * Select how the report is displayed. * Available options include: * **Compact** – Displays the report in a condensed format. * **Full** – Displays the complete report with all available information. * **Free** – Displays the report without predefined formatting, allowing flexible viewing.
**Filter by Condition** * Apply report-specific filters such as table, ticket number, user, entity, payment status, or other available conditions before generating the report.
**Filter by Date** * Specify the required date or date range for generating the report.
**Export as PDF** * Exports the generated report as a PDF document.
**Export to Excel** * Exports the generated report as an Excel file.
**Print** * Prints the currently displayed report.
### **Ticket Table Report** The Ticket Table Report displays ticket information associated with restaurant tables, including ticket details, invoice information, payment status, assigned user, and creation date. It helps monitor table activity and review ticket transactions during the selected business period.
#### **Report Fields** The report includes information such as: | **Field** | **Description** | | ------------- | --------------------------------------------------------------------------------------------------------------------------------------- | | ID | Displays the unique identifier assigned to each ticket record. It helps uniquely identify and reference individual ticket transactions. | | Ticket Number | Displays the unique ticket number generated for the order. It helps track and locate specific customer tickets. | | Invoice No | Displays the invoice number associated with the ticket, if available. It helps verify billing information and complete transactions. | | Total | Displays the total bill amount for the ticket. It helps review the overall value of each transaction. | | Table | Displays the table assigned to the ticket. It helps identify where the order was placed within the restaurant. | | Paid | Indicates whether the ticket has been fully paid. It helps distinguish between settled and pending transactions. | | User | Displays the user or staff member who created or handled the ticket. It helps monitor user activity and transaction ownership. | | Created Date | Displays the date and time when the ticket was created. It helps track transaction history and business activity. | | Time | Displays the transaction time for the ticket. It helps analyze ticket activity during different operating hours. | *Note - The information displayed may vary depending on restaurant configuration and available transaction data.* #### **Use Case** Use the Ticket Table Report to: * Review ticket activity by table. * Monitor payment status of table orders. * Verify invoice and ticket information. * Track user-wise ticket transactions. * Support operational monitoring and auditing. ## **Notes** * The information displayed in the reports may vary depending on the selected report, available transaction data, and restaurant configuration. * Report results are generated based on the selected date range and applied conditions. * Some fields, such as Cost, Total Cost, and Profit, are available only when costing is configured in the system. * Empty reports indicate that no transactions match the selected date range or filter conditions. * Report totals are displayed based on the transactions included in the generated report. * Use Export to PDF, Export to Excel, or Print to save or share the generated report as required. --- # 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/dineplan/front-desk/report/entity-reports.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.