> For the complete documentation index, see [llms.txt](https://docs.payfacto.com/payfacto-knowledge/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.payfacto.com/payfacto-knowledge/maitred-pos/maitred/maitred-online-help-contents-by-module/report-center/report/report-media/medias-summary-medias.md).
# Medias Summary (Medias)
Maitre'D medias summary (Medias) report provides you with a total quantity and a total $ amount of the invoices for each type of payment for the selected date or period of time. It also gives you a total tip amount and total tip fees per type of payment. Take note each media type must have the field "included in report" enabled to show up on the media report. From the report filter window, select the appropriate date and time range, Revenue Center, media type and employees to be included in the report. The following is a sample of the medias summary (Medias) report:
**Media:**
Media type name from the POS Control module
**Number:**
Quantity of invoices under the payment type, including the invoices done under training
**Amount**
Total $ amount for all invoices under the payment type, including the invoices done under training
**Tip:**
Total tip amount for all invoices under the payment type, including the invoices done under training
**Tip fees:**
Total tip fees for all invoices under the payment type, including the invoices done under training
---
# 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.payfacto.com/payfacto-knowledge/maitred-pos/maitred/maitred-online-help-contents-by-module/report-center/report/report-media/medias-summary-medias.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.