> For the complete documentation index, see [llms.txt](https://docs.aquiladynamics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aquiladynamics.com/aquila-store-user-manual/products-and-product-records/vat-changes.md).
# VAT changes
## VAT changes
**Menu path:** `Administration -> Dictionaries -> Products`
The `VAT changes` tab shows the history of product VAT rate changes.
Use it when you need to check which VAT rate applies to the product and from when.
### Columns
| Column | Meaning |
| ----------------------- | -------------------------------- |
| `Beginning of validity` | Start date of the rate validity. |
| `Symbol` | VAT rate symbol. |
| `Value` | VAT rate value. |
### What to watch out for
* Changing VAT can affect sales, receipts, documents, reports and integrations.
* Before changing VAT, make sure you know the validity date and tax rules for the country.
* If VAT data is managed centrally or through integration, the change method should be confirmed with the administrator.
### Related pages
* [Source data](/aquila-store-user-manual/products-and-product-records/source-data.md)
* [Prices](/aquila-store-user-manual/products-and-product-records/prices.md)
---
# 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.aquiladynamics.com/aquila-store-user-manual/products-and-product-records/vat-changes.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.
