> 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/asset-tracking/view-device-status-in-chain-of-custody/export-chain-of-custody-details.md).

# Export Chain of Custody details

Export the current Chain of Custody view as a CSV file.

Use this action to export Chain of Custody details as a CSV file.

Use it when you need the current report view outside the platform.

### Before you start

Confirm that:

* the current report view shows the records you want to export
* any filters are already applied
* you want the current visible report scope in **CSV** format

Record the applied filters before exporting. The CSV captures the report scope at export time.

### Export the Chain of Custody report

{% stepper %}
{% step %}

### 1. Open the report

Go to **Device Management** → **Reports** → **Chain of Custody**.
{% endstep %}

{% step %}

### 2. Confirm the report scope

Review the current results and apply filters if needed.
{% endstep %}

{% step %}

### 3. Export the file

Select **Actions** → **Export Report**.
{% endstep %}

{% step %}

### 4. Download the CSV file

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

<div data-with-frame="true"><figure><img src="https://1786380399-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdzivQyj8aHN5Kvmx8apX%2Fuploads%2FlwSNIegQXdfc5I085Xep%2FPicture158.png?alt=media&amp;token=6944f839-ce09-4c1a-9546-eb4f07d90246" alt=""><figcaption></figcaption></figure></div>

### What the export includes

The file reflects the current visible report scope.

Use filters first when you need a narrower export.

### Verify the export

After the file downloads, confirm that:

* the file is in **CSV** format
* the record scope matches the filtered report view
* the file includes the fields you expected

Open the CSV and compare several serial numbers and custody values with the report view.

### Common follow-up checks

Use these checks after export:

* the file is too broad — return to the report, apply filters, and export again
* the file needs validation — compare a few rows with the on-screen custody records
* the file will support a later update — keep the exported scope limited to the records you intend to review
* the file needs a new scope — correct the filters and export again before using it

### Result

You have a validated CSV snapshot of the selected custody records.

### Sample output

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

### Next steps

* [View device status in Chain of Custody](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/asset-tracking/view-device-status-in-chain-of-custody) — return to the report view
* [Import Chain of Custody device details](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/asset-tracking/view-device-status-in-chain-of-custody/import-chain-of-custody-device-details) — upload a template file to merge updates


---

# 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/asset-tracking/view-device-status-in-chain-of-custody/export-chain-of-custody-details.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.