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 disbursement schedule, a future-installments table, and a refund activity card; select any schedule row to open its payout detail. For what buyers still owe you, see Invoices.

Summary cards

The cards read left to right — Received, then Outstanding Payout, then Issues, which is a count of payouts rather than an amount.

Payout statuses

Each row in the disbursement schedule carries one status, and the cards add the rows up by it:

GCP payouts

Google reports a payout amount in its Detailed Disbursements report but never a payout date, so Fours tracks a GCP row against its expected payout date — the 21st of the month after the charge month:

• Before the expected date, the row is Pending even when Google has already confirmed the amount. The confirmed amount shows in the row’s Received column, but the row counts toward Outstanding Payout.
• Once the expected date has passed, a row Google has given a non-zero amount shows Est. Received and counts toward Received. A negative amount — a clawback — settles the row too, but adds nothing to Received.
• Past the expected date with no amount from Google, the row is Overdue and counts as an issue.

The schedule export flags GCP rows that have no disbursed date Is Estimated. See GCP Revenue for the full lifecycle.

Schedules and installments

• The disbursement schedule table lists each payout with its source, buyer name, expected and disbursed dates, expected and received amounts, partner fee, currency, and status.
• The future installments table lists upcoming installment payouts by marketplace, offer, buyer, due date, currency, and amount. An offer with several buyers names the first, followed by +N more — hover it for the rest. The buyer is the one named on the offer or, when the offer names none, the buyers the marketplace sync recorded for the offer, then the buyers of its entitlements.

The Disbursed Date, Expected, and Received columns are sortable. A row is placed in the date range by its disbursed date, or by its expected date until the payout lands.

Filter the disbursement schedule by search, date range (the last 90 days by default), source, status, and currency — its search matches buyer names as well as the IDs on each payout; filter future installments by search, source, date range, and currency — its search matches an offer’s name or ID, a buyer ID, or part of a buyer’s name. Use Export on the schedule or Export CSV on installments to download — the schedule export adds the period, Is Estimated, and the disbursement, bank trace, and invoice IDs, and the installments export lists every buyer’s ID and name.

The future installments table covers every offer with a payment schedule except drafts, previews, tests, and offers that were canceled, rejected, expired, deleted, deprecated, voided, invalid, or failed to create — so offers still awaiting acceptance are included, with a first installment that has no charge date yet listed as At acceptance. Installments dated before today are left out.

The future installments date range looks forward from today: This Month, Next 3 Months (the default), Next 6 Months, Next 12 Months, Next 24 Months, Next 36 Months, or All Time. Each range runs from today to the last day of its final month — Next 3 Months ends on the last day of the third month after this one — and All Time has no end date, so it lists every installment still to come. The table’s Total row adds up every installment that matches the filters, not just the page on screen, with a separate total for each currency.

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 and the linked invoices in the detail modal.
4. 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 lists the linked invoices and an expandable raw payload section that shows the source data behind the row: for marketplace and Stripe rows the source revenue record or payment payload, and for AWS rows the payout header plus its components. It does not currently show refund details for a payout — use Refund activity for refunds.

The Linked invoices table lists every invoice the payout covers:

The same modal opens from Matched To on Bank Reconciliation when a matched record belongs to a payout.

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

Refund activity

A Refund activity card on this page collects the refunds recorded on your revenue records across the channels, so you do not have to open payouts one at a time to find them. It follows the schedule’s date range, source, and currency filters.

Two totals sit at the top, one set per currency, and they also follow the card’s own status filter:

Filter the rows by status:

The filter also offers Request pending, but no refund is currently given that status. Credit memos and refund requests that have not been issued are not listed, while a refund attempt that failed but still carries an amount is.

Each row shows the invoice the refund is matched to, and the card has its own Export.

KPI calculation formulas

Each row is in its payout’s own currency: marketplace records converted to USD at their stored rate, AWS payouts in the payout currency, and Stripe payouts in the settlement currency. With all currencies selected, the cards add these amounts together as they are. See Revenue Settings for FX handling.

Received