> For the complete documentation index, see [llms.txt](https://docs.payrexx.com/platform/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.payrexx.com/platform/english/admin/settings/invoicing.md).

# Invoicing

This article explains how to configure settings for the invoicing and dunning process.

To access the settings, navigate in the platform administration to **Settings > Invoicing**.

Using the following settings, you can define the deadlines for invoices and reminders sent to the connected merchants:

<div align="left"><figure><img src="https://13947520-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McKWr2N1ZENCggMlAH5%2Fuploads%2Fp6nvivXufftVXnrog1LY%2Fimage.png?alt=media&amp;token=c1668a4d-10d6-427b-a3d9-51fca3bb90f9" alt=""><figcaption><p>Setting up invoicing and dunning process parameters for connected merchants</p></figcaption></figure></div>

1. **Payment term in days:** This number of days is set as the payment term on invoices. It defines how long the merchant has to settle their invoice.
2. **First to fifth reminder emails for unpaid invoices:** If the merchant does not pay within the payment term, up to five reminder emails are sent. In the example above, the first email is sent 15 days after the payment term expires, the second after 35 days, the third after 60 days, and so on.
3. **Blocking:** When enabled, the blocking process is carried out automatically.
4. **Days until blocking:** After this number of days, the merchant account is suspended, and the merchant can no longer receive live payments.
5. **Days until deactivation:** After this number of days, the merchant account is deactivated, and the merchant can no longer log in.

Finally, click the green button at the bottom right to save your settings.


---

# 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.payrexx.com/platform/english/admin/settings/invoicing.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.
