# Transaction List

The **List of Transactions** view displays all transactions imported or created in the system.\
From here, you can verify if transactions are correctly matched with members, check their values, and access detailed data.

<figure><img src="/files/t4lHGGF5TES3p8WX19gz" alt=""><figcaption></figcaption></figure>

Each transaction includes:

* **Document number and type** (e.g. purchase, return)
* **Date and value**
* **Matched status** — whether it’s linked with a member
* **Member data** (full name, email, phone number, loyalty card number)

{% hint style="warning" %}
Member data is based on the details passed in the transaction, not on the member profile.

The details refer to the customer engaged in the transaction and can vary from the information of an existing member in the system.
{% endhint %}

* **Transaction value**&#x20;

{% hint style="info" %}
💡 **Tip:** Use filters to quickly find transactions by date, type, or matching status.
{% endhint %}

***

### Actions available

From this view, you can:

* Open transaction details
* Add new transactions manually
* Import transactions in bulk
* Import matches
* Match transactions with members

***

### Add transaction menu

Click the **Add transaction** button to choose from four options:

| Action                              | Description                                                                                      |
| ----------------------------------- | ------------------------------------------------------------------------------------------------ |
| **Add transaction manually**        | Create a new transaction directly in the Admin Panel by entering transaction and member details. |
| **Import matches**                  | Upload a file containing matches between transactions and members.                               |
| **Import transactions**             | Bulk import multiple transactions from an external source (e.g. POS, eCommerce).                 |
| **Match transaction with a member** | Link existing transactions with members based on selected identifiers.                           |

***

#### Columns

Each row represents a single transaction. The main columns are:

| Column                                       | Description                                                                |
| -------------------------------------------- | -------------------------------------------------------------------------- |
| **Document number**                          | Unique transaction identifier from the source system.                      |
| **Document type**                            | Type of document — *Purchase* or *Return*.                                 |
| **Document date**                            | Date and time when the transaction occurred.                               |
| **Full name / Email / Phone / Loyalty card** | Data of the member associated with the transaction.                        |
| **Matched**                                  | Indicates if the transaction is already linked to a member (*Yes* / *No*). |
| **Transaction value**                        | Monetary value of the transaction (in tenant’s currency).                  |

{% hint style="info" %}
💡 You can customize visible columns using the **Manage Columns** button at the bottom of the list.
{% endhint %}

***

#### Example

A typical transaction list might show:

| Document number | Date        | Matched | Transaction value |
| --------------- | ----------- | ------- | ----------------- |
| 6lkgwm0qzb      | 04 Nov 2025 | Yes     | 1,206.88 CAD      |
| ujryw337c8      | 04 Nov 2025 | Yes     | 1,287.13 CAD      |
| i8vk60u7sr      | 04 Nov 2025 | Yes     | 1,098.78 CAD      |

***

#### Next steps

➡️ Go to [Transaction Details](/main-features/transactions/transaction-details.md) to explore what information is available for each transaction.


---

# Agent Instructions: 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:

```
GET https://help.openloyalty.io/main-features/transactions/transaction-list.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.