> 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/fiscal-hosts/expense-payment.md).

# Expense Payment

This section includes information about paying expenses as a Fiscal Host on Open Collective

As a Fiscal Host admin, you can use Open Collective to track your expenses and expenses submitted to your hosted Collectives.

Once a Collective has approved an expense, you can use our platform to:

* Examine expenses and available funds
* View relevant agreements and receipts
* Request more information or clarification
* Process for payment

### Find out more

[**Pay an Expense**](https://documentation.opencollective.com/fiscal-hosts/expense-payment/paying-expenses-as-a-fiscal-host.md)

Learn more about how to process an expense as a Fiscal Host admin

[**Security Checks**](https://documentation.opencollective.com/fiscal-hosts/expense-payment/understanding-security-checks.md)

Read about our security checks for expenses

[**Request information about expenses**](https://documentation.opencollective.com/fiscal-hosts/expense-payment/asking-for-information-about-expenses.md)

Find out what to do if an expense requires more information

[**Payment Errors**](https://documentation.opencollective.com/fiscal-hosts/expense-payment/handling-payment-errors-through-wise.md)

Learn what to do if you encounter a payment error

\ <br>


---

# 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://documentation.opencollective.com/fiscal-hosts/expense-payment.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.
