> For the complete documentation index, see [llms.txt](https://docs.solutioo.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.solutioo.de/vr-payment-gateway/zahlungen/zahlungslink-per-e-mail.md).

# Zahlungslink per E-Mail

HTML-Zahlungsmail mit Button, PDF-Anhang und optionaler Ablauf-Erinnerung.

Auf gebuchter Rechnung, Auftrag und Angebot finden Sie **Zahlungslink per E-Mail senden**.

#### Voraussetzungen

* Aktiver Payment Link zum Beleg
* E-Mail-Adresse am Debitor (bzw. am Beleg)
* Druckregel erlaubt den Beleg
* In Business Central ist ein **E-Mail-Konto** eingerichtet

#### Inhalt der Mail

* Betreff z. B. `Rechnung 103217 – Online bezahlen`
* Belegtyp, Nummer, Kunde, Fälligkeit, Betrag
* Großer Button **Jetzt sicher bezahlen**
* Sicherheitshinweis (SSL über VR Payment)
* Fallback-Link im Footer
* PDF der Rechnung als Anhang (bei Rechnungen)

#### Ablauf-Erinnerung

Wenn **Ablauf-Erinnerung per E-Mail** aktiv ist, sendet die Job Queue automatisch eine Erinnerung. Standard: **3 Tage** vor Gültig-bis. Betreff z. B. `Erinnerung: Zahlungslink zu 103217 läuft bald ab`.

{% hint style="warning" %}
Schlägt der Versand fehl, prüfen Sie **E-Mail-Konten** und den **E-Mail-Postausgang** in Business Central.
{% endhint %}


---

# 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.solutioo.de/vr-payment-gateway/zahlungen/zahlungslink-per-e-mail.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.