> For the complete documentation index, see [llms.txt](https://docs.diro.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.diro.app/en/payments-and-finance/wallet-and-withdrawals.md).

# Wallet & Withdrawals

**Settings → Balance.** Every successful payment goes into your business's wallet.

## Two figures to tell apart

| Figure             | Meaning                                                                                   |
| ------------------ | ----------------------------------------------------------------------------------------- |
| **Active balance** | Funds that can be withdrawn right now.                                                    |
| **Held balance**   | Funds from bookings that have been paid but haven't yet passed the payout waiting period. |

Funds move from held to active at **H+3** — three business days after payment is received. This waiting period is standard across all payment processors and exists so that problematic payments can be resolved before funds are released.

```mermaid
flowchart LR
  A["Customer pays"] --> B[("Held balance")]
  B -->|"H+3"| C[("Active balance")]
  C -->|"manual or automatic<br/>withdrawal"| D["Processed"]
  D --> E(["Your bank account"])
```

## Registering a bank account

Add an account in **Settings → Balance**. The account holder's name must match your business data; an account that doesn't match will be rejected during verification.

## Requesting a withdrawal

1. Make sure the active balance is sufficient.
2. Open **Settings → Balance → Withdraw Funds**.
3. Enter the amount and select the destination account.
4. Submit.

The request enters the processing queue, and its status can be tracked in the withdrawal history.

## Two ways to receive payouts

**Manual withdrawal.** You submit a request yourself whenever the active balance is sufficient, for the amount you decide. Suited to when you want to control the payout pace yourself.

**Automatic withdrawal.** The active balance is paid out automatically to the registered account without you needing to submit a request each time. Suited to when you want the money to arrive without doing anything.

Both go through the same H+3 waiting period — automatic withdrawal speeds up *submitting the request*, not the waiting period.

### Automatic withdrawal schedule

Automatic withdrawal runs **every day at 23:00 WIB**. Balance that is already active at that time is submitted for payout to the registered account. Balance that becomes active after 23:00 is included in the next day's schedule.

```mermaid
flowchart LR
  A["Customer pays<br/>Monday"] --> B[("Held<br/>Mon - Wed")]
  B -->|"H+3"| C[("Active<br/>Thursday")]
  C -->|"Thursday 23:00 WIB"| D["Automatic withdrawal<br/>submitted"]
  D --> E(["Arrives in account"])
```

So for a payment received on Monday, the automatic payout submission runs Thursday night. The time funds actually arrive in the account follows the destination bank's processing hours.

```mermaid
flowchart TD
  A[("Active balance")] --> B{"Payout mode"}
  B -->|"Manual"| C["You submit<br/>amount & account"]
  B -->|"Automatic"| D["System submits<br/>on schedule"]
  C --> E["Processed to bank"]
  D --> E
  E --> F(["Your bank account"])
```

## Transaction history

The history shows every balance movement: incoming payments, fees, and outgoing withdrawals. It can be filtered by date, type, and status, and searched by booking code.

{% hint style="warning" %}
Access to the Balance menu means being able to submit fund withdrawals. Restrict which roles have access to this module. See Staff, Roles & Access.
{% endhint %}


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.diro.app/en/payments-and-finance/wallet-and-withdrawals.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.