> 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/finanzen-1/gutschriften.md).

# Credit invoices

![](https://4063991107-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-La4YdZ1Gw5iHapqZfIo%2F-M1tkhQcXOZe9b6hcb_d%2F-M1tmEDNAyUPi2F0FJCn%2FBildschirmfoto%202020-03-08%20um%2017.53.18.png?alt=media\&token=3e07613a-dce2-48bc-ac75-35097d7e518c)

## Filters in the list of credit invoices

The list of credit invoices can be narrowed using filters above the list.

### Search with wildcards \*

The search allows searching by document number, job number, customer/supplier or subject of the document.\
With the asterisk (\*) wildcard searches can also be performed; in the illustrated example, for instance, by entering the search term `AD*19`  Finds all documents in which "AD" is followed by "19". For example, we would have a match on the second document in the list.

### Search by responsible person

This filter allows a user to be selected and the list will then show only that user's documents. The filter also includes the entry "My invoices".

### **Search by status**

This filter restricts the list to documents that are in a certain status.

{% hint style="info" %}
Filter settings are saved until the next login to the system.
{% endhint %}

## Status of credit invoices

Credit invoices go through the following process steps:

#### in progress

This document is currently being created or edited; it is not included in any reports. Documents in this status do not appear in any statistics.

#### awaiting dispatch

This document is completed but is still awaiting review by another user before it can be sent. Documents in this status do not appear in any statistics.

#### sent

This document has already been sent to the customer. In statistics the *negative* revenue of the document is now taken into account.

#### complained

The customer has not accepted this document for formal or content-related reasons. In statistics it does not appear as *negative* revenue.

#### posted

This document has already been handed over to the accounting department.

{% hint style="info" %}
**Note:** Not all process steps may be activated in your company. Contact customer service if you want to change this: <info@dieagenturverwaltung.de>
{% endhint %}

## Usage examples for credit invoices

#### Payment of freelancers

Some of your freelancers or suppliers may have difficulty creating a formally correct invoice document. You can also pay these suppliers via a credit invoice.\
Coordinate with the worker regarding VAT liability.\
In case of doubt, the credit invoice should not include VAT if the supplier is considered a [small business owner](https://de.wikipedia.org/wiki/Kleinunternehmerregelung_\(Deutschland\)) .

#### Refund of already billed partial services

If a customer complains about a service already billed to them, it can be refunded or offset using a credit invoice.

An invoice is copied into a credit invoice in the process. Subsequently, all items that should not be credited are deleted from the credit invoice's item list.

{% hint style="info" %}
**Note:** Deductions are also copied into the credit invoice here and must be removed if necessary.
{% endhint %}

Here is how an invoice can be copied into a credit invoice:

{% content-ref url="/pages/d0f767cc34f216774abb42d46bf1fe57acb1f5e1" %}
[Copy document or convert it to another document](https://wiki.dieagenturverwaltung.de/die-agenturverwaltung-en/finanzen-1/allgemeines-zu-finanzdokumenten/ausgangsrechnung-in-ein-anderes-dokument-kopieren.md)
{% endcontent-ref %}


---

# 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/finanzen-1/gutschriften.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.
