> 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/statements.md).

# Statements & Receipts

The **Statements** page (visible in the sidebar once you have at least one transaction) lists every card payment you've made, with downloadable receipts and a CSV export. It's the place to reconcile your filing spend.

## Summary Cards

* **Total Charged** -- court costs plus processing fees, **net of refunds**.
* **Transactions** -- successful charges.
* **Failed** -- attempts where no funds moved.

## The Transactions Table

A rolling list of your most recent transactions (up to 500), with one row per charge, top-up, or refund:

| Column                                      | What it shows                                             |
| ------------------------------------------- | --------------------------------------------------------- |
| Date                                        | When the transaction happened                             |
| Case # / Suit                               | The case the payment belongs to                           |
| Type                                        | Filing charge, New suit filing, Deposit top-up, or Refund |
| Court                                       | The parish                                                |
| Card                                        | Brand and last four digits                                |
| Status                                      | paid, refund, failed, or pending                          |
| Court Fees / E-Filing / Conv. 3.05% / Total | The per-column fee breakdown                              |

* Click a column header to **sort**; the funnel icon **filters** by value or date range. There's also a search box ("Search suits, cases, cards…") and a **Clear filters** link.
* **Failed rows** are struck through -- hover to see the decline reason. No funds moved on those.
* **Refunds** show as negative amounts and are netted out of the footer **Totals (net)** row.
* The receipt icon downloads the PDF receipt for that row (failed rows download a *transaction record* instead).

## Export CSV

Click **Export CSV** to download the table (respecting any active filters). The file includes the visible columns plus the filing number, transaction ID, and failure reason -- ready for your accounting system.

{% hint style="info" %}
**📹 GIF:** The Statements page -- filtering by date range, sorting by Total, downloading a receipt, and clicking Export CSV.
{% endhint %}

## Who Sees What

You see your own transactions. Org admins with **Accounting access** (set under Settings → Team Members) see the whole firm's transactions, with sealed case captions masked.

If you belong to more than one firm, both views follow your **active practice**: your other firm's transactions (and its firm-card top-ups) appear after you switch to it, and accounting access is per firm -- a grant from one never shows the other's books. Transactions from before you had a firm, and from firms you've since left, always show. Unpaid bills are the exception -- the **Payments due** page lists every firm's dues at all times.

{% hint style="info" %}
Court staff have their own version of this page under **Clerk Portal → Payments**, scoped to money collected for their court.
{% endhint %}


---

# 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/statements.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.