> For the complete documentation index, see [llms.txt](https://docs.finpay.id/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.finpay.id/documentation/disbursement/finpayku-disbursement-user-guide/disbursement-statement-report.md).

# Disbursement statement report

Search, review, and export disbursement history.

## Disbursement statement report

Open **FinpayKU Disbursement** → **Disbursement Statement Report**. The report lists completed, pending, and failed transactions.

### Filter transaction status

* **All** is selected by default.
* **Success** shows completed transactions.
* **Pending** shows transactions awaiting approval or processing.
* **Failed** shows unsuccessful transactions.

The pending badge updates when you refresh the data.

### Review transaction details

Click **Info** to open the proof of money transfer. Click **Detail Transaction** to open full details and processing logs.

Transaction details include:

* Transaction ID, created time, updated time, status, and currency.
* Amount, product type, payment channel, batch reference, and external ID.
* Beneficiary name, bank or e-money service, account, and transaction note.

Currency defaults to `IDR`. Batch Reference ID shows **Not Available** for single transactions.

Product types include BI-Fast, RTOL, and Finpay Money.

### Transaction statuses

* **SUCCESS** — The transfer completed.
* **PENDING** — The transfer remains in progress.
* **SUSPECT** — The transfer requires investigation.
* **FAILED** — The transfer failed.
* **Waiting for Process** — The transaction is not processed.
* **Inquiry Success** — Beneficiary validation succeeded.

### Export report data

1. Click **Export** in the toolbar.
2. Select the columns and file format.
3. Click **Export** to submit the request.

When processing completes, open **Export List** to download the file. You can also stay on the current page.


---

# 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.finpay.id/documentation/disbursement/finpayku-disbursement-user-guide/disbursement-statement-report.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.
