> ## Documentation Index
> Fetch the complete documentation index at: https://docs.paymend.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Reporting

> Period-based reports covering payment creation, processing, disputes and settlement.

Paymend makes processing and settlement detail available across four different reports, which
collectively describe the full lifecycle of a payment, from the moment it is created through to
the money settling in your account.

<CardGroup cols={2}>
  <Card title="Payments created" icon="plus" href="/reporting/payments_created">
    Every payment record opened, whether or not it was later processed.
  </Card>

  <Card title="Transactions succeeded" icon="circle-check" href="/reporting/transactions_succeeded">
    Sales captured and refunds returned.
  </Card>

  <Card title="Payments disputed" icon="triangle-exclamation" href="/reporting/payments_disputed">
    Alerts, RDRs, chargebacks and fraud reports raised against your payments.
  </Card>

  <Card title="Settlement paid out" icon="money-bill-transfer" href="/reporting/settlement_paid_out">
    Every event that contributed to a payout, with associated fees.
  </Card>
</CardGroup>

## Reports are period-based and immutable

Each report covers one closed period. It is generated after the period ends and
never changes afterwards.

<Note>
  Regenerating a report for a period you already hold returns byte-identical
  content. If a report you already downloaded differs from a later copy, treat
  that as a defect and contact support rather than reconciling against it.
</Note>

This has two consequences worth designing around:

* **A report is a safe primary key source.** Once you have ingested a period,
  you never need to re-read it to pick up amendments.
* **Late-arriving data lands in a later period, not a restated one.** A dispute
  raised in September against a payment created in July appears in the September dispute
  report. It does not cause July's report to change.

Every row in every report carries an `event_id` that is unique to that event. This is the event-level
join key between processing and settlement reports. Non-payment events also have a `payment_id` - the
same `paymentId` value returned in responses from the payments API - which allows reconciliation
between an event and the payment that it relates to.

## File naming

```
{report_type}-{merchant_name}-{period_start}_to_{period_end}.csv
```

Dates are `YYYYMMDD`, and both bounds are inclusive.

| Report                 | Example filename                                                     |
| ---------------------- | -------------------------------------------------------------------- |
| Payments created       | `report_payments_created-my_merchant-20260801_to_20260831.csv`       |
| Transactions succeeded | `report_transactions_succeeded-my_merchant-20260801_to_20260831.csv` |
| Payments disputed      | `report_payments_disputed-my_merchant-20260801_to_20260831.csv`      |
| Settlement paid out    | `report_settlement_paid_out-my_merchant-20260912.csv`                |

<Note>
  **Settlement reports carry a single date, not a range.** That date is the
  payout date, not the period the report covers. The events inside it fall in
  the settlement period that closed before the payout ran — which depends on
  your payout schedule.
</Note>

`merchant_name` is your merchant identifier as configured on your Paymend
account. It is stable and safe to parse.

## Which timestamp defines the period

Each report is bounded on its own event timestamp, so the same payment can
appear in reports covering different periods.

| Report                 | Period column        | Meaning                                                                         |
| ---------------------- | -------------------- | ------------------------------------------------------------------------------- |
| Payments created       | `event_created_at`   | When the payment record was created                                             |
| Transactions succeeded | `event_processed_at` | When the transaction was processed                                              |
| Payments disputed      | `event_created_at`   | When Paymend recorded the dispute event                                         |
| Settlement paid out    | `event_effective_at` | When effective date for settlement, determining the period the event falls into |

A payment created in June, captured in July and charged back in August appears
in three different processing reports, each in the period matching that stage.

## Amounts and currency

All amounts are decimal strings in major units — `97.00`, not `9700`. Negative
values are debits against your payout. Each report states its own currency
column; see the individual pages.

## Next steps

<Card title="Reconciliation guide" icon="link" href="/reporting/reconciliation">
  How to join the four reports and prove that every processed event was paid out.
</Card>