> 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/tcs-client-engage/transaktioner-og-afregning/sadan-ser-du-transaktionsdetaljer.md).

# Sådan ser du transaktionsdetaljer

Sådan går du fra en dag i Clearing Status til de enkelte transaktioner i TCS (Engage).

{% hint style="info" %}
Brug denne vejledning, når du vil se de enkelte transaktioner for en dag, en gruppe eller en terminal.
{% endhint %}

## Se transaktionsdetaljer trin for trin

{% stepper %}
{% step %}

### Åbn dagen

Klik på den ønskede dato med **blå tekst** i kolonnen **Date** i **Clearing Status**. Du får derefter vist alt, hvad der er gået ind den dag, opdelt efter gruppe og korttype.

<figure><img src="https://4238701851-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkHppABR62cHvY5tNexuE%2Fuploads%2FfrmeGaxLdQMkqrZDyoNj%2Ftcs-dk-engage-day.png?alt=media&amp;token=0be86cf1-249e-4a4f-94ad-48d4009a605b" alt="En dag i Clearing Status"><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Åbn gruppen

Klik på **firmanavnet** med blå tekst i kolonnen **Group**. Du ser derefter dagens batcher for terminalgruppen, opdelt efter korttype.

<figure><img src="https://4238701851-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkHppABR62cHvY5tNexuE%2Fuploads%2FvsLK5Uh8yFh4BNxuQug6%2Ftcs-dk-engage-group.png?alt=media&amp;token=15fadd8c-8142-40f4-af21-a7e2299b137f" alt="Batcher for en terminalgruppe"><figcaption></figcaption></figure>

{% hint style="info" %}
Kolonnen **Status** viser batchens status. Hvis en batch har status **Partly rejected**, vises knappen **Confirm** i kolonnen **Actions**.
{% endhint %}
{% endstep %}

{% step %}

### Åbn terminalen

Klik på terminalens **serienummer** med blå tekst i kolonnen **Payment method type / Terminal** for at se de enkelte transaktioner.

<figure><img src="https://4238701851-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkHppABR62cHvY5tNexuE%2Fuploads%2F24rdF3zAIoWQPMAG3RCX%2Ftcs-dk-engage-terminal.png?alt=media&amp;token=6d1e341f-462a-4fa5-ad6e-9b9da7f2791c" alt="Transaktioner for en terminal"><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Vis alle detaljer

Markér **Show details**, eller klik på **pilen** foran tidspunktet for at få mere information om en transaktion.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
På hvert niveau kan du hente listen ned ved at klikke på **Excel-ikonet** ud for overskriften.
{% endhint %}

<details>

<summary>Nøgleord</summary>

Også kaldt: transaktionsdetaljer, gennemgang af hændelser, terminal-batch. Søgeord: Clearing Status, Date, Group, Terminal group, serienummer, Show details, Partly rejected, Confirm, Excel.

</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/tcs-client-engage/transaktioner-og-afregning/sadan-ser-du-transaktionsdetaljer.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.