> 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/configuration/dashboard.md).

# Dashboard and navigation

The **VR Payment Dashboard** is a card part on the **Business Manager** and **Accountant** role centers.

#### Tile groups

**Payments**

* Active payment links
* Paid links
* Expired links

**Matching**

* Paid externally
* Open cash receipt
* Overdue links

**Finance & refunds**

* Open refunds
* Unmatched payouts
* Stored payment methods

A click on a tile opens the filtered list.

#### VR Payment navigation

In the **VR Payment** menu:

* Setup
* Transactions
* Payment links
* Refunds
* Payouts / bank matching
* Payment tokens
* **Synchronize everything with VR Payment**

{% hint style="info" %}
The **VR payment status** column on lists (order, quote, posted invoice) is controlled by **Show payment status in lists**. Colours: green = paid, yellow = waiting, red = expired/cancelled.
{% 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/configuration/dashboard.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.