> For the complete documentation index, see [llms.txt](https://wiki.beabee.io/help-center-english/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.beabee.io/help-center-english/payment/revenue-dashboard.md).

# Revenue Dashboard

In the revenue dashboard, you get a central overview of all payments received through your instance. This includes both one-time contributions and recurring payments.

Log in to your beabee instance and click *Dashboard* in the sidebar. You can access your revenue dashboard by clicking on the highlighted blue text *Revenue*.

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

***

### Structure of the revenue dashboard

In the revenue dashboard, you get a detailed overview of all incoming payments and their status.

Unlike the contact database, all payments are listed individually here and evaluated according to their status (e.g. successful, pending, or failed). This means you can see the financial level of each individual transaction.

In the contact database, on the other hand, payments are aggregated by contact. The focus is not on individual transactions, but on which contributions a contact has made and how their overall payment or support behavior looks.

<details>

<summary><strong>Types of payments in the revenue dashboard</strong></summary>

Your payments are divided into five different categories, all structured in the same way.

Above the selected segment, you see the total sum of all payments in that category. Next to it, the resulting average amount per contact is displayed. Below that, you will find all contacts belonging to the respective category, including their payment status, the debit date, and the contribution amount.

The status *Successful* means that the payment has been completed successfully and the amount has been credited. *Pending* indicates that the payment has not yet been completed and may still be processing. *Failed* means that the payment could not be completed, for example due to a technical error or a declined payment method. *Cancelled* indicates that the payment was actively stopped or reversed, for example due to a cancellation.

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

</details>

***

### Filter in the revenue dashboard

In the revenue dashboard, you can use filters to narrow down and analyze your data in a targeted way. You can choose whether the results must match all selected rules or whether it is sufficient for at least one of the selected rules to apply. This logic is especially useful when combining multiple filters.

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

In general, you have four filter categories available: *Amount*, *charge date*, *contact*, and *type*.

<details>

<summary><strong>Amount</strong></summary>

The following conditions are available here:

* **is**\
  The amount exactly matches the specified value.
* **isn't**\
  The amount does not match the specified value.
* **between**\
  The amount is between two specified values.
* **isn't between**\
  The amount is outside the specified range.
* **less than**\
  The amount is lower than the specified value.
* **more than**\
  The amount is higher than the specified value.
* **at most**\
  The amount is less than or equal to the specified value.
* **at least**\
  The amount is greater than or equal to the specified value.

</details>

<details>

<summary><strong>Charge date</strong></summary>

The following conditions are available:

* **is on**\
  The payment was made on exactly this date.
* **is not on** \
  The payment was not made on this date.
* **between**\
  The payment falls within a specific time range.
* **isn't between**\
  The payment falls outside the specified time range.
* **before**\
  The payment was made before a specific date.
* **after**\
  The payment was made after a specific date.
* **before or on**\
  The payment was made on or before a specific date.
* **after or on**\
  The payment was made on or after a specific date.

</details>

<details>

<summary><strong>Contact</strong></summary>

The following conditions are available:

* **is**\
  The payment belongs to the contact you specify in the free text field.
* **is not**\
  The payment does not belong to the specified contact.

</details>

<details>

<summary><strong>Type</strong></summary>

The following conditions are available:

* **is**\
  The payment matches the selected type.
* **is not**\
  The payment does not match the selected type.

Available types:

* **Prorated**\
  There is a contribution change within a month or year.
* **recurring**\
  The payment is collected automatically on a regular basis (e.g. monthly or annually).
* **one-time**\
  A single payment without recurrence.
* **unknown**\
  The payment type could not be clearly assigned. No payment type is stored in the system (e.g. if entered manually).

</details>

***

### These filters can be useful

<details>

<summary><strong>Average recurring revenue</strong></summary>

Insigh&#x74;**:** What is the average revenue generated from recurring payments.

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

</details>

<details>

<summary><strong>Share of one-time vs. recurring payments</strong></summary>

Insigh&#x74;**:** How your revenue is distributed between recurring and one-time payments.

Approac&#x68;**:** Filter by both contribution types and calculate the total amount for each. You can then determine the respective shares.

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

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

</details>

<details>

<summary><strong>Identify additional payments</strong></summary>

Insigh&#x74;**:** Which payments are received in addition to regular recurring income.

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

</details>

<details>

<summary><strong>Identify large donations</strong></summary>

Insigh&#x74;**:** Which payments have particularly high amounts and where the financial peaks in your revenue occur.

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

</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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://wiki.beabee.io/help-center-english/payment/revenue-dashboard.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.