> 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-nordics/tcs-client/transactions-and-clearing/how-to-read-the-clearing-status.md).

# How to Read the Clearing Status

Understand the TCS Clearing Status view — daily totals, amounts in progress, and batch status.

{% hint style="info" %}
**Use this when** you want to see the money flowing through your service, or check whether a day's payments have been paid out.
{% endhint %}

The **Clearing Status** tab gives a near real-time view of the money flowing through the service. The top level shows your **total daily transactions** and number of transactions, split by card type.

<figure><img src="https://content.gitbook.com/content/H3VBt0P9E0VJDk5TJ2jp/blobs/MDKtTqC1hZK2Do3YEKd0/tcs-clearing-status.png" alt=""><figcaption></figcaption></figure>

## Columns

| Column               | What it shows                                                                                       |
| -------------------- | --------------------------------------------------------------------------------------------------- |
| **Total**            | The amount received from your payment terminals, and the number of transactions.                    |
| **In progress**      | The amount and number of items still to be processed. Once processed and settled, this shows **0**. |
| **Paid to merchant** | The amount paid, after commission. Shows **0** if the item hasn't been settled yet.                 |
| **Status**           | Whether the batch has been settled or is still being processed.                                     |

## Batch status

| Status      | Meaning                                                                 |
| ----------- | ----------------------------------------------------------------------- |
| **OK**      | The batch has been settled — the money should be in your account.       |
| **Pending** | The terminal has received the payment, but it hasn't been paid out yet. |

{% hint style="warning" %}
TCS only shows full details of transactions for **two months**. After that, they're removed from the service automatically — the totals stay in your reports, but you can't view the transactions in detail or take any action on them.
{% endhint %}

To see more detail for a day, see [How to View Transaction Details](/support-nordics/tcs-client/transactions-and-clearing/how-to-view-transaction-details.md).

<details>

<summary>Keywords</summary>

Also called: clearing status, settlement status, batch status, payouts, deposits. Search terms: clearing, clearing status, batch, OK, pending, paid to merchant, settlement.

</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-nordics/tcs-client/transactions-and-clearing/how-to-read-the-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.
