> 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/device-management/device-report.md).

# Device report

Review device-level report output and export it as a CSV file.

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

Use it when you need:

* device details in one report view
* device data with related custody context
* a downloadable device report export

### Before you export

Confirm that the visible report data matches the device population you need.

Use **Chain of Custody report** when you need movement or custodian history. Use **Device report** for a broader device snapshot.

### Open Device report

Go to **Device Management** → **Reports** → **Device Report**.

<div data-with-frame="true"><figure><img src="https://content.gitbook.com/content/dzivQyj8aHN5Kvmx8apX/blobs/vMGHziF2wea7ITiO4C2s/image.png" alt=""><figcaption></figcaption></figure></div>

### What the report shows

Common fields include:

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

Use this page to review the current device report before you export it.

### Export the Device report

{% stepper %}
{% step %}

### 1. Review the report scope

Check the visible records before you export.
{% endstep %}

{% step %}

### 2. Open Actions

Go to **Device Management** → **Reports** → **Device Report** → **Actions**.
{% endstep %}

{% step %}

### 3. Download the export

Download the generated CSV file.
{% endstep %}
{% endstepper %}

<div data-with-frame="true"><figure><img src="https://content.gitbook.com/content/dzivQyj8aHN5Kvmx8apX/blobs/kuVW1bDPW6xNfEMF6khv/image.png" alt=""><figcaption></figcaption></figure></div>

### Verify the export

After you export the file, confirm that:

* the file is in **CSV** format
* the report data matches the current view
* the output includes the fields you need

Open the CSV and compare several device identifiers with the report view.

If the output does not match the visible report data, recheck the report scope before sharing or analyzing the file.

### Sample export output

<div data-with-frame="true"><figure><img src="https://content.gitbook.com/content/dzivQyj8aHN5Kvmx8apX/blobs/m47Qooz98GfTlvEsnzIv/image.png" alt=""><figcaption></figcaption></figure></div>

### Result

You have a validated device-data export for analysis or sharing.

### Next steps

* [Device management](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/reports/device-management) — return to the report hub
* [Chain of Custody report](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/reports/device-management/chain-of-custody-report) — switch to custody-specific reporting


---

# 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/device-management/device-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.