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

# Payment Statements

Each parish has a monthly **Payment Statements** page (open a parish, then **Statements** in the parish sidebar). It shows the **court's portion** of every charge, refund, and chargeback in the period -- the money that settles to the court.

## Reading a Statement

* The page defaults to the **previous month**; arrows step month by month (you can't go past the current month).
* Summary cards: **Gross Deposits** (court portion of charges), **Refunds**, **Chargebacks**, and **Net Deposited**.
* If there were chargebacks, an alert flags them: "N chargeback(s) this period -- Total reversed: $X (court portion). Review flagged rows below."
* The table lists each transaction: **Date**, **Type** (Deposit / Refund / Chargeback), **Filing #**, **Case #**, **PSP Reference**, and **Court Amount**, with a **Net Deposited** footer.

## Exports

* **Export CSV** -- `statement-{court}-YYYY-MM.csv`, with summary lines prefixed `#`.
* **Export PDF** -- a landscape PDF of the same statement.

## Refunds

Refunds are **not** issued from CottFile. Issue the refund in the ValPay portal -- it flows back automatically, appears on the statement, and is netted out of the filer's totals. A full refund on a filing that hasn't been accepted yet releases its payment lock so the clerk can reject or edit it.

{% hint style="info" %}
**📹 GIF:** Opening a parish's Payment Statements page, stepping back a month, reviewing the summary cards, and clicking Export CSV.
{% 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/admin-guide/payment-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.