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

# Donor Statements

Set up and send year-end Donor Statements from Settings > Finance > Donor Statements, then find, download, or create single statements in Relationships.

**Donor Statements** are year-end summaries of each donor's giving to your organization in the previous calendar year. You set up the email and send the annual batch in **Settings > Finance > Donor Statements**, and you find, download, or create individual statements in **Relationships > Donor Statements**. This article covers what a statement includes, and how to set up, send, download, and create statements.

## Before You Begin

* To set up and send statements, you need **Account Management: Edit Account Details and Configuration** permissions, and your account must be active.
* To find and download statements in Relationships, you need **Finance: View Transactions** permissions.
* Statements always cover the previous calendar year, January 1 through December 31.

{% hint style="danger" %}
You can send Donor Statements only once per calendar year. This cannot be undone.
{% endhint %}

## What A Statement Includes

Each statement is a PDF that includes:

* Your account logo or name, and your disclaimer.
* The donor's name, address, phone, and email.
* A summary of the date range, total transactions, and total given.
* Each donation, with its date, Action Page, and amount.
* Your organization's public address, phone, and website.

Statements include donations with a status of completed, partially refunded, or chargeback reversed. This includes cash, check, in-kind, and offline card gifts recorded with [Terminal (Offline Entry)](/finance/internal-processing/offline-entry.md). Amounts include any processing fees the donor chose to cover, minus partial refunds.

For nonprofit accounts that aren't political, statements also show a **Tax deductible amount** column. It matches the donation amount unless the donor received a product.

## Set Up the Statement Email

To set up the email:

1. Go to **Settings > Finance > Donor Statements**.
2. Enter a **Sender Name**. This is the name donors see in their inbox.
3. Enter a **Reply Email** for donor replies.
4. Enter a **Subject**.
5. Enter a **Message**, or click **Insert Default Message**.
6. Enter a **Disclaimer**, or click **Insert Default Disclaimer**. The disclaimer prints at the top of each statement.
7. Click **Save Settings**.

## Send Donor Statements

The **Before sending** checklist shows whether your sender details, message, and disclaimer are complete, your latest edits are saved, and that year's statements haven't been sent yet.

To send the annual batch:

1. Go to **Settings > Finance > Donor Statements**.
2. Check that every item under **Before sending** is complete.
3. Click **Send \[year] Statements**.
4. Click **Yes, send donor statements** to confirm.

Statements start sending right away. Each donor with an email address gets an email with a **View Statement** link to their PDF. The batch status changes to **Queued** while emails are sending and **Sent** when they're done.

{% hint style="warning" %}
Statements are emailed only to donors with an email address. For donors who gave with only a phone number, create and download a statement in Relationships, then send it to them yourself.
{% endhint %}

## Download A Statement

To download a statement after the annual batch is sent:

1. Go to **Relationships > Donor Statements**.
2. Filter by **Email**, **Phone**, or **Statement Year**. You need at least one filter. Enter the full email address in lowercase, and phone numbers as 10 digits with no formatting.
3. In the donor's row, click **Download**.

## Create An Individual Statement

You can create a statement for one donor after that year's annual batch has been sent. Creating a statement doesn't email the donor.

To create a statement:

1. Go to **Relationships > Donor Statements**.
2. Click **New Statement**.
3. Enter the donor's **Email** or **Phone**, and the **Statement Year**.
4. Click **Submit**.
5. Download the statement and send it to the donor.

{% hint style="info" %}
Each donor email can have one statement per year. Statements created with only a phone number aren't checked for duplicates, so check before you submit.
{% endhint %}

## Related Articles

* [Finance](/settings/finance.md)
* [Terminal (Offline Entry)](/finance/internal-processing/offline-entry.md)
* [Year-End Giving Statement](/donor-support/faq/year-end-giving-statement.md)
* [Timezone](/settings/setup/timezone.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/settings/finance/donor-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.