Cash & Disbursements
The Cash & Disbursements page (sidebar → Cash & Disbursements) tracks the money on its way to you — marketplace and Stripe payouts, plus the installments still to come.
Overview
Open Revenue → Cash & Disbursements. The page has three summary cards, a per-channel payout summary, a disbursement schedule, and a future-installments table; select any schedule row to open its payout detail. For what buyers still owe you, see Invoices.
Summary cards
| Card | Meaning |
|---|---|
| Received | Payouts received for the current scope — the amount that actually landed, counting both Received payouts and flagged ones (where some, but not all, of the expected amount arrived). |
| Outstanding Payout | Expected payout amount not yet received. |
| Issues | Count of disbursement rows that need review — Overdue, flagged, or Failed. The card’s in-product subtitle reads Overdue, flagged, or failed disbursements. |
A flagged payout is one where the amount received did not match the amount expected, so it deliberately lands in all three cards at once: its received amount counts toward Received, its shortfall counts toward Outstanding Payout, and it counts once toward Issues.
The cards read left to right — Received, then Outstanding Payout, then Issues, which is a count of payouts needing review rather than an amount.
A per-channel summary shows received, pending, and issue counts with each connection’s sync status.
Each row rolls up one channel’s payout health — ① its total received amount and ② its received · pending · issues breakdown — so you can see, for example, that AWS has 0 received · 30 pending · 30 issues while Azure shows no issues (one payout still pending).
Schedules and installments
- The disbursement schedule table lists each expected payout with its source, invoice period, expected and received dates, amount, and status.
- The future installments table lists upcoming installment payouts by marketplace, offer, buyer, due date, currency, and amount.
Filter the disbursement schedule by search, date range, source, and status; filter future installments by source, date range, and currency. Use Export on the schedule or Export CSV on installments to download.
To inspect a single payout:
- Locate the disbursement in the disbursement schedule table.
- Select View Detail on its row.
- Review the payout summary, linked invoices, refund activity, and the source payload in the detail modal.
- Close the modal to return to the schedule.
The payout summary circles the three figures you reconcile most: ① Expected (what the channel owed), ② Received (what actually landed), and ③ Partner fee amt (the channel’s cut). Below the summary the modal also lists the linked invoices and the raw source payload.
KPI calculation formulas
All amounts are in your base currency. See Revenue Settings for base-currency and FX handling.
| KPI | Applies to | Formula | Calculation details |
|---|---|---|---|
| Received | AWS, Azure, GCP, Stripe | Σ received amount of RECEIVED **and FLAGGED** payouts in scope | Rows are windowed by expected date; received date is used only when there’s no expected date. A flagged payout contributes the amount that actually arrived, so it counts here as well as in Outstanding Payout (for its shortfall) and in Issues. |
| Outstanding Payout | AWS, Azure, GCP, Stripe | Σ expected amount of pending and overdue payouts + Σ max(0, expected − received) for flagged payouts | Payouts the channel still owes you, on the same expected-date window as Received. A flagged payout — one where the amount received did not match the amount expected — contributes only its shortfall, so a payout that arrived in full adds nothing. |
| Issues | AWS, Azure, GCP, Stripe | count(payouts in Overdue, Flagged, or Failed status) | Matches the card’s subtitle, Overdue, flagged, or failed disbursements. Unmatched deposits and reconciliation variances are surfaced elsewhere, not in this count. |
Spotted something wrong or out of date on this page? Tell us and we'll correct it.