> For the complete documentation index, see [llms.txt](https://docs.bossithq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bossithq.com/logistics/cashout-history.md).
# Cashout History
The Cashout history shows the record of all cashouts made. Each cashout transaction provides:
* date and time
* driver name
* amount collected or given
Once you click a cashout entry, it would show the following information:
* Driver
* Driver id: this is a unique alphanumeric character for each driver
* Total order: Total order driver Collected
* **Cashout total:**
* “**Give to driver**” means the venue needs to give the amount to the driver.
* “**Get from Driver**” means the venue needs to collect money from the driver.
## Accessing Cashout History
To view cashout history in the [**Admin Portal**](https://admin.gobossit.com/), go to the venue level and navigate to **Logistics > Cashout history**.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.bossithq.com/logistics/cashout-history.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.
