> For the complete documentation index, see [llms.txt](https://docs.maitredpos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.maitredpos.com/maitred/maitred-online-help-contents-by-module/report-center/report/report-invoice/check-summary.md).
# Check Summary
Maitre'D check summary report provides you with a summary of the total check sales (gross sales before any discounts, service charge and taxes), meal sales and an average $ amount per check for specific employees and Revenue Centers. From the report filter window, select the appropriate date and time range, Revenue Center and employees to be included in the report. The following is a sample of the check summary report:
**Id**
Employee code from POS Control module
**Employee:**
Employee name
**Meals:**
Amount of meal served. The option must be activated and configured to get a figure in that field.
**Total sales:**
Total invoiced sales for the selected period of time excluding discounts, service charge, and gratuity.
**Main sales:**
Total meal sales for the selected period of time excluding discounts, service charge, and gratuity.
**Other sales:**
Total sales less meal sales for the selected period of time excluding discounts, service charge, and gratuity.
**% Other sales:**
Other sales divided by the Total sales, multiply by 100
**Average amount / check:**
Total sales divided # Meals
---
# 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://docs.maitredpos.com/maitred/maitred-online-help-contents-by-module/report-center/report/report-invoice/check-summary.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.