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

# Disbursement overview

> Configure how a merchant's collected funds are split and fee'd, then run human-reviewed batches that export a bank payment file.

<Note>
  Disbursement is in **beta**. Track B (settlement-config batches → bank CSV) is
  available; the automated rail engine (Track A) is on the roadmap.
</Note>

klikit Disbursement answers a single question: **when a merchant collects money,
how is it split between the parties involved and what fees apply — and how do we
pay everyone?** You define the split and fees once as a reusable **template**,
bind it to a merchant as an **instance** (with bank details), then run
**batches** that compute each party's payout and export a **bank file** a human
takes to the bank.

There is **no automated money movement** in beta — the exported CSV is the
deliverable. Every batch is reviewed and approved by a second person before it
can be exported.

## The loop

<Steps>
  <Step title="Create a template">
    Define the split parties (as integer percentages that must total 100%) and
    the fees (MDR, service charge, tax). See [Templates](/disbursement/templates).
  </Step>

  <Step title="Instance it to a merchant">
    Bind the template to a business (and optionally a brand), add each payable
    party's bank details, and verify them. See
    [Instances](/disbursement/instances).
  </Step>

  <Step title="Run a batch">
    Feed gross amounts (manual grid or CSV), **compute** the per-party split,
    review the lines and any flags, then get a second-tier **approval**. See
    [Batches](/disbursement/batches).
  </Step>

  <Step title="Export the bank file">
    Download the bank CSV for the approved batch and submit it to the bank.
  </Step>
</Steps>

## Vocabulary

The engine produces **batches** — reviewed CSV files a human takes to a bank.
This is deliberately distinct from rail **runs** (automated pushes), which are a
future capability. Keep the two terms separate.

<CardGroup cols={2}>
  <Card title="Template" icon="file-lines">
    A reusable, versioned settlement config: split parties + fees. One template
    can be instanced for many merchants.
  </Card>

  <Card title="Instance" icon="store">
    A template bound to a specific merchant (business/brand), with per-party bank
    details and optional overrides.
  </Card>

  <Card title="Batch" icon="wallet">
    A period's disbursement run for one template: gross inputs → computed
    per-party lines → approval → bank file.
  </Card>

  <Card title="Party" icon="users">
    A recipient in a split — the merchant, klikit, or any other counterparty
    (e.g. a landlord).
  </Card>
</CardGroup>

See [Concepts](/disbursement/concepts) for the money model (basis points, minor
units, the split algorithm) and the permission model.