> 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-laeser-du-clearing-status.md).

# Sådan læser du Clearing Status

Sådan læser du fanen Clearing Status i TCS (Engage): daglige totaler, beløb bekræftet af banken og status.

{% hint style="info" %}
Brug denne vejledning, når du vil se en oversigt over dine transaktioner eller tjekke, om en dags betalinger er bekræftet af banken.
{% endhint %}

Fanen **Clearing Status** viser løbende status for de penge, der bevæger sig gennem tjenesten. Det øverste niveau viser de **samlede daglige transaktioner** og antallet, opdelt efter korttype. Vælg perioden under **Start date** og **End date**, og klik på **Search**.

<figure><img src="https://4238701851-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkHppABR62cHvY5tNexuE%2Fuploads%2F4Uck9rvFjdQ8GJDAA1Mq%2Ftcs-dk-engage-clearing.png?alt=media&amp;token=4ca7cff1-6d63-4798-bbe0-696826e65179" alt="Fanen Clearing Status i TCS"><figcaption></figcaption></figure>

## Kolonner

| Kolonne                    | Det viser den                                                                                       |
| -------------------------- | --------------------------------------------------------------------------------------------------- |
| **Date**                   | Dagen. Klik på datoen for at se dagens transaktioner.                                               |
| **Payment method type**    | Korttypen, f.eks. Visa, MasterCard eller Dankort.                                                   |
| **Received from terminal** | Beløbet (**Sum**) og antallet af transaktioner (**Ct**), der er modtaget fra betalingsterminalerne. |
| **Confirmed by bank**      | Beløbet (**Sum**) og antallet af transaktioner (**Ct**), som banken har bekræftet.                  |
| **Status**                 | Batchens status, f.eks. **OK** eller **Partly rejected**.                                           |

{% hint style="info" %}
Du kan hente totalerne og de enkelte betalinger pr. korttype ned som en liste ved at klikke på **Excel-ikonet**.
{% endhint %}

{% hint style="warning" %}
**Vigtigt:** TCS viser kun detaljer om transaktioner i **to måneder**. Derefter kan du ikke længere se dem i detaljer eller foretage handlinger på dem.
{% endhint %}

Vil du se flere detaljer for en dag? Følg vejledningen [Sådan ser du transaktionsdetaljer](/support-denmark/tcs-client-engage/transaktioner-og-afregning/sadan-ser-du-transaktionsdetaljer.md).

<details>

<summary>Nøgleord</summary>

Også kaldt: Clearing Status, afregning, oversigt over afregning, batchstatus, udbetalinger. Søgeord: Clearing Status, Received from terminal, Confirmed by bank, Status, OK, Partly rejected, 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-laeser-du-clearing-status.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.
