Suger

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.

Cash & Disbursements: summary cards, channel summary, disbursement schedule, and future installments

Summary cards

CardMeaning
ReceivedPayouts received for the current scope — the amount that landed, counting Received, Est. Received, and flagged payouts alike.
Outstanding PayoutExpected payout amount not yet received.
IssuesCount 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.

Est. Received — a GCP-only status

GCP rows carry a status the other channels do not: ESTIMATED, labelled Est. Received in the table. Google reports a payout amount but never a payout date, so Suger settles a GCP row against its expected payout date — the 21st of the month after the charge month — instead of an actual one. A row that has passed that date with a confirmed amount shows Est. Received; one that has passed it with nothing confirmed shows Overdue; one that has not reached it yet stays Pending. See GCP Revenue for the full lifecycle.

Cash & Disbursements summary cards with each value circled

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.

Channel summary with a channel's payout total and its pending/issue counts circled

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.

The schedule identifies the buyer by Buyer ID and Buyer Name as separate columns, and carries the payout Currency. Both the Expected and Received columns are sortable.

Filter the disbursement schedule by search, date range, source, status, and currency; filter future installments by source, date range, and currency. Use Export on the schedule or Export CSV on installments to download — the schedule export includes Buyer ID, Buyer Name, and Is Estimated.

To inspect a single payout:

  1. Locate the disbursement in the disbursement schedule table.
  2. Select View Detail on its row.
  3. Review the payout summary, linked invoices, refund activity, and the source payload in the detail modal.
  4. Close the modal to return to the schedule.

Disbursement detail modal payout summary with Expected, Received, and Partner fee circled

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. Refunds are shown per linked invoice, so a refund is attributed to the invoice it reversed rather than to the payout as a whole.

To confirm the deposit itself reached your bank, match it in Bank Reconciliation.

KPI calculation formulas

All amounts are in your base currency. See Revenue Settings for base-currency and FX handling.

KPIApplies toFormulaCalculation details
ReceivedAWS, Azure, GCP, StripeΣ received amount of **RECEIVED, ESTIMATED and FLAGGED** payouts in scopeAll three statuses count. 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. ESTIMATED is GCP-only.
Outstanding PayoutAWS, Azure, GCP, StripeΣ expected amount of pending and overdue payouts + Σ max(0, expected − received) for flagged payoutsPayouts 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.
IssuesAWS, Azure, GCP, Stripecount(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 — see Bank Reconciliation.

Spotted something wrong or out of date on this page? Tell us and we'll correct it.