Automate weekly Stripe payout reconciliation

A payout in the bank rarely matches one sale. A scheduled agent matches each Stripe payout to the transactions it settles, lists any that do not add up, and drafts a report that its department head reviews and you approve.

What you’ll set up

Connections

Stripe restricted key (read) · Required

Reads payouts and the balance transactions each one settles. Nothing changes in Stripe.

Upgrades

Delivery (channel or inbox)

Delivers the approved reconciliation to your channel or inbox.

Inputs

Where to send the report · Optional

Email, defaults to your account email

Difference tolerance · Optional

Number, default 0

Ready by · Required

Time, default 09:00

Brief · Required

Text, prefilled and editable during setup.

Runs

Runs every Monday at 08:00

Done by Business analyst

You approve before anything goes out.

Set up this job

You approve every report · Free to start

How it runs

One agent does the work. Its department head reviews it, then you approve.

  1. 1Business analyst

    Runs every Monday at 08:00 and prepares the report from your connected sources.

  2. 2COO · Review

    The department head reviews the report before it reaches you.

  3. 3You

    You approve before anything goes out.

What you get

Sample, not live dataSample payout reconciliation (Sample, not live data)

Sample, not live data. Payout IDs, amounts and dates are invented.

Payouts, week of 26 Oct (sample)

3 payouts, 2 match their transactions, 1 needs a look.

PayoutPayout amountSum of transactionsDifference
po_sample11,204.501,204.500.00
po_sample3640.00600.0040.00

Next steps (need your approval)

  1. Check po_sample3 for a refund or fee booked after the payout date.

Why payouts do not match sales

A bank deposit from Stripe bundles many payments, minus fees and refunds, so it equals none of the sales behind it. Stripe's payout reconciliation report exists to match each payout with the batch of transactions it settles. Doing that for every payout each month is slow, and it is where errors hide: a refund booked late, a dispute, or a fee that shifted a total.

How the scheduled job works

You add the job and share a restricted Stripe key with read access. Each Monday a scheduled agent lists last week's payouts. For automatic payouts, the balance transactions endpoint accepts a payout parameter that returns the transactions paid out on that payout. The agent sums charges, refunds, fees and adjustments and checks the total equals the payout. It lists each payout's date and amount so you can match it to your bank statement. Instant payouts are listed for manual review, as Stripe documents. It reads and reports, and changes nothing.

Review and approval

The COO agent, as department head, reviews the report before it goes out: do the sums add up, is each payout matched to the right transactions, is a difference real or a timing gap. Then you approve, edit or skip it, and nothing is sent until you do. Compare the opening month against Stripe's own report before relying on it.

What to do with a difference

Most differences are timing: a payout that arrives after your cut-off date. Check dates, then refunds and disputes, then fees. A difference that survives all three is worth a closer look in Stripe. Keep the tolerance at zero while you learn what normal looks like, and widen it if rounding noise appears. Never book an adjustment because the report suggested one; confirm in the source records.

Questions

Start with one report

Set up this job

You approve every report · Free to start