> For the complete documentation index, see [llms.txt](https://docs.dataloy.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dataloy.com/release-7.8/voyage-management-system/step-by-step-guides/voyages/maintain-voyages/various-cost-revenue.md). # Various Cost/Revenue From the "Various Cost/Revenue" tab in the voyage drawer, you can view various cost/revenue from the voyage, cargoes on the voyage and Offhires on the voyage. #### Search and Filter Variouses * If there are either existing various cost/revenue on the Voyage's Cargoes or Offhires there will appear a filter on the top-right of the list where you can select which other types of various cost/revenue you want to be displayed in the list. * Variouses can also be filtered by the Currency filter on the top-right of the list . * The Searchbar can be used to search for Variouses in the list containing the entered search-text in the Description or/and Various Text. --- # 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.dataloy.com/release-7.8/voyage-management-system/step-by-step-guides/voyages/maintain-voyages/various-cost-revenue.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.