> 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/using-manager-workstation/logging-in-as-cashier.md).

# Logging in as Cashier

{% stepper %}
{% step %}
**Open Manager Workstation**

Open a web browser and connect to the Manager Workstation.
{% endstep %}

{% step %}
**Employee Type**

Select **\[Employee Type]** from the drop-down menu, then choose **Cashier**.
{% endstep %}

{% step %}
**Cashier credentials**

Enter the Cashier ID and password.
{% endstep %}

{% step %}
**Sign in**

Press **\[Enter]**, or click **\[Sign In]**.

![](https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/jmI8KB8nC8xScWej0G9S/Unknown%20image)
{% endstep %}
{% endstepper %}

## Cashier Reporting

Navigate to **Cashier > Cashier Reporting**.

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

The logged in Cashier’s Reports List shows all available Closed Cashier Reports within the reporting period associated with the logged in cashier account.

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

Each entry shows MOP Amounts Entry status: Pending or Complete.

The Cashier may click the report number link for any reports marked as Complete to print or reprint the Cashier Report.

The Cashier may click to select a report number link to enter amounts for any reports marked as Pending. If more than one Report is “Pending”, the Cashier must complete the oldest report first.

## Editing Pending Reports

The Cashier may click to select the link to any reports marked as Pending to enter amounts.

The report header includes the Cashier ID and Name, the Report Sequence Number, the Register Number and the date/time stamp of when the report was closed.

The report body includes an entry for each MOP, configured to prompt for a cashier amount and provides a field into which amounts are entered.

The MOP configuration flag to permit zero entry is enforced in this form. MOPs configured to permit zero entry default to zero when no amount is entered.

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

After counting the till, the Cashier enters the counted amounts for Cash, Check, and Coupons.

Click **\[Save]** to save the form contents, or to exit without saving, click **\[Cancel]** to return to the Reports List screen.

## Cashier Reporting Print Preview

After entering till amounts, a Reconciliation Report is generated comparing the ECR Totals with the Actual entered totals, and the variance between the two.

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

The Cashier may opt to Print/Preview the Cashier Report. When selected, the output report will be generated and displayed on-screen in Preview mode, and is available to print. The system will return to the Reconciliation Report screen.

Click **\[Cancel]** to return to the Reports List screen.


---

# 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/using-manager-workstation/logging-in-as-cashier.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.
