billingHelp

Payouts, the ledger and statements

How payee balances are kept (an append-only ledger with a hold period), building and sending payout batches, payout statuses, failed, returned and unclaimed payouts, statements (PDF), settings, the yearly tax summary and the API.

Every payee has a ledger: a list of entries that is only ever added to. Their balance is the sum:

balance = earnings − reversals − payouts + returned payouts ± adjustments

EntryWhen
EarningA payment they share in is paid (or a won dispute restores it).
ReversalThat payment is refunded or disputed.
PayoutTheir balance goes into a batch.
Payout returnedA payout failed, was returned, or you withdrew it — the money is back.
AdjustmentYou add or deduct an amount by hand, with a note the payee sees.

Nothing is ever edited or deleted. A mistake is corrected with a new entry, so a statement printed last month still adds up today. The self-check verifies the ledger every day.

The hold period#

An earning becomes available a number of days after the payment (Settings → Hold, 7 by default), so most refunds and disputes arrive before money leaves. Until then it is on hold. A refund of money still on hold reduces the held part.

Negative balances#

If a payment is refunded after the payee's share was paid out, the reversal takes the balance below zero. Nothing is clawed back from the payee's account; their next earnings pay off the negative part first, and only what remains is paid out.

Build and send a batch#

Payouts → Build a batch takes every payee whose available balance reaches the minimum payout and whose route can pay, and reserves those amounts at once (they leave the available balance, so they cannot go into a second batch). Payees that cannot be paid are listed under Not in this batch with the reason — below the minimum, no Stripe account yet, no funding account chosen — and keep their balance.

Check the batch, then press Send. Nothing moves before that. Withdraw puts every amount back.

Payout batch and payout statuses A batch is Scheduled, then Building while every available balance that reaches the minimum becomes a payout. A Ready batch waits for an owner to press Send, or is withdrawn (Canceled) and its money goes back. Executing: each payout is Queued, then Sent to Stripe or PayPal, then Paid; a payout can end Failed or Returned, which gives its money back to the payee's balance. A payout you make yourself stays Queued until you record it as Manual paid. When every payout has ended the batch is Completed (all paid), Partial (some not paid) or Failed (none paid). Batch Scheduled Building Ready Executing Completed Partial Failed Canceled withdrawSend Payout Queued Sent Paid Failed Returned Manual paid money back onthe payee's balance you pay off-system and record it
Payout batch and payout statuses
Text description

A batch is Scheduled, then Building while every available balance that reaches the minimum becomes a payout. A Ready batch waits for an owner to press Send, or is withdrawn (Canceled) and its money goes back. Executing: each payout is Queued, then Sent to Stripe or PayPal, then Paid; a payout can end Failed or Returned, which gives its money back to the payee's balance. A payout you make yourself stays Queued until you record it as Manual paid. When every payout has ended the batch is Completed (all paid), Partial (some not paid) or Failed (none paid).

  • Stripe — one Transfer per payout from your Stripe balance. Accepted transfers are Paid at once. If you later reverse a transfer in Stripe, the reversal is booked from the webhook — and, should a webhook be missed, the system also re-reads each paid transfer once a day for 30 days. If your Stripe balance cannot cover it, the payout fails and its money returns to the payee's balance; add funds or wait for your Stripe balance to become available, and the next batch takes it.
  • PayPal — one PayPal payout batch. Items are Sent, then Paid when PayPal confirms. Unclaimed items (the address has no PayPal account yet) stay Sent until claimed; after 30 days PayPal returns them (Returned, money back). Not waiting? Press Cancel unclaimed on the batch page: PayPal cancels the item at once, the payout is Returned and the money is back on the payee's balance (recorded in the audit log). Only unclaimed items can be canceled.
  • Paid by you — stays Queued. Pay the payee, then enter how (cheque number, wire reference) and press Record paid. The payee is e-mailed.

A provider that cannot be reached leaves the payout Queued; the system tries again every 15 minutes with the same request (so it is never paid twice) and marks it Failed after five attempts.

The batch ends Completed (all paid), Partial (some not paid) or Failed (none paid). Owners are e-mailed when payouts fail.

Settings#

Payouts → Settings (owners):

  • Stripe account — your own Stripe credential set that is the Connect platform for your payees. PayPal REST app — your own PayPal set whose Payouts API sends. Sets connected through the platform cannot fund payouts.
  • Hold, Minimum payout.
  • Batches — by hand, weekly (weekday) or monthly (day 1–28), UTC. A scheduled batch is built on that day; owners get an e-mail and press Send, unless Send scheduled batches automatically is ticked.
  • E-mail payees their monthly statement — on the 1st of each month, for the previous month. A payee can opt out on their earnings page.
  • Require a tax form before paying — live payouts wait until the payee has a W-9 or W-8 on file.
  • Allow sending payout batches over the API — off by default: API keys can build, read and withdraw batches, but only someone signed in can send unless you tick this.
  • 1099 threshold from 2027 — the tax summary uses $600 for 2025 and earlier and $2,000 for 2026; enter the amount for 2027 and later once the IRS publishes it.

Add the payout webhook events listed on the settings page to each funding set's webhook, so payouts update within seconds.

Statements#

Each payee page lists months with activity. A statement shows the opening balance, the month's entries by kind and the closing balance (closing = opening + the month's entries), as a page, PDF (US Letter, every entry, "Page n of N") or CSV. Exports has the whole ledger and every payout as CSV.

Tax forms#

The system collects W-9 / W-8BEN / W-8BEN-E forms from payees (see Payees) and adds up what each was paid, but it does not file forms.

Payouts → Tax summary lists, for a calendar year, every payee paid that year: the form on file, the masked tax number, what was paid by route (by date paid; returned payouts do not count and transfer reversals are subtracted) and whether the total reaches the year's 1099 threshold. CSV gives the same with masked numbers; Export with full tax numbers asks for your password and is recorded in the audit log. Owners and finance viewers see the summary; only owners export full numbers.

  • In the United States, payments to independent contractors and royalties above the IRS thresholds may need a 1099 form from you; collect a W-9 from US payees before paying them (a W-8BEN from foreign payees).
  • For payees paid through Stripe, Stripe can collect tax details and issue 1099s for your platform if you turn on Stripe Tax Reporting for Connect in your Stripe Dashboard.
  • PayPal may issue its own forms to recipients who receive enough through PayPal; that does not replace forms you owe as the payer.

Ask your accountant which forms apply to you. The tax summary, the statements and the ledger export give them the figures.

Payouts over the API#

Owner API keys with write access can build a batch (POST /api/v1/payout-batches), read it, and withdraw it; sending (POST /api/v1/payout-batches/{id}/send) is refused with api_send_disabled unless Settings allows it. GET /api/v1/tax-summary?year= returns the summary with masked numbers. See the API reference.