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

# Invoices

![](https://4063991107-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-La4YdZ1Gw5iHapqZfIo%2F-M1tc_wzsi7RLieqypFw%2F-M1tdtWNVTcHPEX6lnJS%2FBildschirmfoto%202020-03-08%20um%2017.18.29.png?alt=media\&token=0fc3a5d7-bc5c-47f8-bd4e-ebeb6951d758)

## Filters in the invoice list

The list of 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.\
With the asterisk (\*) wildcard searches can also be performed in the example shown I can, for example, by entering the search term `12*2020`  Find all documents in which "12" is followed by "2020". For example, we would have a match here on the second document in the list.

### Search by responsible person

Using this filter a user can be selected and the list then shows only that user's documents. The filter also includes the entry "My 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 %}

## Invoice statuses

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

Invoices go through the following process steps:

#### in progress

This document is currently being created or edited; it is not included in any reporting. Documents in this status do not appear in any statistics.

#### awaiting dispatch

This document is completed but is still awaiting review by another user before it can be sent. Documents in this status do not appear in any statistics.

#### sent

This document has already been sent to the customer. In statistics the revenue of the document is now taken into account.

#### claimed

The customer has not accepted this document for formal or substantive reasons. In statistics it does not appear as revenue.

#### posted

This document has already been handed over to accounting.

{% hint style="info" %}
**Note:** Not all process steps may be activated in your company. Contact customer service if you want to change this: <info@dieagenturverwaltung.de>
{% endhint %}

In the list of 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-M1tc_wzsi7RLieqypFw%2F-M1te1QODJt-zcHdGWni%2FBildschirmfoto%202020-03-08%20um%2017.19.12.png?alt=media\&token=32e5cab5-da3b-4df7-8489-c18656c492b6)


---

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