> For the complete documentation index, see [llms.txt](https://docs.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verifone.com/support-denmark/v660p/vejledninger/sadan-genudskriver-du-en-kvittering.md).

# Sådan genudskriver du en kvittering

Genudskriv en forhandler- eller kundekvittering på din V660P fra ordrehistorikken.

{% hint style="info" %}
**Brug dette, når** du har brug for en kopi af en kvittering.
{% endhint %}

{% stepper %}
{% step %}

### Åbn ordrehistorikken

Tryk på **menuikon (☰)** i øverste venstre hjørne af **Connect Express** skærmen, og tryk derefter på **Ordrehistorik**.
{% endstep %}

{% step %}

### Find transaktionen

Tryk på den transaktion, du vil have en kvittering for.

{% hint style="info" %}
For hurtigt at finde en transaktion skal du trykke på **søgeikonet** i øverste højre hjørne og indtast **de sidste 4 cifre af kortet**, eller 5 eller flere cifre af transaktions-id'et.
{% endhint %}
{% endstep %}

{% step %}

### Udskriv kvitteringen

Tryk på **Kvittering**, og vælg derefter **Forhandlerkopi** eller **Kundekopi**.
{% endstep %}
{% endstepper %}

<details>

<summary>Nøgleord</summary>

Også kaldet: genudskriv kvittering, kvitteringskopi, duplikatkvittering, kundekopi, forhandlerkopi. Søgetermer: genudskriv, kvittering, kopi, ordrehistorik, forhandlerkopi, kundekopi, søg.

</details>


---

# 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.verifone.com/support-denmark/v660p/vejledninger/sadan-genudskriver-du-en-kvittering.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.