> 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/summary-reports.md). # Summary Reports ## **Overview** The Summary Reports category provides consolidated sales, payment, and business performance reports for the selected reporting period. These reports help restaurant managers analyze revenue, payment collections, terminal performance, meal-time sales, and overall sales trends for better operational and financial decision-making.

## **Reports Available** The Summary Reports category includes the following reports: * Payment Summary by Terminal Report * Payment Summary Report * Daily Sales Summary Report * Daily Terminal Sales Summary Report * Meal Time Sales Report * Sales by Period Report

#### **Screen Elements** The following screen elements are common to all reports in the Summary 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 terminal, payment method, meal period, sales period, entity, 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.

### **Payment Summary by Terminal Report** The Payment Summary by Terminal Report provides a consolidated summary of payments processed through each POS terminal during the selected reporting period. It helps managers compare terminal-wise payment collections and monitor transaction activity across different billing stations.

#### **Report Fields** The report includes information such as: | **Field** | **Description** | | --------------- | -------------------------------------------------------------------------------------------------------------------------------------- | | Terminal | Displays the name of the POS terminal where payments were processed. It helps identify payment collections handled by each terminal. | | Cash | Displays the total cash payments received through the terminal. It helps monitor cash collections for reconciliation purposes. | | Card | Displays the total payments received through card transactions. It helps track electronic payment collections for the selected period. | | Digital Payment | Displays the total amount received through digital payment methods such as UPI or wallets. It helps analyze non-cash payment trends. | | Total | Displays the combined payment amount collected through all payment methods. It helps evaluate the terminal's total payment collection. | *Note - The information displayed may vary depending on restaurant configuration and available transaction data.* #### **Use Case** Use the Payment Summary by Terminal Report to: * Compare terminal-wise collections. * Verify payment reconciliation. * Monitor payment methods. * Track billing performance. * Review total payment collections. ### **Payment Summary Report** The Payment Summary Report provides an overall summary of payments received through different payment methods during the selected reporting period. It helps managers reconcile collections, monitor payment distribution, and analyze overall revenue.

#### **Report Fields** The report includes information such as: | **Field** | **Description** | | ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | | Payment Type | Displays the payment method used for transactions, such as Cash, Card, or Digital Payment. It helps categorize collections based on payment mode. | | Transaction Count | Displays the total number of transactions processed using each payment method. It helps measure payment method usage. | | Amount | Displays the total amount collected through each payment method. It helps evaluate revenue generated from different payment types. | | Percentage | Displays the percentage contribution of each payment method to total collections. It helps analyze payment preferences among customers. | *Note - The information displayed may vary depending on restaurant configuration and available transaction data.* #### **Use Case** Use the Payment Summary Report to: * Review payment collections. * Compare payment methods. * Reconcile daily revenue. * Analyze customer payment preferences. * Generate financial summaries. ### **Daily Sales Summary Report** The Daily Sales Summary Report provides a day-wise summary of sales, including ticket count, tax, and total sales amount. It helps managers review daily business performance and monitor sales trends over a selected period.

#### **Report Fields** The report includes information such as: | **Field** | **Description** | | -------------- | --------------------------------------------------------------------------------------------------------------------------------------- | | Period | Displays the selected reporting interval, such as hourly, daily, weekly, or monthly. It helps organize sales information based on time. | | Ticket Count | Displays the total number of tickets generated during the selected period. It helps measure customer transaction volume. | | Pre Tax Total | Displays the sales amount before taxes are applied. It helps evaluate the actual revenue generated. | | Tax Total | Displays the total tax collected during the reporting period. It helps verify tax calculations and reporting accuracy. | | Post Tax Total | Displays the sales amount after tax calculations. It helps review the billed sales value for the selected period. | | Total | Displays the final total sales amount for the reporting period. It helps analyze overall revenue performance. | *Note - The information displayed may vary depending on restaurant configuration and available transaction data.* #### **Use Case** Use the Sales by Period Report to: * Compare sales across periods. * Monitor revenue trends. * Analyze transaction volumes. * Verify tax collections. * Support business performance analysis. ## **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/summary-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.