> 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/vr-payment-gateway_en_us/payments/collective-payment-link.md).

# Collective payment link

On the customer card and customer list: **Create VR Payment collective link**.

The app collects the customer's open sales invoices. Direct debit is excluded. All invoices must use the same currency.

{% stepper %}
{% step %}

#### Open the customer

Open the card or select the customer in the list.
{% endstep %}

{% step %}

#### Create the collective link

Confirm the count and total amount. The link source type is **Collective link**.
{% endstep %}

{% step %}

#### Share the link

The customer pays the total once. After payment, the G/L distributes the receipt via **Applies-to ID** across the stored invoices.
{% endstep %}
{% endstepper %}

{% hint style="warning" %}
Different currencies on the open invoices are not allowed. Harmonise the currency first or create separate links.
{% 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.solutioo.de/vr-payment-gateway/vr-payment-gateway_en_us/payments/collective-payment-link.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.