> For the complete documentation index, see [llms.txt](https://docs.codegiganten.de/plugin-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.codegiganten.de/plugin-documentation/en/apps/affiliate-marketing/configuration/automatic-payouts.md).

# Automatic payouts

The automatic payout generation feature, which can be set up via scheduled tasks, is very practical. For example, a payout transaction can be created at the beginning of each month for every affiliate who has exceeded the payout limit.

You can also generate a SEPA XML file that can be used to import all outstanding payouts directly into your bank.

Using the command `bin/console cogi-affiliate:create-payouts`, any affiliate credit that is payable can be automatically converted into a payout. We recommend setting up a cron job.

#### Send SEPA payout document with all open payouts by email

This allows an email with a SEPA XML payment document to be sent to the configured email address when the above command is executed. It is essential that the file is checked manually again before sending the payments. Despite taking the utmost care during development, we cannot guarantee that it is complete and correct.

#### E-mail address for receiving the SEPA payment document

Here you can define the email address to which the SEPA payment receipts are sent. If no email address is set, the email will be sent to the shop operator.

#### Intended purpose of the transfers

This configuration defines the intended purpose specified for the transfers.

#### Name of the sender

Defines the name of the sender specified for the transfer.

#### IBAN of the sender

Specifies the IBAN to be used for the transfer.

#### BIC of the sender

The BIC, which is specified in the transfers, is stored here.


---

# 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://docs.codegiganten.de/plugin-documentation/en/apps/affiliate-marketing/configuration/automatic-payouts.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.