> For the complete documentation index, see [llms.txt](https://docs.allforclimate.earth/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.allforclimate.earth/services/level-up-your-collective-extra-features/track-your-budget-finances.md).
# Track your budget/finances
*Do you want a clear overview of the donations and contributions your Collective receives?*\
*Would you like to track your income per month, quarter, or year?*\
*Or better understand what is coming in vs. going out?*\
\
Good news 😊 You can easily access and customize these reports directly from your dashboard.
{% hint style="success" %}
To view your financial reports, go to:\
**Dashboard → (left menu) → Reports**
{% endhint %}
#### What you can do
* **Filter your data** by month, quarter, or year to get the overview you need
* Click on the **🧪 (experiment) icon** in the top right corner to split columns and clearly distinguish between **debit and credit**
* Use the **three dots (⋯)** next to transactions to:
* View more details
* Access the exact transaction
* **Export your data**:
* Export specific transactions via the three dots
* Or export the entire report (or your filtered selection) using the export button in the top right corner
These tools can help you keep track of your funding, improve transparency within your team, and make reporting to donors or partners much easier.
---
# 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.allforclimate.earth/services/level-up-your-collective-extra-features/track-your-budget-finances.md?ask=&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.
