> 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/pay-suppliers-directly-with-vendors.md).

# Pay suppliers directly with vendors

Do you need to pay a supplier directly from your collective budget?\
Is the amount too large for a volunteer to pay upfront and request reimbursement afterwards?\
\
Good news. You can ask the fiscal host to create a vendor profile for your supplier. This allows the supplier to be paid directly through the platform without needing to create their own account.

\
**How to request a vendor**\
Send an e-mail to <info@allforclimate.earth> with the request to create a vendor profile with:

* Official registration/business name
* Correct banking details
* Official address
* It is very helpful to also include the invoice, as most of the required information is usually listed there already.

\
**Using the vendor in the expense flow**

* Once the vendor has been created:
* Go to the expense submission flow
* Under “Who is getting paid?”
* Select “Vendor”
* Search for and select the supplier/vendor profile

<div align="left"><figure><img src="https://215776803-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LyUeVe8jLnvP3xxLMBQ%2Fuploads%2FbV4lwY17abrmSSd0ucx8%2Fimage.png?alt=media&amp;token=db96de4f-04c3-4958-a5ed-0691cfab2e6d" alt="" width="375"><figcaption></figcaption></figure></div>

\
This helps ensure payments are made correctly, improves transparency, and avoids using personal accounts to pay third parties.


---

# 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/pay-suppliers-directly-with-vendors.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.