> 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/coupon-scanning/reporting-coupon-scanning/cashier-and-summary-reports.md).

# Cashier & Summary Reports

Scanned coupons are not reflected in Sales MOP totals. They are reflected only in the coupon totals provided in the Memo Items section of the Cashier and Summary Reports.

## **Memo Items**

Various transaction-related items have happened but they either do not affect totals or have already been counted in totals.

![](https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/iXG6gsSMVs5zU5Yi8fme/images/image11.png)

**Report Details**

* TITLE: CASHIER DETAILS REPORT.

**MEMO ITEMS**

* ITEMS: Quantity of items sold.
* CUSTOMERS: Number of customers (individual transactions).
* NO-SALES: Number of times the \[NO SALE] key has been pressed.
* VOID LINES: Number of times and total amount caused by using the \[VOID LINE] key. This does not include lines voided as part of a void ticket.
* VOID TICKETS: Number of times and total amount caused by using the \[VOID TICKET] key. This includes a line for positive amounts and a line for negative amounts.
* SCANNED COUPONS TICKET LEVEl: Coupon amounts applied to the entire transaction.


---

# 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/coupon-scanning/reporting-coupon-scanning/cashier-and-summary-reports.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.
