> 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/allgemeines-zu-finanzdokumenten/ausgangsrechnung-in-ein-anderes-dokument-kopieren.md).

# Copy document or convert it to another document

In estimates, invoices, credit invoices and templates there is in the "Options" tab the possibility to copy the entire document:

![](https://4063991107-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-La4YdZ1Gw5iHapqZfIo%2F-M1o972gk8n6ToxPok9S%2F-M1oAD13SOHqt4mv7t7S%2FBildschirmfoto%202020-03-07%20um%2015.46.30.png?alt=media\&token=6d7e8256-f171-4f07-bd2a-9b3605d47ad9)

The selected target format decides what kind of document is created (e.g. estimate or template).

Job and date can be defined before creating the document, since the document number (e.g. the invoice number) may result from this depending on your company's configuration.

{% embed url="<https://www.youtube.com/watch?v=pVmCgD1S0Ac>" %}

## Automatic adjustment of prices when copying into jobs with different price lists

Changing the job for the newly created document can result in the prices in the target job being different from the job in which our document currently resides.

{% hint style="info" %}
**An example**

Our estimate for customer A calculated 12 h of graphic design at 90 EUR. We now copy this estimate into a job of customer B. However, with customer B only 75 EUR for a graphic design hour have been agreed. \
\
In this case we leave the checkbox "Adjust prices ...." under the copy dialog checked and the prices of our document will be automatically adjusted to the price list of the target customer account when copying.
{% 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://wiki.dieagenturverwaltung.de/die-agenturverwaltung-en/finanzen-1/allgemeines-zu-finanzdokumenten/ausgangsrechnung-in-ein-anderes-dokument-kopieren.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.