> 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/verifone-central-getting-started/verifone-central/verifone-central-device-manager/reports.md).

# Reports

Choose the right report to review audit activity, device data, or chain of custody records.

Use **Reports** to review operational activity, device data, and chain of custody output.

Start with the question you need to answer. Then choose the report and filter scope.

Use it when you need to:

* trace user or system activity in **Audit Log**
* review device-level report output
* export or bulk update chain of custody data

### Available reports

This section includes:

* [Audit log](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/reports/audit-log) — review chronological events and filter by interval, organization, user, or event type
* [Device management](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/reports/device-management) — open report pages for chain of custody and device data

### Choose the right report

Use **Audit log** when you need activity history, including who performed an action and when.

Use **Device management** when you need device records, custody output, exports, or custody updates.

### Open Reports

{% stepper %}
{% step %}

### 1. Open Device Management

Go to **Verifone Central** → **Device Management**.
{% endstep %}

{% step %}

### 2. Open Reports

Select **Reports**.
{% endstep %}

{% step %}

### 3. Choose the report area

Select **Audit Log** or **Device Management** based on the outcome you need.
{% endstep %}
{% endstepper %}

### What each report gives you

#### Audit Log

Use **Audit Log** to review events by:

* time interval
* organization
* user
* event type

#### Chain of Custody report

Use **Chain of Custody report** to review device custody history, export report data, or bulk update chain of custody values.

Common fields include:

* event date
* serial number
* tamper evident label serial number
* role
* custodian
* location
* address
* status

#### Device report

Use **Device report** to review device-level report output and export it in **CSV** format.

Common fields include:

* serial number
* tamper evident label serial number
* status
* model ID
* event date
* unique device ID
* role
* custodian
* location
* address

### Verify the result

After you open a report, confirm that:

* you selected the correct report type
* the visible data matches the expected time and organization scope
* any export or import action uses the correct report page

If the expected data is absent, review the selected filters and active organization before exporting.

### Result

You can choose the right report page, validate its scope, and then filter, export, or update report data.

### Next steps

* [Audit log](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/reports/audit-log) — review activity history
* [Device management](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/reports/device-management) — open device-focused reports


---

# 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/verifone-central-getting-started/verifone-central/verifone-central-device-manager/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.