> For the complete documentation index, see [llms.txt](https://guide.charityvest.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.charityvest.org/governance-and-legal/financial-reporting.md).

# Financial Reporting

Displaying the history of Charityvest's audited financials and IRS Form 990 submissions.

## Audited Financials

We are audited annually by Smith & Howard, P.C. in Atlanta, Georgia.

{% file src="/files/ujWGY6O7Z0UnEAscW4S9" %}
FY2024 Audit
{% endfile %}

{% file src="/files/NpUnQMDTAwREyZxUSMO8" %}
FY2023 Audit
{% endfile %}

{% file src="/files/Q6GJegs2q6QSaktOY4tH" %}
FY2022 Audit
{% endfile %}

{% file src="/files/Z4YQ3GyFlcq5ENjY0pyg" %}
FY2021 Audit
{% endfile %}

{% file src="/files/-MjA0pIdVMXHRKrmT8az" %}
FY2020 + FY2019 Audit
{% endfile %}

## IRS Form 990s

We file a full IRS Form 990 annually.

{% file src="/files/ZxHi3BTPphjhtLngINyK" %}
2024 Form 990
{% endfile %}

{% file src="/files/EcEOU4N9SbUK8cz4Z3v2" %}
2023 Form 990
{% endfile %}

{% file src="/files/HsBovGf2q9a04XfFTTG4" %}
2022 Form 990
{% endfile %}

{% file src="/files/puA2Nj47KMHIUfZWMcmi" %}
2021 Form 990
{% endfile %}

{% file src="/files/0rUwqS6yAb3Ea7aVb2AP" %}
2020 Form 990
{% endfile %}

{% file src="/files/izUY2cfiFdTL9eEQoJZ9" %}
2019 Form 990
{% endfile %}


---

# 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://guide.charityvest.org/governance-and-legal/financial-reporting.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.