> For the complete documentation index, see [llms.txt](https://docs.payfacto.com/payfacto-knowledge/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.payfacto.com/payfacto-knowledge/maitred-pos/maitred/maitred-complete-online-documentation/chap-4-point-of-sale-control/help-contents/workstation/options/invoice.md).

# Invoice

The Invoice option from the Workstation menu allows to display messages on the guest check. There are 6 lines of 30 characters each for a guest check and an additional 5 lines of 30 characters each to get the customer information needed for room charge entry. You must type the authorization message separately for each workstation. This option gives you more flexibility since you can change the messages for the different locations of your workstation. For the room charge message, instead of typing the same text on every workstation, you can link every workstation room charge message to another one with the appropriate text.

**Authorization**

**Line 1 to Line 6**

Type in these fields the lines of the message. This message appears on every guest check, following the total of the check.

**Room charge**

**Line 1 To Line 5**

Type in these fields the lines of the message to print on the room charge guest check.

**Same As**

Instead of typing the same text on every workstation setup screen, use this field to link this workstation setup screen to another one that already has the appropriate


---

# 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.payfacto.com/payfacto-knowledge/maitred-pos/maitred/maitred-complete-online-documentation/chap-4-point-of-sale-control/help-contents/workstation/options/invoice.md?ask=<question>&goal=<user_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.