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.

Cash & Disbursements page with its summary cards and the disbursement schedule

Summary cards

CardMeaning
ReceivedPayouts counted as received — Received, plus GCP payouts in Est. Received — for the current scope.
Outstanding PayoutThe expected amount of every other payout — pending, awaiting payout, overdue, flagged, and failed ones alike.
IssuesThe number of Overdue, Flagged, and Failed payouts.

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 rather than an amount.

Received and Outstanding Payout add up amounts in a single currency. When the payouts in scope are in more than one — AWS payouts stay in their payout currency beside rows converted to USD — both cards read Unavailable rather than a sum of unlike currencies; choose a currency in the Currency filter to see them. Issues counts payouts in every currency.

Payout statuses

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

StatusWhen a row has itCounted in
ReceivedThe payout landed: AWS reported the disbursement, a marketplace record carries a disbursed date, or a Stripe payment succeeded and its funds are available.Received
Est. ReceivedGCP only — see GCP payouts.Received
PendingNot paid out yet and not past its due date. The residual row for the part of an AWS receivable its payouts don’t cover yet is Pending until AWS reports that the buyer has paid in full.Outstanding Payout
Awaiting payoutAWS only. AWS reports that the buyer has paid it in full — the buyer’s invoice less any credit — but the payout to you hasn’t arrived. The residual row of an AWS receivable takes this status once the buyer has paid, and so does an AWS receivable with no payout in the ledger yet. It is never Overdue.Outstanding Payout
OverdueA marketplace record whose payment due date has passed with no payout — on AWS, only while the buyer hasn’t paid in full.Outstanding Payout, Issues
FailedAWS reported the disbursement failed, a Stripe payment failed, or a marketplace record’s payment failed or was canceled, voided, or marked refunded — or its refund failed.Outstanding Payout, Issues
FlaggedNo payout is currently given this status.Outstanding Payout, Issues
Non-cash offsetAWS only. A payout batch whose amount is zero because each charge in it is cancelled by its own refund in the same batch, so no cash moved. It has no disbursed date, its linked invoices carry the same status, and the status filter has no option for it — choose All statuses to see it.Neither — its amounts are zero

An AWS receivable moves through its statuses as AWS reports the buyer’s payment and then the payout:

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. When Google pays one charge across several monthly reports, each report’s payout is a row of its own, with its own amount and an expected date of the 21st of the month after that report’s month; the export’s period for the row is the report month. Each row then follows the same rules:

  • 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. A GCP row’s Partner fee shows the fee when Google’s reports confirm it for that row (see Reading the GCP partner fee). When Fours can confirm a fee only for the group of charges the row belongs to — one order and SKU in one report month — it shows At order level, which opens Order partner fee details; otherwise it reads Unavailable. See GCP Revenue for the full lifecycle.

Schedules and installments

  • The disbursement schedule table lists each payout with its channel, 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), Channel, status, and currency; filter future installments by search, source (All Marketplaces or one), date range, and currency — its search matches an offer’s name or ID, a buyer ID, or part of a buyer’s name.

  • The schedule’s Channel filter lists every channel your organization has — its revenue connections and the channels in its revenue data — so its choices stay available when the results are empty, on an entitlement’s or buyer’s Disbursements tab too. When the Channel filter in the page’s title row is set, this one shows that channel and can’t be changed.
  • The schedule’s search matches the channel, the period, buyer names, and the IDs on each payout and its linked invoices — disbursement, invoice, record, buyer, and entitlement IDs. It also matches an amount: type a number — plain, with thousands separators, with a currency code or symbol (USD 1,234 or $1,234), or in parentheses — to find the rows whose Expected or Received amount has that whole-number part.

Use Export CSV on the schedule — at the end of its filter bar — or on future installments to download every row that matches that list’s filters, from all pages, not just the rows on screen; Saved views describes the dialog. The files are cash_disbursements_<date>.csv and future_installments_<date>.csv. Their columns are a fixed set rather than the table’s: the schedule export adds the period, Is Estimated, the disbursement, bank trace, and invoice IDs, Partner Fee Status (CONFIRMED or UNAVAILABLE; on GCP INVOICE, ORDER, or UNAVAILABLE), and Partner Fee Group (the GCP order-level fee groups the row belongs to), leaves an amount Fours doesn’t know blank, and still titles its channel column Source. 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.

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 (the channel’s cut; the image shows the field’s earlier label, Partner fee amt). On a GCP payout, Partner fee follows the same rule as the schedule’s column — the fee, At order level, or Unavailable. 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.

