> 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/understanding-security-checks.md).
# Understanding Security Checks
When an expense is submitted to Open Collective, we carry out automated checks to identify potential concerns.
We want to make sure that Fiscal Hosts are confident an expense is accurate and complete before approving it.
This is why we carry out some automated Security Checks for factors you may want to keep in mind during the approval process.
You can find the results of these checks by clicking the shield icon on the bottom right of any expense.
Example of security check details pop up.
{% hint style="warning" %}
Our Security Checks are based on checks that experienced Fiscal Hosts commonly make as part of their due diligence process. They are designed as a guideline only, and should only be used to inform your own personal verification process. We do not provide conclusive advice on whether to accept or reject individual expenses.
{% endhint %}
### How do our security checks work?
Our Security Checks are designed to spot errors, missing information, and details that Fiscal Host admins may want to be aware of.
These categories have been selected following discussions with Fiscal Hosts, and many have been created based on the activity we have seen before on the platform.
When you click on the shield icon for the expense, it will display only the checks that are relevant to that expense, in one of four colors:
**Blue:** This detail is for information only
**Green:** This detail highlights information about the expense which may be a sign it is trustworthy (ie. The submitter is a Collective admin, or has already been paid in the past by this Collective)
**Yellow:** This indicates a warning, or a message that the admin should be aware of when deciding to pay
**Red:** This indicates an alert, or information the admin should resolve or address before deciding whether to pay
{% hint style="info" %}
Red indicators are warnings, not blocks. Fiscal Host admins can still proceed with processing payments even if a red security check is applied to an expense.
{% endhint %}
---
# 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/understanding-security-checks.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.
