> 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/manager-workstation/reporting-manager-workstation/print-preview-cashier-report.md).

# Print Preview Cashier Report

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

**Report Details**

* *Store #: Store ID.*
* *CSR Name: The cashier name.*
* *Reg #: The register number.*
* *Open: The cashier shift open time.*
* Close: The cashier shift close time.
* Seq #: The sequence number.
* MOP: Method of Payment used.
* ECR Total: Electronic cash register total.
* Actual: The amount entered by the closing cashier after counting the mop in the drawer.
* Manager Correx: The amount that the manager corrected.
* Variance: Actual Amount - Manager Correction.
* *Cash Passed: The amount passed on to the next cashier.*
* To: *To whom the ECR cash was passed on to in the next shift.*
* Cashier Sig: Closing cashier signature.
* MOP Amounts Entry: Entry status.
* Entered By: Name of the employee who entered the drawer 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/manager-workstation/reporting-manager-workstation/print-preview-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.
