> For the complete documentation index, see [llms.txt](https://commanderhelp.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://commanderhelp.verifone.com/feature-references/features-and-products-references/in-house-accounts/reporting-in-house-accounts/summary-report.md).

# Summary Report

The Summary Flash Report provides an overview of all sales from the beginning of the current period up to the time the Flash Report prints.

**Report Details:**

![](https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/AZ3fCCHPSFSbuwuW0jAh/Unknown%20image)

* **TITLE:** SUMMARY REPORT
* **SUMMARY**
  * **MOP SALES:** Total sales amount by method of payment.
  * **NET SALES TOTAL:** Total amount tendered after cancellations and refunds are deducted.
  * **PAYMENT OUT:** Total amount of non-sales transactions that removed money from the drawer. The total is in parentheses because the number is negative.
  * **PAYMENT IN:** The total amount of non-sales transactions that added payment to the drawer.
  * **TOTAL TO ACCOUNT FOR:**
    * Net Sales Total
    * Payment Out
    * Payment In
* **CASHIER DETAILS**
  * **MOP SALES**
    * **CASH:** Summary of cash sales.
    * **IN-HOUSE:** Summary of House Account sales.
    * **TOTAL MOP SALES:** Total sales by method of payment.
  * **MOP CANCEL/REFUNDS**
    * **TOTAL MOP CANCEL/REFUNDS:** Total amount of cancelled or refunded transactions. The total is in parentheses because the number is negative.
  * **PAYMENT OUT:** Summary of transactions removed from the drawer.
    * **IN-HOUSE:** Summary of House Account pay outs.
    * **TOTAL PAYMENT OUT:** Total pay out amount.
  * **PAYMENT IN:** Summary of non-sales payment added to the drawer.
    * **IN-HOUSE:** Summary of House Account pay ins.
    * **TOTAL PAYMENT IN:** Total pay in amount.


---

# 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://commanderhelp.verifone.com/feature-references/features-and-products-references/in-house-accounts/reporting-in-house-accounts/summary-report.md?ask=<question>&goal=<user_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.
