> 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/action-pages/advanced-features/donor-covers-fees.md).

# Donor Covers Fees

The Donor Covers Fees feature allows donors to add extra to their contribution in order to cover processing fees.

The **Donor Covers Fees** feature allows donors to add extra to their contribution in order to cover processing fees. This ensures that the organization receives the full intended donation amount.

## How To Enable Donor Covers Fees

The feature can be enabled or disabled at the **page level** for Donation and Event Pages.

1. Go to **Finance → Payment** inside the [Page Builder](/action-pages/page-builder.md) for your Donation Page or Event Page.
2. **Toggle** the setting as needed.
3. **Save** changes before exiting the Builder.

***Important for Political Organizations*** *Check with a compliance officer before enabling this feature. It can complicate reporting and donation limits.*

## How To See When a Donor Covers Fees

Covered fees can be identified in the **Finance → Transactions** tab within the fundraising account. See [Transactions](/finance/management-and-reporting/transactions.md).

* When fees are covered by a donor, the fee amount will appear crossed out.
* A **Person** icon will also be displayed to indicate that the donor covered the fee.

**Refunds and Covered Fees**

* If a refund is issued, the full amount *(donation + fees)* is returned to the donor, making the organization responsible for the fees.
* Optionally, a partial refund may be issued that excludes the fee portion.

## Donor Covers Fees in CSV Exports

CSV Exports provide visibility into whether the donor or the organization covered the fees.

* The **Donor Covered Fees** column indicates this with **True** or **False**.
  * **True** = Donor covered the fee.
    * The **Donor Covered Fee Amount** column will display the amount covered by the donor.
  * **False** = Organization covered the fee.
    * The **Donor Covered Fee Amount** column will display $0.
    * The actual fee covered by the organization will be listed in the **Anedot Fee** column.

The **Donation Amount** column always reflects the **total submitted by the donor** *(donation + fees)*.

## Related

* [Page Builder Overview](/action-pages/page-builder.md)
* [Payment Methods and Fees in the Page Builder](/action-pages/page-builder/payment-methods-and-fees.md)
* [Transactions](/finance/management-and-reporting/transactions.md)
* [Payment Methods](/get-started/anedot-101/payment-methods.md)
* [Advanced Features](/action-pages/advanced-features.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/action-pages/advanced-features/donor-covers-fees.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.