When the payout carries a refund, the modal shows it too. On an AWS payout, each refunded invoice gets a Refund for invoice section with its Refund status, Refund disbursement amt, and Refund disbursement date. On any other payout, a Linked refund info section gives the refund’s status, date, amounts — refund, refund invoice, and refund disbursement — and its invoice and disbursement dates. Refund status reads Refund in progress, Refund completed, Refund processing failed, Refund was canceled, Needs manual action, or Non-cash offset. Opening a payout from Refund activity scrolls to that refund’s section and highlights it.

On a GCP payout the summary also lists Google’s payout adjustments, each only when Google reported one: Withheld by Google (reported), Released by Google, and Abandoned payout. Google pays you an amount it released or abandoned, so that amount is part of the payout’s expected and received figures, on the row for the month Google reports it. A GCP row that carries only such an adjustment, with no charge of its own, links no invoice; the modal names its Buyer instead.

The Linked invoices table lists every invoice the payout covers:

ColumnWhat it shows
InvoiceThe invoice number, linked to that invoice’s detail on Invoices. Beneath it: the buyer’s name — or No buyer linked / Buyer name unavailable — and how many entitlements the invoice covers.
Disbursed AmountOn an AWS payout, the invoice’s share of the cash in that payout. On a Stripe row, the net amount Stripe settled. On any other row, the record’s disbursed amount less refunds when it has one — otherwise its collectable amount, else its invoice amount — converted at the record’s stored rate, so it can show a figure before the payout lands.
Partner Fee AmountThe channel’s fee on that invoice: the AWS fee lines allocated to it, the channel fee recorded on the record for other marketplaces, or the Stripe processing fee (never below zero). On a GCP invoice it is the fee Google’s reports confirm, View order partner fee with Individual fee unavailable beneath when only an order-level fee is known, or Unavailable.
StatusThe invoice’s payment status on that payout — NO CASH OFFSET on a Non-cash offset payout.

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, Channel, and currency filters. Each refund is in its own invoice’s currency.

Search the card by buyer name, or by any part of an invoice ID or entitlement ID. The search narrows the rows, the two totals, and the card’s export. It is not part of a saved view and resets when you leave the page. When nothing matches, the card says No refunds match ”…” and offers Clear search.

Two totals sit at the top, in a single currency: the one chosen in the schedule’s Currency filter — or, with all currencies, the schedule’s own currency when its payouts are all in one, otherwise US dollars. When no refund is in that currency, the totals show US dollars, else the first currency that has refunds. They also follow the card’s own status filter and search:

TotalWhat it is
Deducted From PayoutsRefunds already taken out of a payout.
Pending RefundsRefunds not yet deducted. For an AWS refund that Fours has AWS credit memos for, it is the cash AWS still has to take back from a later payout. It reads Unavailable while any AWS refund’s cash amount can’t be confirmed, with Known pending and the number of such refunds beneath.

Filter the rows by status:

StatusMeaning
DisbursedThe refund has been settled through a payout.
IssuedThe refund has been issued but not yet settled.
Non-cash offsetAWS only. A credit that moved no cash: AWS credited the invoice before the buyer paid, or after the buyer paid AWS but before AWS paid you, and the credit memos Fours recorded cover the whole refund. Nothing is deducted from a payout.

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, and neither are refunds that failed, were canceled, or need manual action.

Each row shows:

  • the channel, and the Invoice, linked to its detail on Invoices;
  • the Buyer and Entitlement, each named and linked to its page with its ID beneath — or No buyer linked;
  • for a Disbursed refund, the Linked Disbursement: the payout the refund was taken out of, with +N more listing the rest when it spans several payouts. Select a payout to open its detail with the refund highlighted, even when it isn’t on the schedule’s current page or within its filters;
  • the refund’s reason, amount, issue date, deducted amount, disbursed date, and status.

The card has its own Export CSV, which downloads every refund matching the card’s filters and search as refund_activity_<date>.csv. It gives buyer and entitlement names and IDs in separate columns, lists the linked payouts, and writes each status as its code — NO_CASH_OFFSET, for example.

Saved view

The page’s views are listed in the rail under Saved views · Cash & Disbursements — see Saved views for saving, sharing, and who can change a view. One view covers the whole page. It keeps the Channel filter, a selected summary card, the disbursement schedule’s search, Channel, status, currency, and date range (a preset or custom dates), the Refund activity status filter, and the future installments’ search, source, currency, and date range. It does not keep a table’s sort or the Refund activity search.

Without a view, the disbursement schedule’s date range, Channel, status, currency, search, and selected summary card are remembered in this browser for your organization, and so is its sort; the Refund activity filter and search and the future installments’ filters reset when you leave the page. An entitlement’s or buyer’s Disbursements tab remembers none of them.

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. The two amount cards add rows of one currency only: when the rows in scope span more than one, they read Unavailable. See Revenue Settings for FX handling.

