> 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/financial-contributors/collective-to-collective.md).

# Collective to Collective

## Within the same Fiscal Host

If you have a Collective with funds in its balance, you may use that as a payment method when contributing to another Collective within the same [Fiscal Host](/help/fiscal-hosts/fiscal-hosts.md). There are no fees for this payment method. Simply make a contribution to the payee Collective and select the payer Collective as your payment method during checkout.

## Across different Fiscal Hosts

We are working on the functionality to enable Collectives to give directly to Collectives in a different host (see [#3190](https://github.com/opencollective/opencollective/issues/3190)). As a workaround for now, use the following process:

1. Contact the Fiscal Host of the payee Collective and ask them to submit an expense to the payer Collective for your donation
2. The payer Collective will approve the expense and its Fiscal Host will pay the Fiscal Host of the payee Collective.
3. The payee Fiscal Host will then allocate the money to the payee Collective manually using '[add funds](/help/fiscal-hosts/receiving-money/add-funds-manually.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.opencollective.com/help/financial-contributors/collective-to-collective.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.