> 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/custom-fields-custom-fields.md).

# Custom fields (Custom Fields)

For financial documents as well as customer, customer account and job, the support team at Die Agenturverwaltung can define custom fields for you.\
Please contact us at <info@dieagenturverwaltung.de>\
\
Custom fields can be defined on these data objects:

* customer
* customer account
* job
* estimate
* invoice
* credit invoice
* purchase invoice
* supplier order
* template

The fields can have the following types:

* Text fields (single-line)
* Check boxes (Yes/No)
* URLs (as link)
* Email addresses (as link)
* Select field (with predefined selection options)

### **Custom fields in the print version**

Some field types can be configured so that their values are output in the print version of a financial document.

{% hint style="info" %}
**Example 1**\
If a field is defined on the estimate, it can be configured so that it is included in the print version of the estimate\
\
**Example 2**\
If a field is defined on the customer or job, it can be configured so that it is included in the print version of a financial document for this customer or job.\
This makes sense, for example, for a customer-specific supplier number if it is defined on the customer.
{% endhint %}

### Special features for the E- and X-invoice

There are a number of field types that we can activate for you, which then also have corresponding representations in the E- and X-invoice. \
\
These are the following fields:

* **PO number** / order number - it is provided to you by the customer
* **routing ID** for PEPPOL deliveries - it is provided to you by the customer
* **cost center**  - it is provided to you by the customer

Other custom fields are transferred in the XML of an E- or X-invoice unstructured as informational text - like the data in the tabular additional fields of an invoice or credit invoice.

### **Searchability**

Some field contents can be configured so that they can be found in the *full-text search* of the respective lists (e.g. list of invoices).

### Limitations

Custom fields are explicitly not available as possible filters in reports, dashboard elements, etc.


---

# 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/custom-fields-custom-fields.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.
