> 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-purchase-invoices.md). # Process configurator for purchase invoices Under Settings > Process definitions, you will find the process configurator for purchase invoices. Here you can define which status steps a purchase invoice goes through. The following statuses are available: #### Waiting for entry A document has, for example, already been uploaded as an attachment, but has not yet been further recorded. #### Waiting for job assignment This document has been recorded 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 by followup. #### Waiting for payment approval (optional) This document is waiting for a person authorized to approve payments to release the document for payment. #### Waiting for posting (optional) The assignment of the document to one or more jobs has been completed. Depending on the configuration, payment approval may also have been granted. The document can now, if applicable, be paid and transferred to a third-party accounting system, e.g. DATEV. #### Posted This document has been handed over to accounting. #### Disputed (optional) If a disputed document is not deleted immediately, this status can be used to document that this document was disputed. For purchase invoices, an automatic status change can also be defined. In the dropdown, you select to which status a purchase invoice automatically jumps when it has been posted 100% to one or more jobs. ## Define permissions for the individual steps In the configurator, you can define who is allowed to move a purchase invoice into a specific status step at all and who is allowed to change the status of a purchase invoice that is in a certain status step at all: ![](https://4063991107-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-La4YdZ1Gw5iHapqZfIo%2Fuploads%2F8xzlaM5SOcjq9jQdVvCk%2Fprozess-konfiguration.png?alt=media\&token=faaa5337-5417-4d12-ad63-07b7fbba8a99) Optional status steps (here: waiting for posting) can be disabled. They will then no longer be available in the future. ### Application examples for configuring permissions Documents with the status "posted" have been handed over to the tax advisor; the status should only be allowed to change if a specific person from accounting permits this. After the job assignment, the status changes to "payment approval". In this step, only 3 people may change the status; that is, once the status has been reached, one of these 3 people must approve the payment by moving the invoice to the next step - e.g. "waiting for posting". ### Configure payment approval If this status is active and a group of people is specified in the field "Who is allowed to change this status?", then when recording the supplier document, it can be selected which person from this group should approve the invoice for payment after the job assignment. This person then receives a [followup](/die-agenturverwaltung-en/wiedervorlagen-1.md)as soon as the invoice status changes to "waiting for payment approval". ![](https://4063991107-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-La4YdZ1Gw5iHapqZfIo%2Fuploads%2FnLat9QXvqHJkVYJBbQ5E%2FBildschirmfoto%202021-10-24%20um%2015.18.18.png?alt=media\&token=40fb15da-eb79-41ba-aa7f-e517058dbf1c) --- # 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-purchase-invoices.md?ask=&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.