> For the complete documentation index, see [llms.txt](https://docs.opencollective.com/help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.opencollective.com/help/collectives/collective-settings/zero-collective-balance.md).
# Zero Collective Balance
Before [changing hosts](/help/collectives/add-fiscal-host.md#changing-fiscal-host) or [closing a Collective](/help/collectives/collective-settings/closing-a-collective.md), the balance must be at zero.
You can move money out of your Collective in several ways:
* [Submitting expenses](/help/expenses-and-getting-paid/submitting-expenses.md) to withdraw funds.
* [Donating to another Collective](/help/financial-contributors/collective-to-collective.md) in the same fiscal host.
* Giving the remaining balance to your Fiscal Host. You can access that option by navigating to your Collective's Dasboard > Settings > Advanced**.**
## Leftover Balance
#### Let the Payee cover the fees
When emptying the balance for a collective, you have the option of charging the payment processor fees on the payee which will guarantee that 100% of the collective's balance will go out. This option is only available for bank transfers for hosts that support Transferwise at the moment.
When these conditions are met, the host admins will see a checkbox on the *Pay expense modal*:
#### Dealing with small leftovers
When it's not possible to use the feature previously described, you may sometimes end up with a small amount left behind if you try to withdraw 100% of your balance. This is usually caused by fees being hard to predict exactly.
If this happens, go to your Collective's page, click on the gear icon next to your logo, head to **Advanced** and use the **Empty Balance** button to transfer the remaining funds to your Fiscal Host.
---
# 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.opencollective.com/help/collectives/collective-settings/zero-collective-balance.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.
