> For the complete documentation index, see [llms.txt](https://documentation.opencollective.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.opencollective.com/giving-to-collectives/giving-as-a-company/bulk-transfers.md). # Bulk Transfers Instead of making multiple financial transactions, Bulk Transfers let you send funds to your organization in one transfer, which you can then share as you wish. Let’s say that your organization wants to make several contributions to different collectives on the Open Collective platform. If you made each of these transactions individually, they would each be subject to their own payment processing fee. In these cases, many Fiscal Hosts offer Bulk Transfers. Bulk Transfers allow your organization to send them the total funds in one transfer, which they then deposit in your organization’s balance. Once the money has arrived, you can share it with one or many collectives, as you wish. Fiscal Hosts have different processes around Bulk Transfers, so contact the appropriate host in advance to clarify what you need to do. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://documentation.opencollective.com/giving-to-collectives/giving-as-a-company/bulk-transfers.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.