> For the complete documentation index, see [llms.txt](https://wiki.dieagenturverwaltung.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.dieagenturverwaltung.de/die-agenturverwaltung-en/finanzen-1/kva/die-positionsliste.md).

# VAT in the estimate

In the item list of a financial document (e.g. an estimate) the items or services of the order are listed. 

You can find more information about the item list in financial documents on the following page in our wiki:

{% content-ref url="/pages/46132c2c2db8252f8bf48abe1c714641ca37e1ee" %}
[The item list](/die-agenturverwaltung-en/finanzen-1/allgemeines-zu-finanzdokumenten/die-positionsliste-1.md)
{% endcontent-ref %}

### No sales tax in estimates

The estimate differs from other documents such as invoices or credit invoices in that there is no field for sales tax below the net total.

That means the services are offered net, a reference in the footnote below the item list explains that the offer is understood plus statutory sales tax.

{% hint style="info" %}
This reference is a legal part of the estimate and must not be missing.
{% endhint %}

The reference is usually inserted automatically when creating the document if it has been created as the default template for estimates.


---

# 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://wiki.dieagenturverwaltung.de/die-agenturverwaltung-en/finanzen-1/kva/die-positionsliste.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.