> 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.md).

# Purchase invoices

Purchase invoices are invoice documents and receipts from the suppliers of our company. They are often job-related and arrive digitally or on paper.

![](https://4063991107-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-La4YdZ1Gw5iHapqZfIo%2F-M1tXpFM-kyTak6Z5tjk%2F-M1t_0t_CNS_fLCXuBD9%2FBildschirmfoto%202020-03-08%20um%2016.56.42.png?alt=media\&token=75a80a2b-a601-47ed-8066-3b51d1eeea95)

## Filter in the purchase invoice list

The list of purchase invoices can be narrowed using filters above the list.

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

### Search with wildcards \*

The search allows searching by document number, job number, supplier or subject of the document.\
Using the asterisk (\*) wildcard searches can also be performed; in the illustrated example I can, for instance, by entering the search term `12*2020`  Find all documents in which "12" is followed by "2020". For example, we would have a search hit on the second document in the list here.

### Search by responsible person

Through this filter a user can be selected and the list then shows only that user's documents. The filter also includes the entry "My purchase invoices".

### **Search by status**

This filter restricts the list to documents that are in a certain status.

{% hint style="info" %}
Filter settings are saved until the next login to the system.
{% endhint %}

## Status of purchase invoices

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

Purchase invoices progress from capturing the document to handing it over to accounting through the following process steps:

#### waiting for capture

A document has, for example, already been uploaded as an attachment but has not yet been further captured.

#### waiting for job assignment

This document has been captured and is waiting for a project manager to post it as an external service to one or more jobs.\
Under certain circumstances the project manager may already have been notified via followup.

#### waiting for payment approval (optional)

This document is waiting for a person authorized to approve payments to approve the document for payment.

#### waiting for booking (optional)

The assignment of the document to one or more jobs has been completed. Depending on configuration, payment approval may also have been granted. The document can now, if applicable, be paid and handed over to a third-party accounting system, e.g. DATEV.

#### booked

This document has been handed over to accounting.

{% hint style="info" %}
**Maybe not all process steps are enabled in your company?**

As an administrator you can activate the optional steps under Settings > Process Definitions > Process Configurator for purchase invoices.

[Learn more](https://wiki.dieagenturverwaltung.de/die-agenturverwaltung-en/einstellungen-1/process-definitions/process-configurator-for-purchase-invoices.md)
{% endhint %}

In the list of purchase invoices you can see at a glance which status a document is in:

![](https://4063991107-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-La4YdZ1Gw5iHapqZfIo%2F-M1tXpFM-kyTak6Z5tjk%2F-M1t_62jSiQb-MzAMAHG%2FBildschirmfoto%202020-03-08%20um%2016.56.58.png?alt=media\&token=3784a342-0783-495b-9157-f082dcb71817)


---

# 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.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.
