> 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/eingangsrechnungen/paginiernummern.md).

# Pagination numbers

Pagination numbers are automatically assigned by the system for each new purchase invoice - for most of our clients it is a year and a consecutive number e.g. `2021-0342`

Pagination numbers are nowadays really only used when working with original paper documents. The pagination number can then be noted on the paper document. It thus indicates that the document has been recorded in the system. Further information, e.g. who recorded the document, whether it was assigned to a job or has already been paid, can then be obtained from the system.

{% hint style="info" %}
If your company requires a different pattern for creating pagination numbers, please contact our customer service: [info@dieagenturverwaltung.de](mailto:info@dieagenturverwaltung.de?subject=Alternatives%20Paginiernummern-Muster)
{% 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/eingangsrechnungen/paginiernummern.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.