KPIApplies toFormulaCalculation details
ReceivedAWS, Azure, GCP, StripeSee Received belowWhich status counts, and how the received amount is measured, differ by channel. Rows are placed by their disbursed date, or by their expected date until the payout lands. Unavailable when the rows in scope span currencies.
Outstanding PayoutAWS, Azure, GCP, StripeΣ expected amount of payouts not counted as receivedEvery status but Received and Est. Received — Pending, Awaiting payout, Overdue, Flagged, and Failed, plus Non-cash offset, whose expected amount is 0 — on the same date window as Received. Selecting the card lists Pending, Awaiting payout, Overdue, and Flagged payouts. An AWS residual row expects the receivable’s collectable amount less what its payouts cover, and an AWS receivable with no payout in the ledger expects its collectable amount. Unavailable when the rows in scope span currencies.
IssuesAWS, Azure, GCP, Stripecount(payouts in Overdue, Flagged, or Failed status)Statuses as defined in Payout statuses; no payout is currently flagged, and an AWS receivable the buyer has paid in full is Awaiting payout, never Overdue. Counts every currency. Unmatched deposits and reconciliation variances are surfaced elsewhere — see Bank Reconciliation.
Future installments TotalOffers with a payment schedule, on any channelΣ installment amount, per currencyOver every installment that matches the source, currency, date-range, and search filters — not just the page on screen — including offers still awaiting acceptance. Each currency is totalled separately and not converted. The range starts today and ends on the last day of its final month; All Time has no end.
Deducted From PayoutsAWS, Azure, GCP, StripeΣ amount deducted of Disbursed refunds in the card's currencyTotalled per currency; the card shows one currency, chosen as Refund activity describes, and amounts in other currencies are not converted into it. A Non-cash offset deducts 0. Follows the card’s date range, Channel, currency, and status filters and its search; refunds that failed, were canceled, or need manual action are not counted.
Pending RefundsAWS, Azure, GCP, StripeSee Pending Refunds belowIn the card’s currency, like Deducted From Payouts; the same filters and search.

Received

Channel partnerFormulaIncluded/excluded dataDate, currency, and rounding rules
AWSΣ received amount of Received payoutsThe payouts AWS reported in its billing-event ledger. A FAILED payout, a Non-cash offset, and the residual row (Pending or Awaiting payout) carry no received amount. An AWS receivable with no payout in the ledger counts max(0, disbursed amount − refund disbursed amount) once it has a disbursed date: only a refund AWS took out of a payout is subtracted, never the refund invoice amount.Payout currency for ledger payouts; a receivable with no ledger payout is converted at the record’s stored rate. Placed by the disbursed date.
AzureΣ max(0, disbursed amount − refund) of Received payoutsReceived = the record carries a disbursed date. Refund = the refund disbursed amount, else the refund invoice amount — only for a refund that hasn’t failed, been canceled, or needed manual action.Converted at the record’s stored rate; placed by the disbursed date.
GCPΣ max(0, reported payout amount − refund) of Est. Received payoutsEst. Received = the expected payout date has passed and Google reported a non-zero amount; a negative amount settles the row but adds 0. GCP rows are never in Received. A charge Google paid across several monthly reports counts each report’s payout as its own row. The reported payout amount includes any withheld amount Google released or abandoned with that month’s payout. Refund as for Azure.Converted at the record’s stored rate; placed by the expected payout date — for a per-report row, the 21st of the month after its report month.
StripeΣ net amount Stripe settled of Received payoutsReceived = the payment succeeded and its funds are available in Stripe.Settlement currency and its decimals; placed by the date the funds became available.

Pending Refunds

Channel partnerFormulaIncluded/excluded dataDate, currency, and rounding rules
AWS, when Fours has recorded AWS credit memos for the refundΣ max(0, net credit − cash already refunded) over the credits AWS issued after it had paid youThe cash AWS still has to take back from a later payout. A credit issued before the buyer paid, or before AWS paid you, adds 0. Counted whatever the row’s status. When the credit memos are missing, don’t add up to the refund, or can’t be placed before or after the payout, the card reads Unavailable, with Known pending (the sum of the refunds that could be confirmed) and N refunds have an unconfirmed cash amount beneath; that row’s Refund Reason reads Cash allocation needs review. Only refunds in the card’s currency count toward its figure.Each refund in its own currency, totalled per currency; the card shows one currency’s total.
AWS records not synced since Fours began recording AWS credits, Azure, GCP, StripeΣ refund amount of Issued refundsRefund amount = the refund invoice amount, else the amount deducted. Disbursed and Non-cash offset refunds add nothing.Each refund in its own currency, totalled per currency; the card shows one currency’s total.

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