> 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/delivery-notes.md).

# Delivery notes

To include a delivery note with a physical shipment, a delivery date can be specified in an invoice.

In the Options tab the delivery note can then be downloaded as a PDF print version.

It contains the same contents as the invoice however

* the title reads "Lieferschein" or "Delivery Slip"
* no header and footer note is specified
* currency indications are removed
* only title, description, quantity and unit of line items are visible
* no currency totals are specified
* the invoice number corresponds to the delivery note number
* the delivery date is stated as "Date of delivery (arriving)"

{% embed url="<https://youtu.be/MprY3sjhPi8>" %}

#### Sending the delivery note by e-mail

If it is necessary for you to send a delivery note by e-mail, you can do so by composing a new e-mail on the invoice and selecting the delivery note PDF as an attachment.

This can make sense, for example, if your logistics provider then prints this delivery note at the fulfillment location and includes it with the shipment.


---

# 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/delivery-notes.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.
