Skip to content

Disbursements and payouts

How disbursement requests, eligibility, bank destinations, and identity verification relate — and what is still capability-gated.

What Disbursements is

Disbursements track payout obligations and instructions in Zyelra’s control plane. Bank destinations store where money can be sent later. Identity verification cases prepare participants — they do not alone move money.

Operator flow

  1. Maintain operating balances and obligations as your process requires.
  2. Add bank destinations (records only — no money moves on that screen).
  3. Complete identity verification cases when required before payout eligibility.
  4. Create/review disbursements, approve when allowed, and submit only when provider rails are enabled.

Do not confuse with

  • Guest Collect / Connect payments (Settings → Payments)
  • SaaS Billing subscription charges
  • Vendor bill AP payment records
  • Custodial Zyelra stored-value wallets (not the product model)

Next step

Ledger, collections, operating balances, AP, disbursements, and QuickBooks.

More Finance guides →

Related guides

  • Finance overview

    Zyelra’s ledger and operating balances are the financial source of truth. Payment providers are rails — not a custodial Zyelra wallet.

  • Vendor bills and accounts payable

    Create, approve, post, and record payment on vendor bills. Draft bills can also come from maintenance tasks.

  • Chart of accounts and ledger

    Zyelra’s chart of accounts and ledger are the canonical books of record. Providers and QuickBooks are downstream rails and destinations.

  • Stripe (guest payments)

    Prefer Finance → Collection payments and guest payment links (Zyelra-managed). Connect Stripe via Stripe Connect OAuth in Settings → Payments → Advanced only for legacy stay checkout. Separate from Zyelra SaaS billing.

  • Paystack (guest payments)

    Connect a Paystack subaccount code from your Paystack dashboard so guests can pay through Paystack checkout. Manual connect — not SaaS billing.