> For the complete documentation index, see [llms.txt](https://docs.goldenedi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.goldenedi.com/business-central/configuration/invoicing/vat.md).

# VAT

Converting internal VAT representations to standard formats.

Now we will create an conversion document to convert your internal representation of VAT to something more standard and understandable. The possible values you can convert to are listed in the table below.

| Code               | Percentage |
| ------------------ | ---------- |
| ExcludedFromVat    | 0%         |
| Food               | 12%        |
| RestaurantServices | 12%        |
| Standard           | 25%        |
| PapersBooksEtc     | 6%         |
| ZeroTax            | 0%         |

{% hint style="info" %}
You can find your internal codes for VAT types on the **Moms Produktbokföringsmallar** page. 
{% endhint %}

Create a new conversion document called **VAT-STD**, enable it and start filling in the conversion between your internal VAT and the standard ones.

![](https://785456668-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LVO7c8MSQ0ieazusCSE%2F-LXstNHeI9YRKzBfdmFI%2F-LXt6rVGrZ6M6DtsgbTT%2FScreenshot%202019-01-04%20at%2015.17.26.png?alt=media\&token=17570d54-d528-4e1f-8391-f04b4097b2bf)

As before you can give it a nice description so that you know what it does in case you need to go back in the future to add or remove a conversion. When you are done press back to go back to the list over your conversion documents.

{% hint style="success" %}
We can now convert your internal VAT representations to standardized versions.
{% 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.goldenedi.com/business-central/configuration/invoicing/vat.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.