> 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/expense-policy.md).
# Expense Policy
{% hint style="danger" %}
With the implementation of the new [Dashboard interface](https://docs.opencollective.com/help/product/understanding-your-dashboard), we are currently in the process of updating our documentation and some pages may be out of date. Thank you for your patience. Please [contact](https://opencollective.com/contact) our support team if you need any assistance.
{% endhint %}
You can specify an expense policy, which appears on the right of the submit expense form, to give guidance to expense submitters. Making it clear what expenses will be approved and what submitters need to do will save time for you and them.
To update your expense policy, go to your Collective's page, click on the settings button and go to the **Policies** page.
## Examples
### Webpack
> We distribute the money according to the contributions on Github. There is a minimum threshold. You'll receive a mail when you made enough contributions last month.
### Babel
> Feel free to expense a public transport for a conference/meetup as a community member, or for things like stickers. For core members, transport/stay for things like TC39 meetings. For other expenses you can ask. Otherwise, we plan on spending most of the money trying to pay people full time.
## Limit Who Can Submit and Approve Expenses
At the bottom of the Policies Settings screen, you'll see a set of options that allow you to limit who can submit and approve expenses to your collective:
* Ticking *"Admins cannot approve their own expenses"* will block admins from approving expenses submitted by themselves, effectively requiring another admin to approve their expenses.
* Ticking "Only allow expenses to be created by Team Members and Financial Contributors (they may invite expenses from other payees)." will limit who can see the "Submit Expense" button.
## Fiscal Host Expense Policy
Your Fiscal Host can also set an [expense policy](/help/fiscal-hosts/fiscal-host-settings.md#expenses). It will appear on the submit expense page, underneath the Collective policy.
Often times, Collective expense policies are focused on what categories of things are allowed as expenses, while the Fiscal Host policy pertains to required documentation, like details on invoices.
---
# 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/expense-policy.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.
