> For the complete documentation index, see [llms.txt](https://help.enterprise.ledger.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.enterprise.ledger.com/help-center-v2/guides/reporting.md).

# Reports

How to generate and download reports of your transactions, balances, and Requests on Ledger Enterprise.

**Role: Operators and Administrators.** You can report on the Accounts you have access to.

Reports export your activity as a .CSV file you can download. Use them for reconciliation, accounting, and audit.

## Generate a report

1. Open **Reports** and select **Generate report**.
2. Choose the **report type**.
3. Choose the **Accounts** to include.
4. Choose the **date range**.
5. Apply any filters you need.
6. Submit.

The report is prepared in the background. You do not have to wait on the page. It appears in the reports list when it is ready.

> **Note:** A report is not a governed Request. It needs no approval, and it does not use your device. It only reads data you can already see.

### Report types

<table><thead><tr><th width="162.7421875">Type</th><th>Contains</th></tr></thead><tbody><tr><td><strong>Transactions</strong></td><td>Money movements in and out of the selected Accounts</td></tr><tr><td><strong>Balances</strong></td><td>What the selected Accounts held over the period</td></tr><tr><td><strong>Requests</strong></td><td>Governance activity, including who approved what</td></tr></tbody></table>

Choose **Requests** for audit questions about approvals. Choose **Transactions** for reconciliation.

### Accounts

Include **all Accounts** you have access to, or select specific ones. When you select, the form shows how many Accounts are included, and you can filter the list by name.

> **Note:** "All Accounts" means all the Accounts **you** can see. Two people can generate the same report and get different results, because their access differs. For an audit, say which Account set the report covers.

### Date range

Pick a preset of **last week**, **last month**, or **last 6 months**, or set a custom start and end date.

The end date cannot be earlier than the start date. Both are required for a custom range.

### Filters

**Transactions** and **Requests** reports can be narrowed by type and by status. Leave a filter empty to include everything.

## Find and download a report

The reports list shows every report generated in your Workspace:

<table><thead><tr><th width="146.703125">Column</th><th>Shows</th></tr></thead><tbody><tr><td>Date</td><td>When it was generated</td></tr><tr><td>Type</td><td>Transactions, Balances, or Requests</td></tr><tr><td>Parameters</td><td>The Accounts, dates, and filters used</td></tr><tr><td>Author</td><td>Who generated it</td></tr><tr><td>Status</td><td>Ready, or Error</td></tr></tbody></table>

Download a **Ready** report from its row. Reports download as a **CSV** file.

The **Parameters** column matters more than it looks. It is how you tell two similar reports apart, and how you prove months later what a report actually covered.

## What is in the file

Each report type produces its own columns. Use these tables to check a file contains what you expect before you build a process around it.

### Transactions report

| Column | What it contains |
| ------ | ---------------- |
|        |                  |

### Balances report

| Column | What it contains |
| ------ | ---------------- |
|        |                  |

### Requests report

| Column | What it contains |
| ------ | ---------------- |
|        |                  |

## Delete a report

You can delete a report. It then disappears from the list.

## Reports expire

**A report does not stay available forever.** After a period, its content is deleted and you can no longer download the file.

The report's **configuration survives**. You can reuse it as a template to generate the same report again, with the same Accounts, dates, and filters.

> **Important:** A report expires. Its file is then deleted and only its configuration remains, reusable as a template. The reports list is not an archive.

## If a report fails

A report with the status **Error** did not complete. Generate it again from its row.

If it fails repeatedly, narrow it: use a shorter date range, or fewer Accounts. If it still fails, contact support and quote the report's date and parameters.

## Related

* [**Reviewing operation history**](/help-center-v2/guides/transactions/operation-history.md)
* [**Requests and approvals**](/help-center-v2/guides/requests.md)
* [**Finding Accounts and balances**](/help-center-v2/guides/accounts/finding-accounts-and-balances.md)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.enterprise.ledger.com/help-center-v2/guides/reporting.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.