> 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/projektverwaltung-1/finanzen-in-der-projektverwaltung.md).

# Finance in job management

On the three hierarchy levels of project management (Kunde, customer account and job) you can, in the "Finanzen" tab, **view all relevant financial documents** and the associated **payments** .

The view is structured into the three sections estimate, invoice and credit invoice. In each section the financial documents are displayed row by row with the relevant information. \
By clicking on a row you can jump to the respective financial document.

For an **estimate** the following information is displayed:

* Status: indicator shows whether and which portion of the estimate budget has already been billed
* Date
* Subject
* Number
* job
* Address
* Amount: net amount of the estimate

For a **invoice** the following information is displayed:

* Status: indicator with three states:
  * in progress
  * sent/overdue
  * paid 
* Invoice date: incl. display of invoice type (progress invoice, final invoice)
* Subject
* Invoice number
* job
* Billing address
* net
* gross

For a **Credit invoice** the following information is displayed:

* Invoice date
* Subject
* Invoice number
* job
* Billing address
* Status 
  * in progress
  * sent
* Payment
  * open
  * paid
  * cancelled
* net
* gross


---

# 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/projektverwaltung-1/finanzen-in-der-projektverwaltung.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.