> 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/special-discounts/reporting-special-discount/cashier-report.md).

# Cashier Report

The Cashier Report calculates the sales totals for that cashier on the terminal where the cashier performed the sales.

<img src="https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/ZPKXvjcuTX6hJSR5U6TD/images/image28.png" alt="" width="375">

## *Report Details:*

* TITLE: CASHIER REPORT
* REG#: register for which the Cashier Report was generated
* CASHIER #: ID and name of the employee who used the register
* RCPTS: beginning and ending receipt numbers issued during the cashier period
* TOT: total number of receipts printed on this terminal
* ACT: total number of receipts used by this cashier.
* OPEN CASHIER: date and time this cashier started using the register
* CLOSE CASHIER: date and time this register was closed

**SUMMARY**

* BEGINNING CASH: amount with which cashier started the drawer
* MOP SALES: total amount from the MOP SALES section
* NET SALES TOTAL: total amount in sales transacted for the drawer
* TOTAL TO ACCOUNT FOR: total amount that should be in the closed drawer

**CASHIER DETAILS**

* MOP SALES: summary of sales by method of payment
  * CASH: cash summary of sales by MOP
  * SPECIAL DISC: special discount summary of sales by MOP
  * TOTAL MOP SALES: total amount of sales by MOP

**MEMO ITEMS**

* \#ITEMS: quantity of items sold
* \#CUSTOMERS: individual transactions

**TOTALS**

* TOTAL MERCH SALES: total amount of merchandise sales


---

# 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/special-discounts/reporting-special-discount/cashier-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.
