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

# Finance

Track donations, recurring commitments, payouts, and internal processing from Finance in your fundraising account. Open a child article for details.

Track donations, recurring commitments, payouts, and internal processing from **Finance** in your fundraising account.

Use Finance to review donation activity, reconcile deposits, manage refunds and voids, process card and ACH gifts through **Terminal**, and record cash, check, and other offline gifts through **Terminal (Offline Entry)**.

## Where Should I Start?

| If you want to...                                                              | Go to                                                                                     |
| ------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------- |
| Review individual donations and fees                                           | [Transactions](/finance/management-and-reporting/transactions.md)                         |
| Issue a refund or void                                                         | [Refunds and Voids](/finance/management-and-reporting/transactions/refunds-and-voids.md)  |
| Reconcile bank deposits and ledger activity                                    | [Entries](/finance/management-and-reporting/entries.md)                                   |
| Manage recurring gifts and future pledges                                      | [Commitments](/finance/management-and-reporting/commitments.md)                           |
| Help a donor whose recurring gift failed                                       | [Failed Commitments](/finance/management-and-reporting/commitments/failed-commitments.md) |
| Track payouts and transfer status                                              | [Payouts](/finance/management-and-reporting/payouts.md)                                   |
| Process a card or ACH gift on behalf of a donor                                | [Terminal](/finance/internal-processing/terminal.md)                                      |
| Record cash, check, offline card, or in-kind gifts that Anedot doesn't process | [Terminal (Offline Entry)](/finance/internal-processing/offline-entry.md)                 |

## Management & Reporting

Review transactions, ledger entries, payouts, commitments, refunds, and voids.

* [Management & Reporting](/finance/management-and-reporting.md)

## Internal Processing

Process card and ACH donations on behalf of donors, or record offline gifts for reporting.

* [Internal Processing](/finance/internal-processing.md)

## Related

* [Action Pages](/action-pages.md)
* [Settings > Finance](/settings/finance.md)
* [Donor Support](/donor-support.md)
* [Integrations](/integrations.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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.anedot.com/finance.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.