> 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/weitere-einstellungen.md).

# Payment terms & deadlines

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

The standard payment term for purchase invoices and invoices as well as credit invoices and the standard validity period of estimates can be defined under *Settings > Finance* defined:

<figure><img src="https://4063991107-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-La4YdZ1Gw5iHapqZfIo%2Fuploads%2Fk3mgebd83j3KgZRJcuRj%2FBildschirmfoto%202023-11-06%20um%2012.26.12.png?alt=media&amp;token=ab9a8488-4aac-4049-a3b6-18f7084c2236" alt=""><figcaption></figcaption></figure>

#### Customer account settings

For certain customer accounts, standard payment terms for invoices as well as the standard validity period of estimates can be changed, so that for new documents in jobs for this customer account, the corresponding default values are used.

The setting can be adjusted in the customer account under the tab *Settings > Deadlines* adjusted:

<figure><img src="https://4063991107-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-La4YdZ1Gw5iHapqZfIo%2Fuploads%2FvBGvgH2VWZz0hYkRlCVB%2FBildschirmfoto%202023-11-06%20um%2012.34.28.png?alt=media&amp;token=c55ed1ce-9aa2-4c20-ac1e-3d9496d1b850" alt=""><figcaption></figcaption></figure>

#### Settings for creditors and debtors

If nothing is stored for the creditor or debtor, the default value from the customer account is used for a new document. If nothing is defined there either, the company-wide default value.

The hierarchy is therefore: global payment term -> customer account -> debtor

If a customer has many customer accounts, all of which have their own payment terms and these now need to be changed, the payment term can simply be set on the debtor instead of editing all customer accounts individually. If, on the other hand, the global payment term or the payment term stored on the customer account is to apply, then the payment term on the debtor must be removed.&#x20;

Debtors can be edited via *Finance > Open items > Debtors* in the tab *Debtor contacts* and creditors via *Finance > Open items > Creditors* in the tab *Creditor contacts* can be edited. The field may be left blank, then the respective default value from the customer account or from the company is used.

<figure><img src="https://4063991107-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-La4YdZ1Gw5iHapqZfIo%2Fuploads%2FCSZXu1u4kpYsFSXa9Ep6%2FBildschirmfoto%202023-11-06%20um%2012.25.35.png?alt=media&amp;token=132005ba-f84d-4b09-a18e-0865af387f10" alt=""><figcaption></figcaption></figure>


---

# 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/weitere-einstellungen.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.
