> 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/proforma-invoice.md).
# Proforma Invoice
A proforma invoice is a preliminary document issued to a buyer before the final sale, outlining the estimated cost of goods or services. It is not a demand for payment but provides details such as pricing, quantities, and terms for reference.
#### To create a proforma invoice
1. Go to Front Office>> Cashier>> Proforma Invoice
2. Click on the Plus button .png?alt=media)on the toolbar.
3. Clicking the plus button makes the screen active.
4. From the Guest field, select the guest to be billed.
5. Upon selecting the guest, the system automatically populates all outstanding bills that are to be settled.
6. Click on the save button to create the proforma invoice.
#### Viewing a proforma Invoice
1. Click on the File Open icon .png?alt=media).
2. Click on the proforma number field.
3. Upon clicking the proforma field, the system lists out all the proforma invoices created.
4. Select the previously saved record from the list to view.
5. The recreate button .png?alt=media)helps the user recreate the invoice.
6. The refresh button .png?alt=media)helps refresh the screen.
7. The Print button .png?alt=media)helps print, and the Excel button .png?alt=media)helps export the file to Excel.
---
# 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/proforma-invoice.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)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)