> For the complete documentation index, see [llms.txt](https://help.rbsgo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rbsgo.com/front-office-module/fo-cashier/misc-payments-collections/miscellaneous-collections.md).
# Miscellaneous collections
Miscellaneous collections refer to revenue received from guests on the sale of miscellaneous items or services provided.
* Go to **Front Office>> Cashier>> Miscellaneous payment/collections**.
* Select Miscellaneous Collections from the Type field.
* Enter the voucher number if available.
* Select the revenue account to which the revenue will be charged from the Revenue Account drop-down.
* Enter the amount.
* Use the narration field to provide a detailed explanation of the transaction, especially when the receipt is not part of the regular transaction records
* Select the payment mode.
* Save .png?alt=media)the transaction.
These revenues find their way to the night audit list.
The toolbar has options to modify(Open​ .png?alt=media)), and view .png?alt=media)(to delete), but this access is usually given only to( to delete). Still, usually this access is given only to the administrators.
---
# 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://help.rbsgo.com/front-office-module/fo-cashier/misc-payments-collections/miscellaneous-collections.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.
.png?alt=media)
.png?alt=media)