> 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/invoicing/online-invoicing/online-invoicing-and-vouchers.md).
# Online Invoicing and Vouchers
If the venue has vouchers enabled, a fee is also applied to sale orders paid by vouchers.
Voucher fees are applied, and Voucher sales are deducted from the payout.
In the different sections of the invoice, Voucher has it's own split like the other payment methods. In Orders, Voucher also appears as the Tender.
{% file src="/files/VMNnrXtFYgHTdJA7n7LF" %}
{% hint style="info" %}
If an order contains multiple payments (e.g., voucher and card), we split the service charge proportionally based on the payment amount and its weight against the total value. This does not have any impact on the total service charge that we are charging for one transaction.
{% endhint %}
---
# 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/invoicing/online-invoicing/online-invoicing-and-vouchers.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.