---
title: "User-level reporting"
description: "An overview of the key reporting use cases to prioritize for your platform's users."
url: "https://docs.adyen.com/platforms/reconciliation-use-cases/first-year-focus/platform-user-level-reporting"
source_url: "https://docs.adyen.com/platforms/reconciliation-use-cases/first-year-focus/platform-user-level-reporting.md"
canonical: "https://docs.adyen.com/platforms/reconciliation-use-cases/first-year-focus/platform-user-level-reporting"
last_modified: "2026-06-01T15:33:15+02:00"
language: "en"
---

# User-level reporting

An overview of the key reporting use cases to prioritize for your platform's users.

[View source](/platforms/reconciliation-use-cases/first-year-focus/platform-user-level-reporting.md)

The following use-cases for platform reporting are designed to help your platform build reports to support your **Small and Medium-sized Business (SMB)** users. These reports allow them to view and plan their business, using the data generated through their transactions.

| Job to be done                                                        | Reporting data to generate |
| --------------------------------------------------------------------- | -------------------------- |
| [Review transactions and confirm sales](#transactions-overview)       | Transactions overview      |
| [Reconcile sales and cash flow](#payout-overview)                     | Payout overview            |
| [View, open, and resolve payment disputes](#chargebacks-and-disputes) | Chargebacks and disputes   |

## Transactions overview

**Job to be done: Review transactions and confirm sales**\
A business reviews transactions processed on a daily basis so that they can reconcile their sales. A platform with a point-of-sale element to their offering typically uses this overview as input to a total overview of transactions that includes cash, so that they can then close out the register.

### Content overview

Provide a list of all transactions on the account, including (but not limited to) sales, refunds, and chargebacks. The transactions should include the gross amount, fees that were charged, and the net amount that the business will receive in the payout to their bank account.

**Example template for a list of Transactions and Fees**

| Transaction Amount | Transaction Type             | Card Type        | Fees incurred | Net Payout | Payout Batch | Payout Date     |
| ------------------ | ---------------------------- | ---------------- | ------------- | ---------- | ------------ | --------------- |
| 100                | Payment                      | Visa Credit      | 2             | 820        | 001          | 1 February 2025 |
| 80                 | Refund                       | Mastercard Debit | 0.10          | -80.10     | 001          | 1 February 2025 |
| 5                  | Other - Instant Deposit Fees | N/A              | 5             | -5         | 001          | 1 February 2025 |
| ...                | ...                          | ...              | ...           | ...        | ...          | ...             |

**Recommendation for how to build**\
**Option one: Transactions Overview Component**\
The [Transactions Overview Component](/platforms/build-user-dashboards/?component=Transaction\&integration=components#transactions-overview-component) is a drop-in solution built for you to cover key reporting and dashboard use cases for your users. When you use components, you can avoid having to set up complex data pipelines or extensive frontend solutions for your users.

**Option two: Balance Platform Accounting Report**\
The [Balance Platform Accounting Report](/platforms/reports-and-fees/balance-platform-accounting-report) is a csv-file that includes all transactions processed on your platform on a given day, from sales to refunds to payouts.

After enabling automatic generation and setting up ingestion pipelines, the Accounting Report provides you with the minimum required data to then build your custom dashboards and reporting on top of it. This solution requires more product and engineering resources than the component. However, it does allow you to customize how to deliver the data to your users. For example, you may want to deliver a report through email.

## Payout overview

**Job to be done: Reconcile sales and cash flow**

A business needs to reconcile their sales, and how their gross sales resulted in a net payout on their bank account. They should this dashboard to understand the gross amount, the fees that were withheld, and any other transactions that might have impacted their payout.

### Content overview

Provide a simplified view of the total list of transactions and fees that sum up to a payout.

**Example template for a daily summary**

| Payments Received | Refunds | Fees | Other [1](#fn:1) | Net Payout |
| ----------------- | ------- | ---- | ---------------- | ---------- |
| 1000              | 100     | 50   | 30               | 820        |
| ...               | ...     | ...  |                  | ...        |

**Recommendation for how to build**\
**Option one: Adyen's Payout Component**\
The [Payout Component](/platforms/build-user-dashboards/?component=Payout\&integration=components#payouts-overview-component) is a drop-in solution built for you to cover key reporting and dashboard use cases for your users. When you use components, you can avoid having to set up complex data pipelines or extensive frontend solutions for your users.

**Option two: Payout report**\
The [Payout Report](/platforms/reports-and-fees/payout-report) is a csv-file that includes all payouts processed on your platform on a given day, including the transactions that make up those payouts. After enabling automatic generation and setting up ingestion pipelines, the Payout Report provides you with the minimum required data to then build your custom dashboards and reporting on top of it. This solution requires more product and engineering resources than the Payout Component. However, it does allow you to customize how to deliver the data to your users. For example, you may want to deliver a report through email.

## Chargebacks and disputes

**Job to be done: View, open, and resolve payment disputes**

Your users need to manage disputes and chargebacks, to defend against disputes where possible, and to reconcile the corresponding costs related to chargebacks.

The users on your platform need direct control of their disputes. They need a clear, centralized place to view all chargeback notifications, understand the reason codes and requirements, and submit evidence to defend the transaction.

### Content overview

At a minimum, you want to show your users the following information:

* **Chargebacks**: shows undefended or unresponded chargebacks and Requests for Information (RFIs) that require user action. Each dispute record includes details such as the respond by date, payment method, dispute reason, and disputed amount.
* **Fraud alerts**: shows fraud alerts to help users identify suspicious activity. Each record includes the payment method, fraud reason, total payment amount, and date of the alert.
* **Ongoing & closed**: shows ongoing chargebacks, RFIs, and resolved disputes to help users track and match disputes against payment activity. Each dispute record includes details such as the payment method, dispute reason, and disputed amount as well as the status of a dispute.
* **Financial impact**: What has the financial impact of disputes been over a set period of time, and how has it impacted the user’s cashflow?

**Recommendation for how to build**\
**Option one: Adyen's Disputes Component**\
Use Adyen's [Disputes Component](/platforms/build-user-dashboards/?component=Dispute\&integration=components#disputes-overview-component) to provide your users with a ready-to-use self-service tool for managing chargebacks. By integrating this component into your platform, you can significantly reduce your operational overhead by automating the dispute process. Your users will be able to directly view, accept, or defend disputes, upload necessary documents, and track their status. They can do all of this without requiring manual intervention from your support team.

**Option two: Balance Platform Accounting Report**\
The [Balance Platform Accounting Report](/platforms/reports-and-fees/balance-platform-accounting-report/#-balance-platform-accounting-report-) contains the financial chargeback-related events, but no non-financial dispute events. This solution requires more product and engineering resources than the component. However, it does allow you to customize how to deliver the data to your users. For example, you may want to deliver a report through email.

Within the **platformPayment** category, you can find event types like **chargeback**, **chargebackReversal**, and **secondChargeback**.

* **Chargeback**: When a dispute is initiated, Adyen debits the disputed amount from the designated balance account. In your report, this appears as a **platformPayment** `category` event with a **chargeback** `type`, and the **Balance (BC)** column shows a negative value.
* **Chargeback Reversal**: If you successfully defend a chargeback or the customer repays the funds, Adyen credits the disputed amount back to your account. In your report, this appears as a **platformPayment** `category` event, with a **chargebackReversal** `type`, and the **Balance (BC)** column shows a positive value for this event.
* **Second Chargeback**: If the issuing bank rejects your defense, Adyen debits the disputed amount again. In your report, this appears as a **platformPayment** `category` event, with a **secondChargeback** `type`, and the **Balance (BC)** column shows a negative value for this event.
* **Fees**: Adyen charges fees related to disputes. These fees are recorded as separate line items in the report, and are listed as fees of `type` **Chargeback Fee** or **SecondChargeback Fee**.

***

1. "Other" includes Chargebacks, withholdings for capital loans, and costs for early or instant settlement. [↩](#fnref1:1)
