> For the complete documentation index, see [llms.txt](https://docs.doku.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.doku.com/changelog/july-2026/sub-account-v2-collect-and-route.md).

# Sub Account V2 - Collect and Route

Effective Date: July, 2026

Collect & Route is a fund orchestration capability within Sub Account that enables businesses to collect payments, automatically distribute funds, manage balances, and process payouts through a single integration.

Designed for platforms that manage transactions across multiple parties, Collect & Route helps automate fund movement while reducing manual reconciliation, allowing businesses to operate more efficiently as they scale.

#### [<mark style="color:$primary;">Explore More about Collect and Route</mark> ](https://docs.doku.com/wallet-as-a-service/sub-account/collect-and-route)

#### [<mark style="color:$primary;">Try Collect and Route Sandbox DEMO</mark>](https://sandbox.doku.com/demo/sub-account)

<figure><img src="https://2961485474-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5XrPPWlRNNTQG72DaVGd%2Fuploads%2FousyFSX4NDLbYep1R4F3%2FMonthly%20Product%20Update%20July_3.png?alt=media&amp;token=55865c50-da2e-44e3-ae1d-cdc25268f490" alt=""><figcaption></figcaption></figure>

***

### 🔍 What’s New?

Collect & Route now supports a complete end-to-end fund orchestration flow, including:

* Multiple money-in methods through DOKU Checkout, Direct API, or built-in BRI Virtual Account
* Automatic fund distribution using configurable Split Rules
* Balance management across multiple sub-accounts
* Real-time balance deduction through the Debit API
* Double-entry ledger for accurate fund tracking
* Payouts to bank accounts and supported e-Wallets

***

### 💡 Why It Matters

Businesses that collect payments on behalf of multiple parties often spend significant time reconciling transactions manually. Payments usually arrive in one merchant account, requiring teams to determine how much belongs to each seller, agent, or partner before initiating payouts.

Collect & Route automates this entire process by identifying where every payment belongs the moment it is received, reducing operational effort while improving financial accuracy.

***

### ✨ Updated Experiences

### 🔄 Before

Previously, businesses typically managed payment distribution manually.

A customer payment was first received into a single merchant account before finance teams needed to:

* Identify which seller or partner owned each transaction.
* Calculate commissions manually.
* Perform internal fund reconciliation.
* Transfer funds individually to each recipient.
* Track balances using spreadsheets or internal systems.

As transaction volumes increased, these processes became increasingly time-consuming and prone to operational errors.

### 🆕 After

With Collect & Route, payment routing becomes part of the payment process itself.

When accepting a payment, merchants simply specify the destination sub-account and, if required, a Split Rule. DOKU automatically routes incoming funds, applies revenue sharing rules, records every balance movement, and prepares funds for payout after settlement.

This allows businesses to automate complex fund flows while maintaining complete visibility over every transaction.

***

### 🚀 How It Works

* Register a Sub-Account for each seller, partner, or operational entity.
* Create a Split Rule to define how incoming payments should be distributed.
* Accept payments through DOKU Checkout API or Direct API by including the destination sub-account and optional Split Rule.
* DOKU automatically routes and distributes funds according to the configured business rules.
* Once settlement is completed, merchants can initiate payouts directly to bank accounts or supported destination

[Or learn more how to integrate in API References](https://developers.doku.com/wallet-as-a-service/sub-account/sub-account-v2)

***

### **💼 Key Capabilities**

* Collect payments through Checkout API, Direct API, or built-in BRI Virtual Account.
* Automatically distribute funds using configurable Split Rules.
* Support Percentage and Flat Amount revenue sharing models.
* Monitor balances across multiple sub-accounts in real time.
* Track fund movement through a double-entry ledger.
* Process payouts to supported Indonesian bank accounts.
* Manage multiple business models through a single integration.

***

### **📌** Things to Know

* Collect payments through Checkout API, Direct API, or built-in BRI Virtual Account.
* Automatically distribute funds using configurable Split Rules.
* Support Percentage and Flat Amount revenue sharing models.
* Monitor balances across multiple sub-accounts in real time.
* Track fund movement through a double-entry ledger.
* Process payouts to supported Indonesian bank accounts.
* Manage multiple business models through a single integration.

***

For assistance, contact our Care Team at <care@doku.com> or (021) 1500963.

***

Thank you and best regards,\
**DOKU Product Team**


---

# 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.doku.com/changelog/july-2026/sub-account-v2-collect-and-route.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.
