> 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/troubleshooting-and-support/faq.md).

# Frequently asked questions

<details>

<summary><strong>The QR code does not appear on the invoice</strong></summary>

Check in this order:

* Is the integration **Enabled**?
* What does the FactBox on the document say – which print rule applies?
* Is **Respect payment terms** on, and do the terms have the QR flag? Use **Prepare payment terms**.
* Is there an **active** payment link?
* Is invoice print mode not **None**?
* Are you printing the VR Payment report or a report that uses the extension?

</details>

<details>

<summary><strong>Connection test fails (401)</strong></summary>

* Space ID, User ID, and API key must belong to the same application user.
* In sandbox mode the **Test Space ID** must be set.
* The JWT timestamp uses UTC. Is the BC server date/time correct?
* Use **Test connection (debug)** and read the message.

</details>

<details>

<summary><strong>Payment status stays Active</strong></summary>

* Was the payment actually completed at VR Payment?
* Is the job queue **Ready** and the integration enabled?
* Run **Update payment status** on the document or **Synchronize** on setup.
* Check the **API log** for errors.

</details>

<details>

<summary><strong>Transaction without a document number</strong></summary>

Matching uses merchant reference and amount. The next sync backfills unmatched transactions. Check that amount and currency match the document.

</details>

<details>

<summary><strong>Cash receipt is not posted</strong></summary>

* Balancing account type and number must be set.
* If **Post automatically** is off, only a journal line is created.
* For a collective link the invoices must still be open – otherwise only the transaction is imported.

</details>

<details>

<summary><strong>Direct-debit customers still get a QR code</strong></summary>

**Respect payment terms** must be on. Direct debit must not have the QR flag. **Prepare payment terms** applies that.

</details>

<details>

<summary><strong>Do I still need the Azure webhook portal?</strong></summary>

No. Status comes from the job queue. Remove a leftover listener on setup with **Remove old Azure webhook**.

</details>

### Your question is not listed?


---

# 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/troubleshooting-and-support/faq.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.