> 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/einstellungen-1/process-definitions/process-configurator-for-invoices.md).

# Process configurator for invoices

Under Settings > Process Definitions you can find the process configurator for invoices. 

Here you can define which status steps an invoice goes through.

The following statuses are available:

#### In progress

The invoice is a draft and has not been sent yet. 

#### Awaiting internal approval (optional)

An invoice that, for example, was created by a junior and should be checked internally within the company before it is sent. 

#### Awaiting dispatch (optional)

The reviewed invoice has been set to this status by the team leader (or another reviewing person). The junior could send it now.

#### Sent

The invoice has been sent to the customer. 

#### Disputed

The customer has, for example, complained about the invoice. It can later be reissued or cancelled.

#### Booked

The invoice has already been handed over to accounting.

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

## Define permissions for the individual steps

In the configurator you can define who is allowed to move an invoice into a particular status step at all and who is allowed to change the status of an invoice that is in a particular status step.

Optional status steps can be deactivated. They will no longer be available in the future.


---

# 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/einstellungen-1/process-definitions/process-configurator-for-invoices.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.