> For the complete documentation index, see [llms.txt](https://docs.solutioo.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.solutioo.de/differenzbesteuerung/differenzbesteuerung_en_us/maintenance/uninstall.md).

# Uninstallation and data retention

1. Resolve open documents, settlements, returns and later corrections before uninstalling. Preserve setup, fiscal evidence and related standard entries under your retention and backup process.
2. Check dependent extensions, customer-specific report selection and layouts. Their fields, reports and protection checks may be unavailable without the app.
3. If reinstallation is intended, use standard Extension Management and initially retain extension data. Deleting extension data is a separate irreversible decision, not an ordinary maintenance uninstall.
4. Before reinstalling, check the same app identity, compatible schema and supported upgrade path. Compare evidence and standard entries afterwards.

Uninstallation does not reverse existing general ledger, VAT or item entries. CSV/Excel alone do not back up the full app schema. For questions about reinstallation, [contact solutioo](/differenzbesteuerung/differenzbesteuerung_en_us/help/support.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.solutioo.de/differenzbesteuerung/differenzbesteuerung_en_us/maintenance/uninstall.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.