> For the complete documentation index, see [llms.txt](https://docs.cottfile.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cottfile.com/filer-guide/reports.md).

# Reports

The Reports page is an analytics and accounting dashboard for your organization's filing activity. It appears in the sidebar for **attorneys and org admins with Accounting access** -- a per-member switch set under **Settings > Team Members > Edit** ("Accounting access"), or by a platform administrator. Without it, the page says "Accounting access not enabled."

For members of more than one firm, Reports shows your **active practice** -- both the grant and the data are per firm, counted by the practice each filing was *submitted under* (so a colleague who changes firms doesn't move numbers between reports). Switch practices from the top bar to see the other firm.

## Filters

At the top of the page:

* **Date Range** -- presets (Today, 7d, 30d, Month, YTD) or custom from/to dates with **Apply**.
* **Court**, **Doc Type**, and **Status** (Submitted, Under Review, Accepted, Rejected, Partial Accept, Recorded).
* An active-filter count with **Clear all**.

## Summary Cards

Three stat cards reflect the current filters:

* **Total Filings** -- filings submitted by your organization
* **Total Fees** -- with a court vs. convenience breakdown ("Court $X · Conv. $Y")
* **Acceptance Rate** -- percentage of decided filings that were accepted

## Charts

* **Top Cases** -- the cases with the most filing activity, ranked with their fees
* **Daily Spending** -- filing fees per day

## Filing Ledger

A detailed table of every filing: **Case #**, **Internal Ref** (the matter number or file reference entered at filing time), **Court**, **Case Type**, **Doc Types**, **Total Fee** (hover for the court/convenience split), **Status**, and **Submitted**. Click any column header to sort.

## Case Deposits

A second table lists deposit activity by case: **Case #**, **Court**, **Total Charged**, and **Paid**. Deposits are filtered by date and court only. Receipts download from the [Payments](/filer-guide/wallet-and-payments.md) or [Statements](/filer-guide/statements.md) pages.

## Export to Excel

Click **Export to Excel** to download an `.xlsx` workbook with four sheets -- **Filing Ledger**, **Case Deposits**, **Daily Counts**, and **Summary** -- respecting your active filters.

{% hint style="info" %}
**📹 GIF:** The Reports page -- picking a date preset, filtering by court, scrolling the Filing Ledger, and clicking Export to Excel.
{% endhint %}

## Related Pages

* Your filing history also lives on the **dashboard** in the My Filings table.
* For per-transaction financials with receipts and CSV export, use [Statements & Receipts](/filer-guide/statements.md).
* For court-stamped copies of recorded documents, open the case detail page -- stamped documents include the court name, date, and recording number.


---

# 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.cottfile.com/filer-guide/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.