> 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/chain-of-custody-report.md).

# Chain of Custody report

Review custody history, filter results, and run export or import actions.

Use **Chain of Custody report** to review custody history for tracked devices.

Use it when you need to:

* review location and custodian history
* search for specific custody records
* export custody data
* bulk update custody values with an import file

### Before you start

Confirm that you know:

* which devices or custody records you need to review
* whether you need to export data or upload a merge file
* whether the expected result is a review task or a bulk update task

### Open the report

{% stepper %}
{% step %}

### 1. Open the report

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

{% step %}

### 2. Review the records

Scan the visible custody list and confirm you are on the correct report.
{% endstep %}

{% step %}

### 3. Narrow the result set

Use the available filters to focus on the custody records you need.
{% endstep %}
{% endstepper %}

### Use this report to

* view shipped device records
* search for specific devices
* export report data
* import merged updates

### Choose a safe workflow

Use **review** when you need to inspect history or investigate one device.

Use **export** when you need a shareable snapshot of the current result set.

Use **import** only when a reviewed template contains the intended bulk changes.

{% hint style="warning" %}
An import changes multiple custody records. Confirm the target scope before you upload a file.
{% endhint %}

### What the report shows

Common output fields include:

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

Use these fields to trace where the device moved and who last handled it.

### Prepare a bulk update

1. Filter the report to the intended records.
2. Export the filtered data as your pre-change reference.
3. Review each changed value in the template.
4. Import the file and recheck the affected records.

Stop if the report scope or template rows do not match.

### Verify the result

After you review or filter the report, confirm that:

* the visible records match the devices or custody events you expected
* the result set is narrow enough before export
* the report is the correct source before you prepare an import update
* each imported record shows the intended custody values

### Related tasks

* [Export Chain of Custody report](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/reports/device-management/chain-of-custody-report/export-chain-of-custody-report) — download the visible report data
* [Import Chain of Custody report data](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/reports/device-management/chain-of-custody-report/import-chain-of-custody-report-data) — 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/reports/device-management/chain-of-custody-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.