> 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/onboarding/nummernsysteme/order-numbers.md).
# Order numbers
#### Why order numbers
When you commission suppliers with the supplier orders of Die Agenturverwaltung, the system automatically assigns an order number.
The supplier is instructed in the order to include this order number on their invoice when billing.
The AI of Die Agenturverwaltung then recognizes this order number during entry and can the purchase invoice fully automatically
a) assign it to the job it belongs to and
b) to the estimate item from which the order originated
assign. Even the cost type - that is the information whether the invoice will later be billed to your customer as a flat fee or passed on 1:1 - is already defined when commissioning so that the supplier invoice will later be posted entirely automatically based on the order number.
The recommended system for order numbers is simple:
{% hint style="info" %}
**Example of an order number**\
PO-2023-0001
{% endhint %}
PO (for Purchase Order) is prefixed, followed by the current year and a running number within that year.
The PO prefix ensures that supplier orders can be distinguished from other documents such as invoices or estimates based on the number alone.
In this way, supplier order numbers sort themselves alphanumerically (e.g. in file systems) and can also be used as file names because they do not contain special characters such as hashes or slashes.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://wiki.dieagenturverwaltung.de/die-agenturverwaltung-en/onboarding/nummernsysteme/order-numbers.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.