Indonesia customer funds + settlement ops
Approved customer-money perimeter, funding recognition, governed payout release, and signed statement close for Indonesia licensed digital-asset operators.
Overview
Indonesia customer-money operations with approved perimeter, governed payouts, and statement-led close.
Use this when an Indonesia-licensed operator needs one controlled lane for separated customer money, governed payout release, and statement-led bank close.
Route coverage
- 4-stage customer-money lane
- Approved customer-money perimeter and separated-account setup
- Funding recognition, ledger post, and route lock
- Payout approval, beneficiary validation, and item finality
- Statement-led reconciliation and sign-off
- Controlled close and retention export
Infrastructure
- Approved bank and support-entity controls on one lane
- Funding status, ledger-post, and exception monitoring
- Beneficiary approval chain and item-finality tracking
- Statement-led reconciliation with named discrepancy ownership
- Signed close and retention-tagged exports
Lifecycle stages
| Stage | Flow steps |
|---|---|
| Customer Funds Scope | Record the operator approval perimeter, approved separated account, support-entity matrix, and collection policy before opening the run; Bind callback security, statement source, and close-signoff rules so funding, payout, and reconciliation stay on one governed bank lane |
| Virtual Account Funding | Match bank callbacks and status inquiry against the operator ledger, then keep unmatched credits in an exception queue until the funding batch is release-ready; Lock the payout route only after ledger-posted funding, status-source agreement, and cut-off ownership are all posted |
| Payout And Settlement | Run beneficiary inquiry, approval chain, and payout batch release on the selected bank rail while preserving item-level bank references; Hold returned or ambiguous items in an exception queue until finality or repair is posted |
| Reconcile And Audit | Match statement lines, payout finality, and operator ledger balances, then assign any discrepancy to a named close owner before publication; Publish the signed close pack and retention-tagged archive only after statement reconciliation, exception resolution, and final approval are complete |
Setup reference
| Field | Explanation | Related terms |
|---|---|---|
| Safeguarded funds amount | Sets the rupiah amount carried through collection recognition, payout release, and statement-led close. | |
| Bank lane | Sets whether the workflow follows the collections-and-payout path or a collections-and-reconciliation branch before close. | |
| Close timing | Keeps authoritative close tied to bank status and statement cadence rather than only the initial payment event. | Statement-led reconciliation |
| Collection rail | Fixed for this case. Identifies the bank-side collection-account context used to recognize incoming customer funds. | |
| Safeguarded settlement rail | Fixed for this case. Identifies the safeguarded destination used before verified payout and reconciliation close. | |
| Settlement currency | Fixed for this case. Scoped to IDR customer funds and payouts. |