> For the complete documentation index, see [llms.txt](https://docs.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verifone.com/support-uk/v200c/how-tos/how-to-run-reports-from-the-terminal.md).

# How to Run Reports from the Terminal

Run end-of-day and transaction reports directly from a V200C terminal.

{% hint style="info" %}
**Use this when** you need to run a report — such as an end-of-day Z Report — directly from a V200C terminal.
{% endhint %}

This guide runs reports from the terminal's Reports menu, including end-of-day settlement and transaction reports.

{% hint style="info" %}
You'll need the Configuration password to complete this process. The default is `12345`. If it has been changed and you don't know it, refer to page 43 of the [Webcom Manual](https://verifone.gitbook.io/uk-help-centre/webcom-manual/).
{% endhint %}

## Run a report

{% stepper %}
{% step %}

### Open the Menu

On the Sale screen after logging in, tap the blue banner at the top of the screen.
{% endstep %}

{% step %}

### Open Reports

Select `Reports` and enter your Configuration password.
{% endstep %}

{% step %}

### Choose a report

The terminal shows the available reports:

* Q Report
* X Report
* Z Report
* Stored Offline Report
* Transaction Report
* Live Store Report
* Session Report
* Summary Settlement Report
* Detailed Settlement Report
* System Info Report

For end-of-day reporting, select the `Z Report`.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
Reports only show transactions currently held in the LIVE store on the device. Transactions that have already been submitted won't appear.
{% endhint %}

<details>

<summary>Keywords</summary>

Also called: run reports, terminal reports, Z report, X report, end of day report, settlement report. Search terms: reports, Z report, X report, end of day, settlement, transaction report, live store.

</details>


---

# 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://docs.verifone.com/support-uk/v200c/how-tos/how-to-run-reports-from-the-terminal.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.
