> 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/ausgangsrechnungen/attach-supplier-receipts-to-invoices.md).

# Attach supplier receipts to invoices

If external services of the cost type "billable by effort" are billed in your invoice, and there is also an original document for them - e.g. the PDF of the supplier invoice - these documents can also be attached to the PDF of the invoice in the Print Version Settings tab.

<figure><img src="https://4063991107-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-La4YdZ1Gw5iHapqZfIo%2Fuploads%2Fwx5qAmbOrXdhVhnNx6wL%2FBildschirmfoto%202024-11-10%20um%2014.10.28.png?alt=media&amp;token=6adb00bd-d5c1-4105-8683-a1bb3a825722" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
**Note**

Of course, the file size of your invoice grows accordingly with the documents. If you are interested in fast performance in the invoice preview during editing, attach the documents only at the very end, just before sending.
{% endhint %}

#### Troubleshooting

In some cases, PDF files cannot be attached to the invoice; these files are then simply skipped, and the checkmark in the Print Version Settings changes accordingly.

It can help to download such documents, open them with a PDF viewer, and then print them again as PDF and upload them once more to the purchase invoice.


---

# 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/ausgangsrechnungen/attach-supplier-receipts-to-invoices.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.